Date: Sun, 29 May 2011 09:54:22 +0300 From: Alexander Motin <mav@FreeBSD.org> To: Michael Sinatra <michael@rancid.berkeley.edu> Cc: freebsd-stable@freebsd.org, Jeremy Chadwick <freebsd@jdc.parodius.com> Subject: Re: ICH9 panic/instability on recent kernel Message-ID: <4DE1ED9E.9070303@FreeBSD.org> In-Reply-To: <20110529045615.GA44303@icarus.home.lan> References: <4DE1C723.2070903@rancid.berkeley.edu> <20110529045615.GA44303@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29.05.2011 07:56, Jeremy Chadwick wrote: > On Sat, May 28, 2011 at 09:10:11PM -0700, Michael Sinatra wrote: >> 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:<Intel ICH9 SATA300 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1c40-0x1c4f,0x1c30-0x1c3f at device 31.2 on pci0 >> May 13 13:52:53 sonicyouth kernel: ata0:<ATA channel 0> on atapci1 >> May 13 13:52:53 sonicyouth kernel: ata0: [ITHREAD] >> May 13 13:52:53 sonicyouth kernel: ata1:<ATA channel 1> on atapci1 >> May 13 13:52:53 sonicyouth kernel: ata1: [ITHREAD] >> May 13 13:52:53 sonicyouth kernel: atapci2:<Intel ICH9 SATA300> controller> 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:<ATA channel 0> on atapci2 >> May 13 13:52:53 sonicyouth kernel: ata3: [ITHREAD] >> May 13 13:52:53 sonicyouth kernel: ata4:<ATA channel 1> 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: The only change in 8-STABLE ata-all.c since April 27 was the SVN rev 221155. But I don't see how can it cause problems. I would really like to see full _verbose_ demsg output to better understand what is going on there. If it even panics, I need to see how exactly. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DE1ED9E.9070303>