From owner-freebsd-hackers Fri Dec 11 07:22:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17664 for freebsd-hackers-outgoing; Fri, 11 Dec 1998 07:22:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail-oak-1.pilot.net (mail-oak-1.pilot.net [198.232.147.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17659 for ; Fri, 11 Dec 1998 07:22:18 -0800 (PST) (envelope-from wadlow@pilot.net) Received: from corsair.pilot.net (corsair.pilot.net [204.48.17.12]) by mail-oak-1.pilot.net with ESMTP id HAA11335 for ; Fri, 11 Dec 1998 07:22:10 -0800 (PST) Received: from arrow.pilot.net (arrow.pilot.net [204.48.17.29]) by corsair.pilot.net with ESMTP id HAA21326 for ; Fri, 11 Dec 1998 07:22:10 -0800 (PST) Received: from localhost (wadlow@localhost) by arrow.pilot.net (arrow) with ESMTP id HAA04706 for ; Fri, 11 Dec 1998 07:22:09 -0800 (PST) Date: Fri, 11 Dec 1998 07:22:09 -0800 (PST) From: Tom Wadlow To: freebsd-hackers@FreeBSD.ORG Subject: A problem with SCSI Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I built a system on 3.0-RELEASE, with a SCSI disk. The system works fine, except that occasionally, the da driver says: "Invalidating pack", and drops the disk offline and everything hangs. This is unfortunate. Reading through the code, there seemed to have been a bunch of changes made recently to the sys/cam/scsi/scsi_da.c code (among others) that deal with invalidating packs. Seeing this, I upgraded my /sys to 3.0-CURRENT last night, rebuilt the kernel and rebooted. This morning I woke to a crashed system and an "Invalidating pack" message on the console. Thus far, I've built 3 different SCSI systems from 3.0-RELEASE, and two of them have had this problem, with the third complaining about da related issues, but not dying. The third machine is a system that ran the 3.0-mumble-SNAP release from the CD for months without problem. So I don't think it is a hardware problem. What can I do to fix or workaround this problem? A quick answer would be appreciated, as the system which is crashing is one that I *really* need to be stable, and I'd rather not have to downrev to 2.2.x, which I'm going to need to do very soon, like today, if I can't get this issue stabilized. Thanks, --Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message