Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news2.acs.oakland.edu!news.tacom.army.mil!ulowell.uml.edu!tribune.meitca.com!bloom-beacon.mit.edu!newsfeed.internetmci.com!swrinde!elroy.jpl.nasa.gov!lll-winken.llnl.gov!fnnews.fnal.gov!unixhub!news.Stanford.EDU!microunity!usenet From: deborah@gallifrey.microunity.com (Deborah Gronke Bennett) Subject: Re: FreeBSD 2.1.0-Release Install Problems. HELP! In-Reply-To: Jamie Bowden's message of Mon, 24 Jun 1996 00:07:33 -0400 X-Nntp-Posting-Host: gallifrey.microunity.com Message-ID: <oq4tnvdb8d.fsf@gallifrey.microunity.com> Sender: deborah@gallifrey.microunity.com Organization: MicroUnity Systems Engineering, Inc. X-Newsreader: Gnus v5.1 References: <4q9t84$ih@gde.gdesystems.com> <4qjo31$4ds@uriah.heep.sax.de> <Pine.3.91.960624000524.9733B-100000@fog.cs.odu.edu> Date: Fri, 28 Jun 1996 18:39:29 GMT Lines: 40 In article <Pine.3.91.960624000524.9733B-100000@fog.cs.odu.edu> Jamie Bowden <bowden@cs.odu.edu> writes: On 23 Jun 1996, J Wunsch wrote: > This is either a problem with your memory (or chipset), or you are > suffering from some problems the 2.1R driver had with the AHA2940UW > controller. I have several servers with AHA2940UW's on them that I have been using since the day 2.1-R was out. They haven't yet given me a problem, what possible things should I be on the lookout for, just in case, and will they be fixed in 2.1.5-R? I don't like using -snap, -stable, or -current on production boxes. I submitted the problem as report kern/1296. What you might see is this: ahc0: target 6, lun 0 (st0) timed out st0(ahc0:6:0): BUS DEVICE RESET message queued and then: st0(ahc0:6:0): Target Busy (where st0 could be some other scsi device like cd0) followed by the machine hanging so only a reset will get you out. The evaluator of the PR sent me this comment: >I believe these problems are caused by a bug in how the driver >handled parity. This has been fixed in -stable. Please >update your kernel and tell me if that doesn't solve your problem. I haven't had a chance to do this - the machine is not heavily used and I've been too busy. -- ---------- Deborah Gronke Bennett (WD5HJH) kernel and device drivers engineer deborah@microunity.com (408)-734-8100 MicroUnity Systems Eng., 255 Caspian Drive, Sunnyvale, CA 94089-1015 USA Want cscope? See http://www.att.com/ssg/new/cscope.html