Port-xen archive

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

Re: NetBSD domU + pygrub = panic



On Fri, Oct 22, 2010 at 02:23:32PM +0100, Hugo Silva wrote:
> Hello,
> 
> While trying to setup a netbsd domU with pygrub, I noticed that my
> 5.99.39/amd64 machine immediately panics. This happens every time.
> 


 
> Manual copy of the panic follows:
> 
> 0 rsp ffffa000498a3760
> Stopped in pid 296.1 (python 2.6) at netbsd:breakpoint+0x5: leave
> breakpoint() at netbsd:breakpoint+0x5
> panic() at netbsd:panic+0x28f
> kern_assert() at netbsd:kern_assert+0x2d
> wapbl_add_buf() at netbsd:wapbl_add_buf+0x36
> bdwrite() at netbsd:bdwrite+0xc2
> ffs_update() at netbsd:ffs_update+0x1d1
> ffs_full_fsync() at netbsd:ffs_full_fsync+0x38f
> ffs_fsync() at netbsd:ffs_fsync+0x4b
> VOP_FSYNC() at netbsd:VOP_FSYNC+0x34
> vinvalbuf() at netbsd:vinvalbuf+0xee
> spec_close() at netbsd:spec_close+0x80
> VOP_CLOSE() at netbsd:VOP_COSE+0x29
> vn_close() at netbsd:vn_close+0x4b
> closef() at netbsd:closef+0x6a
> fd_close() at netbsd:fd_close+0x211
> syscall() at netbsd:syscall+0x92
> 

> If it matters, the domU storage runs on lvm on top of a raid-1 (raidframe).
> 
> Should it be necessary, I can retrigger the panic with a proper
> keyboard at a later date.
> 
> Please advise.

This seems somewhat like kern/41189. Try not mounting /dev with -o log.

        Jonathan Kollasch


Home | Main Index | Thread Index | Old Index