From owner-freebsd-bugs Tue Jan 2 02:54:43 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA12479 for bugs-outgoing; Tue, 2 Jan 1996 02:54:43 -0800 (PST) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA12474 for ; Tue, 2 Jan 1996 02:54:40 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id CAA18917 for ; Tue, 2 Jan 1996 02:54:09 -0800 Message-Id: <199601021054.CAA18917@precipice.shockwave.com> To: bugs@freebsd.org Subject: Buslogic lockups accessing both sync and async devices Date: Tue, 02 Jan 1996 02:53:53 -0800 From: Paul Traina Sender: owner-bugs@freebsd.org Precedence: bulk I recall someone mentioning a while back that the buslogic cards had problems probing for both sync and async scsi devices on the same bus. I've never seen that problem, but I have had some pretty obnoxious behavior happen when using the single async device (a CDROM player) on my bus with my BT455S (3.7 roms). The card will lock up, the driver will attempt to abort the operation, and the abort operation itself will time-out, at which point, the system is wedged and as luck would have it, it's often the root directory or superblock we're trying to sync. :-( I am quite curious if anyone else has seen this behavior. I'm even more curious if there is a way of doing a hard-reset on the card's controller logic and the scsi bus when an operation times out and then re-try the operation, which would provide a much more robust behavior. Almost 3 years of running FreeBSD and this finally rears its ugly head (I never use my CDROM drive). (This occurs with both 2.1 and 2.2-current). Any advice? Anyone know if Buslogic has a fix? Paul