Bug#575924: linux-image-2.6.32-4-amd64: fuse module oops on boot

[Denis Laxalde <dlaxalde@gmail.com>]

Hi,

Le lundi 12 avril 2010 à 01:18 +0100, Ben Hutchings a écrit :
> On Sun, 2010-04-11 at 18:23 -0400, Denis Laxalde wrote:
> > forwarded 575924 https://bugzilla.kernel.org/show_bug.cgi?id=14347
> > thanks
> > 
> > On Sun, 11 Apr 2010 16:05:57 +0100, Ben Hutchings wrote:
> > > On Sat, 2010-04-10 at 23:05 -0400, Denis Laxalde wrote:
> > > > Hi,
> > > > 
> > > > On Sun, 11 Apr 2010 00:28:24 +0100, Ben Hutchings wrote:
> > > > > The more serious error messages suggest memory  corruption.  Have
> > > > > you tested the RAM with memtest86+ yet?
> > > > 
> > > > Yes, I've just run a pretty long test with memtest86+ and there was
> > > > no error reported.
> > > 
> > > OK, so we can be fairly sure this is a kernel bug.  Please report this
> > > at <https://bugzilla.kernel.org>.  It is hard to know where the bug
> > > may be, but try submitting it under product 'Memory Management',
> > > component 'Slab Allocator'.  Let us know the bug number so we can
> > > track it.
> > 
> > The above bug report looks similar, so I just added comments and dmesgs
> > there.
> > Maybe the bug should be retitled ?
> 
> I'm not convinced that these are the same bug.  Let's see what the
> response is.

There was no response so far and, since boot failures still happen from
time to time (once a week or so), I may open a new bug upstream...
In fact, there are even worse than before since I cannot recover using
SysRq keys combination anymore (I just power-off the computer now).
Hence, I cannot save a relevant dmesg anymore.
Is there any way to recover messages in such situations?

Cheers,

Denis