Bug 67118 - kernel-smp-2.4.18-4 won't boot
Summary: kernel-smp-2.4.18-4 won't boot
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel   
(Show other bugs)
Version: 7.3
Hardware: athlon Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2002-06-20 10:44 UTC by Bent Terp
Modified: 2008-08-01 16:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-30 15:39:41 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Bent Terp 2002-06-20 10:44:19 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i586; U;) Gecko/20020408

Description of problem:
Cannot boot kernel-smp on dual athlon, kernel-up boots without problems.

System worked previously with RedHat 7.2 and kernel-smp-2.4.9-31.athlon.rpm

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install RedHat 7.3 on a dual-athlon
2. rpm --upgrade kernel-smp-2.4.18-4.athlon.rpm; rpm --upgrade
3. shutdown -r now

Additional info:

system hangs during boot, at this point:
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 933.1310 MHz.
..... host bus clock speed is 133.3040 MHz.
cpu: 0, clocks: 1333040, slice: 444346

this was copied from dmesg on another machine, just to pinpoint exactly WHERE in
the bootprocess things went haywire.

Comment 1 Pietro Amodeo 2002-07-01 15:02:02 UTC
- Same problem detected with an installation from scratch of RH7.3, even after
upgrading kernel to kernel-smp-2.4.18-5.
- However, with both kernel-smp-2.4.18-3 and kernel-smp-2.4.18-5, boot stops
(apparently in a random fashion) either at the point listed above, or few lines
...changing IO-APIC physical APIC ID to 2 ... ok
..TIMER: vector=0x31 pin1=2 pin2=0

- In addition, with both kernel versions, the two AMD Athlon 2000+ MP processors
are incorrectly recognized as 1900+.
- HW configuration: M/B: Asus A7 M266-D BIOS Rev. 1004 ; RAM: 2x512MB unbuff.
DDR DIMM ; HD: 40 Gb Maxtor D740X-6L ; Video: TNT2 M64 32MB ; Network: 3COM

Comment 2 Pietro Amodeo 2002-07-01 18:20:18 UTC
Addendum to my previous comment:
I added a second HD (identical to the first one) on which I installed RH7.2.
The system was unable to boot (with the same errors described for RH7.3) both
with the default kernel-smp-2.4.7-10 and with the updated
kernel-smp-2.4.9-34.athlon.rpm. Of course, all the standard (single-processor)
athlon kernels (7.2 and 7.3 with the corresponding updates) boot without

Comment 3 Pietro Amodeo 2002-07-01 19:25:58 UTC
After updating the M/B BIOS to the 1006 revision the system boots without
problems with the smp kernel kernel-smp-2.4.18-5 (I have not yet retried the
other three versions quoted in my previous comments). However, I noticed that by
restoring the default BIOS setup values, as suggested in the BIOS updating
procedure, the "PnP O/S" value in the "Boot" menu changed from "Yes" to "No".
I experienced that this setting may be critical with previous RH releases (6.2
to 7.1) for athlon-based PC's. I'll try asap to reset the variable to "Yes" with
the new BIOS revision, and I'll post the results soon after.

Comment 4 Pietro Amodeo 2002-07-01 20:43:00 UTC
Last (for today) result:
after resetting PnP O/S variable value to "Yes" the system is still able to boot
(kernel-smp-2.4.18-5), but insmod is no more able to recognize USB. By switching
back to "No", a boot without any error message is recovered. Incidentally,
MPICH-1.2.4 has been compiled and tested successfully.

Comment 5 Bugzilla owner 2004-09-30 15:39:41 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

Note You need to log in before you can comment on or make changes to this bug.