Your message dated Fri, 10 Aug 2012 14:52:07 +0200
with message-id <[email protected]>
and subject line Re: Bug#684484: base: Watchdog detected hard LOCKUP on cpu 4
has caused the Debian Bug report #684484,
regarding base: Watchdog detected hard LOCKUP on cpu 4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
684484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684484
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: base
Severity: normal
The server was running one KVM Guest (which was running apache) and the guest
suddenly
became unresponsive and this seems to have ben caused by whatever produced the
trace at the bottom of this message.
I can provide more info if required.
0 18:52:56 hostname kernel: [1468300.680408] WARNING: at
/usr/src/squeeze64/linux-2.6.38-2.6.38/debian/build/source_amd64_none/kernel/watchdog.c:226
watchdog_overflow_callback+0x96/0xa1()
Aug 10 18:52:56 hostname kernel: [1468300.680411] Hardware name: PowerEdge R310
Aug 10 18:52:56 hostname kernel: [1468300.680412] Watchdog detected hard LOCKUP
on cpu 4
Aug 10 18:52:56 hostname kernel: [1468300.680413] Modules linked in:
ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables
x_tables kvm_intel kvm fuse bridge stp ext2 mbcache vhost_net macvtap macvlan
tun joydev evdev snd_pcm tpm_tis snd_timer snd soundcore tpm ghes tpm_bios
snd_page_alloc dcdbas button processor pcspkr hed power_meter thermal_sys xfs
exportfs dm_mod raid1 md_mod sg sr_mod sd_mod cdrom crc_t10dif usbhid hid
ata_generic ata_piix libata ehci_hcd usbcore scsi_mod bnx2 nls_base [last
unloaded: scsi_wait_scan]
Aug 10 18:52:56 hostname kernel: [1468300.680445] Pid: 25869, comm: kvm Not
tainted 2.6.38-sis-1-amd64 #1
Aug 10 18:52:56 hostname kernel: [1468300.680446] Call Trace:
Aug 10 18:52:56 hostname kernel: [1468300.680448] <NMI> [<ffffffff81046ac2>]
? warn_slowpath_common+0x78/0x8c
Aug 10 18:52:56 hostname kernel: [1468300.680455] [<ffffffff81046b75>] ?
warn_slowpath_fmt+0x45/0x4a
Aug 10 18:52:56 hostname kernel: [1468300.680458] [<ffffffff81090032>] ?
watchdog_overflow_callback+0x96/0xa1
Aug 10 18:52:56 hostname kernel: [1468300.680461] [<ffffffff810b1417>] ?
__perf_event_overflow+0x12a/0x189
Aug 10 18:52:56 hostname kernel: [1468300.680466] [<ffffffff810165a8>] ?
intel_pmu_save_and_restart+0x80/0x8f
Aug 10 18:52:56 hostname kernel: [1468300.680470] [<ffffffff81018e65>] ?
intel_pmu_handle_irq+0x386/0x3f5
Aug 10 18:52:56 hostname kernel: [1468300.680474] [<ffffffff81328686>] ?
perf_event_nmi_handler+0x50/0x98
Aug 10 18:52:56 hostname kernel: [1468300.680477] [<ffffffff8132a284>] ?
notifier_call_chain+0x2e/0x5b
Aug 10 18:52:56 hostname kernel: [1468300.680479] [<ffffffff8132a2fb>] ?
notify_die+0x2d/0x32
Aug 10 18:52:56 hostname kernel: [1468300.680482] [<ffffffff81327dd1>] ?
do_nmi+0x63/0x204
Aug 10 18:52:56 hostname kernel: [1468300.680484] [<ffffffff81327890>] ?
nmi+0x20/0x30
Aug 10 18:52:56 hostname kernel: [1468300.680490] [<ffffffffa032c656>] ?
vmx_vcpu_run+0x24c/0x2ef [kvm_intel]
Aug 10 18:52:56 hostname kernel: [1468300.680491] <<EOE>>
[<ffffffffa02ce28e>] ? kvm_arch_vcpu_ioctl_run+0x8de/0xbf3 [kvm]
Aug 10 18:52:56 hostname kernel: [1468300.680504] [<ffffffffa032d44b>] ?
vmx_vcpu_load+0x28/0x168 [kvm_intel]
Aug 10 18:52:56 hostname kernel: [1468300.680507] [<ffffffff8132652f>] ?
mutex_lock+0xd/0x33
Aug 10 18:52:56 hostname kernel: [1468300.680513] [<ffffffffa02c1a29>] ?
kvm_vcpu_ioctl+0x10d/0x4e8 [kvm]
Aug 10 18:52:56 hostname kernel: [1468300.680518] [<ffffffff8105536f>] ?
__dequeue_signal+0xf6/0x121
Aug 10 18:52:56 hostname kernel: [1468300.680521] [<ffffffff810569ad>] ?
dequeue_signal+0x9b/0x107
Aug 10 18:52:56 hostname kernel: [1468300.680525] [<ffffffff81103b7c>] ?
do_vfs_ioctl+0x484/0x4d1
Aug 10 18:52:56 hostname kernel: [1468300.680528] [<ffffffff81103c14>] ?
sys_ioctl+0x4b/0x6f
Aug 10 18:52:56 hostname kernel: [1468300.680531] [<ffffffff81009992>] ?
system_call_fastpath+0x16/0x1b
Aug 10 18:52:56 hostname kernel: [1468300.680533] ---[ end trace
98d614e99c2dfb74 ]---
-- System Information:
Debian Release: 6.0.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On Freitag, 10. August 2012, Kesavan Rengarajan wrote:
> The server was running one KVM Guest (which was running apache) and the
> guest suddenly became unresponsive and this seems to have ben caused by
> whatever produced the trace at the bottom of this message.
[...]
> -- System Information:
> Debian Release: 6.0.1
> Kernel: Linux 2.6.38-1-amd64 (SMP w/8 CPU cores)
this is not a stable kernel, closing the bug.
--- End Message ---
