From owner-freebsd-scsi Wed Jun 30 6:41:34 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 596BF15109 for ; Wed, 30 Jun 1999 06:41:30 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id IAA13135; Wed, 30 Jun 1999 08:41:29 -0500 (CDT) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.6.13/8.6.4) with ESMTP id IAA11937; Wed, 30 Jun 1999 08:41:28 -0500 Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id IAA14025; Wed, 30 Jun 1999 08:41:28 -0500 (CDT) Date: Wed, 30 Jun 1999 08:41:28 -0500 (CDT) From: Jonathan Lemon Message-Id: <199906301341.IAA14025@free.pcs> To: ken@plutotech.com, scsi@freebsd.org Subject: Re: FreeBSD panics with Mylex DAC960SX X-Newsgroups: local.mail.freebsd-scsi In-Reply-To: References: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you write: >Joe Greco wrote... >> >> da1: Fixed Direct Access SCSI-2 device >> da1: 40.0MB/s transfers (20.0MHz, offset 16, 16bit), Tagged Queueing Enabled >> da1: A > >That should probably read "Attempt to query device size failed ...." > >You may be losing characters over the serial console or something. > >> If I can provide further information to assist in tracking down this bug, >> please let me know. > >My first guess is that it's happening during the open() routine, for some >reason. That's why fsck seems to cause the problem. > >You're probably right about the device returning a size of zero. It isn't >immediately clear to me why the open routine would cause a panic, *unless* >the Mylex unit returns good status for the read capacity command, but >returns a capacity of 0. I have a situation that sounds similar to this, with similar results. In my case, I have a mostly-bad SCSI disk that doesn't work until it is sufficiently warmed up. When booting, one of the SCSI commands sent to the drive (mode sense, I think) fails, and the kernel panics. Basically, the SCSI bus recognizes some thing is there, but can't even read the vendor string from the disk. "Device connected, but has a fault." -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message