Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:2066 comp.os.386bsd.questions:8455 comp.os.386bsd.misc:1900 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!decwrl!nic.hookup.net!swrinde!menudo.uh.edu!uuneo.NeoSoft.com!nobody From: smace@metal.neosoft.com (Scott Mace) Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions,comp.os.386bsd.misc Subject: Re: NetBSD problems with BL 747... more info... Date: 1 Feb 1994 21:43:55 -0600 Organization: NeoSoft (Katy Research Center) Lines: 27 Message-ID: <2in7id$e6@metal.neosoft.com> References: <michaelv.759897821@ponderous.cc.iastate.edu> <michaelv.760039636@ponderous.cc.iastate.edu> NNTP-Posting-Host: metal.neosoft.com Hmm, this is strange, I've a a buslogic 747s and is appears to be working fine under FreeBSD... In article <michaelv.760039636@ponderous.cc.iastate.edu>, Michael L. VanLoon <michaelv@iastate.edu> wrote: >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?