From: Stephan von Krawczynski <skraw@ithnet.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug Report 2.6.17.8
Date: Mon, 21 Aug 2006 12:09:18 +0200 [thread overview]
Message-ID: <20060821120918.8fa676d3.skraw@ithnet.com> (raw)
In-Reply-To: <20060820170717.e6f98f23.akpm@osdl.org>
On Sun, 20 Aug 2006 17:07:17 -0700
Andrew Morton <akpm@osdl.org> wrote:
> > Aug 20 03:43:11 a01 kernel: BUG: unable to handle kernel paging request at virtual address 02000044
> > Aug 20 03:43:11 a01 kernel: printing eip:
> > Aug 20 03:43:11 a01 kernel: c0176356
> > Aug 20 03:43:11 a01 kernel: *pde = 00000000
> > Aug 20 03:43:11 a01 kernel: Oops: 0000 [#1]
> > Aug 20 03:43:11 a01 kernel: Modules linked in: speedstep_lib freq_table ipv6 intel_agp agpgart hw_random nfs lockd sunrpc e100 mii e1000
> > Aug 20 03:43:11 a01 kernel: CPU: 0
> > Aug 20 03:43:11 a01 kernel: EIP: 0060:[dqput+14/338] Not tainted VLI
> > Aug 20 03:43:11 a01 kernel: EIP: 0060:[<c0176356>] Not tainted VLI
> > Aug 20 03:43:11 a01 kernel: EFLAGS: 00010206 (2.6.17.8 #1)
> > Aug 20 03:43:11 a01 kernel: EIP is at dqput+0xe/0x152
> > Aug 20 03:43:11 a01 kernel: eax: 02000000 ebx: 02000000 ecx: f5fd0c00 edx: 00000000
>
> Looks like a single-bit error. Try running memtest86 for 24 hours?
Hi Andrew,
I have done that some weeks ago. What bothers me is that I have about 20 of these boxes and all run smoothly with kernel 2.4. Only the two running kernel 2.6 crash every now and then, mostly without usable output. This time I was lucky ...
--
Regards,
Stephan
prev parent reply other threads:[~2006-08-21 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 11:40 Stephan von Krawczynski
2006-08-20 23:14 ` Oleg Verych
2006-08-21 0:07 ` Andrew Morton
2006-08-21 10:09 ` Stephan von Krawczynski [this message]
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=20060821120918.8fa676d3.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome