Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!math.ohio-state.edu!jussieu.fr!univ-lyon1.fr!swidir.switch.ch!newsfeed.ACO.net!Austria.EU.net!EU.net!sunic!isgate!veda.is!adam From: adam@veda.is (Adam David) Subject: BT-445C not quite supported Organization: Veda Systems, Iceland Message-ID: <Cw0tws.4zz@veda.is> Date: Mon, 12 Sep 1994 14:36:26 GMT Lines: 25 I've been trying to use a BT-445C instead of a BT-445S but there are problems: bt0: mbi at 0xf09359b4 should be found, stat=81..resync What does this mean? The address varies each time the message occurs. After some activity, it gets stuck in a continous loop doing: bt0: Try to abort bt0: Try to abort bt0: Abort Operation timed out bt0: Try to abort ..... vnode pager read error 5 (various error messages from the vm system, can't flush dirty pages, etc). Basically the controller gets hosed, but it does NOT fail with "bt0: not accepting commands!" but instead keeps on trying although it is stuck. The disk sounds like it is "stuck in a groove", i.e. continually scanning the same cylinder (or so). The same disk works perfectly on an aha1542 or a BT-445S. What is so different between the 2 BT-445 controllers? -- Adam David <adam@veda.is>