http://bugzilla.kernel.org/show_bug.cgi?id=13793
--- Comment #16 from Christophe Dumez <dch...@gmail.com> 2009-07-21 08:48:32 --- Ok, still using kernel tree up to 0c26d7cc31cd81a82be3b9d7687217d49fe9c47e commit (excluded) with the following cherry picked patches: 412af97838828bc6d035a1902c8974f944663da6 : ACPI NULL reference check c6223048259006759237d826219f0fa4f312fb47 : JFS ACL race condition fix d5bb68adda7cc179e8efadeaa3a283cb470f13a6 : Another JFS ACL race condition fix but with the same config file as I used for rc3, I can see the call trace this time. Therefore, the crash was not caused by ACPI changes. Although the call trace is not exactly the same, it looks similar: I will post it anyway. The problem was introduced after v2.6.30 release and 0c26d7cc31cd81a82be3b9d7687217d49fe9c47e commit (ACPI changes). -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
