Date: Sun, 3 Dec 1995 04:54:20 +0800 (WST) From: Peter Wemm <peter@haywire.DIALix.COM> To: "Justin T. Gibbs" <gibbs@freefall.freebsd.org> Cc: freebsd-questions@freebsd.org Subject: Re: Help!!!! Message-ID: <Pine.SV4.3.91.951203043818.3346A-100000@haywire.DIALix.COM> In-Reply-To: <199512021722.JAA14480@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2 Dec 1995, Justin T. Gibbs wrote: > >Just by coincidence, the people that described their hardware were running > >EISA and 284X controllers. Guess what? There was a major EISA rewrite > >about the same time as John committed his benign Async changes.... > > Actually, I was able to reproduce it on a asystem with a 2940 before any of > my eisaconf/aic7xxx changes went into the tree (it was the last machine I > was to test my changes on before committing them). There was also a > report from someone with a Buslogic VLB card... From the two hangs I got > on my EISA machine (running my new eisaconf code) that I analized with DG, > the flags on the buffer that the system was sleeping on where in an > inconsistant state. Neither the eisaconf code nor the aic7xxx code munge > buffers on a personal level, so I don't know how they could cause this type > of problem. Anything is possible though. :) I'm sorry.. I didn't mean to point the finger at your code either.. I was trying to point out that there were a lot of other things happening about the same time as John's "extreme async" changes. Actually, I think I was the one with the Buslogic VLB card. I remember mentioning it in the discussion. I've not had getblk hangs. We have other machines with 1542CF and CP controllers that are panicing and/or doing a silent reboot (clearing the dmesg buffer and no crash dump). One of them was caught with an "invalid page directory", the other one was something corrupt in the pmap system when the machine was idle and cron forked, I was on the phone to the person and it went right in front of him. All of these are boring old 486 boxes.. Hmm.. This thread is getting way off topic.. The original problem in this thread was that the user's machine was trashing it's root and /usr filesystem. Unfortunately, he didn't supply any version or configuration information. At the risk of doing what I flamed Terry for, I'll mention that it vaguely reminds me of some interaction with msdosfs.. I hope this will jog somebody's memory to see if the symptoms match... > I haven't seen a getblk hang on my machine for more than a week now. > Perhaps the problem has been inadvertantly fixed??? The best kind of bug... the one that keeps you guessing.. :-/ -Peter > >-Peter > -- > Justin T. Gibbs > =========================================== > FreeBSD: Turning PCs into workstations > =========================================== >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SV4.3.91.951203043818.3346A-100000>