Bug#600656: linux-image-2.6.32-5-amd64: Crash after nullpointer dereference during gparted reading a disk
- To: Andreas Feldner <pelzi@flying-snail.de>
- Cc: 600656@bugs.debian.org
- Subject: Bug#600656: linux-image-2.6.32-5-amd64: Crash after nullpointer dereference during gparted reading a disk
- From: Moritz Mühlenhoff <jmm@inutil.org>
- Date: Fri, 1 Apr 2011 21:35:01 +0200
- Message-id: <20110401193501.GA11579@pisco.westfalen.local>
- Reply-to: Moritz Mühlenhoff <jmm@inutil.org>, 600656@bugs.debian.org
- In-reply-to: <1289355600.2816.94.camel@localhost>
- References: <20101018214306.3643.64059.reportbug@localhost.localdomain> <1287452085.20865.161.camel@localhost> <201011092341.39105.pelzi@flying-snail.de> <1289355600.2816.94.camel@localhost>
On Wed, Nov 10, 2010 at 02:20:00AM +0000, Ben Hutchings wrote:
> On Wed, 2010-11-10 at 00:41 +0200, Andreas Feldner wrote:
> > Hi Ben,
> >
> > somehow netconsole doesn't do anything for me. But it turned out the the
> > system behaviour is not exactly reproducible and anyway I can see the messages
> > on screen if X is not started (because nvidia module banned ;-) ).
> >
> > So, here I have the following error message, hope that helps!
> [...]
>
> OK, this looks really weird. I looked for reports of similar crashes
> and found <http://lkml.org/lkml/2009/11/11/302> which apparently turned
> out to be due to a hardware fault.
>
> Could you test Linux 2.6.36 as packaged in experimental? If that has
> the same problem, try running memtest86+ for a while to check whether
> this is due to bad RAM. I suspect it isn't, but we have to check.
Andreas, did you test later kernels (now also in unstable) and memtest?
Cheers,
Moritz
Reply to: