From owner-freebsd-scsi@FreeBSD.ORG Tue Mar 22 02:52:39 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41C7816A4CE for ; Tue, 22 Mar 2005 02:52:39 +0000 (GMT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id E716143D48 for ; Tue, 22 Mar 2005 02:52:38 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.1/8.13.1) with ESMTP id j2M2qVbg078163; Mon, 21 Mar 2005 18:52:35 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200503220252.j2M2qVbg078163@gw.catspoiler.org> Date: Mon, 21 Mar 2005 18:52:31 -0800 (PST) From: Don Lewis To: rloef@interfold.com In-Reply-To: <200503220221.j2M2LS0v078118@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: freebsd-scsi@FreeBSD.org Subject: Re: Any changes in SCSI code between 4.10 and 4.11? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 02:52:39 -0000 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: 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: 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.