Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!cs.utexas.edu!convex!news.duke.edu!MathWorks.Com!news.kei.com!travelers.mail.cornell.edu!newstand.syr.edu!rodan.syr.edu!smcarey From: smcarey@rodan.syr.edu (Shawn M Carey) Newsgroups: comp.os.386bsd.questions Subject: Re: BT-445C SCSI controller Date: 11 Sep 1994 04:30:54 GMT Organization: Syracuse University, Syracuse, NY Lines: 34 Message-ID: <34u15u$l1q@newstand.syr.edu> References: <Cvxs0p.L8s@veda.is> NNTP-Posting-Host: rodan.syr.edu In article <Cvxs0p.L8s@veda.is> adam@veda.is (Adam David) writes: >What's wrong with the BT-445 SCSI controller or the bt742 driver? > >bt0: mbi at 0xf09359b4 should be found, stat=81..resync >....... >bt0: Try to abort >bt0: Try to abort >bt0: Try to abort >bt0: Abort Operation timed out >bt0: Try to abort >....... >vnode pager read error 5 >[all kinds of vm errors] >[bt0 and sd0 are in an endless loop retrying something] > This just happened to me today while doing a from-scratch install on a new system. The cause of the problem for me was that the card was at irq12, and the kernel was expecting it to be at irq11. The BT445C was found, and worked for a while until I saw "stray interrupt c" (0xc, or 12, I assume) and then the infamous "bt0: try to abort" After scratching my grape for a bit, the lone stray interrupt gave me a clue to check the interrupts... >-- >Adam David <adam@veda.is> -Shawn Carey