On Wed, 2010-10-06 at 09:53 -0700, Vagrant Cascadian wrote: > On Mon, Sep 27, 2010 at 09:29:28AM -0700, Vagrant Cascadian wrote: > > On Tue, Sep 21, 2010 at 01:37:42PM -0700, Vagrant Cascadian wrote: > > > On Mon, Sep 20, 2010 at 02:04:23AM +0100, Ben Hutchings wrote: > > > > 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. > > > > > > added this now, will reboot and see if that fixes it... presuming it just > > > doesn't hide itself for another several weeks. > > > > ok, didn't have to wait for weeks, apparently. > > still getting crashes every week or two, but not sure if they're related to the > initial problem... > > so i've been running with memory_corruption_check=1: Unlesss you also see messages reporting 'Corrupted low memory at ...' then what you're seeing is not the problem that memory_corruption_check deals with. [...] > anything else that could possibly be of use in troubleshooting this? You could test a newer kernel package from experimental. 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