From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 10 13:42:16 2007 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5B48316A403 for ; Wed, 10 Jan 2007 13:42:16 +0000 (UTC) (envelope-from cstdenis@ctgameinfo.com) Received: from luna.ctgameinfo.com (luna.ctgameinfo.com [65.110.52.10]) by mx1.freebsd.org (Postfix) with ESMTP id 2FF6F13C457 for ; Wed, 10 Jan 2007 13:42:16 +0000 (UTC) (envelope-from cstdenis@ctgameinfo.com) Received: from [192.168.1.100] (S01060016b606ed02.vc.shawcable.net [24.87.22.207]) (AUTH: LOGIN chris@ctgameinfo.com) by luna.ctgameinfo.com with esmtp; Wed, 10 Jan 2007 05:02:38 -0800 id 00078C19.45A4E3EF.00015860 Message-ID: <45A4E3AD.1040600@ctgameinfo.com> Date: Wed, 10 Jan 2007 05:01:33 -0800 From: Cstdenis User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Bug in aac? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 13:42:16 -0000 I am running 6.1-p11 with a Adaptec SAS RAID 4800SAS running a mirror of 2 15k rpm SCSI drives. Under heavy IO load (Its a database server) I get the following accompanied by serious system lag: Jan 9 20:52:42 ayu kernel: aac0: COMMAND 0xc8f56f80 TIMEOUT AFTER 34 SECONDS Jan 9 20:52:42 ayu kernel: aac0: COMMAND 0xc8f54f00 TIMEOUT AFTER 34 SECONDS Jan 9 20:52:42 ayu kernel: aac0: COMMAND 0xc8f56b40 TIMEOUT AFTER 34 SECONDS Jan 9 20:52:42 ayu kernel: aac0: COMMAND 0xc Jan 9 20:52:43 ayu kernel: 8f56740 TIMEOUT AFTER 34 SECONDS Jan 9 20:52:43 ayu kernel: aac0: COMMAND 0xc8f57640 TIMEOUT AFTER 34 SECONDS Jan 9 20:52:43 ayu kernel: aac0: COMMAND 0xc8f58440 TIMEOUT AFTER 34 SECONDS Jan 9 20:52:43 ayu kernel: aac0: COMMAND 0xc8f57bc0 TIMEOUT AFTER 34 SECONDS Jan 9 20:52:43 ayu kernel: aac0: COMMAND 0xc8f59b40 TIMEOUT AFTER 35 SECONDS Jan 9 20:52:43 ayu kernel: aac0: COMMAND 0xc8f57c80 TIMEOUT AFTER 35 SECONDS Jan 9 20:52:43 ayu kernel: aac0: COMMAND 0xc8f59600 TIMEOUT AFTER 35 SECONDS Jan 9 20:52:43 ayu kernel: aac0: COMMAND 0xc8f5a0c0 TIMEOUT AFTER 35 SECONDS Jan 9 20:52:43 ayu kernel: aac0: COMMAND 0xc8f58c00 TIMEOUT AFTER 35 SECONDS Jan 9 20:52:43 ayu kernel: aac0: COMMAND 0xc8f55f40 TIMEOUT AFTER 35 SECONDS Jan 9 20:52:43 ayu kernel: aac0: COMMAND 0xc8f580c0 TIMEOUT AFTER 35 SECONDS Jan 9 20:52:43 ayu kernel: aac0: COMMAND 0xc8f53280 TIMEOUT AFTER 35 SECONDS Jan 9 20:52:43 ayu kernel: aac0: COMMAND 0xc8f58bc0 TIMEOUT AFTER 35 SECONDS Jan 9 20:52:43 ayu kernel: aac0: COMMAND 0xc8f59940 TIMEOUT AFTER 35 SECONDS (hex after command and number of seconds varies) Excerpts from dmesg ------------------- FreeBSD 6.1-RELEASE-p11 #0: Wed Jan 3 19:06:12 CST 2007 root@ayu.ctgameinfo.com:/usr/obj/usr/src/sys/AYU Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU 3060 @ 2.40GHz (2394.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff Features2=0xe3bd,CX16,,> AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 real memory = 3622699008 (3454 MB) avail memory = 3545722880 (3381 MB) aac0: mem 0xd8400000-0xd85fffff,0xd8200000-0xd83fffff,0xe0000000-0xe7ffffff irq 26 at device 14.0 on pci11 aac0: New comm. interface enabled aac0: Adaptec Raid Controller 2.0.0-1 aacd0: on aac0 aacd0: 69988MB (143335424 sectors) The problem happens a few times a day each time lasting only a matter of minutes. I searched the mailing lists for other having this problem, but all I found were older ones from early 5.x that are supposed to be fixed now.