From owner-freebsd-bugs Thu Apr 3 08:02:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA29507 for bugs-outgoing; Thu, 3 Apr 1997 08:02:52 -0800 (PST) Received: from kaiwan.kaiwan.com (4@kaiwan.kaiwan.com [198.178.203.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA29502 for ; Thu, 3 Apr 1997 08:02:48 -0800 (PST) Received: from exit.com (uucp@localhost) by kaiwan.kaiwan.com (8.6.12/8.6.12) with UUCP id IAA25749 for freebsd-bugs@freebsd.org; Thu, 3 Apr 1997 08:02:40 -0800 *** KAIWAN Internet Access *** Received: (from frank@localhost) by exit.com (8.8.5/8.7.3) id HAA00463 for freebsd-bugs@freebsd.org; Thu, 3 Apr 1997 07:58:10 -0800 (PST) From: Frank Mayhar Message-Id: <199704031558.HAA00463@exit.com> Subject: Severe SCSI problems with latest -STABLE. To: freebsd-bugs@freebsd.org Date: Thu, 3 Apr 1997 07:58:09 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yesterday, I booted with the latest bits from -STABLE. I cvsupped and built the kernel on the first, and booted it yesterday morning. There were apparently some SCSI-related fixes that went in. This morning, I found my system quite wedged. I didn't think to note the exact messages, but it was something to do with a lost SCB (I think), and an overrun. The system was completely unresponsive. I reset (sigh), and tried to go through fsck. This failed, complaining of unreadable blocks, with numerous complaints from the SCSI subsystem. I punted (since I need the system to be up _now_), and booted the previous kernel, dated 3/11/97. It's working fine. So what gives? What's broken in the latest -STABLE? My system in a P100 with an Adaptec 2049W. The disk giving the most trouble was an IBM 32160W (a wide disk), although there was a narrow drive also giving trouble, just not as much. -- Frank Mayhar frank@exit.com