Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:2060 comp.os.386bsd.questions:8408 comp.os.386bsd.misc:1890
Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!news.kei.com!eff!news.umbc.edu!europa.eng.gtefsd.com!howland.reston.ans.net!vixen.cso.uiuc.edu!newsrelay.iastate.edu!news.iastate.edu!ponderous.cc.iastate.edu!michaelv
From: michaelv@iastate.edu (Michael L. VanLoon)
Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions,comp.os.386bsd.misc
Subject: Re: NetBSD problems with BL 747... more info...
Date: 31 Jan 94 18:07:16 GMT
Organization: Iowa State University, Ames, Iowa
Lines: 48
Message-ID: <michaelv.760039636@ponderous.cc.iastate.edu>
References: <michaelv.759897821@ponderous.cc.iastate.edu>
NNTP-Posting-Host: ponderous.cc.iastate.edu
I managed to capture the message exactly as it appears when my kernel
panics hanging on my BusLogic 747:
bt0: 0 device timed out
bt0 not taking commands
panic: should call debugger here (adaptec.c) # (actually, bt742a.c)
syncing disks... vm_fault(f818a294, 0, 1, 0) -> 5
fatal page fault in supervisor mode
trap type 6 code f8a50000 eip f811dfcd cs f8450008 eflags
10246 cr2 18 cpl ffffffff # (long line)
panic: trap
dumping to dev 1, offset 1952 .........
Could it be that it's somehow waiting on a bogus event or something?
Or that it's waiting for something when the BL747 thinks it's not
busy? Maybe the BL747 returns a slightly different status code in
this case than the BT742a did, and the driver thinks it just timed out
because it didn't return what the driver was expecting? Have the
status codes changed at all between the BT742 the driver was written
for and brand-new BL747's?
I'd really like to know what could be hanging it up, because, except
for this bug, the controller (and drive) work really great. If I
mount the IDE drives first, then mount the SCSI drives by hand after
the system comes up, the machine will stay up for hours at a time
compiling on and swapping to SCSI partitions (though it will crash
eventually). So, I know the card isn't actually timing out, the
driver must be getting status information it's not expecting or
something.
Can anyone shed any light on this? I'd like to make this controller
card work because 1) it looks like it's 99% functional already, and 2)
I spend a lot of money on it and it's too late to send it back now.
Thanks!
--Michael
------------------------------------------------------------------------------
Michael L. VanLoon -- michaelv@iastate.edu -- gg.mlv@isumvs.bitnet
Iowa State University of Science and Technology -- The way cool place to be!
Project Vincent Systems Staff, Iowa State University Computation Center
------------------------------------------------------------------------------
--
------------------------------------------------------------------------------
Michael L. VanLoon Project Vincent Systems Staff
michaelv@iastate.edu Iowa State University Computation Center
------------------------------------------------------------------------------