On Tue, 2009-02-10 at 02:26 +0800, Darren Salt wrote: > I'm seeing various oopses with -rc4, where -rc3 is fine; config, dmesg > (captured via netconsole) and decoded oops data attached ¹. The last few > oopses were followed by a scrambled display and a hard lockup. > > All oopses follow an otherwise successful suspend-to-RAM. > > Also, I see that Fn-Fx don't seem to be reported via /proc/acpi/events any > more, or at least I'm seeing no evidence of them via acpi_listen (and, not > coincidentally, I can't adjust the volume etc. via eeepc-acpi-scripts). > > The only other (significant) change is that I've installed X from Debian > experimental, though -rc3 and 2.6.28.* seem fine with this. (Oh, and I can > get UXA to cause OOM quite trivially... several Iceweasel tabs is enough.) > >From the description it seems that this is a regression. Will you please use git-bisect to identify which commit causes the regression? Thanks. > > ¹ Yes, I decided not to include symbol names in the running kernel... > -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
