Bug 131571 - [apic] [panic] Running with APIC enabled crashes a Supermicro server running 7.0/7.1
Summary: [apic] [panic] Running with APIC enabled crashes a Supermicro server running ...
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: crash
Depends on:
Blocks:
 
Reported: 2009-02-10 19:30 UTC by Matt Hempel
Modified: 2022-10-17 12:18 UTC (History)
0 users

See Also:


Attachments
file.txt (54.42 KB, text/plain)
2009-02-10 19:30 UTC, Matt Hempel
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Hempel 2009-02-10 19:30:01 UTC
Dual Xeon 1.8 GHz with hyperthreading.  2 Gigs of Memory.  Server ran 4.11 successfully in production for 5+ years.

http://www.supermicro.com/products/system/1U/6013/SYS-6013P-8+.cfm

Boot fails more than 50% of the time running 7.0/7.1.  It often panics at the APIC initialization (at the beginning of boot).  Less often, it locks up towards the end, at "Trying to mount root from ufs:/dev/mirror/gm0s1a".

Panic'ced boots randomly report failures on two different AP#s (2 and 3) and two different PHY#s (6 and 7).   See attached document.

Disabling ACPI/hyperthreading has no effect.  The only way to get the machine to boot consistently is to disable APIC (and so disable SMP).  When APIC is disabled, machine boots 100% of the time.

Verbose boot messages attached from one successful and two failed boots (search for Failed boot).

Thanks 

M

Fix: Disable APIC.

Patch attached with submission follows:
How-To-Repeat: Boot into version 7 kernel with APIC enabled.
Comment 1 Gavin Atkinson freebsd_committer freebsd_triage 2009-02-11 11:49:11 UTC
State Changed
From-To: open->feedback

To submitter: a couple of questions:  Forstly, did you jump straight 
from 4.11 to 7.x, or do you know if (e.g.) 6.x had the same issue? 
Also, if you answer "N" to the "Panic? (y/n)" question, does the 
machine boot and run successfully? 
Lastly, is there a pattern as to when the machine does and doesn't boot? 
For example, does it always boot or not from a power on (rather than a 
reset)? 


Comment 2 Gavin Atkinson freebsd_committer freebsd_triage 2009-02-11 11:49:11 UTC
Responsible Changed
From-To: freebsd-bugs->gavin

Track
Comment 3 Matt Hempel 2009-02-13 15:04:09 UTC
The BIOS on the server is from 3/2002.  The last released Supermicro 
BIOS is from 11/2003.

I was incorrect about the model of the server (these boxes are remote).

http://www.supermicro.com/products/system/1U/6012/SYS-6012P-6.cfm

I disabled hyperthreading in the BIOS and the system will now boot 
reliably with an SMP 7.1 kernel (APIC enabled).   I'm debating whether 
it's worth the trouble to update the BIOS when all I'm losing is two 
virtual processors.
Comment 4 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:01:42 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped
Comment 5 Graham Perrin freebsd_committer freebsd_triage 2022-10-17 12:18:22 UTC
Keyword: 

    crash

– in lieu of summary line prefix: 

    [panic]

* bulk change for the keyword
* summary lines may be edited manually (not in bulk). 

Keyword descriptions and search interface: 

    <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>