mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops in 2.6.19.1
Date: Thu, 21 Dec 2006 14:22:32 +0000	[thread overview]
Message-ID: <200612211422.32650.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <200612210308_MC3-1-D5D4-3328@compuserve.com>

On Thursday 21 December 2006 08:05, Chuck Ebbert wrote:
> In-Reply-To: <200612202215.50315.s0348365@sms.ed.ac.uk>
>
> On Wed, 20 Dec 2006 22:15:50 +0000, Alistair John Strachan wrote:
> > > I'd guess you have some kind of hardware problem.  It could also be
> > > a kernel problem where the saved address was corrupted during an
> > > interrupt, but that's not likely.
> >
> > Seems pretty unlikely on a 4 year old Via Epia. Never had any problems
> > with it before now.
> >
> > Maybe a cosmic ray event? ;-)
>
> The low byte of eip should be 5f and it changed to 60, so that's
> probably not it.  And the oops report is consistent with that being
> the instruction that was really executed, so it's not the kernel
> misreporting the address after it happened.
>
> You weren't trying kprobes or something, were you? Have you ever
> had another unexplained oops with this machine?

Nope, it's a stock kernel and it's running on a server, kprobes isn't in use.

And no, to my knowledge there's not been another "unexplained" oops. I've had 
crashes, but they've always been known issues or BIOS trouble.

The machine was recently tampered with to install additional HDDs, but the 
memory was memtest'ed when it was installed and passed several times without 
issue. I'm rather puzzled.

-- 
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

  reply	other threads:[~2006-12-21 14:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21  8:05 Chuck Ebbert
2006-12-21 14:22 ` Alistair John Strachan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-31 21:43 Chuck Ebbert
2006-12-31 22:16 ` Alistair John Strachan
2006-12-30 17:21 Chuck Ebbert
2006-12-30 18:29 ` Alistair John Strachan
2006-12-31 16:28   ` Adrian Bunk
2006-12-31 16:48     ` Alistair John Strachan
2007-01-02 21:12       ` Adrian Bunk
     [not found] <200612232325_MC3-1-D634-10E4@compuserve.com>
2006-12-24 14:40 ` Alistair John Strachan
2006-12-24 14:51 ` Alistair John Strachan
2006-12-20 20:48 Chuck Ebbert
2006-12-20 22:15 ` Alistair John Strachan
2006-12-21 15:31   ` Valdis.Kletnieks
2006-12-30 18:06 ` James Courtier-Dutton
2006-12-30 18:32   ` Alistair John Strachan
2006-12-20 14:21 Alistair John Strachan
2006-12-20 16:30 ` Greg KH
2006-12-20 16:44   ` Alistair John Strachan
2006-12-23 15:40 ` Alistair John Strachan
2006-12-27  2:07   ` Zhang, Yanmin
2006-12-27 12:35     ` Alistair John Strachan
2006-12-28  2:41       ` Zhang, Yanmin
2006-12-28  4:02         ` Alistair John Strachan
2006-12-28  4:14           ` Alistair John Strachan
2006-12-30 16:59             ` Alistair John Strachan
2006-12-31 13:47               ` Alistair John Strachan
2006-12-31 16:27               ` Adrian Bunk
2006-12-31 16:55                 ` Alistair John Strachan

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=200612211422.32650.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=76306.1226@compuserve.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

all inboxes | Powered by JetHome®