Return to BSD News archive
From: Jordan Klein <haplo @ ibm . net> Subject: FreeBSD 3.0-current panics on reboot Newsgroups: comp.unix.bsd.freebsd.misc Lines: 35 X-Newsreader: TIN [UNIX 1.3 unoff BETA 970309; i386 FreeBSD 3.0-CURRENT] Message-ID: <333b1bce.0@dilbert.ibm.net> Date: 28 Mar 97 01:15:58 GMT NNTP-Posting-Host: slip129-37-233-99.mi.us.ibm.net Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!ais.net!news.stealth.net!newsfeed.de.ibm.net!ibm.net!news-m01.ny.us.ibm.net!news.ibm.net!news-beta01.advantis.com!dilbert.ibm.net!slip129-37-233-99.mi.us.ibm.net!haplo Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37840 Here's an interesting one. I've been following the 3.0 current tree for a bit and now, when I go to reboot my machine using shutdown, reboot, or halt, it starts the shutdown process, kills most of my programs (maybe all, kinda hard to tell), and panics at the end. The panics have been: panic lockmgr: pid 263 not exclusive lock holder 1 unlocking (pid differs depending on how long it's been running) and: panic: unmount: dangling vnode This has caused me some anxiety, as it doesn't cleanly shut down the file systems when this happens. The panics occur every time I go to reboot. The wierd thing is that if I reboot via ctrl-alt-del, it doesn't panic. I've talked to others running the same level of 3.0 code that I'm running, on similar hardware, and they've not experienced this. My hardware: DFI G586IPC system board intel triton iii chipset cyrix 6x86 p166+ cpu 512kb L2 cache 64mb non-parity 60ns ram adaptec aha2940W pci scsi controller 3com 3c595 pci 10/100 ethernet card genoa phantom 64v-2001 s3 trio64+ pci video card w/2mb vram sb16 value edition (not pnp) Any insight on this would be greatly appreciated. -- Jordan Klein Advantis - Internet Server Support jklein @ theramp . net haplo @ ibm . net http://www.theramp.net/jklein http://www.ibm.net Spam me and die Remove spaces from email addr to reply