Date: Wed, 30 Jun 1999 22:17:54 -0600 (MDT) From: "Kenneth D. Merry" <ken@plutotech.com> To: wilko@yedi.iaf.nl (Wilko Bulte) Cc: jgreco@ns.sol.net, scsi@FreeBSD.ORG Subject: Re: FreeBSD panics with Mylex DAC960SX Message-ID: <199907010417.WAA39579@panzer.kdm.org> In-Reply-To: <199906301727.TAA00581@yedi.iaf.nl> from Wilko Bulte at "Jun 30, 1999 07:27:26 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Wilko Bulte wrote... > As Kenneth D. Merry wrote ... > > 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. > > Although this definitely a bogus response I don't see the point in panic-ing > the machine. An offensive message on the console, by all means. A panic? Well, I think the panic is certainly a bug. There should probably be a check for a sector size of 0 somewhere. The only question is whether it should be centralized in the slice code or broken out into each individual driver. I think it may make sense to centralize it. > This remark assumes you are not booting from the raid of course :) Of course. :) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907010417.WAA39579>