From owner-freebsd-bugs  Sun Dec 12 19: 0: 7 1999
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 DBF3014CA3
	for <freebsd-bugs@FreeBSD.org>; Sun, 12 Dec 1999 19:00:02 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id TAA67925;
	Sun, 12 Dec 1999 19:00:02 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 4ED6114D2D; Sun, 12 Dec 1999 18:52:28 -0800 (PST)
Message-Id: <19991213025228.4ED6114D2D@hub.freebsd.org>
Date: Sun, 12 Dec 1999 18:52:28 -0800 (PST)
From: klh@netcom.com
To: freebsd-gnats-submit@freebsd.org
X-Send-Pr-Version: www-1.0
Subject: kern/15448: Would be nice if the kernel could detect/report problems with SCSI tagged queueing
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         15448
>Category:       kern
>Synopsis:       Would be nice if the kernel could detect/report problems with SCSI tagged queueing
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Dec 12 19:00:02 PST 1999
>Closed-Date:
>Last-Modified:
>Originator:     Ken Harrenstien
>Release:        3.1-RELEASE
>Organization:
>Environment:
FreeBSD <hostname> 3.1-RELEASE FreeBSD 3.1-RELEASE #<n>: <buildstring>  i386
>Description:
I just spent a nerve-wracking day backing up some drives that I thought
were about to crash their little heads, only to finally discover that
the problem was a failure of SCSI command tagged queueing to work
properly.

I was very surprised that even though I was getting user program I/O
errors (from tar), the kernel gave me no feedback at all on the
console.  This was really mystifying.  I don't know enough about how
tagging works to know whether it's even feasible to detect when it's
not working -- but the kernel is clearly getting SOME kind of error
that it's relaying back to the user.

Would it be possible to make sure that I/O errors of this nature send
*something* to the console log?  (Actually, that's a good idea for
any sort of I/O error; I know most of them are reported OK).  This
would be a huge help tracking down potentially buggy drives; the effort
to zero in on this possibility is otherwise very time-consuming.

Thanks...


>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message