From owner-freebsd-bugs Sun Jan 9 13:30: 4 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A51F514F9F for ; Sun, 9 Jan 2000 13:30:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id NAA24992; Sun, 9 Jan 2000 13:30:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Sun, 9 Jan 2000 13:30:02 -0800 (PST) Message-Id: <200001092130.NAA24992@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Ken Harrenstien Subject: Re: kern/15448: Would be nice if the kernel could detect/report problems with SCSI tagged queueing Reply-To: Ken Harrenstien Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/15448; it has been noted by GNATS. From: Ken Harrenstien To: "Kenneth D. Merry" Cc: Ken Harrenstien , freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/15448: Would be nice if the kernel could detect/report problems with SCSI tagged queueing Date: Sun, 9 Jan 100 13:23:34 PST > Anyway, why don't we leave this PR open, and you can verify that you get > more diagnostics when you upgrade to the newer amd driver, and then we can > close it. > > Ken > -- > Kenneth Merry > ken@kdm.org Just an update. I can't actually verify whether there are more diagnostics with the current Tekram driver, because I no longer have user-level I/O errors and I'm reluctant to deliberately generate them. The bug was more of a concern that this was evidence of a general loophole allowing I/O errors to be propagated up to the user without ever causing a kernel error message. I *could* try to arrange for a sacrificial system and do a number of horrible things to the bus. But if the driver folk are confident that they've covered all the bases, that's good enough for me. --Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message