From: Andrea Arcangeli <andrea@suse.de>
To: Matteo Fago <fago@venere.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory problem with SuperMicro s2qr6
Date: Mon, 6 May 2002 18:57:31 +0200 [thread overview]
Message-ID: <20020506185731.E31998@dualathlon.random> (raw)
In-Reply-To: <003601c1f51c$15241460$1f01a8c0@venere.it>
On Mon, May 06, 2002 at 06:35:49PM +0200, Matteo Fago wrote:
> Apr 29 04:03:46 pegaso kernel: Unable to handle kernel paging request at
> virtual address 51c0347a
> Apr 29 04:03:46 pegaso kernel: c0117d1e
> Apr 29 04:03:46 pegaso kernel: *pde = 00000000
> Apr 29 04:03:46 pegaso kernel: Oops: 0000
> Apr 29 04:03:46 pegaso kernel: CPU: 2
> Apr 29 04:03:46 pegaso kernel: EIP: 0010:[__wake_up+46/256] Not
> tainted
> Apr 29 04:03:46 pegaso kernel: EIP: 0010:[<c0117d1e>] Not tainted
> Using defaults from ksymoops -t elf32-i386 -a i386
> Apr 29 04:03:46 pegaso kernel: EFLAGS: 00010002
> Apr 29 04:03:46 pegaso kernel: eax: ccf4166c ebx: c1891770 ecx: 00000001
> edx: 00000003
> Apr 29 04:03:46 pegaso kernel: esi: 51c0347a edi: 00000803 ebp: e0e51d80
> esp: e0e51d64
> Apr 29 04:03:46 pegaso kernel: ds: 0018 es: 0018 ss: 0018
> Apr 29 04:03:46 pegaso kernel: Process updatedb (pid: 2974,
> stackpage=e0e51000)
> Apr 29 04:03:46 pegaso kernel: Stack: 00000001 00000286 00000003 ccf4166c
> c1891770 00001000 00000803 003
> d8572
> Apr 29 04:03:46 pegaso kernel: c0143714 c1891770 00000803 003d8573
> 00001000 00000000 e0e50000 000
> 00803
> Apr 29 04:03:46 pegaso kernel: 00001000 c01413b2 00000803 003d8572
> 00001000 ed782a60 00000000 000
> 00000
> Apr 29 04:03:46 pegaso kernel: Call Trace: [grow_buffers+212/256]
> [getblk+98/112] [ext3_getblk+189/704]
> Apr 29 04:03:46 pegaso kernel: Call Trace: [<c0143714>] [<c01413b2>]
> [<c01661dd>] [<c013643c>] [<c012f0f
> Apr 29 04:03:47 pegaso kernel: [<c0167d94>] [<c0166402>] [<c0163ded>]
> [<c01522fc>] [<c012765e>] [<c01
> 49489>]
> Apr 29 04:03:47 pegaso kernel: [<c014abb8>] [<c014e460>] [<c014e014>]
> [<c014e460>] [<c014e5ef>] [<c01
> 4e460>]
> Apr 29 04:03:47 pegaso kernel: [<c013e196>] [<c0108b0b>]
> Apr 29 04:03:47 pegaso kernel: Code: 8b 16 e9 a0 00 00 00 8b 5e fc 8b 03 85
> 45 ec 0f 84 8c 00 00
Well, the first guess is that the ram is bad, or that it's a driver bug,
unfortunately with just the above oops it's hard to tell, the real bug
is going to be miles away from grow_buffers and wake-up. Did you tried
memtest86 or cerberus? (both can report bitflips in memory)
Andrea
parent reply other threads:[~2002-05-06 16:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <003601c1f51c$15241460$1f01a8c0@venere.it>]
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=20020506185731.E31998@dualathlon.random \
--to=andrea@suse.de \
--cc=fago@venere.it \
--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
all inboxes | Powered by JetHome®