From owner-freebsd-scsi Wed Jun 30 21:20:11 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 960241555A for ; Wed, 30 Jun 1999 21:20:08 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA39599; Wed, 30 Jun 1999 22:20:05 -0600 (MDT) (envelope-from ken) Message-Id: <199907010420.WAA39599@panzer.kdm.org> Subject: Re: FreeBSD panics with Mylex DAC960SX In-Reply-To: <199906301341.IAA14025@free.pcs> from Jonathan Lemon at "Jun 30, 1999 08:41:28 am" To: jlemon@americantv.com (Jonathan Lemon) Date: Wed, 30 Jun 1999 22:20:05 -0600 (MDT) Cc: scsi@freebsd.org From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jonathan Lemon wrote... > 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. Hmm, that's likely a different problem. The mode sense happens early in the boot process, right after the inquiry. > 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." A stack trace, and the boot messages would be helpful if you have the time. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message