Just a quick update, down too the last few bisect's building them to be 100% sure.
Last Good: 5b28a2ae632698758bf84364a5d87c6fcaaff03b UBUNTU: Remove depmod created files from packages. Bug: #250511 All depmod files are created immediately upon installation. Signed-off-by: Tim Gardner <[EMAIL PROTECTED]> Last Bad: 67d9b90a1c844bf1c6daaffd2c60561fc8c445f7 disable CONFIG_DYNAMIC_FTRACE due to possible memory corruption on module unload While debugging the e1000e corruption bug with Intel, we discovered today that the dynamic ftrace code in mainline is the likely source of this bug. This leaves as the first possible bad commits: 0020f5cf510e3225fc4b0eefdcfdc0caba2f2097 x86: register a platform RTC device if PNP doesn't describe it Most if not all x86 platforms have an RTC device, but sometimes the RTC is not exposed as a PNP0b00/PNP0b01/PNP0b02 device in PNPBIOS or ACPI: http://bugzilla.kernel.org/show_bug.cgi?id=11580 https://bugzilla.redhat.com/show_bug.cgi?id=451188 It's best if we can discover the RTC via PNP because then we know which flavor of device it is, where it lives, and which IRQ it uses. But if we can't, we should register a platform device using the compiled-in RTC_PORT/RTC_IRQ resource assumptions. Signed-off-by: Bjorn Helgaas <[EMAIL PROTECTED]> Acked-by: Rafael J. Wysocki <[EMAIL PROTECTED]> Acked-by: David Brownell <[EMAIL PROTECTED]> Reported-by: Rik Theys <[EMAIL PROTECTED]> Reported-by: [EMAIL PROTECTED] Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]> Signed-off-by: Tim Gardner <[EMAIL PROTECTED]> or: c25072126a591fec9481197aab361469661c050e UBUNTU: SAUCE: Add back in lost commit for Apple BT Wireless Keyboard OriginalAuthor: Dean McCarron OriginalLocation: http://sourceforge.net/mailarchive/message.php?msg_id=473118CB.5090804%40mercuryresearch.com Bug: #162083 Ignore: no This patch was present in Hardy, but got dropped by accident in Intrepid. I've submitted it upstream so it can get into Jaunty, but will need to be carried as extra baggage for now in Intrepid. Signed-off-by: Mario Limonciello <[EMAIL PROTECTED]> Signed-off-by: Tim Gardner <[EMAIL PROTECTED]> Since c25072126a591fec9481197aab361469661c050e only changes a keyboard, it's more then likely, 0020f5cf510e3225fc4b0eefdcfdc0caba2f2097 "x86: register a platform RTC device if PNP doesn't describe it" does not work on Intel Atom 330 D945GCLF2. Like i mentioned, i'm building these last few commits to be 100% sure, will have a final update tomorrow. Regards, Robert -- kernel oops on boot (dual-core Atom 330 board D945GCLF2) https://bugs.launchpad.net/bugs/279186 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs