Subject: Re: panic during chrooted build of emulators/peace
To: Jaromir Dolecek <jdolecek@netbsd.org>
From: Andreas Wrede <andreas@planix.com>
List: port-i386
Date: 08/31/2002 16:36:20
On Sat, 31 Aug 2002, Jaromir Dolecek wrote:

> What is /netbsd is chrooted environ? 1.5 kernel?

No.  -current from Aug 25th sources. It's a copy of the running
kernel.

> Andreas Wrede wrote:
> > I get a reproducable panic when building pkgsrc/emulators/peace via
> > the bulk build scripts in a chrooted environment. It looks like
> > /sbin/modload, which is called during the package install, is the
> > cause.
> >
> > Also, for some reason I cannot get a dump: dump device not ready, see
> > below.
> >
> > What can I do to help debug this?
> >
> >
> > uname -a
> > NetBSD woffi.planix.com 1.6F NetBSD 1.6F (PLANIX) #0: Sun Aug 25 17:54:35 EDT 2002     root@woffi.planix.com:/m5/netbsd-current/src/sys/arch/i386/compile/WOFFI i386
> >
> >
> > Console log:
> > uvm_fault(0xe51e0c90, 0x0, 0, 1) -> e
> > fatal page fault in supervisor mode
> > trap type 6 code 0 eip c02246a3 cs 8 eflags 10283 cr2 11 cpl 0
> > panic: trap
> > Begin traceback...
> > trap() at trap+0x206
> > --- trap (number 6) ---
> > _lkm_exec(c0493f40,1,1,c024a92b,e44b5dc4) at _lkm_exec+0x4b
> > lkmioctl(1c00,80044b03,e44b5ec0,3,e53d64e8) at lkmioctl+0x33b
> > spec_ioctl(e44b5dc4,0,e44b5de0,c01ebe0b,e3b8b068) at spec_ioctl+0x49
> > VOP_IOCTL(e46e4d10,80044b03,e44b5ec0,3,c11a7100) at VOP_IOCTL+0x49
> > vn_ioctl(e3b8b068,80044b03,e44b5ec0,e53d64e8,e44b5f80) at vn_ioctl+0xb1
> > sys_ioctl(e53d64e8,e44b5f80,e44b5f78,c03052ac) at sys_ioctl+0x325
> > syscall_plain(1f,1f,1f,1f,bfbfd693) at syscall_plain+0xa7
> > End traceback...
> > syncing disks... 40 40 40 40 40 40 39 39 39 39 39 39 39 39 39 39 39 38 38 38 38 38 giving up
> >
> > dumping to dev 0,1 offset 263047
> > dump panic: wddump: polled command has been queued
> > Begin traceback...
> > wddump(1,40387,e44b59a0,200,140000) at wddump+0x1f9
> > cpu_dump(100,c042dcbb,100,281e1203,40) at cpu_dump+0xcd
> > dumpsys(e44b5c3c,1,fff8,c0414bc9,c02341cc) at dumpsys+0x101
> > cpu_reboot(100,0,e44b5c80,c0304fce,0) at cpu_reboot+0x63
> > panic(c042dcbb,c042dc5b,e44b5c88,1,1) at panic+0x123
> > trap() at trap+0x206
> > --- trap (number 6) ---
> > _lkm_exec(c0493f40,1,1,c024a92b,e44b5dc4) at _lkm_exec+0x4b
> > lkmioctl(1c00,80044b03,e44b5ec0,3,e53d64e8) at lkmioctl+0x33b
> > spec_ioctl(e44b5dc4,0,e44b5de0,c01ebe0b,e3b8b068) at spec_ioctl+0x49
> > VOP_IOCTL(e46e4d10,80044b03,e44b5ec0,3,c11a7100) at VOP_IOCTL+0x49
> > vn_ioctl(e3b8b068,80044b03,e44b5ec0,e53d64e8,e44b5f80) at vn_ioctl+0xb1
> > sys_ioctl(e53d64e8,e44b5f80,e44b5f78,c03052ac) at sys_ioctl+0x325
> > syscall_plain(1f,1f,1f,1f,bfbfd693) at syscall_plain+0xa7
> > End traceback...
> >
> > dumping to dev 0,1 offset 263047
> > dump device not ready
> >
> >
> > wd1: flush cache command didn't complete
> > wd0: flush cache command didn't complete
> > rebooting...
> >
> >  --
> >     - aew
> >
>
>
>

-- 
    - aew