On Mon, 2010-09-06 at 17:05 -0700, Vagrant Cascadian wrote: > On Tue, Sep 07, 2010 at 12:10:09AM +0100, Ben Hutchings wrote: > > On Mon, 2010-09-06 at 12:27 -0700, Vagrant Cascadian wrote: > > > Package: linux-2.6 > > > Version: 2.6.32-21 > > > > > > i'm experiencing very similar issues, although also with earlier versions of > > > linux-image-2.6.32-5-686. > > > > > > i first started having this problem after upgrading to squeeze from lenny, > > > although i was running the exact same linux-image-2.6.32-* directly on lenny > > > for quite some time without problems. > > > > > > i had been using uswsusp, but after experiencing this problem several times, i > > > purged uswsusp and switched to using the in-kernel resume with pm-hibernate. > > [...] > > > > And did that make any difference? > > heh. sorry for being unclear :) > > unfortunately, no, it's still Oops'ing after resume. > > i also didn't mention, largely because i'm pretty unsure if it's really the > case, but the issue *seems* to occur more reliably when hibernating (to disk) > while on battery, but i'm really unsure of that. > > i'll see if i can more reliably trigger the same problem on a clean squeeze > install on the same hardware in another partition... where i'm not as worried > about crashing. Please add 'memory_corruption_check=1' to the kernel parameters and report whether that fixes the problem and whether it results in any new log messages. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Description: This is a digitally signed message part