linux-kernel - Re: 2.6.18 BUG: unable to handle kernel NULL pointer dereference at virtual address 000,0000a

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20060925142630.fb39a613.akpm@osdl.org>
Date:	Mon, 25 Sep 2006 14:26:30 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Christian Weiske <cweiske@...iske.de>
Cc:	linux-kernel@...r.kernel.org, reiserfs-dev@...esys.com,
	Ingo Molnar <mingo@...e.hu>,
	Nick Piggin <nickpiggin@...oo.com.au>
Subject: Re: 2.6.18 BUG: unable to handle kernel NULL pointer dereference at
 virtual address 000,0000a

On Mon, 25 Sep 2006 20:36:57 +0200
Christian Weiske <cweiske@...iske.de> wrote:

> >> I assume that you have confirmed that the machine doesn't have hardware
> >> problems?  Does it run some earlier kernel OK?  
> > The disks are both fine, they worked in other pcs without problems. The
> > ide controller card also worked fine, and the motherboard is new -
> > whatever you can expect with that. Maybe the combination is the problem.
> 
> So this is definitely a hardware problem?

Is it?  I don't recall us having established that.  Does the machine run
any earlier kernel without failing?

> Which component is most likely
> to be the bad one?

Motherboard, I guess.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/