From owner-freebsd-bugs Sun Dec 12 20:40: 4 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 3094114DE4 for ; Sun, 12 Dec 1999 20:40:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id UAA76021; Sun, 12 Dec 1999 20:40:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Sun, 12 Dec 1999 20:40:02 -0800 (PST) Message-Id: <199912130440.UAA76021@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Kenneth D. Merry" Subject: Re: kern/15448: Would be nice if the kernel could detect/report problems with SCSI tagged queueing Reply-To: "Kenneth D. Merry" 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: "Kenneth D. Merry" To: klh@netcom.com Cc: 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, 12 Dec 1999 21:31:52 -0700 On Sun, Dec 12, 1999 at 06:52:28PM -0800, klh@netcom.com wrote: > >Synopsis: Would be nice if the kernel could detect/report problems with SCSI tagged queueing [ ... ] > FreeBSD 3.1-RELEASE FreeBSD 3.1-RELEASE #: 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. I don't know why the kernel didn't print out any errors, but you'll get a lot more information if you boot with the '-v' switch. At the boot loader prompt, you can type: boot kernel -v To get the verbose boot messages. You may need to increase your message buffer size, using the MSGBUF_SIZE kernel option (see LINT for details) to avoid overflowing the kernel's message buffer. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message