Difference between revisions of "Known problems"
(structured a bit better, use Template:Forum) |
m (→NMI interrupts: - HP DL180G6) |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 10: | Line 10: | ||
At least the following hardware is known to be faulty/have problems with it: | At least the following hardware is known to be faulty/have problems with it: | ||
* HP DL140G3 ({{Bug|514}}) | * HP DL140G3 ({{Bug|514}}) | ||
| + | * HP DL180G6 | ||
== APIC problems == | == APIC problems == | ||
| Line 20: | Line 21: | ||
At least the following hardware is known to be faulty/have problems with it: | At least the following hardware is known to be faulty/have problems with it: | ||
| − | * Tyan S5372 motherboard and e1000 adapters ({Forum|2213}}) | + | * Tyan S5372 motherboard and e1000 adapters ({{Forum|2213}}) |
| + | |||
| + | [[Category:Kernel]] | ||
| + | [[Category:Troubleshooting]] | ||
Latest revision as of 04:28, 6 December 2011
If any of those below help you, please do not forget to inform about this or add your hardware to the list below.
NMI interruptsEdit
Some hardware doesn't handle NMI interrupts correctly, and a machine oopses on boot.
Solution: try boot it with nmi_watchdog=0
At least the following hardware is known to be faulty/have problems with it:
- HP DL140G3 (OpenVZ Bug #514)
- HP DL180G6
APIC problemsEdit
Some nvidia chipsets are known to have buggy APIC. In this case user can experience different strange problems like crashes/hangs on boot, or peripheral device problems (like non-working ethernet adapter)
Solution: try boot your kernel with 'noapic' option.
At least the following hardware is known to be faulty/have problems with it:
- Tyan S5372 motherboard and e1000 adapters (Forum thread #2213)