This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Problem with debian lenny domu.

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Problem with debian lenny domu.
From: John McMonagle <johnm@xxxxxxxxxxx>
Date: Mon, 15 Nov 2010 16:26:54 -0600
Delivery-date: Mon, 15 Nov 2010 14:29:39 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Advocap Inc
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.10 (enterprise35 20100122.1078643)
Have a problem with kernel errors on a debian lenny xen system.

Both Dom0 and domu have 2.6.26-2-xen-686 kernel

it's a Dell Poweredge 1600sc.

Dom0 and another domu have no errors

It can run fine for days and at some point will get messages like this about 
ever 2 minutes.

[99893.452427] INFO: task cron:11193 blocked for more than 120 seconds.
[99893.452461] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[99893.452481] cron          D 8c6c25a5     0 11193   2360
[99893.452506]        eb8c65e0 00000282 00000001 8c6c25a5 0000315c eb8c6768 
c127ab40 00000001
[99893.452554]        ec93fd80 00000000 00000000 0002c54b 00000000 00000005 
000873e5 00000000
[99893.452597]        c1276060 e4318092 c0106149 c0e67f14 e4318092 0002dfb7 
7fffffff 7fffffff
[99893.452647] Call Trace:
[99893.452686]  [<c0106149>] get_runstate_snapshot+0x69/0xec
[99893.452734]  [<c02caf77>] schedule_timeout+0x13/0x86
[99893.452771]  [<c02ca62a>] wait_for_common+0xd9/0x166
[99893.452801]  [<c0117957>] default_wake_function+0x0/0x8
[99893.452840]  [<c011dcaa>] do_fork+0x17f/0x1dc
[99893.452873]  [<c010239e>] sys_vfork+0x18/0x1c
[99893.452900]  [<c0103f76>] syscall_call+0x7/0xb
[99893.452938]  =======================

Load is 1 but looks idle.
top - 15:52:11 up 1 day,  3:55,  1 user,  load average: 1.00, 1.00, 1.00
Tasks: 124 total,   1 running, 122 sleeping,   0 stopped,   1 zombie
Cpu(s):  0.0%us,  0.0%sy,  0.0%ni,100.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   2097348k total,  1212396k used,   884952k free,     9596k buffers
Swap:  2097144k total,        0k used,  2097144k free,   649000k cached

The only way I have been able to get the load back down is to reboot the domu.

I thought I had it licked as it has sometime worked for over 5 days with no 
errors so I have installed it in a  remote office so at this point rather not 
do any major changes.

Any Ideas?


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Problem with debian lenny domu., John McMonagle <=