public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dennis Schoen <dennis@cns.dnsalias.org>
To: linux-kernel@vger.kernel.org
Cc: andrea@suse.de
Subject: Re: BUG: 2.4.19-pre6aa1 (i586) ?
Date: Tue, 23 Apr 2002 17:15:36 +0200	[thread overview]
Message-ID: <20020423151536.GA25788@smart.cobolt.net> (raw)
In-Reply-To: <20020423092731.GA6327@smart.cobolt.net> <20020423150709.A4982@dualathlon.random>

On Tue, Apr 23, 2002 at 03:07:09PM +0200, Andrea Arcangeli wrote:
> On Tue, Apr 23, 2002 at 11:27:32AM +0200, Dennis Schoen wrote:
> > Apr 21 21:40:03 opel kernel: kernel BUG at page_alloc.c:234!
> > Apr 21 21:40:03 opel kernel: invalid operand: 0000
> > Apr 21 21:40:03 opel kernel: CPU:    0
> > Apr 21 21:40:03 opel kernel: EIP:    0010:[rmqueue+112/548]    Not tainted
> > Apr 21 21:40:03 opel kernel: EFLAGS: 00010086
> > Apr 21 21:40:03 opel kernel: eax: 0000c000   ebx: c119f37c   ecx: 00001000   edx: e8bac588
> > Apr 21 21:40:03 opel kernel: esi: c119f37c   edi: 00000000   ebp: c0230310   esp: ca569e64
> > Apr 21 21:40:03 opel kernel: ds: 0018   es: 0018   ss: 0018
> > Apr 21 21:40:03 opel kernel: Process w3m-en (pid: 1963, stackpage=ca569000)
> > Apr 21 21:40:03 opel kernel: Stack: c02304d4 00000000 00000001 00000001 c0230310 0000a9b0 00000286 c023034c 
> > Apr 21 21:40:03 opel kernel:        00000000 c0230310 c012bac4 c1002ccc 00000000 c6ebb274 00000001 c0230310 
> > Apr 21 21:40:03 opel kernel:        00000001 c0122684 0000000c c0230310 c02304d0 000001d2 0809deb0 c012213b 
> > Apr 21 21:40:03 opel kernel: Call Trace: [__alloc_pages+116/664] [do_no_page+56/380] [do_wp_page+127/440] [handle_mm_fault+144/208] [do_page_fault+447/1336] 
> > Apr 21 21:40:03 opel kernel:    [do_page_fault+0/1336] [do_brk+283/508] [sys_brk+193/240] [error_code+52/64] 
> > Apr 21 21:40:03 opel kernel: 
> 
> I doubt it's a bug in the page freelist management, but it seems the
> freelist got corrupted somehow. So I'd say it's either a bug in another
> subsystem or faulty dram. Can you try some memchecker to rule out the
> hardware possibility?
Ok, I'll let memtest run that night and report back.

Ciao
  Dennis

  reply	other threads:[~2002-04-23 15:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23  9:27 BUG: 2.4.19-pre6aa1 (i586) ? Dennis Schoen
2002-04-23 13:07 ` Andrea Arcangeli
2002-04-23 15:15   ` Dennis Schoen [this message]
2002-04-24  8:54   ` Dennis Schoen
2002-04-24 11:25     ` Dave Jones
2002-04-24 11:32       ` Dennis Schoen
2002-04-24 11:39         ` Dave Jones

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=20020423151536.GA25788@smart.cobolt.net \
    --to=dennis@cns.dnsalias.org \
    --cc=andrea@suse.de \
    --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