From: "John Madden" <jmadden@ivy.tec.in.us>
To: <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.14 reboot on/before boot
Date: Thu, 15 Nov 2001 09:45:48 -0500 (EST) [thread overview]
Message-ID: <4687.168.91.2.45.1005835548.squirrel@mail.ivy.tec.in.us> (raw)
In-Reply-To: <E1649VZ-0006K9-00@the-village.bc.nu>
In-Reply-To: <E1649VZ-0006K9-00@the-village.bc.nu>
>> Two machines, identical hardware (Dell 2450's, Dual PIII/667, 1gig
>> ram). One one, 2.4.14 boots and runs nicely, as one would expect. On
>> the other, "as close to exact as I can imagine" compile configs, the
>> machine reboots just after LILO's "Loading Linux..." Same version of
>> LILO on both as well.
>>
>> Has anyone else experienced this? Any ideas on a fix?
>
> Check they are the same BIOS. If so run memtest86 across them. The Lilo
> load/unpack might be enough to stress memory and find real faults
Checked the BIOS versions and memtested the 'bad' machine, versions match,
no bad memory found.
I tried upgrading on multiple machines, some others failed, some didn't. So
far, two of our 2450's take 2.4.14 without issue and three don't.
Working:
Dual PIII/667, 1gig, 3x18gb scsi, adaptec 7xxx
Dual PIII/1000, 1gig, 4x18gb scsi, ami megaraid
Not working:
Single PIII/667, 256mb, 2x18gb scsi, adaptec 7xxx
2 x (Dual PIII/667, 1gig, 3x18gb scsi, adaptec 7xxx)
All 5 machines have the same BIOS and 'backplane' rev.
In the 'not working' machines, all three do exactly the same thing: LILO ->
"Loading Linux.." (or something similar, text that flashes very quickly) ->
reboot. All of these boxes have and are running 2.2.19 without so much as a
single crash (or any other issue, for that matter) since upgrading from
2.2.16. I can swallow one machine having a fluky RAM issue, but not three.
I'm strongly considering dropping back to 2.2.20...
Thanks,
John
--
John Madden
UNIX Systems Engineer
Ivy Tech State College
jmadden@ivy.tec.in.us
prev parent reply other threads:[~2001-11-15 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-14 23:12 John Madden
2001-11-14 23:31 ` Alan Cox
2001-11-15 14:45 ` John Madden [this message]
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=4687.168.91.2.45.1005835548.squirrel@mail.ivy.tec.in.us \
--to=jmadden@ivy.tec.in.us \
--cc=alan@lxorguk.ukuu.org.uk \
--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®