Hello,
I am running two DELL R410/8GB RAM/Intel E5504 4x2.00GHz. Both machines runs exact same configuration:
openvz-02:~# uname -a
Linux openvz-02 2.6.24-9-pve #1 SMP PREEMPT Tue Nov 17 09:34:41 CET 2009 x86_64 GNU/Linux
One of the machines started filling logs with entries (fill rate is 1000 messages/sec, 20GB log space is filled in about 2h):
Dec 19 22:43:30 openvz-02 kernel: BUG: scheduling while atomic: swapper/0/0x00000002
Dec 19 22:43:30 openvz-02 kernel: Pid: 0, comm: swapper Not tainted 2.6.24-9-pve #1
Dec 19 22:43:30 openvz-02 kernel:
Dec 19 22:43:30 openvz-02 kernel: Call Trace:
Dec 19 22:43:30 openvz-02 kernel: [<ffffffff804c7485>] thread_return+0x103/0x67e
Dec 19 22:43:30 openvz-02 kernel: [<ffffffff8026424b>] clockevents_notify+0x2b/0x80
Dec 19 22:43:30 openvz-02 kernel: [<ffffffff8820b58f>] rocessor:acpi_idle_enter_bm+0x2c1/0x319
Dec 19 22:43:30 openvz-02 kernel: [<ffffffff80423ea4>] menu_select+0xb4/0xe0
Dec 19 22:43:30 openvz-02 kernel: [<ffffffff80422a90>] cpuidle_idle_call+0x0/0x100
Dec 19 22:43:30 openvz-02 kernel: [<ffffffff8020a000>] default_idle+0x0/0x50
Dec 19 22:43:30 openvz-02 kernel: [<ffffffff8020b587>] cpu_idle+0xc7/0x110
Except huge amout of log entries system seems to run stable. It runs about 25 OpenVZ VEs. Average load is below 1.
What may cause this kind of problem (broken hardware, kernel bug?). The other machine with exact same configuration does not log this error. Please let me know if additional system information is required.
Thanks,
-Maciej
I am running two DELL R410/8GB RAM/Intel E5504 4x2.00GHz. Both machines runs exact same configuration:
openvz-02:~# uname -a
Linux openvz-02 2.6.24-9-pve #1 SMP PREEMPT Tue Nov 17 09:34:41 CET 2009 x86_64 GNU/Linux
One of the machines started filling logs with entries (fill rate is 1000 messages/sec, 20GB log space is filled in about 2h):
Dec 19 22:43:30 openvz-02 kernel: BUG: scheduling while atomic: swapper/0/0x00000002
Dec 19 22:43:30 openvz-02 kernel: Pid: 0, comm: swapper Not tainted 2.6.24-9-pve #1
Dec 19 22:43:30 openvz-02 kernel:
Dec 19 22:43:30 openvz-02 kernel: Call Trace:
Dec 19 22:43:30 openvz-02 kernel: [<ffffffff804c7485>] thread_return+0x103/0x67e
Dec 19 22:43:30 openvz-02 kernel: [<ffffffff8026424b>] clockevents_notify+0x2b/0x80
Dec 19 22:43:30 openvz-02 kernel: [<ffffffff8820b58f>] rocessor:acpi_idle_enter_bm+0x2c1/0x319
Dec 19 22:43:30 openvz-02 kernel: [<ffffffff80423ea4>] menu_select+0xb4/0xe0
Dec 19 22:43:30 openvz-02 kernel: [<ffffffff80422a90>] cpuidle_idle_call+0x0/0x100
Dec 19 22:43:30 openvz-02 kernel: [<ffffffff8020a000>] default_idle+0x0/0x50
Dec 19 22:43:30 openvz-02 kernel: [<ffffffff8020b587>] cpu_idle+0xc7/0x110
Except huge amout of log entries system seems to run stable. It runs about 25 OpenVZ VEs. Average load is below 1.
What may cause this kind of problem (broken hardware, kernel bug?). The other machine with exact same configuration does not log this error. Please let me know if additional system information is required.
Thanks,
-Maciej