Bug 2437 - SMP incorrectly detected on non-SMP board; kernel panic; docs slightly wrong
SMP incorrectly detected on non-SMP board; kernel panic; docs slightly wrong
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
6.0
All Linux
medium Severity high
: ---
: ---
Assigned To: Cristian Gafton
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-04-30 10:01 EDT by dripton
Modified: 2008-08-01 12:22 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description dripton 1999-04-30 10:01:14 EDT
I have a Tyan Tomcat I board, which is a single-processor
Pentium board but a close cousin of the dual Tomcat II.
Apparently too close.

At boot, the kernel says :
total of 2 processors activated (66.36 BogoMIPS)
enabling symetric IO mode done
enabling IO-APIC IRQs
IO-APIC pm 0,20,21,22,23,...,255 not connected
MP-BIOS bug: 8254 timer not connected to IO-APIC
trying to set up timer as ExtINT (found pm 0) failed
trying to set up timer as BP IRQ failed
Kernel panic IO-APIC + timer doesn't work
In swapper task not syncing
<hard lock>

The Red Hat manual points out that on an SMP machine, two
kernels are built.  It says the LILO labels are smp and
linux, but they were actually called linux and linux-u.
(Might want to consider syncing the labels and the manual.)
Anyway, linux-u works fine.  If false SMP detection is a
common problem, it might be a good idea to run the
single-processor kernel by default and make those who want
smp choose smp.
Comment 1 Jay Turner 1999-06-04 11:12:59 EDT
This issue has been forwarded to a developer for further action.  In
addition the manual correction has been forwarded to the docs staff.

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