Kernel error kernel:[360783.353677]

[Arcesilaus]

Hi

Having upgraded earlier this week from V6, I just received the following kernel error:

2012/09/27 20:45:21 kernel:[360783.353677] Pid: 0, comm: swapper Not tainted 2.6.35.14-oe64-00000-ga36704d #69
2012/09/27 20:45:21 kernel:[360783.353679] Call Trace:
2012/09/27 20:45:21 kernel:[360783.353680] <IRQ> [<ffffffff814d3455>] ? dev_watchdog+0x215/0x220
2012/09/27 20:45:21 kernel:[360783.353684] [<ffffffff814d3455>] ? dev_watchdog+0x215/0x220
2012/09/27 20:45:21 kernel:[360783.353688] [<ffffffff8104590c>] ? warn_slowpath_common+0x8c/0xc0
2012/09/27 20:45:21 kernel:[360783.353691] [<ffffffff81045a16>] ? warn_slowpath_fmt+0x56/0x60
2012/09/27 20:45:21 kernel:[360783.353693] [<ffffffff8103cdf1>] ? enqueue_task+0x61/0xa0
2012/09/27 20:45:21 kernel:[360783.353695] [<ffffffff8103d873>] ? try_to_wake_up+0xb3/0x2b0
2012/09/27 20:45:21 kernel:[360783.353699] [<ffffffff8129091e>] ? strlcpy+0x4e/0x80
2012/09/27 20:45:21 kernel:[360783.353701] [<ffffffff814b9933>] ? netdev_drivername+0x43/0x50
2012/09/27 20:45:21 kernel:[360783.353703] [<ffffffff814d3455>] ? dev_watchdog+0x215/0x220
2012/09/27 20:45:21 kernel:[360783.353706] [<ffffffff81040d93>] ? __wake_up+0x43/0x70
2012/09/27 20:45:21 kernel:[360783.353708] [<ffffffff814d3240>] ? dev_watchdog+0x0/0x220
2012/09/27 20:45:21 kernel:[360783.353710] [<ffffffff8105122f>] ? run_timer_softirq+0x19f/0x200
2012/09/27 20:45:21 kernel:[360783.353712] [<ffffffff810649c2>] ? ktime_get+0x52/0xd0
2012/09/27 20:45:21 kernel:[360783.353715] [<ffffffff8104b5fd>] ? __do_softirq+0xad/0x150
2012/09/27 20:45:21 kernel:[360783.353718] [<ffffffff819e2140>] ? early_idt_handler+0x0/0x71
2012/09/27 20:45:21 kernel:[360783.353721] [<ffffffff8100ab5c>] ? call_softirq+0x1c/0x30
2012/09/27 20:45:21 kernel:[360783.353723] [<ffffffff8100c505>] ? do_softirq+0x65/0xa0
2012/09/27 20:45:21 kernel:[360783.353725] [<ffffffff8104b54c>] ? irq_exit+0x7c/0x80
2012/09/27 20:45:21 kernel:[360783.353728] [<ffffffff8102289a>] ? smp_apic_timer_interrupt+0x6a/0xa0
2012/09/27 20:45:21 kernel:[360783.353730] [<ffffffff8100a613>] ? apic_timer_interrupt+0x13/0x20
2012/09/27 20:45:21 kernel:[360783.353731] <EOI> [<ffffffffa00a0d6a>] ? acpi_idle_enter_simple+0xf7/0x128 [processor]
2012/09/27 20:45:21 kernel:[360783.353738] [<ffffffffa00a0d63>] ? acpi_idle_enter_simple+0xf0/0x128 [processor]
2012/09/27 20:45:21 kernel:[360783.353741] [<ffffffff81474298>] ? cpuidle_idle_call+0x98/0x110
2012/09/27 20:45:21 kernel:[360783.353744] [<ffffffff81008ba7>] ? cpu_idle+0x57/0x90
2012/09/27 20:45:21 kernel:[360783.353746] [<ffffffff819e2e25>] ? start_kernel+0x2e5/0x3c0
2012/09/27 20:45:21 kernel:[360783.353748] [<ffffffff819e23df>] ? x86_64_start_kernel+0xff/0x130

I don't know to what extent I should be worried, because everything seems to work just fine, but it might be useful for me and others to know how we should respond to such errors.

[To-M]

Could be an IRQ issue, try to disable any and all power management features from the BIOS of the motherboard. Also if you have additional NIC like a quad port or dual port nic maybe move that to a different slot.

[Arcesilaus]

Ok, will try that at the next reboot and will keep this thread up to date.
It just seemed to come completely out of the dark now, so I'll see if I can find out what unusual things happened around that time.

[Arcesilaus]

Well, the issue might be a different one:

Last week, I replaced all hardware (motherboard, processor, memory, nics) except the Areca Raid Controller and the DOM, after I had seen a apparently random few system freezes.
So far so good for last week, but half an hour ago, yet again, the system froze completely.

The RAID controller does not indicate any errors, so it might be the DOM (Transcend Industrial Flash 2GB SLC DOM with 1 million hours MTBF).
To be honest, I do not know what role the DOM plays once the server has started, but I thought that is minimal and all vital information is stored on the system volume.
Would it make sense to think it is unlikely the DOM is the problem here?

Anyway, this time I would like to know a little more precise what causes the problems, so I downloaded the log files but there seems to be no useful info in the critical_errors.log.
What other logs could reveal some useful hints what causes the freezes?

[To-M]

Try re-formatting the DOM after you save your settings in Maint. > Misc and take all options so that you can save the file called settings.cnf then use to restore. You can look at the dmesg2.log as well to see if there are any errors and the packages ones during the time of the crash.

[Al-S]

Also try to "Disable" in BIOS all power management options.
Try to disable APM and ACPI in CTRL+ALT+T menu(in console mode ).ctrl+alt+t->boot options(9)->Boot parameters(1).