From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Christopher S. Aker" Subject: Re: BUG: soft lockup detected on CPU#0! Date: Wed, 05 Apr 2006 13:32:29 -0500 Message-ID: <44340D3D.8060903@theshore.net> References: <44332DC7.3040707@theshore.net> <19373d679e65ffe279bbb2bb4fd94700@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <19373d679e65ffe279bbb2bb4fd94700@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel List-Id: xen-devel@lists.xenproject.org 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