Package: linux-image-2.6.26-1-xen-686
Version: 2.6.26-4
Severity: normal

Hi,

Yesterday afternoon three out of our four Lenny virtual machines froze.
The consoles went unresponsible, the buffers contained no interesting
messages, the Munin graphs didn't show any anomaly before the freeze.
According to dom0 (Etch with hypervisor from Backports.org) the domUs
are stuck in r state (constantly running). I let them running in case
it is possible to extract any info from the system; if not, please tell
me so I can reboot them. See also the thread on linux-kernel:
http://lkml.org/lkml/2008/9/21/21
Both the host and the paravirtual guest are up-to-date systems. The
Etch domUs kept on running without any problem.

Thanks,
Feri.

-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-xen-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.26-1-xen-686 depends on:
ii initramfs-tools 0.92j tools for generating an initramfs
ii linux-modules-2.6.26-1-xen-68 2.6.26-4 Linux 2.6.26 modules on i686

Versions of packages linux-image-2.6.26-1-xen-686 recommends:
ii libc6-xen 2.7-13 GNU C Library: Shared libraries [X

Versions of packages linux-image-2.6.26-1-xen-686 suggests:
pn grub <none> (no description available)
pn linux-doc-2.6.26 <none> (no description available)

-- no debconf information



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sun, Sep 21, 2008 at 02:18:37PM +0200, Ferenc Wagner wrote:
> Yesterday afternoon three out of our four Lenny virtual machines froze.
> The consoles went unresponsible, the buffers contained no interesting
> messages, the Munin graphs didn't show any anomaly before the freeze.
> According to dom0 (Etch with hypervisor from Backports.org) the domUs
> are stuck in r state (constantly running).

Please show the complete versions of all related components. Especially
the hypervisor needs to be 3.2.1 or higher. Please note that
backports.org versions of Xen and Linux are not supported by the
original maintainers.

Bastian

--
Earth -- mother of the most beautiful women in the universe.
-- Apollo, "Who Mourns for Adonais?" stardate 3468.1



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Bastian Blank <waldi@debian.org> writes:

> On Sun, Sep 21, 2008 at 02:18:37PM +0200, Ferenc Wagner wrote:
>> Yesterday afternoon three out of our four Lenny virtual machines froze.
>> The consoles went unresponsible, the buffers contained no interesting
>> messages, the Munin graphs didn't show any anomaly before the freeze.
>> According to dom0 (Etch with hypervisor from Backports.org) the domUs
>> are stuck in r state (constantly running).
>
> Please show the complete versions of all related components.

I guess they are these:

ii xen-hypervisor-3.2-1-i386 3.2.0-3~bpo4+2 The Xen Hypervisor on i386
ii linux-image-2.6.26-1-xen-686 2.6.26-4 Linux 2.6.26 image on i686

> Especially the hypervisor needs to be 3.2.1 or higher.

As you can see, it isn't currently. Sounds like you know about
possibly relevant changes since 3.2.0. If so, I'm willing to upgrade
dom0 to Lenny, too.

> Please note that backports.org versions of Xen and Linux are not
> supported by the original maintainers.

Understood. Please don't get me wrong: I'm willing to follow expert
advice, but don't want to destabilise our hosting environment for no
reason. And I don't expect you to support *anything* in particular.
I'm grateful you actually do.
--
Regards,
Feri.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Ferenc Wagner <wferi@niif.hu> writes:

> Bastian Blank <waldi@debian.org> writes:
>
>> On Sun, Sep 21, 2008 at 02:18:37PM +0200, Ferenc Wagner wrote:
>>> Yesterday afternoon three out of our four Lenny virtual machines froze.
>>> The consoles went unresponsible, the buffers contained no interesting
>>> messages, the Munin graphs didn't show any anomaly before the freeze.
>>> According to dom0 (Etch with hypervisor from Backports.org) the domUs
>>> are stuck in r state (constantly running).
>>
>> Please show the complete versions of all related components.

This still happens under current Lenny with the same kernel running in
the virtual machine (which is current Lenny, too):

libc6-xen 2.7-14
libxenstore3.0 3.2.1-2
linux-image-2.6.26-1-xen-686 2.6.26-8
linux-modules-2.6.26-1-xen-686 2.6.26-8
xen-hypervisor-3.2-1-i386 3.2.1-2
xen-linux-system-2.6.26-1-xen-686 2.6.26-8
xen-utils-3.2-1 3.2.1-2
xen-utils-common 3.2.0-2
xenstore-utils 3.2.1-2

Some possibly interesting console output is available:

[322998.720866] INFO: task apache2:735 blocked for more than 120 seconds.
[322998.720878] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[322998.720883] apache2 D 90fac331 0 735 703
[322998.720892] c69d6da0 00000246 00000000 90fac331 0001250f c69d6f28 c1391b40 00000000
[322998.720907] c6ef8780 c9141d4a 00011570 000b0d69 00000000 00014005 00000000 00000001
[322998.720921] 00000000 000002d0 c66bb480 c913f03e c9137a91 00000000 ffffffff c0cc3578
[322998.720935] Call Trace:
[322998.720949] [<c9141d4a>] xfs_buf_get_flags+0xa6/0x10a [xfs]
[322998.721003] [<c913f03e>] kmem_zone_alloc+0x46/0x8a [xfs]
[322998.721034] [<c9137a91>] xfs_trans_read_buf+0x3f/0x2ae [xfs]
[322998.721064] [<c02cb32a>] rwsem_down_failed_common+0x176/0x191
[322998.721076] [<c02cb35d>] rwsem_down_write_failed+0x18/0x1f
[322998.721083] [<c02cb3c6>] call_rwsem_down_write_failed+0x6/0x8
[322998.721094] [<c02ca856>] down_write+0x12/0x13
[322998.721100] [<c9145ee0>] xfs_write+0x184/0x70d [xfs]
[322998.721127] [<c01041ef>] device_not_available+0x23/0x28
[322998.721137] [<c0104471>] math_state_restore+0x60/0x70
[322998.721145] [<c9142f2a>] xfs_file_aio_write+0x52/0x59 [xfs]
[322998.721173] [<c016fbd2>] do_sync_write+0xbf/0x100
[322998.721188] [<c012eba0>] autoremove_wake_function+0x0/0x2d
[322998.721198] [<c0133104>] getnstimeofday+0x37/0xbc
[322998.721207] [<c013c828>] do_acct_process+0x5a5/0x5cd
[322998.721218] [<c0106151>] get_runstate_snapshot+0x69/0xec
[322998.721228] [<c011611c>] dequeue_entity+0x13/0x9b
[322998.721234] [<c011601c>] __dequeue_entity+0x1f/0x71
[322998.721242] [<c02ca00d>] schedule+0x631/0x6b1
[322998.721257] [<c013cd52>] acct_process+0x89/0xab
[322998.721264] [<c0121310>] do_exit+0x1f0/0x5f9
[322998.721272] [<c01217ad>] do_group_exit+0x94/0xbd
[322998.721282] [<c01292ad>] get_signal_to_deliver+0x3a0/0x3f0
[322998.721291] [<c010357c>] do_notify_resume+0x7e/0x696
[322998.721301] [<c010ea9e>] do_page_fault+0x604/0xb2e
[322998.721312] [<c010eb04>] do_page_fault+0x66a/0xb2e
[322998.721318] [<c01b7e07>] security_file_permission+0xc/0xd
[322998.721326] [<c016fc13>] do_sync_read+0x0/0xfe
[322998.721332] [<c017045a>] vfs_read+0x81/0x11e
[322998.721343] [<c01708ab>] sys_read+0x3c/0x63
[322998.721348] [<c01708ca>] sys_read+0x5b/0x63
[322998.721355] [<c0104055>] work_notifysig+0x13/0x1a
[322998.721363] =======================
--
Thanks,
Feri.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org