mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Adam Kropelin <akropel1@rochester.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.1 oops in prune_dcache()
Date: Thu, 22 Jan 2004 16:23:48 -0800	[thread overview]
Message-ID: <20040122162348.46637991.akpm@osdl.org> (raw)
In-Reply-To: <20040122181751.A2101@mail.kroptech.com>

Adam Kropelin <akropel1@rochester.rr.com> wrote:
>
> At 4 AM this morning (during cron run, I suppose) a box running 2.6.1
> hit the oops below. It locked solid, had to hit the reset button to
> reboot it. The machine had been running 2.6.1 for about a week prior
> with no problems.
> 
> Hardware is single Pentium Pro 200, 128 MB RAM (extensively
> memtest86'ed).

Yes, but it is old.

> Kernel is no-SMP, no-preempt, and (obviously) no-highmem.
> 
> Feel free to ask for more details if I can help. This is the first oops
> I've seen since mid 2.5.x on this machine.
> 
> --Adam
> 
> 
> Jan 21 04:06:32 print kernel: Unable to handle kernel paging request at virtual address 00008014
> Jan 21 04:06:32 print kernel:  printing eip:
> Jan 21 04:06:32 print kernel: c01570e5
> Jan 21 04:06:32 print kernel: *pde = 00000000
> Jan 21 04:06:32 print kernel: Oops: 0000 [#1]
> Jan 21 04:06:32 print kernel: CPU:    0
> Jan 21 04:06:32 print kernel: EIP:    0060:[<c01570e5>]    Not tainted
> Jan 21 04:06:32 print kernel: EFLAGS: 00010206
> Jan 21 04:06:32 print kernel: EIP is at prune_dcache+0xe5/0x130
> Jan 21 04:06:32 print kernel: eax: 00008000   ebx: c1dc83e0   ecx: c577da74   edx: c577da74

Bit 15 of %eax got flipped.  The kernel indexed off it and oopsed.

This is most likely a hardware failure.

  reply	other threads:[~2004-01-23  0:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22 23:17 Adam Kropelin
2004-01-23  0:23 ` Andrew Morton [this message]
2004-01-23  0:29   ` Adam Kropelin

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=20040122162348.46637991.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=akropel1@rochester.rr.com \
    --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