Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: current dom0 panic on domu launch

On 16/10/2009 10:34 AM, Sarton O'Brien wrote:
On 15/10/2009 5:54 AM, Manuel Bouyer wrote:
On Mon, Oct 05, 2009 at 10:43:42PM +1100, Sarton O'Brien wrote:
# uvm_fault(0xffffffff80c2da00, 0x0, 1) -> e
fatal page fault in supervisor mode
trap type 6 code 0 rip ffffffff805651f3 cs e030 rflags 10246 cr2 0 cpl
0 rsp ff
kernel: page fault trap, code=0
Stopped in pid 0.43 (system) at netbsd:sdioctl+0x506: movl 0(%rcx),%r8d
sdioctl() at netbsd:sdioctl+0x506
VOP_IOCTL() at netbsd:VOP_IOCTL+0x31
xbdback_do_io() at netbsd:xbdback_do_io+0xd2
workqueue_worker() at netbsd:workqueue_worker+0x81

Could you see if xbdback_xenbus.c 1.26 fixes your issue ?

Sorry for the delay. This being the latest email I'll give this a shot
asap and report back. Thanks both of you for giving it some attention,
greatly appreciated.

Seems to working and stable again (updated Mon Oct 19 21:00:37 EST 2009), however there seems to be a problem I've had before (regression?).

When shutting down a domU, xm list shows that it has been removed but the vnd is still tied up. Issuing 'vnconfig -u vnd2' says device busy. Issuing 'vnconfig -uF vnd2' succeeds but then I'm still unable to relaunch the domU, an error mentions unable to detach xvif but not much else.

If there is further information I can provide please let me know. In the meantime I'm updating xentools, python and expat to see if that helps.


Home | Main Index | Thread Index | Old Index