Difference between revisions of "Known problems"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
(New page: 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 correct...)
 
m (NMI interrupts: - HP DL180G6)
 
(4 intermediate revisions by 2 users not shown)
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.
If you machine Oopses on the boot, try boot it with '''nmi_watchdog=0'''
 
  
At least this hardware is known to be faulty:
+
'''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}})
 +
* HP DL180G6
  
 
== APIC problems ==
 
== APIC problems ==
Line 16: Line 18:
 
or peripheral device problems (like non-working ethernet adapter)
 
or peripheral device problems (like non-working ethernet adapter)
  
Try boot your kernel with 'noapic' option.
+
'''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}})
  
* Tyan S5372 motherboard and e1000 adapters (http://forum.openvz.org/index.php?t=msg&th=2213&start=0&)
+
[[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 interrupts[edit]

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:

APIC problems[edit]

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: