Date: Tue, 10 Oct 1995 22:14:00 -0400 From: Gene Stark <gene@starkhome.cs.sunysb.edu> To: clinet.fi!hsu@sbstark.cs.sunysb.edu Cc: freebsd.org!bugs@sbstark.cs.sunysb.edu Subject: Re: kern/772: Stable panic Message-ID: <199510110214.WAA04016@starkhome.cs.sunysb.edu> In-Reply-To: <199510110158.DAA03824@katiska.clinet.fi> (message from Heikki Suonsivu on Wed, 11 Oct 1995 03:58:27 %2B0200)
next in thread | previous in thread | raw e-mail | index | archive | help
> > This appears to be the same crash as #744 (which didn't get mailed > > to the list, for some reason). I had a crash dump for this, if > > anyone is interested. I hope I still have the symbols for that kernel... > >We also got this exactly the same situation (page fault in kernel and then >IO lockup when trying to dump) on a 486-40 with IDE disks, so it is very >high probability of software problem, not a hardware one. This is very >annoying as the systems get stuck, they don't reboot automatically. The "crash in chflags" problem that I observed occurred with slirp as the current process. The system didn't get stuck, it just rebooted automatically. I did some tracing on the crash dump, reported what I found in bug report #744. I only had an hour or two to spend on it, and I concluded that the problem was caused by something in the vnode cache/pool code. Since I have not studied this code, I decided my likelihood of finding this bug quickly was small, and that David Greenman or John Dyson could make more efficient use of the dump information. I don't know if they actually ever saw bug report #744, as at least I didn't get it mailed back to me via the bugs list. - Gene Stark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510110214.WAA04016>