[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] BUG: soft lockup detected on CPU#0!
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_lvlThat 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 syslogApr 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 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |