From owner-freebsd-current Thu Sep 17 14:15:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03494 for freebsd-current-outgoing; Thu, 17 Sep 1998 14:15:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.amis.net (server.amis.net [195.10.52.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03243 for ; Thu, 17 Sep 1998 14:14:22 -0700 (PDT) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id XAA05812; Thu, 17 Sep 1998 23:13:34 +0200 (CEST) Received: from localhost (blaz@localhost) by gold.amis.net (8.9.1/8.8.8) with SMTP id XAA00304; Thu, 17 Sep 1998 23:11:28 +0200 (CEST) Date: Thu, 17 Sep 1998 23:11:28 +0200 (CEST) From: Blaz Zupan To: "Justin T. Gibbs" cc: freebsd-current@FreeBSD.ORG Subject: Re: More CAM trouble In-Reply-To: <199809171943.NAA08113@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > One of your devices doesn't handle the synchronize cache command > correctly. Please verify that this is the case by going into > sys/cam/scsi/scsi_da.c:daclose() and doing something like this: Hit the hammer on the nail on the first try. Now the machine boots just fine. > If this addresses your problem, we can add a quirk to prevent the > command from being run on certain devices. So it seems we need a new quirk for this behaviour. Now I need to find out which of the disks is causing this. Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message