Difference between revisions of "Known problems"
(structured a bit better, use Template:Forum) |
|||
| Line 4: | Line 4: | ||
== NMI interrupts == | == NMI interrupts == | ||
| − | Some hardware doesn't handle NMI interrupts correctly | + | Some hardware doesn't handle NMI interrupts correctly, and a machine oopses on boot. |
| − | |||
| − | At least | + | '''Solution:''' try boot it with '''nmi_watchdog=0''' |
| + | |||
| + | At least the following hardware is known to be faulty/have problems with it: | ||
* HP DL140G3 ({{Bug|514}}) | * HP DL140G3 ({{Bug|514}}) | ||
| Line 16: | Line 17: | ||
or peripheral device problems (like non-working ethernet adapter) | or peripheral device problems (like non-working ethernet adapter) | ||
| − | + | '''Solution:''' try boot your kernel with 'noapic' option. | |
| − | * Tyan S5372 motherboard and e1000 adapters ( | + | At least the following hardware is known to be faulty/have problems with it: |
| + | * Tyan S5372 motherboard and e1000 adapters ({Forum|2213}}) | ||
Revision as of 09:27, 28 March 2007
If any of those below help you, please do not forget to inform about this or add your hardware to the list below.
NMI interrupts
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)
APIC problems
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|2213}})
