From owner-freebsd-current Tue May 21 8: 5:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 549CC37B400 for ; Tue, 21 May 2002 08:05:25 -0700 (PDT) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) by bunrab.catwhisker.org (8.12.3/8.12.3) with ESMTP id g4LF5OvF019312; Tue, 21 May 2002 08:05:25 -0700 (PDT) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.12.3/8.12.3/Submit) id g4LF5O7b019311; Tue, 21 May 2002 08:05:24 -0700 (PDT) Date: Tue, 21 May 2002 08:05:24 -0700 (PDT) From: David Wolfskill Message-Id: <200205211505.g4LF5O7b019311@bunrab.catwhisker.org> To: current@FreeBSD.ORG, david@catwhisker.org Subject: Re: panic "mutex sockbuf rcv not owned at /usr/src/sys/fs/fifofs/fifo_vnops.c:229" In-Reply-To: <200205211428.g4LEStrB019131@bunrab.catwhisker.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG OK; after restart, I got a slightly different panic. The laptop is still cranking along, and has nearly finished the "make -j4 buildworld" without incident (so far), but the build machine (which is SMP -- 2x866 PIII) has died again during the ">>> stage 4: building libraries" step: lock order reversal 1st 0xc032e820 sched lock (sched lock) @ /usr/src/sys/kern/kern_synch.c:839 2nd 0xc039db60 sio (sio) @ /usr/src/sys/dev/sio/sio.c:3186 Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 01000000 fault virtual address = 0x79 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01af409 stack pointer = 0x10:0xd7b71cc0 frame pointer = 0x10:0xd7b71cdc code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 13 (swi6: tty:sio clock) kernel: type 12 trap, code=0 Stopped at schedcpu+0x12b: cmpb $0x9f,0x79(%ebx) db> show pcpu 0 cpuid = 0 curthread = 0xdb30e100: pid 40054 "sh" curpcb = 0xdb1bada0 fpcurthread = none idlethread = 0xd6960a3c: pid 11 "idle: cpu0" currentldt = 0x28 spin locks held: db> show pcpu 1 cpuid = 1 curthread = 0xd6960414: pid 13 "swi6: tty:sio clock" curpcb = 0xd7b71da0 fpcurthread = none idlethread = 0xd6960d50: pid 10 "idle: cpu1" currentldt = 0x28 spin locks held: exclusive spin mutex sched lock r = 0 (0xc032e820) locked @ /usr/src/sys/kern/kern_synch.c:839 db> tr schedcpu(0) at schedcpu+0x12b softclock(0) at softclock+0x14e ithread_loop(ce513700,d7b71d48,d6960414,c019cfd0,0) at ithread_loop+0x11c fork_exit(c019cfd0,ce513700,d7b71d48) at fork_exit+0x8a fork_trampoline() at fork_trampoline+0x37 db> show locks shared sx allproc r = 0 (0xc032ee00) locked @ /usr/src/sys/kern/kern_synch.c:267 exclusive spin mutex sched lock r = 0 (0xc032e820) locked @ /usr/src/sys/kern/kern_synch.c:839 db> I'm not seeing an overwhelming degree of commonality between the two panics so far.... Cheers, david -- David H. Wolfskill david@catwhisker.org Trying to support or use Microsoft products makes about as much sense as painting a house with watercolors. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message