Any changes in SCSI code between 4.10 and 4.11?

[Don Lewis]

On 21 Mar, Don Lewis wrote:

> I've seen something similar with one of the disks on my 4-STABLE box.
> The working -> non-working timeframe sounds similar.  I thought the disk
> was going bad.  It tended to fail under load, but I was able to retrieve
> all the data from it and I replaced it with a couple of older and
> smaller disks that I had as spares.  The symtoms were timeouts and this
> disk would sometimes go offline, resulting in an "Invalidating pack"
> error.  It also exhibited the same problems on my 6-CURRENT box until
> just recently, which makes me think that something in the CAM, SCSI, or
> driver code recently got fixed.  I'm now totally unable to reproduce the
> problem on my 6-CURRENT box and I'm planning on moving the disk back to
> by 4-STABLE box to see if the problem comes back.
> 
> In my case, the controller is a
> 	ahc0: <Adaptec 19160B Ultra160 SCSI adapter> port 0xe000-0xe0ff mem 0xef022000-0xef022fff irq 16 at device 12.0 on pci0
> and the disk is a
> 	da1 at ahc0 bus 0 target 1 lun 0
> 	da1: <SEAGATE ST336737LW 0105> Fixed Direct Access SCSI-3 device 
> 	da1: 160.000MB/s transfers (80.000MHz, offset 31, 16bit), Tagged Queueing Enabled
> 	da1: 35242MB (72176566 512 byte sectors: 255H 63S/T 4492C)

I did some digging, and it looks like I replaced the disk on July 7,
2004, and my last kernel+world build before that was on June 20.  I
don't remember if I was seeing problems before then, but my previous
builds were on May 28, May 22, and Apr 23.  4.10 was released on May
27.

I looked around in CVS and didn't see any suspicious commits around that
time.