Red Hat Bugzilla – Bug 100691
kernel-smp unstable - apps crash and/or oopses
Last modified: 2015-01-04 17:02:44 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Description of problem:
SMP kernel unstable. Randomly placed oopses and/or application segfaults when
able to boot fully. Cannot duplicate any single instance reliably, but can get
errors on demand. Single processor kernel works fine on same machine. ACPI
on/off, pci=noacpi doesn't matter. Motherboard is a Tyan Tiger MPX with USB
support on the mobo (earlier Tiger MPX mobos had no USB support because 760MPX
chipset is broken w.r.t. USB). BIOS version is 4.0.5, which is the latest and
greatest at the time of this writing.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot SMP kernel on Tyan Tiger MPX
2. Experience random oopses during boot and/or app failures afterward.
Actual Results: Seemingly random oopses and segfaults.
Expected Results: No problems.
Attaching lspci output
Created attachment 93102 [details]
output of "lspci -v"
Can you post some of the oopses/crashes?
Can post oopses but can't run them through ksymoops because ksymoops isn't
included in serern. Will the stock one mentioned in the ksymoops README work
for this beta kernel?
the kernel itself will ksymoops the oopses, if you do it by hand they just get
Created attachment 93271 [details]
oops number 1
oops in ext3_write_super - looks bad, fellas. Only occurs when booted into SMP
kernel. System ran without a hitch for a week with UP kernel.
Created attachment 93272 [details]
oops in ext3_new_block - another nasty looking beast.
Installing RHES on this same machine generated a CPU1 machine check exception.
So, I suspect that the hardware is to blame - probably the second CPU is toast
(not hard to do with exposed silicon without heatspreader protection and a
cranky heatsink mechanism). It would be nice if the Severn/Cambridge kernels
also trapped these exceptions well enough to report this.
Closing as working for us, then.