|
|
|
|
|
|
|
|
|
|
xen-users
RE: [Xen-users] Domain Crash and Xend can't restart
Seems like something you should put into bugzilla.
"sleeping function called from ..." is definitely broken code - it means
that someone tried to make the current thread go to sleep when in an a
mode where you can't go to sleep (Not a good idea to sleep the kernel
when interrupts are disabled).
--
Mats
> -----Original Message-----
> From: Mike Lemoine [mailto:mlemoine@xxxxxxxxxxx]
> Sent: 27 October 2006 18:13
> To: Petersson, Mats; Xen-users
> Subject: Re: [Xen-users] Domain Crash and Xend can't restart
>
> Happened again. While the problem VM is useless, connecting
> to the console
> of an idle VM I had on the machine (for exactly this purpose)
> had this in
> the buffer:
>
> BUG: sleeping function called from invalid context at
> kernel/workqueue.c:270
> in_atomic():0, irqs_disabled():1
>
> Call Trace: <ffffffff80294742>{flush_workqueue+26}
> <ffffffff80370914>{blkif_free+67}
> <ffffffff80371135>{blkfront_resume+37}
> <ffffffff8036d62c>{xenbus_exists+33}
> <ffffffff8029767d>{keventd_create_kthread+0}
> <ffffffff8036e724>{resume_dev+88}
> <ffffffff8036a265>{__do_suspend+0}
> <ffffffff8036e6cc>{resume_dev+0}
> <ffffffff80363f23>{bus_for_each_dev+67}
> <ffffffff8036a265>{__do_suspend+0}
> <ffffffff8036e63e>{xenbus_resume+37}
> <ffffffff8036a7ce>{__do_suspend+1385}
> <ffffffff80282af9>{__wake_up_common+62}
> <ffffffff8029767d>{keventd_create_kthread+0}
> <ffffffff8029767d>{keventd_create_kthread+0}
> <ffffffff80237f3f>{kthread+212}
> <ffffffff8026721a>{child_rip+8}
> <ffffffff8029767d>{keventd_create_kthread+0}
> <ffffffff80237e6b>{kthread+0} <ffffffff80267212>{child_rip+0}
>
>
>
> On 10/26/06 10:37 AM, "Petersson, Mats"
> <Mats.Petersson@xxxxxxx> wrote:
>
> >
> >
> >> -----Original Message-----
> >> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> >> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> >> Mike Lemoine
> >> Sent: 26 October 2006 17:16
> >> To: Xen-users
> >> Subject: [Xen-users] Domain Crash and Xend can't restart
> >>
> >> I have a single VM (of 11) that has a recurring problem.
> >> This image has
> >> moved from machine to machine, with the problem following it.
> >> This image
> >> has been rebuilt from scratch, and the problem recurred. It
> >> would appear
> >> that there is something in the behaviour of this VM which
> >> causes it to crash
> >> and causes Xend to become unhappy.
> >
> > Do you have a log from an attempt to boot it once it's been
> "broken"? I
> > think that would be useful.
> >
> > I would also suggest that you try the latest stable Xen
> (3.0.3), because
> > there has been quite a few changes since August...
> >
> > [Snip logs etc]
> >
> > --
> > Mats
> >
> >
>
>
>
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|