On Sun, February 17, 2008 07:33, Justin T. Gibbs wrote: > Niki Denev wrote: > > I was playing around with DTrace, tracing cam/xpt and the ahd driver > and > > found out that if i comment the following code : > > > > if ((spi3caps & SID_SPI_IUS) == 0) > > spi->ppr_options &= ~MSG_EXT_PPR_IU_REQ; > > > > at line 6655 in sys/cam/cam_xpt.c my disks again negotiate as U320 : > > > > da0 at ahd0 bus 0 target 0 lun 0 > > da0: <SEAGATE ST336807LW 0C01> Fixed Direct Access SCSI-3 device > > da0: 320.000MB/s transfers (160.000MHz DT, offset 63, 16bit) > > da0: Command Queueing Enabled > > da0: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) > > The aic79xx driver was not properly exporting its capabilities to > CAM. This has been addressed as of version 1.30 of aic79xx_osm.c. > Please let me know if you still have problems. hulk# uname -a FreeBSD hulk.superhero.nl 7.0-RC2 FreeBSD 7.0-RC2 #0: Sun Feb 17 17:58:36 CET 2008 admin_at_hulk.superhero.nl:/usr/obj/usr/src/sys/GENERIC amd64 hulk# camcontrol inquiry da1 pass1: <SEAGATE ST336753LW HPS3> Fixed Direct Access SCSI-3 device pass1: Serial Number 3HX35KPH000075191ZRW pass1: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Command Queueing Enabled Working. Thanks! Any chance of mfc-ing this to RELENG_7_0 before 7_0 gets released? Rgds, Patrick > > > > > Unfortunately I began seeing again the "Invalid sequencer interrupt" > > messages that i was seeing before(with fbsd 6.2) with Seagate drives > > on Adaptec at U320 speeds, and I prey that they are harmless (as they > > used to be?) > > While I do not know their root cause, they do appear to be harmless. > Do you happen to have your drives in a SES enclosure (on a backplane > with a SES chip)? One user claimed this was only reproducible when > a GEM318 SES chip was on the bus. > > -- > Justin > >Received on Sun Feb 17 2008 - 16:50:45 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:27 UTC