From: "Jarmo Järvenpää" <Jarmo.Jarvenpaa@softers.net>
To: linux-kernel@vger.kernel.org
Subject: Strange 2.6 booting / freeze problems
Date: Fri, 28 May 2004 15:20:51 +0300 [thread overview]
Message-ID: <40B72EA3.6090106@softers.net> (raw)
Dear list,
I have two servers which share same problem; kernel starts booting and
freezes to line 'DMI 2.3 present' (thus, almost immediately).
The servers were installed with RH7.3 and RH9 (2.4 kernel) and later,
were updated(=tested with) to 2.6.3,.4,.5 and .6.
1st server:
After compiling the 2.6 kernel, rebooted, kernel loading -> froze to
line 'DMI 2.3 present'.
Tried to update to newer kernel(s) but with no success. Changed back to
2.4.25 -> server ok.
2nd server:
Compiled 2.6.5, rebooted, kernel loaded ok. After release of 2.6.6,
updated, rebooted, no problems.
Today, I was hoping to test server's raid 1 functionality, rebooted ->
kernel would not load anymore (lilo and kernel were not touched after
last update), last line to be seen is 'DMI 2.3 present'.
Updated lilo and bios, no help. Tried to boot with kernel parameters:
acpi=off noapic nosmp notsc pci=noacpi apic=off, no help.
I had to downgrade to 2.4. :-(
--
The servers share at least one common thing, a i8xx chipset.
Jarmo
reply other threads:[~2004-05-28 12:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40B72EA3.6090106@softers.net \
--to=jarmo.jarvenpaa@softers.net \
--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