Re: port-xen/46057: NetBSD/Xen DOM-U crash

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Mon, Feb 20, 2012 at 07:55:00AM +0000, dieter.NetBSD%pandora.be@localhost 
wrote:
> >Number:         46057
> >Category:       port-xen
> >Synopsis:       NetBSD/Xen DOM-U crash
> >Confidential:   no
> >Severity:       serious
> >Priority:       medium
> >Responsible:    port-xen-maintainer
> >State:          open
> >Class:          sw-bug
> >Submitter-Id:   net
> >Arrival-Date:   Mon Feb 20 07:55:00 +0000 2012
> >Originator:     dieter roelants
> >Release:        6.0_BETA
> >Organization:
> >Environment:
> NetBSD netbsd-u2.inflamm 6.0_BETA NetBSD 6.0_BETA (SIMULT.domu) #15: Sat Feb 
> 18 19:16:16 CET 2012  
> dieter@netbsd-u2.inflamm:/build/obj/sys/arch/amd64/compile/SIMULT.domu amd64
> >Description:
> 
> I had a Xen guest crash like this:
> 
> uvm_fault(0xffffa000034dea50, 0x0, 1) -> e
> fatal page fault in supervisor mode
> trap type 6 code 0 rip ffffffff801d0c8e cs e030 rflags 10246 cr2  0 cpl 0 rsp 
> ffffa00044d078f0
> kernel: page fault trap, code=0
> Stopped in pid 383.1 (tmux) at  netbsd:sysctl_doeproc+0xd63:    movq    
> 0(%rax),
> %rdx
> sysctl_doeproc() at netbsd:sysctl_doeproc+0xd63
> sysctl_dispatch() at netbsd:sysctl_dispatch+0xb2
> sys___sysctl() at netbsd:sys___sysctl+0xeb
> syscall() at netbsd:syscall+0xc4

Why do you think this is Xen-specific ?

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--