From owner-freebsd-stable@FreeBSD.ORG Sun May 29 04:10:13 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D999106566C for ; Sun, 29 May 2011 04:10:13 +0000 (UTC) (envelope-from michael@rancid.berkeley.edu) Received: from malcolm.berkeley.edu (malcolm.Berkeley.EDU [IPv6:2607:f140:ffff:ffff::239]) by mx1.freebsd.org (Postfix) with ESMTP id 85C818FC0A for ; Sun, 29 May 2011 04:10:13 +0000 (UTC) Received: from towanda.burnttofu.net ([IPv6:2001:470:1f05:17a6:219:d1ff:fe26:5246]) (authenticated bits=0) by malcolm.berkeley.edu (8.14.4/8.13.8m1) with ESMTP id p4T4ADbY013868 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Sat, 28 May 2011 21:10:13 -0700 (PDT) (envelope-from michael@rancid.berkeley.edu) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.96.2 at malcolm.berkeley.edu Message-ID: <4DE1C723.2070903@rancid.berkeley.edu> Date: Sat, 28 May 2011 21:10:11 -0700 From: Michael Sinatra User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110513 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (malcolm.berkeley.edu [IPv6:2607:f140:ffff:ffff::239]); Sat, 28 May 2011 21:10:13 -0700 (PDT) Subject: ICH9 panic/instability on recent kernel X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2011 04:10:13 -0000 Hi, I have a core-2 system with a 3ware SATA RAID controller for the main disks and the built-in Intel ICH9 4-port SATA controller that is only used for the DVDR. An 8-STABLE kernel csup'd and compiled on April 25 works fine on this system. Kernels from source csup'd this week are extremely unstable and usually panic or hang just minutes after booting. The following warning messages appear after the kernel probes the SATA controller and/or ICH9 USB controller and continue about once per 1-2 seconds until the system crashes: May 13 14:21:05 sonicyouth kernel: unknown: WARNING - ATAPI_IDENTIFY requeued due to channel reset LBA=0 Disabling the ICH9 SATA controller in the BIOS allows the system to boot and run normally. Changes were made on April 28 to allow better support for 6-port ICH9 controllers (SVN rev 221156) and I am wondering if my controller is now being incorrectly recognized. Here's the relevant kernel messages: May 13 13:52:53 sonicyouth kernel: atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1c4 0-0x1c4f,0x1c30-0x1c3f at device 31.2 on pci0 May 13 13:52:53 sonicyouth kernel: ata0: on atapci1 May 13 13:52:53 sonicyouth kernel: ata0: [ITHREAD] May 13 13:52:53 sonicyouth kernel: ata1: on atapci1 May 13 13:52:53 sonicyouth kernel: ata1: [ITHREAD] May 13 13:52:53 sonicyouth kernel: atapci2: port 0x1cb8-0x1cbf,0x1cac-0x1caf,0x1cb0-0x1cb7 ,0x1ca8-0x1cab,0x1c60-0x1c6f,0x1c50-0x1c5f irq 18 at device 31.5 on pci0 May 13 13:52:53 sonicyouth kernel: atapci2: [ITHREAD] May 13 13:52:53 sonicyouth kernel: ata3: on atapci2 May 13 13:52:53 sonicyouth kernel: ata3: [ITHREAD] May 13 13:52:53 sonicyouth kernel: ata4: on atapci2 May 13 13:52:53 sonicyouth kernel: ata4: [ITHREAD] If I csup the most recent kernel sources, I get the same problem. However, if, after csuping the latest kernel sources, I then fetch the version of sys/dev/ata/ata-all.c as of April 27, everything works fine. Here's the output of pciconf -l: hostb0@pci0:0:0:0: class=0x060000 card=0xd98015d9 chip=0x29e08086 rev=0x01 hdr=0x00 pcib1@pci0:0:1:0: class=0x060400 card=0xd98015d9 chip=0x29e18086 rev=0x01 hdr=0x01 pcib2@pci0:0:6:0: class=0x060400 card=0xd98015d9 chip=0x29e98086 rev=0x01 hdr=0x01 em0@pci0:0:25:0: class=0x020000 card=0x10bd15d9 chip=0x10bd8086 rev=0x02 hdr=0x00 uhci0@pci0:0:26:0: class=0x0c0300 card=0xd98015d9 chip=0x29378086 rev=0x02 hdr=0x00 uhci1@pci0:0:26:1: class=0x0c0300 card=0xd98015d9 chip=0x29388086 rev=0x02 hdr=0x00 uhci2@pci0:0:26:2: class=0x0c0300 card=0xd98015d9 chip=0x29398086 rev=0x02 hdr=0x00 ehci0@pci0:0:26:7: class=0x0c0320 card=0xd98015d9 chip=0x293c8086 rev=0x02 hdr=0x00 none0@pci0:0:27:0: class=0x040300 card=0xd98015d9 chip=0x293e8086 rev=0x02 hdr=0x00 pcib3@pci0:0:28:0: class=0x060400 card=0xd98015d9 chip=0x29408086 rev=0x02 hdr=0x01 uhci3@pci0:0:29:0: class=0x0c0300 card=0xd98015d9 chip=0x29348086 rev=0x02 hdr=0x00 uhci4@pci0:0:29:1: class=0x0c0300 card=0xd98015d9 chip=0x29358086 rev=0x02 hdr=0x00 uhci5@pci0:0:29:2: class=0x0c0300 card=0xd98015d9 chip=0x29368086 rev=0x02 hdr=0x00 ehci1@pci0:0:29:7: class=0x0c0320 card=0xd98015d9 chip=0x293a8086 rev=0x02 hdr=0x00 pcib5@pci0:0:30:0: class=0x060401 card=0xd98015d9 chip=0x244e8086 rev=0x92 hdr=0x01 isab0@pci0:0:31:0: class=0x060100 card=0xd98015d9 chip=0x29168086 rev=0x02 hdr=0x00 atapci1@pci0:0:31:2: class=0x01018a card=0xd98015d9 chip=0x29208086 rev=0x02 hdr=0x00 none1@pci0:0:31:3: class=0x0c0500 card=0xd98015d9 chip=0x29308086 rev=0x02 hdr=0x00 atapci2@pci0:0:31:5: class=0x010185 card=0xd98015d9 chip=0x29268086 rev=0x02 hdr=0x00 none2@pci0:0:31:6: class=0x118000 card=0x000015d9 chip=0x29328086 rev=0x02 hdr=0x00 vgapci0@pci0:1:0:0: class=0x030000 card=0x216619da chip=0x0e2210de rev=0xa1 hdr=0x00 none3@pci0:1:0:1: class=0x040300 card=0x216619da chip=0x0beb10de rev=0xa1 hdr=0x00 twa0@pci0:3:0:0: class=0x010400 card=0x100413c1 chip=0x100413c1 rev=0x01 hdr=0x00 pcib4@pci0:5:0:0: class=0x060400 card=0x00000000 chip=0x032c8086 rev=0x09 hdr=0x01 ioapic0@pci0:5:0:1: class=0x080020 card=0xd98015d9 chip=0x03268086 rev=0x09 hdr=0x00 fwohci0@pci0:17:3:0: class=0x0c0010 card=0xba8015d9 chip=0x8023104c rev=0x00 hdr=0x00 atapci0@pci0:17:4:0: class=0x010185 card=0x82131283 chip=0x82131283 rev=0x00 hdr=0x00 Anyone else having issues? michael