From: Chuck Ebbert <76306.1226@compuserve.com>
To: Petr Sebor <petr@scssoft.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: 2.6.16.20 kernel oops
Date: Mon, 12 Jun 2006 20:31:35 -0400 [thread overview]
Message-ID: <200606122034_MC3-1-C243-3BA4@compuserve.com> (raw)
In-Reply-To: <448DE077.1040900@scssoft.com>
On Mon, 12 Jun 2006 23:45:27 +0200, Petr Sebor wrote:
> Jun 12 18:53:42 server kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000008
> Jun 12 18:53:42 server kernel: printing eip:
> Jun 12 18:53:42 server kernel: c0237744
> Jun 12 18:53:42 server kernel: *pde = 00000000
> Jun 12 18:53:42 server kernel: Oops: 0002 [#1]
Looks like your hardware is failing.
Disassembly shows:
Code; c0237744 No symbols available <=====
0: ba 08 00 00 00 mov $0x8,%edx <=====
...and there is no way this instruction can cause that fault.
Your previous bug looked flakey too.
Run memtest86 overnight to see if it finds anything. Also
check the CPU temperature.
--
Chuck
next reply other threads:[~2006-06-13 0:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 0:31 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-12 21:45 Petr Sebor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200606122034_MC3-1-C243-3BA4@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
--cc=petr@scssoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®