*BSD News Article 16953


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!agate.berkeley.edu!cgd
From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: [netbsd] aha1542-related bug (was Re: 1542C not taking commands!)
Date: 9 Jun 93 09:57:51
Organization: Kernel Hackers 'r' Us
Lines: 23
Message-ID: <CGD.93Jun9095751@eden.CS.Berkeley.EDU>
References: <C8AFKF.5EH@NeoSoft.com> <1993Jun8.120703.12538@cnplss5.cnps.philips.nl>
	<1v48hl$16d@werple.apana.org.au>
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: andrew@werple.apana.org.au's message of 9 Jun 1993 18:55:17 +1000

In article <1v48hl$16d@werple.apana.org.au> andrew@werple.apana.org.au (Andrew Herbert) writes:
.This is wrong, as I had the same problem (accompanied by a SCSI bus hang)
.earlier today with my aha1542b and the 8 June NetBSD kernel compiled with
.gcc 1.39 (wouldn't boot with gcc 2.4.3).  The timeout occurred about half an
.hour after bootup.  In the past six or so months of running 386bsd with
.Julian's SCSI subsystem and bde's intr/spl code I've never had any SCSI
.problems.  Hmmm. :-(

well, the person who had the problem, right after installing the binary
distribution wasn't even *running* BDE's interrupt code, because it
has yet to be released on a boot disk...

so whatever problem they had, bde's interrupt code has nothing do
do with it...



chris
--
Chris G. Demetriou                                    cgd@cs.berkeley.edu

   "386bsd as depth first search: whenever you go to fix something you
       find that 3 more things are actually broken." -- Adam Glass