Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 14 Dec 1999 23:20:04 -0800 (PST)
From:      "Kenneth D. Merry" <ken@kdm.org>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: kern/15448: Would be nice if the kernel could detect/report problems with SCSI tagged queueing
Message-ID:  <199912150720.XAA67812@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/15448; it has been noted by GNATS.

From: "Kenneth D. Merry" <ken@kdm.org>
To: Ken Harrenstien <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: Wed, 15 Dec 1999 00:19:13 -0700

 On Tue, Dec 14, 1999 at 00:37:04 -0800, Ken Harrenstien wrote:
 > > 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
 > 
 > I know about (and like) -v, but it doesn't make any difference.  Which
 > is to say, there is no error output either way.  Just user-level I/O
 > errors except when a page transfer fails, in which case the pager code
 > then complains.  Never the CAM subsystem.
 > 
 > One way of verifying this might be to test with a known broken drive
 > after re-enabling tagged queueing, and see what happens in the way of
 > error reporting.
 > 
 > Unfortunately I don't have any of the ones in the current table or I
 > could do that test.  Regardless of the actual cause of the I/O errors,
 > it is still worrisome to me that there is no kernel log output at all.
 
 I think the reason you're not seeing any kernel diagnostics is because the
 driver isn't reporting errors to the upper level code.  It may be that it
 is just silently failing to return some buffers or something.  Since we
 already know the Tekram AMD driver is broken (PR readers see PR 15446), I
 suppose this isn't very surprising.
 
 In most cases, booting with the verbose switch turned on causes more SCSI
 diagnostics to be printed than would normally be printed.
 
 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
 


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912150720.XAA67812>