From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011019
Description of problem:
On a slimmerlot with hampton beta3 installed (2.4.18-0.4smp), w/ bios A02, 1GB
ram, 2GB swap, and LSI 22320 as boot device...
3 different configurations give 3 different results:
22320 in slot 2, Perc3QC in slot 3 (with PV210S attached), Perc3DCL in slot 4,
1000XT in slot 5, Dual Pro 100 in slot 6, Pro 100 in slot 7 -- smp kernel only
sees 1 of 4 cpu's
Remove nics from slots 6 and 7 and kernel oops during cpu detection
Then remove Perc3QC and DCL also (leaving 22320 and 1000XT) and 4 cpu's are
Each of these three results are reproducible everytime.
Same results with hyperthreading (logical processors) enabled or disabled in
bios. Of course, in the working configuration, 4 or 8 processors are seen
depending on the setting.
Attaching mptable and pirq output from the two configurations that boot, and
ksymoops output from oopsing configuration.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install hampton beta3 on a slimmerlot with listed configuration
2.Note oops or incorrect cpu detection depending on configuration
Actual Results: Incorrect cpu detection or oops
Expected Results: Correct cpu detection
Created attachment 50905 [details]
pirq output of configuration that incorrectly sees 1 cpu
Created attachment 50907 [details]
mptable output of configuration that incorrectly sees 1 cpu
Created attachment 50908 [details]
pirq output of configuration that correctly sees 8 logical cpu's (hyperthreading enabled)
Created attachment 50910 [details]
mptable output of configuration that correctly sees 8 logical cpu's (hyperthreading enabled)
Created attachment 50911 [details]
ksymoops output of oopsing configuration
This is because the 2.4.18-0.4 kernel on beta3 does not include the MP
Table "MAX_MP_BUSSES" overflow bug fix which kills Merlot/SlimMerlot.
The latest rawhide kernel 2.4.18-0.10 does have the fix. Clay, please try this.
So, I think this is a duplicate of #60754, which claims to have been fixed for
beta3, but clearly wasn't.
Tried 2.4.18-0.10smp with all 6 pci cards in the machine and received expected