SCIENTIFIC-LINUX-USERS Archives

June 2006

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Rob Henderson <[log in to unmask]>
Reply To:
Rob Henderson <[log in to unmask]>
Date:
Tue, 6 Jun 2006 16:05:11 +0100
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (57 lines)
On Tue, 6 Jun 2006, Troy Dawson wrote:

re-€4.2 kernel panic. Put up 4.2 on acer travelmate 8100 laptop. Sort of
worked except for USB. Then machine had a problem and motherboard was
replaced. Now when you install 4.2 kernel consistently gives kernel panic.
Tried 4.3 and this does not give kernel panic (does not work either for
different reason). Knoppix using a much later kernel than 4.2 or 4.3
(2.6.9-XX) does work.

Just though you might find that interesting. There must be chipsets out
there that do not like 2.6.9 in various forms.

Rob Henderson



> Winnie Lacesso wrote:
> > Greetings *,
> >
> > SL4.2 was loaded on a moderately respectable desktop machine here
> > 3 June ca.19:00 & has been used lightly as a desktop since (left on 7x24).
> > This is our first/only SL4.2 box so far.
> >
> > On 6 June 04:02:01 it started the usual cron.daily/* scripts which
> > finished v quick, then at 04:02:21 a kernel panic occurred (Unable to
> > handle kernel paging request at firstual address blahblah, etc, Oops:
> > 0000 [#1] etc).
> >
> > Would any SL developers or debuggers be interested to know the relevant
> > machine architecture, error messages etc.
> >
> > Otherwise, well it may never happen again, could be gremlins.
>
> Hi,
> Although we might not always know the answer, we're interested in the
> problems.
>
> My first thing I always say when someone has a kernel-oops is "Have you
> checked the memory?"  It might be a higher percentage, but at least 75%
> of kernel-oops I know of really stem from hitting a bad section in your
> memory.  In which case you're going to see another kernel-oops again.
>
> If you've already checked the memory, we'd like to know what CPU, if
> you're doing i386, or x86_64.  Also, if you have any extra kernel
> modules not in the standard kernel.  (And yes, that includes AFS)
> And last, but certainly not least, the full kernel oops if possible.
> (We know it's hard because it's often only on the screen, but they do
> sometimes make it to the hard drive)
>
> Troy
>

-- 
Dr Rob C W Henderson
Department of Physics    Lancaster University
Telephone : 01524 593617

ATOM RSS1 RSS2