Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 107446

Summary: After installing "kernel-smp-2.4.22-1.2093.nptl", only one processor is active on a PR440FX dual Pentium Pro system. See attached "dmesg" output.
Product: [Retired] Red Hat Raw Hide Reporter: Joachim Frieben <jfrieben>
Component: kernelAssignee: Dave Jones <davej>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0CC: len.brown, pfrields
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
URL: SMP kernel 2.4.22-1.2093 does not boot 2nd CPU
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-12-09 02:09:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
"dmesg" boot log for "kernel-smp-2.4.22-1.2093.nptl"
none
"dmesg" boot log for "kernel-smp-2.4.22-1.2088.nptl"
none
kernel-smp-2.4.22-1.2108.nptl-dmesg.output
none
"dmesg" boot log for "kernel-smp-2.4.22-1.2115.nptlcustom" none

Description Joachim Frieben 2003-10-18 11:31:13 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031014

Description of problem:
See above.

Version-Release number of selected component (if applicable):
kernel-smp-2.4.22-1.2093.nptl

How reproducible:
Always

Steps to Reproduce:
1. Install "kernel-smp-2.4.22-1.2093.nptl" on a PR440FX dual Pentium Pro system.
2. Reboot system.
3. check system activity by means of "top" or "xosview"


Actual Results:  Only one processor is displayed.

Expected Results:  Both processors should be up.

Additional info:

Comment 1 Joachim Frieben 2003-10-18 11:33:31 UTC
Created attachment 95280 [details]
"dmesg" boot log for "kernel-smp-2.4.22-1.2093.nptl"

Comment 2 Joachim Frieben 2003-10-19 13:30:06 UTC
Same behaviour for "kernel-smp-2.4.22-1.2097.nptl" kernel package :(

Comment 3 Dave Jones 2003-10-19 15:14:40 UTC
What was the last kernel that worked for you ?


Comment 4 Joachim Frieben 2003-10-23 17:57:57 UTC
Well, the last version working normally was the direct precursor of the
"kernel-smp-2.4.22-1.2093.nptl" kernel package, which was
"kernel-smp-2.4.22-1.2087.nptl", I think.

Comment 5 Joachim Frieben 2003-10-23 18:33:02 UTC
Oops, finally it was rather "kernel-smp-2.4.22-1.2088.nptl". "dmesg" output follows.

Comment 6 Joachim Frieben 2003-10-23 18:39:35 UTC
Created attachment 95439 [details]
"dmesg" boot log for "kernel-smp-2.4.22-1.2088.nptl"

Comment 7 Dave Jones 2003-10-24 01:12:24 UTC
Does 2108 fare any better ?


Comment 8 Philipp Hügelmeyer 2003-10-27 07:09:09 UTC
Created attachment 95503 [details]
kernel-smp-2.4.22-1.2108.nptl-dmesg.output

After installing kernel-smp-2.4.22-1.2108 ht sopped working on my 2,6 ghz
pentium 4 box. I think this is related to this bug, eventhough it worked up to
kernel-smp-2.4.22-1.2105.

Comment 9 Joachim Frieben 2003-10-27 07:43:14 UTC
No, unfortunately, "kernel-smp-2.4.22-1.2108.nptl" behaves exactly as any SMP 
kernel later than "kernel-smp-2.4.22-1.2088.nptl" which means it does not boot 
the 2nd CPU.

Comment 10 Eric Jones 2003-10-27 16:51:31 UTC
I am also running the 2108 kernel on a 3.06 GHz P4 box with hyper threading and
though the 2nd cpu is recognized, no processes get assigned to it and it sits
idle at 0% usage all the time.  Dmesg assigns both cpu's, starts the migration
threads, but just never runs any processes on the 2nd.

Comment 11 Dave Jones 2003-10-27 17:26:32 UTC
#8 and #10 are different bugs to this report, please open new ones for those.
In the original report, the 2nd CPU wasn't detected at all. From the look of
your dmesg, your CPUs are being detected.


Comment 12 Joachim Frieben 2003-10-30 18:06:30 UTC
"kernel-smp-2.4.22-1.2111.nptl" still only boots one CPU. "dmesg" output 
identical to previous versions.

Comment 13 Joachim Frieben 2003-11-05 15:10:43 UTC
"kernel-smp-2.4.22-1.2115.nptl" still only boots one CPU.

Comment 14 Len Brown 2003-11-11 05:09:55 UTC
Is it possible for you to answer these three things?: 
 
1. if you boot with "acpi=force" does that fair any better? 
     If it works, we know this is an MPS issue, rather than an SMP issue. 
     If it doesn't work it may or may not help us debug the problem, 
     depending on how it fails. 
 
2. If you re-build your kernel with the following line changed 
- #define APIC_DEBUG 0 
+ #define APIC_DEBUG 1 
in include/asm-i386/apic.h, the dmesg output may explain 
why we don't enable the 2nd processor. 
 
3. if you boot the latest 2.4.23 kernel with acpi=off, does it work? 
    (ie. did the latest baseline regress also, or did just Fedora regress?) 
 
thanks, 
-Len 
 

Comment 15 Joachim Frieben 2003-11-14 08:52:19 UTC
I have performed step 1 and 2 of the suggestions made by Len:

1. Adding the kernel option "acpi=force" leads to a kernel panic while
the machine is booting.

2. The "dmesg" ouput for "APIC_DEBUG=1" is attached hereafter.

I will try step 3 once the final version 2.4.23 of the Linux kernel is
released. BTW, 2 years ago, I had reported a still pending issue
concerning APIC IRQ-routing in bug #55223 related to the INTEL PR440FX
platform.

Comment 16 Joachim Frieben 2003-11-14 08:53:41 UTC
Created attachment 95965 [details]
"dmesg" boot log for "kernel-smp-2.4.22-1.2115.nptlcustom"

Comment 17 Joachim Frieben 2003-12-03 21:44:08 UTC
"kernel-smp-2.4.22-1.2129.nptl" boots the 2nd CPU correctly. "dmesg"
output now essentially identical to that of version
"kernel-smp-2.4.22-1.2088.nptl" again. The original IRQ mapping which
had been corrupted by the later kernel versions has successfully been
reestablished!