Date: Fri, 14 Dec 2001 13:17:18 +0100 From: Stijn Hoop <stijn@win.tue.nl> To: Bruce Montague <brucem@cse.iitkgp.ernet.in> Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: sound/pci/ich drvr hang on Dell OptiPlex 150 Message-ID: <20011214131718.B97466@pcwin002.win.tue.nl> In-Reply-To: <200112140645.fBE6jsm06509@cse.iitkgp.ernet.in>; from brucem@cse.iitkgp.ernet.in on Fri, Dec 14, 2001 at 12:15:54PM %2B0530 References: <200112140645.fBE6jsm06509@cse.iitkgp.ernet.in>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Fri, Dec 14, 2001 at 12:15:54PM +0530, Bruce Montague wrote: > Two solid problems occur with the sound/pci/ich > driver for the ICH2 (Intel 82801BA I/O Controller > Hub) on Dell Optiplex 150 PCs. One problem > (a fatal hang) occurs under 4.4-RELEASE, > 4.4-STABLE, and 5.0-CURRENT (as of yesterday). > > I have a temporary fix for the fatal hang, > but don't claim to understand the Intel ICH2 > enough to know if it is "universal" (e.g., > the right thing.). I doubt it's comprehensive > enough. Problems: > > 1) Systems hang on boot (perhaps half the > time) due to a never-cleared interrupt > condition. The audio device sometimes > comes up with an initial error condition > (X_SR_DCH); this interrupt is never > "dismissed/cleared" by the ich_intr() > interrupt handler; ich_intr() livelocks > (runs constantly). I have a quick ugly > work-around fix (listed below) for this. > Maybe the real fix would involve the device > init routine. Cool! This may be a fix for PR kern/29769. > 2) Microphone input doesn't work, the error > "pcm0: record interrupt timeout, channel dead" > always occurs (it doesn't look like any > channel other than PCM_PLAY is ever even > triggered in the 4.4-RELEASE or 4.4-STABLE > code). The microphone works OK in 5.0-CURRENT. > This problem is just due to the phase-in > of the features in the sound/pci/ich driver > code and appears to be expected behavior > when looked at long enough... I haven't tested my microphone input yet. > The hang-on boot problem is potentially serious > because it is difficult to identify and > precludes unattended reboot (in normal use > one can just attempt reboot until the device > comes up without the DCH error, i.e., "clean"). Indeed. However nobody seems to mind much (Jonathan Lemon pointed out an errata in the ICH2/ICH2-M specification, which was probably the cause; however I don't understand the code enough to fix the bug). > Here is how I kludge/fixed the hang on boot > problem (again, I'm not claiming this is the > "right" fix, but the systems have never hung > on boot with it in, and without it they hang > about half to a third the time). I'll try your fix on monday (4.4-STABLE). --Stijn -- Q: Why is Batman better than Bill Gates? A: Batman was able to beat the Penguin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011214131718.B97466>