NetBSD-Bugs archive

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

kern/41342: BSDi binaries cause panic

>Number:         41342
>Category:       kern
>Synopsis:       BSDi binaries cause panic
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun May 03 07:15:00 +0000 2009
>Originator:     Brian Marcotte
>Release:        NetBSD 5.0
NetBSD 5.0 NetBSD 5.0 (PANIX-XEN3U-WEB) #0: Tue Apr 28 20:29:19 
EDT 2009
BSDi binaries segfault or even panic the system on NetBSD 5.0.

Under Xen, the kernel will panic:
    fatal protection fault in supervisor mode
    trap type 4 code 0 eip c01001f0 cs 9 eflags 10286 cr2 7514 ilevel 0
    panic: trap
    Begin traceback...
    End traceback...

When I told it to drop to DDB so I could try to get a trace, I got this:
  Xosyscall(17,12af,bf7ff9f0,1f,0,0,0,0,d104ad90,d104a4f4) at netbsd:Xosyscall
  ?(1,bf7ffa80,bf7ffa88,bf7ffff0,0,0,1,bf7ffb00,0,bf7ffb0a) at 0x18e5
 at 0x1097

I've tracked this down to the commit described in this message:

which was done to fix PR 40143 (Viewing an mpeg transport stream with mplayer 
causes crash).

Grab a sample binary from

When NetBSD 5.0 is running on hardware, the binary will segfault. When
the system is a Xen domU, the kernel will panic. Under previous versions
of NetBSD, it works fine and will print "Must specify root index


Home | Main Index | Thread Index | Old Index