Date: Sun, 29 Aug 2004 17:06:08 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: Kachun Lee <kachun@pathlink.com> Cc: freebsd-current@freebsd.org Subject: Re: 5.3-BETA1 panic with getnewbuf: locked buf Message-ID: <20040829170534.V69068@carver.gumbysoft.com> In-Reply-To: <5.0.2.1.2.20040826181101.00b933a0@dvl.pathlink.com> References: <5.0.2.1.2.20040826181101.00b933a0@dvl.pathlink.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 26 Aug 2004, Kachun Lee wrote: > >The server (E7501 single XEON 4G RAM) that I upgraded from 4.10 to > 5.3-BETA few days >ago panic'ed twice on 'getnewbuf: locked buf'. I > included the backtrace and dmesg below. I >searched the lists and found > several similar instances mentioned. Anything I can help to >find the > problem. Thanks in advance for any help. > > I forget to mention that I already rebuilt its kernel with 1.75 kern_lock.c > (from current). 1.75 should fix this problem. If it didn't, make sure you're booting the right kernel and run a full fsck. There is another attempt in rev 1.76 you might try too. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040829170534.V69068>