From: "Christopher S. Aker" <caker@theshore.net>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: BUG: soft lockup detected on CPU#0!
Date: Wed, 05 Apr 2006 13:32:29 -0500 [thread overview]
Message-ID: <44340D3D.8060903@theshore.net> (raw)
In-Reply-To: <19373d679e65ffe279bbb2bb4fd94700@cl.cam.ac.uk>
Keir Fraser wrote:
> Since it looks like a problem with the blkback kernel thread, it's worth
> doing:
> echo 1 >/sys/module/blkback/parameters/debug_lvl
>
> That may get some kernel tracing (at level KERN_DEBUG) from that thread
> and we can see if it's got into a bad looping state.
After an update and a reboot, and turning off soft lockup detection, I'm
still getting zombie domains. It also appears that after this happens,
no new block devices can be attached.
Here's a summary of the different debug outputs:
(after restarting Xend)
==> /var/log/xend.log <==
[2006-04-05 14:29:09 xend] DEBUG (XendDomain:197) Cannot recreate
information for dying domain 54. Xend will ignore this domain from now on.
[2006-04-05 14:29:09 xend] DEBUG (XendDomain:197) Cannot recreate
information for dying domain 73. Xend will ignore this domain from now on.
Apr 5 14:28:40 host56 kernel: xvd 73 fd:85: I/O pending, delaying exit
Apr 5 14:28:40 host56 kernel: xvd 73 fd:85: not connected (13 pending)
Apr 5 14:28:40 host56 kernel: xvd 73 fd:85: I/O pending, delaying exit
Apr 5 14:28:40 host56 kernel: xvd 73 fd:85: not connected (13 pending)
^-- these flood syslog
Apr 5 14:28:40 host56 kernel: ined (13 pe, delayed (13 pe, delayined
(13 , delayed (13 , delayied (13 , delayined (13 , delayed (13 pend,
delayed (13 , delayined (13 pe, delayined (13 pe, delayined (13 ,
delayed (13 pe, delayed (13 , delayined (13 , delayed (13 pendin,
delayined (13 p, delayined (13 pen, delayed (13 pe, delayined (13 ,
delayied (13 pe, delayed (13 , delayined (13 , delayed (13 pendin,
delayined (13 , delayined (13 pe, delayed (13 pe, delayined (13 ,
delayed (13 pe, delayed (13 , delayined (13 pe, delayined (13 pendin,
delayined (13 pe, delaying ed (13 pe, delayined (13 pe, delayined (13
pe, delayed (13 pe, delayed (13 , delayin, delayined (13 pending,
delayined (13 , delaying ed (13 pe, delayed (13 pe, delayined (13 ,
delayed (13 pe, delayed (13 , delayined (13 pe, delayed (13 pendin,
delayined (13 , delayined (13 pe, delayed (13 pe, delayined (13 ,
delayed (13 pe, delayed (13 , delayined (13 , delayied (13 pendin,
delayined (13 , delayined (13 pe, delayined (13 pe, delayed (13 pe,
delayed (13
Apr 5 14:28:40 host56 kernel: elayined (13 , delayed (13 pendin,
delayined (13 , delayined (13 pe, delayed (13 pe, delayined (13 pe,
delayed (13 pe, delayed (13 p, delayined (13 , delayed (13 pendin,
delayined (13 , delayined (13 pe, delayed (13 pe, delayined (13 ,
delayed (13 p, delayed (13 pe, delayined (13 pe, delayined (13 pend,
delayined (13 , delaying ed (13 peed (13 , delayined (13 , delayined (13
pe, delayed (13 pe, delayined (13 p, delayined (13 pend, delayined (13 ,
delayined (13 pe, delayined (13 pe, de, delayined (13 pe, delayed (13 ,
delayined (13 , delayed (13 pendin, delayined (13 , delayined (13 pen,
delayed (13 pe, delayined (13 , delayed (13 pe, delayed (13 , delayined
(13 , delayed (13 pendin, delayined (13 , delayined (13 pe, delayined
(13 pe, delayined (13 , delayed (13 pe, delayed (13 , delayined (13 ,
delayed (13 pendin, delayined (13 , delayined (13 pe, delayed (13 pe,
delayined (13 , delayined (13 pe, delayed (13 , delayined (13 p, delayed
(13 pend, delayed (13 , delayined (13 pe, dela
^-- these are flooding, but not quite as often.
This leaves Xen/Xend in an unstable condition, I'm thinking the only way
out is a reboot...
-Chris
next prev parent reply other threads:[~2006-04-05 18:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 2:39 BUG: soft lockup detected on CPU#0! Christopher S. Aker
2006-04-05 2:45 ` Itamar Reis Peixoto
2006-04-05 10:16 ` Keir Fraser
2006-04-05 18:32 ` Christopher S. Aker [this message]
2006-04-06 6:56 ` Keir Fraser
2006-04-06 9:23 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2010-08-02 22:54 Luke S Crawford
2007-09-10 2:14 Abhinav Srivastava
2007-07-25 19:41 Christoph Pfister
2007-07-27 19:30 ` Michal Piotrowski
2007-07-27 20:04 ` Christoph Pfister
2007-08-07 8:49 ` Christoph Pfister
2007-07-14 11:19 CIJOML
2007-06-19 14:34 Hannes Dorbath
2007-06-20 3:29 ` David Chinner
2007-05-09 12:41 Ralf Hildebrandt
2006-06-06 13:06 robee
2006-06-02 1:02 Marc Koschewski
2006-06-02 1:04 ` Marc Koschewski
2006-06-02 1:54 ` Andrew Morton
2006-05-11 17:33 Linux 2.6.16.16 Chris Wright
2006-05-11 18:03 ` BUG: soft lockup detected on CPU#0! Winn Johnston
2006-05-12 15:51 ` Winn Johnston
2006-03-05 12:26 Norbert Wegener
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44340D3D.8060903@theshore.net \
--to=caker@theshore.net \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.