From owner-freebsd-smp Sat Aug 30 08:31:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA22011 for smp-outgoing; Sat, 30 Aug 1997 08:31:04 -0700 (PDT) Received: from spinner.dialix.com.au (spinner.dialix.com.au [192.203.228.67]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA22006; Sat, 30 Aug 1997 08:30:57 -0700 (PDT) Received: from spinner.dialix.com.au (localhost.dialix.com.au [127.0.0.1]) by spinner.dialix.com.au with ESMTP id XAA07166; Sat, 30 Aug 1997 23:30:14 +0800 (WST) Message-Id: <199708301530.XAA07166@spinner.dialix.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Hajimu UMEMOTO cc: smp@csn.net, current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Fatal trap 12 during boot with -current In-reply-to: Your message of "Sat, 30 Aug 1997 15:10:31 +0900." <199708300610.PAA00256@peace.calm.imasy.or.jp> Date: Sat, 30 Aug 1997 23:30:14 +0800 From: Peter Wemm Sender: owner-freebsd-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hajimu UMEMOTO wrote: > Hi, > > >>>>> On Fri, 29 Aug 1997 16:21:32 -0600, > Steve Passe said: > > smp> > Starting final network daemons: moused > > It's my mistake. This is mountd, not moused. Sorry. > > smp> probably what kills it. is this an lkm? try booting without moused. > > I'm using LKM version of NFS. I'm sure all LKM modules was rebuild > by make world. I changed rc.conf to > > nfs_client_enable="NO" > nfs_server_enable="NO" > > due to disable NFS code, and reboot. But, I had same result. > > smp> is this repeatable? > > Yes, the kernel isn't boot at all. But, the kernel build at Aug 25 is > still bootable. > > smp> we need a 'trace' when it stops, and probably a 'show registers' > > db> show registers > cs 0x8 > ds 0xf0180010 _kmem_malloc+0x200 > es 0xff800010 _runtime > ss 0x10 > eax 0xeffd6d1c > ecx 0xeffd6d1c > edx 0xefc00000 _PTmap > ebx 0x927000 > esp 0xff803d00 _idlestack+0xd00 > ebp 0xff803d20 _idlestack+0xd20 > esi 0xf5b47000 > edi 0xf01eeddc _kernel_pmap_store > eip 0xf019eb23 _pmap_enter+0xb3 > efl 0x10282 > _pmap_enter+0xb3 movl 0(%ecx),%ecx > db> trace > _pmap_enter(f01eeddc,f5b47000,927000,7,1) at _pmap_enter+0xb3 > _vm_fault(f01f7720,f5b47000,1,0,0) at _vm_fault+0x1226 > _trap_pfault(ff803e54,0,f0542b60,f0540d00,ff803f0c) at _trap_pfault+0xf 0 > _trap(10,10,ff803f0c,f0540d00,ff803ee4) at _trap+0x31b > calltrap() at calltrap+0x35 > --- trap 0xc, eip = 0xf5b47920, esp = 0xff803e90, ebp = 0xff803ee4 --- > _end(f0542b00,f0542f80,f01ec920,0,ff803f0c) at 0xf5b47920 > _igmp_sendpkt(f053f940,16,0,f01da684,f01da754) at _igmp_sendpkt+0x15b > _igmp_fasttimo(0,f012c970,ff803fb4,f010dfd9,0) at _igmp_fasttimo+0x51 > _pffasttimo(0,c0000000,f08ff000,f08fe600,0) at _pffasttimo+0x21 > _softclock(80000000,f0190010,10,0,f08fe600) at _softclock+0x39 > doreti_swi() at doreti_swi+0x2a > db> Hmm.. Executing code after _end looks suspicously like another LKM. Do you have any other LKM's? I stronly suggect rm -f /lkm/* and see how you go. Just as a note, I see that your stack is: esp 0xff803d00 _idlestack+0xd00 ebp 0xff803d20 _idlestack+0xd20 It looks like you are getting killed from the software network interrupt handler on a cpu that was running the idle `process' when it was serviced. However, if you are not using an LKM, then the problem may be somewhere else and has caused an access to an invalid kernel address and caused the panic that way. Is the igmp reference an accident, or are you participating in multicast on the machine? (perhaps just routed/gated?) > -- > Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan > ume@imasy.or.jp ume@iabs.hitachi.co.jp > http://www.imasy.or.jp/~ume/ > Cheers, -Peter