Date: Tue, 31 May 2011 13:23:21 -0700 (PDT) From: Michael Sinatra <michael@rancid.berkeley.edu> To: Alexander Motin <mav@freebsd.org> Cc: freebsd-stable@freebsd.org, Jeremy Chadwick <freebsd@jdc.parodius.com> Subject: Re: ICH9 panic/instability on recent kernel Message-ID: <alpine.BSF.2.00.1105311113570.95188@rancid.net.berkeley.edu> In-Reply-To: <4DE1ED9E.9070303@FreeBSD.org> References: <4DE1C723.2070903@rancid.berkeley.edu> <20110529045615.GA44303@icarus.home.lan> <4DE1ED9E.9070303@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 29 May 2011, Alexander Motin wrote: >>> 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. I agree that it makes little sense on the surface. I did follow Jeremy's advice and enable AHCI in the BIOS. Even without loding the ACHI module at boot, that still solved the problem. (I also did load AHCI and it worked fine, which the DVD being recognized as a scsi/atapi-style cd0.) I'll turn of AHCI again and try to get a serial port hooked up so that I can do a boot -v and generate the panic (usually a little bit of disk activity will cause a panic). I'll send that in a separate email to you directly. thanks, michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1105311113570.95188>