From owner-freebsd-hackers Mon Nov 17 18:21:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA06641 for hackers-outgoing; Mon, 17 Nov 1997 18:21:23 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from chess.inetspace.com (chess.inetspace.com [206.50.163.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA06615 for ; Mon, 17 Nov 1997 18:21:15 -0800 (PST) (envelope-from kgor@chess.inetspace.com) Received: (from kgor@localhost) by chess.inetspace.com (8.8.5/8.8.5) id UAA05442; Mon, 17 Nov 1997 20:19:59 -0600 Date: Mon, 17 Nov 1997 20:19:59 -0600 Message-Id: <199711180219.UAA05442@chess.inetspace.com> From: "Kent S. Gordon" To: jdp@polstra.com CC: hackers@FreeBSD.ORG In-reply-to: <199711160506.VAA26780@austin.polstra.com> (message from John Polstra on Sat, 15 Nov 1997 21:06:36 -0800) Subject: Re: Problems with BusTek SCSI controller and CD-ROM Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>>> "jdp" == John Polstra writes: > I have an old ISA bus machine with a BusTek (now BusLogic) BT542 > SCSI controller. It works fine with the two hard drives that I > have installed. But when I added a Plextor 4x CD-ROM drive > today, it caused the system to hang during the probe of the > controller. The last message on the console before the hang is: > bt0: reading board settings, dma=5, int=11 > If I wait several minutes, it eventually gives a further message > "bt0: not taking commands!". Then it drops into the kernel > debugger. I had similar problems with a VL Bus machine and a BusLogic BT445. At least your will boot with hard drives only. It had only two hard drive and no other SCSI devices. It stopped working on -current in April. It work in 2.2.2, but not 2.2.5 (It seemed to break somewhere in 2.2-STABLE around June). I could not figure out a solution, so the machine had to migrate to Linux :(. I posted to -hackers (and submitted a PR), but got no responce. I looked at the source and did not see any changes that looked like the source of the problem. The scsi code did not change a lot during the period that broke my machine. > I get identical failures with a -current system from late > September and with a 2.2.2 boot floppy. > It's not a problem with termination, and I've tried rearranging > the devices on the SCSI bus without results. The power-up > Messages from the controller's BIOS show that it recognizes the > CD-ROM drive as well as both hard disks. And booting from hard > disk (up until the hang) works fine. Also, if I boot from a DOS > floppy with the appropriate drivers on it, DOS talks to all the > devices without problems. > So this seems to be a problem specific to FreeBSD. Any ideas? > John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. > Seattle, Washington USA "Self-knowledge is always bad news." -- > John Barth -- Kent S. Gordon Architect iNetSpace Co. voice: (972)851-3494 fax:(972)702-0384 e-mail:kgor@inetspace.com