Date: Thu, 21 Sep 2000 18:19:57 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: "Justin T. Gibbs" <gibbs@plutotech.com> Cc: "Justin T. Gibbs" <gibbs@plutotech.com>, Andy@silverbrook.com.au, Brad Knowles <blk@skynet.be>, stable@FreeBSD.ORG, "Brandon D. Valentine" <bandix@looksharp.net> Subject: Re: MFC of ahc driver updates (long-ish) Message-ID: <Pine.SUN.3.91.1000921175024.8689A-100000@pcnet1.pcnet.com> In-Reply-To: <200009212025.OAA47883@pluto.plutotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 21 Sep 2000, Justin T. Gibbs wrote: > >OK, I got the -current driver integrated into -stable. The > >"ahc0: spurious interrupt..." messages that I was getting > >constantly in 4.1-stable were from option AHC_ALLOW_MEMIO > >in the kernel config file. I guess there's something > >strange about this motherboard/controller combination that > >doesn't let it do memory mapped IO. Removing this option > >makes the -stable driver bootable. > > That is really weird. Did this option ever work on this > motherboard? No, this is a brand new system. > > >I also get the following messages (from the -current driver > >in -stable): > > > > ahc1:A:3: Message reject for 80 -- ignored > > > >These repeat pretty fast while the machine boots and also > >for a while after it has booted. There seem to be about > >255 of them (dmesg | grep "Message reject" | wc -l). In > >this system, there is nothing (not even a cable) attached > >to ahc1. > > What kind of drives are you using? My guess is that this is > caused by the controller attempting to negotiate using the > PPR message rather than SYNC/WIDE. In -current, the XPT > will only allow PPR speeds if the device has the DT_REQ > capability in its inquiry data. -stable does not have this > yet. Unfortunately, the XPT negotiation filtering in CAM > (and similar logic in the Linux version of the aic7xxx > driver) allowed me to get away without properly handling > a message reject for a PPR message. I'll try to add that > today. I'll also look to see how hard it would be to get > the negotiation filtering into -stable. Oops, I had mistakenly said previously that there is nothing connected to ahc1. After more closely examining the boot messages, it is ahc0 that has nothing connected. So ahc1 does have drives attached to it: da0 at ahc1 bus 0 target 0 lun 0 da0: <SEAGATE ST318404LC 0006> Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit) da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da1 at ahc1 bus 0 target 1 lun 0 da1: <SEAGATE ST318404LC 0006> Fixed Direct Access SCSI-3 device da1: 160.000MB/s transfers (80.000MHz, offset 63, 16bit) da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) cd0 at ahc1 bus 0 target 3 lun 0 cd0: <PLEXTOR CD-ROM PX-40TS 1.10> Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed It seems as if the Plextor CD-ROM is the culprit, and judging from the displayed transfer speed, it does seem to be failing to negotiate properly. It should be negotiating at 20 MHz (which is where it was negotiated by the 4.1-RELEASE GENERIC kernel). One positive note is that the Seagates are now negotiating at U160 rates. Let me know if there is anything else you want me to try. Thanks, -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.91.1000921175024.8689A-100000>