From owner-freebsd-current Fri Apr 17 15:55:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26116 for freebsd-current-outgoing; Fri, 17 Apr 1998 15:55:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from proxy.metro.tas.com.au ([147.109.165.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26085 for ; Fri, 17 Apr 1998 22:55:16 GMT (envelope-from kerry.morse@metro.tas.com.au) Received: from mttmail.metro.tas.com.au (MTTMail.metro.tas.com.au [147.109.164.249]) by proxy.metro.tas.com.au (8.8.8/8.8.5) with ESMTP id IAA08691 for ; Sat, 18 Apr 1998 08:54:29 +1000 (EST) Received: by MTTMail.metro.tas.gov.au with Internet Mail Service (5.0.1458.49) id ; Sat, 18 Apr 1998 08:54:30 +1000 Message-ID: <02B01380C828D1119ED70020AF641C53068561@MTTMail.metro.tas.gov.au> From: Kerry Morse To: "'freebsd-current@FreeBSD.ORG'" Subject: RE: Help - please... Adaptec 1542 and Exabyte tape problem... Date: Sat, 18 Apr 1998 08:54:30 +1000 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > So basically it's not going to work for at least a while or a few > fixes > > so swapping the controller out over with a PCI controller while no > ones > > looking is my best solution at present... > > I've just found a whole mess of bounce buffer bitrot in the existing > scsi > code and applied some bandaids. I can't test some of the more obscure > > drivers, but an aha1542B + sd0/sd1/st0/cd0 now seems to work fine. > Before, talking to the tape would fail 50% of the time at startup. > > Ironically, I think I to blame for a good chunk of the original > breakage. > The scsi base code (scsi_scsi_cmd() specifically) had some patchwork > to > detect data transfers to/from the per-process kernel stack and how to > manually bounce them. When I moved the kernel stack out of user space > > last year some time, the glue code that checked for requests on the > kstack > no longer worked as it used assumptions about the VM space layout that > were no longer true. However, there was bitrot in other drivers too, > notably worm, ch and st. > > OK, is there a 'patch' I can apply or do I need to pull a whole new > image of > FreeBSD??, currently running the 980414 SNAP.... > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message