From owner-freebsd-current Mon Aug 20 12:13:42 2001 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 58C5E37B40B for ; Mon, 20 Aug 2001 12:13:28 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.4/8.11.4) id f7KJDSJ03413 for current@freebsd.org; Mon, 20 Aug 2001 12:13:28 -0700 (PDT) Date: Mon, 20 Aug 2001 12:13:28 -0700 (PDT) From: David Wolfskill Message-Id: <200108201913.f7KJDSJ03413@bunrab.catwhisker.org> To: current@freebsd.org Subject: Panic (I think(!)) in today's -CURRENT 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 Just finished building & installing today's -CURRENT on my laptop. (I had already built it on another machine, and it seemed to come UP OK on it.) I had built -CURRENT yesterday, but I was at the BayLISA picnic at the time, so I didn't try using the Cisco/Aironet card. (I had checked for signals earlier, and decided that the probability of anything down in that dip was low enough that is wasn't worth bothering with.) Booting yesterday's kernel (with the an card inserted), I got partway through the "make buildworld" when the system seemed to stop. I was in an X environment at the time, so it's possible that there was a panic or some such thing. However, the machine did respond (in a way) to Ctl+Alt+F2 -- it blanked the screen. Nothing I did caused the screen to display a normal "console" or a normal X environment. Eventually, I tried suspend/resume, and the screen showed a very bizarre pattern, as if it was using something way off somewhere as video RAM. After a power cycle, single-user boot, manual "fsck -p", and re-boot, I was able to bulid today's -CURRENT (in an X environment) without further incident. So I installed it & re-booted, inserting the an card after the "Phoenix BIOS" splash screen displayed. I saw the usual start-up messages, including the messages & chirps indicating that the an card had been recognized. But when xdm came up, I expected the login screen to identify the machine with a name derived from a gethostbyaddr() performed against the IP address assigned by the DHCP server. (I have some code in /etc/dhclient-exit-hooks to do this; I has worked for a couple of months, at least.) So I ejected the an card, saw the messages & heard the chirps indicating that the card was recognized as having been ejected. I then re-inserted it, saw the messages & heard the chirps showing that the card was seen. And I saw the message indicating that a new hostname had been determined. (I was doing a "tail -f /var/log/messages" at the time.) I hit ^C on the "tail -f" mentioned above, and the display switched from vty1 to vty0: login: kernel: type 12 trap, code=0 Stopped at witness_destroy+0x237: cmpl %esi,0xc{%edx) db> trace witness_destroy(d9373fdc,d9373fdc,d9409f40,c01a33b3,d9373fdc) at witness_destroy+0x237 mtx_destroy(d9373fdc,d9373ec0,d937221c,d9372100,4) at mtx_destroy+0x73 wait1(d9372100,d9409f80,0,d9409fa0,c02ffa0d) at wait1+0x897 wait4(d9372100,d9409f80,bfbfb8dc,2,2) at wait4+0x10 syscall(2f,2f,2f,2,2) at syscall+0x5ed syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (7, FreeBSD ELF, wait4), eip - 0x808e31c, esp=0xbfbfb664, ebp = 0xbfbfb680 --- But the *wierd* thing is that I can still bounce among different vtys. Recent CVSup history: CVSup begin from cvsup14.freebsd.org at Thu Aug 16 03:47:01 PDT 2001 CVSup ended from cvsup14.freebsd.org at Thu Aug 16 04:06:40 PDT 2001 CVSup begin from cvsup14.freebsd.org at Fri Aug 17 03:47:01 PDT 2001 CVSup ended from cvsup14.freebsd.org at Fri Aug 17 16:57:21 PDT 2001 (*) CVSup begin from cvsup14.freebsd.org at Sat Aug 18 03:47:01 PDT 2001 CVSup ended from cvsup14.freebsd.org at Sat Aug 18 04:48:54 PDT 2001 CVSup begin from cvsup14.freebsd.org at Sun Aug 19 03:47:01 PDT 2001 CVSup ended from cvsup14.freebsd.org at Sun Aug 19 04:05:30 PDT 2001 CVSup begin from cvsup14.freebsd.org at Mon Aug 20 03:47:01 PDT 2001 CVSup ended from cvsup14.freebsd.org at Mon Aug 20 04:01:59 PDT 2001 (*) I had been having trouble with the Pac*Bell DSL conection. I *think* that's resolved now.) What (else) would be helpful for diagnosing this? Thanks, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message