Summary: | [apic] [panic] Running with APIC enabled crashes a Supermicro server running 7.0/7.1 | ||||||
---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | Matt Hempel <matt> | ||||
Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> | ||||
Status: | Open --- | ||||||
Severity: | Affects Only Me | Keywords: | crash | ||||
Priority: | Normal | ||||||
Version: | Unspecified | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Matt Hempel
2009-02-10 19:30:01 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)? Responsible Changed From-To: freebsd-bugs->gavin Track 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. 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 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> |