[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#596419: Acknowledgement (xen-linux-system-2.6.32-5-xen-amd64: causes a system hangup by the shutdown of the system, aacraid (sw raid) involved in hangup)

After further anaysis it seems to be the fact it occurs not by "mdadm stop"
but by the call of "xendomains stop" because the hangup occurs not only by
the shutdown, but also by the simple call of

/etc/init.d/xendomains stop

- there are 4 domains running, 3 fully virtualized based on qemu and one
paravirtual, also debian squeeze based.

It also does not hang up the computer completely, it just freezes the
keyboard (also the numlock does not react etc.) and services (for example
concurrent ssh connection to the amchine is no longer usefull), but the
system itself does still something. There come after some minutes of waiting
again and again messages, ending by the following call trace (I hope I made
no mistakes in writing it down from monitor):
Call Trace:
[<....>]? smp_call_function_many+0x191/0x1af
[<....>]? drain_local_pages+0x0/0xd
[<....>]? smp_call_function+0x20/0x24
[<....>]? on_each_cpu+0x10/0x2e
[<....>]? __alloc_pages_nodemask+0x3f4/0x5ce
[<....>]? check_events+0x12/0x20
[<....>]? new_slab+0x42/0x1ca
[<....>]? __slab_alloc+0x1f0/0x39b
[<....>]? sock_alloc_send_pskb+0xbd/0x2d8
[<....>]? cap_socket_getpeersec_dgram+0x0/0x6
[<....>]? __kmalloc_node_track_caller+0xbb/0x11b
[<....>]? sock_alloc_send_pskb+0xbd/0x2d8
[<....>]? __alloc_skb+0x69/0x15a
[<....>]? sock_alloc_send_pskb+0xbd/0x2d8
[<....>]? pollwake+0x0/0x5b
[<....>]? unix_stream_sendmsg+0x133/0x2a1
[<....>]? sock_aio_write+0xb1/0xbc
[<....>]? sock_aio_write+0x0/0xbc
[<....>]? do_sync_readv_writev+0xc0/0x107
[<....>]? autoremove_wake_function+0x0/0x2e
[<....>]? rw_copy_check_nvector+0x6d/0xe4
[<....>]? do_readv_writev+0xb2/0x115
[<....>]? pvclock_clocksource_read+0x3a/0x70
[<....>]? sys_writev+0x45/0x93
[<....>]? system_call_fastpath+0x16/0x1b

This stack trace comes multiple times (for hour or more before I pushed the
power button) and unfortunatelly I cannot see anything more usefull in the
error. In the start, there was also some message with aacraid, but It
vanished too quickly to see what was written there.

-----Original Message-----
From: Debian BTS [mailto:debbugs@busoni.debian.org] On Behalf Of Debian Bug
Tracking System
Sent: Saturday, September 11, 2010 10:15 AM
To: Artur Linhart
Subject: Bug#596419: Acknowledgement (xen-linux-system-2.6.32-5-xen-amd64:
causes a system hangup by the shutdown of the system, aacraid (sw raid)
involved in hangup)

Thank you for filing a new Bug report with Debian.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
 Debian Kernel Team <debian-kernel@lists.debian.org>

If you wish to submit further information on this problem, please
send it to 596419@bugs.debian.org.

Please do not send mail to owner@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

596419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596419
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

__________ Informace od NOD32 5441 (20100910) __________

Tato zprava byla proverena antivirovym systemem NOD32.

Reply to: