Date: Tue, 14 Dec 1999 23:20:02 -0800 (PST) From: "Kenneth D. Merry" <ken@kdm.org> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/15446: Unpredictable enabling of SCSI Tagged Queueing Message-ID: <199912150720.XAA67802@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/15446; 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/15446: Unpredictable enabling of SCSI Tagged Queueing
Date: Wed, 15 Dec 1999 00:11:29 -0700
On Tue, Dec 14, 1999 at 02:29:52 -0800, Ken Harrenstien wrote:
> >
> > My guess is that somehow the tagged queueing bit is being enabled and
> > disabled in the drive firmware. None of the other ways of tweaking the
> > tagged queueing settings would explain the behavior you're seeing.
> >
> > Check the settings in mode page 10 with camcontrol and see whether the
> > drive says tagged queueing is enabled or disabled. If the DQue bit is set,
> > the drive should not be reported as a tagged queueing drive in the dmesg.
> >
> > If the DQue bit is set and then cleared somehow between boots on your
> > system, that points fairly strongly to some sort of problem with the drive.
>
> Examining mode page 10 as you suggest reveals no changes between
> boots, although the system's idea of the tagged queueing status
> continues to vary.
>
> More interestingly, a "camcontrol inquiry" shows all 4 of the drives
> as having Tagged Queueing. This information also does not change
> between boots.
That is very interesting. It points to a driver problem I think.
> lnc1: <PCNet/PCI Ethernet adapter> rev 0x02 int b irq 10 on pci0.11.0
> lnc1: PCnet-32 VL-Bus address 00:80:5f:e4:96:18
> amd0: <Tekram DC390(T)/AMD53c974 SCSI Adapter Driver v1.05 01-01-1999 CAM ver. > rev 0x02 int a irq 11 on pci0.12.0
And, as Justin already pointed out, the driver is most likely your problem.
Tekram's default amd driver has a few problems, and you'll probably want
Justin's reworked version of that driver. I believe it went in just before
3.3. It may not be in GENERIC in 3.3, however. It will be turned on by
default for 3.4, and for any -stable snapshot.
You have several options as far as drivers go:
- Grab the -stable driver and put it on your system, and recompile your
kernel. You should just need src/sys/pci/amd.{c,h}. You'll also need
to change sys/conf/files so that the amd driver points to amd.c instead
of tek390.c. You can get the -stable driver here:
ftp://ftp.FreeBSD.ORG/pub/FreeBSD/branches/3.0-stable/src/sys/pci
- Upgrade to 3.3, -stable or 3.4, which should be out shortly. If you
don't want to wait, stable snapshots are located here:
ftp://current.FreeBSD.ORG/pub/FreeBSD/snapshots/i386
- Upgrade to -current. Snapshots are available at the same place as the
stable snapshots. This isn't recommended for most folks, but if you're
ready to deal with the requirements, it might be fun:
http://www.freebsd.org/handbook/cutting-edge.html#CURRENT
Anyway, let me know whether an updated driver fixes your problem.
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.XAA67802>