From owner-freebsd-current Tue May 21 7:29: 6 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 4798837B40A for ; Tue, 21 May 2002 07:28:56 -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 g4LEStvF019132 for ; Tue, 21 May 2002 07:28:55 -0700 (PDT) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.12.3/8.12.3/Submit) id g4LEStrB019131 for current@freebsd.org; Tue, 21 May 2002 07:28:55 -0700 (PDT) Date: Tue, 21 May 2002 07:28:55 -0700 (PDT) From: David Wolfskill Message-Id: <200205211428.g4LEStrB019131@bunrab.catwhisker.org> To: current@freebsd.org Subject: panic "mutex sockbuf rcv not owned at /usr/src/sys/fs/fifofs/fifo_vnops.c:229" 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 This occurred while doing the "make -j8 buildworld" for today's -CURRENT, running -CURRENT built yesterday: panic: mutex sockbuf rcv not owned at /usr/src/sys/fs/fifofs/fifo_vnops.c:229 cpuid = 0; lapic.id = 00000000 Debugger("panic") Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0 db> tr Debugger(c02eee7a) at Debugger+0x46 panic(c02ee068,c02f5253,c02e8b40,e5,d7c744b0) at panic+0xd1 _mtx_assert(da33dc04,1,c02e8b40,e5,d7c744b8) at _mtx_assert+0xa4 fifo_open(db1b7a80,db1b7a44,c0284389,db1b7a80,db1b7b2c) at fifo_open+0x216 fifo_vnoperate(db1b7a80,db1b7b2c,c01f106f,db1b7a80,80) at fifo_vnoperate+0x13 ufs_vnoperatefifo(db1b7a80) at ufs_vnoperatefifo+0x13 vn_open_cred(db1b7c10,db1b7b64,0,da976a80,db1b7cec) at vn_open_cred+0x345 vn_open(db1b7c10,db1b7b64,0,da531870,dbefec00) at vn_open+0x18 open(db0f3728,db1b7d14,3,16,287) at open+0x155 syscall(2f,2f,2f,8089be0,5) at syscall+0x230 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (5, FreeBSD ELF, open), eip = 0x28142a87, esp = 0xbfbfe39c, ebp = 0xbfbfe3c8 --- db> show pcpu 0 cpuid = 0 curthread = 0xdb0f3728: pid 86245 "screen" curpcb = 0xdb1b7da0 fpcurthread = none idlethread = 0xd6960a3c: pid 11 "idle: cpu0" currentldt = 0x28 spin locks held: db> show pcpu 1 cpuid = 1 curthread = 0xd6960d50: pid 10 "idle: cpu1" curpcb = 0xd696cda0 fpcurthread = none idlethread = 0xd6960d50: pid 10 "idle: cpu1" currentldt = 0x28 spin locks held: db> Now, the process had seemed to be running OK until I fired up "screen" again to see what was going on. Some explanation of why "screen" is involved: the machine in question is my "build machine;" it has no keyboard or monitor. I access it in 2 ways: via serial console from another machine (using tip), and via ssh. In practice, I access nearly all of the machines I work with from my laptop, and I track both -STABLE and -CURRENT daily, both on that same laptop and on the build machine. I first update the CVS repository on the build machine, then update the CVS repository on the laptop (from the one on the build machine), update the -STABLE /usr/src CVS working directory, build -STABLE on each machine, reboot to today's -STABLE, then do a "portupgrade -a" while I update the -CURRENT /usr/src CVS working directory, then reboot to -CURRENT to build today's -CURRENT. Usually, the build machine is faster than the laptop (both faster disk & more CPU horsepower), but the laptop is fast enough that I'm likely to need to reboot it before -CURRENT is built on the build machine. So I use "screen" to keep things going on the build machine even though I'm rebooting the laptop. (I also use "script" to record everything.) The version of "screen" in question was built under -CURRENT on 19 March; prior to that time, I had been using the version I had built under -STABLE (and which is a recipient of the daily "portupgrade -a" invocations); the lack of the "nl_langinfo" symbol in /usr/lib/compat/libc.so.4 prevents that, however. Finally, here's my recent CVSup history: freebeast(5.0-C)[1] tail /var/log/cvsup-history.log CVSup begin from cvsup14.freebsd.org at Fri May 17 03:47:03 PDT 2002 CVSup ended from cvsup14.freebsd.org at Fri May 17 03:55:30 PDT 2002 CVSup begin from cvsup14.freebsd.org at Sat May 18 03:47:03 PDT 2002 CVSup ended from cvsup14.freebsd.org at Sat May 18 03:54:42 PDT 2002 CVSup begin from cvsup14.freebsd.org at Sun May 19 03:47:03 PDT 2002 CVSup ended from cvsup14.freebsd.org at Sun May 19 03:54:02 PDT 2002 CVSup begin from cvsup14.freebsd.org at Mon May 20 03:47:03 PDT 2002 CVSup ended from cvsup14.freebsd.org at Mon May 20 03:53:54 PDT 2002 CVSup begin from cvsup14.freebsd.org at Tue May 21 03:47:03 PDT 2002 CVSup ended from cvsup14.freebsd.org at Tue May 21 03:54:36 PDT 2002 freebeast(5.0-C)[2] I've rebooted the build machine, and I'm about to re-start the -CURRENT build; if I get a recurrence, I'll look at it in more detail.... 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