Date: Sun, 20 Mar 2011 16:18:02 +0200 From: Alexander Motin <mav@FreeBSD.org> To: Bob Willcox <bob@immure.com> Cc: svn-src-stable@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, svn-src-stable-8@FreeBSD.org Subject: Re: svn commit: r218347 - stable/8/sys/dev/ata/chipsets Message-ID: <4D860C9A.7020600@FreeBSD.org> In-Reply-To: <20110320141501.GB19338@rancor.immure.com> References: <201102052134.p15LYRmw041695@svn.freebsd.org> <20110316135122.GB7185@rancor.immure.com> <4D814AAA.3070801@FreeBSD.org> <20110320141501.GB19338@rancor.immure.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Bob Willcox wrote: > On Thu, Mar 17, 2011 at 01:41:30AM +0200, Alexander Motin wrote: >> On 16.03.2011 15:51, Bob Willcox wrote: >>> This change has broken SATA disk support on my Intel Atom D525 ITX system. By >>> reverting this change 8.2-STABLE works again on this system. >>> >>> My 'uname -a' output is: >>> >>> FreeBSD maul.immure.com 8.2-STABLE FreeBSD 8.2-STABLE #6: Wed Mar 16 08:15:43 CDT 2011 bob@maul.immure.com:/usr/obj/usr/src/sys/MAUL amd64 >>> >>> When booting the system I get tons of these messages: >>> >>> Mar 16 07:38:19 maul kernel: ad4: WARNING - SETFEATURES ENABLE RCACHE requeued due to channel reset >>> Mar 16 07:38:19 maul kernel: ad4: interrupt on idle channel ignored >> As I can see, it means that channel has some active request, but it is >> in IDLE state. It is strange, but I won't be surprised much if it is the >> result of some locking problem in ata(4) in non-CAM mode. >> >>> repeated over and over, and then lots of these: >>> >>> Mar 16 07:38:21 maul kernel: ad4: WARNING - READ_DMA48 requeued due to channel reset LBA=617964479 >>> Mar 16 07:38:21 maul kernel: ata2: FAILURE - already active DMA on this device >>> Mar 16 07:38:21 maul kernel: ata2: setting up DMA failed >>> >>> for different LBA values. >>> >>> As one might expect, I then start seeing I/O errors on the disk and programs >>> failing >>> >>> I've attached the 'pciconf -lv' output. >> Send me please full verbose log, if you can save it. I am especially >> interested in place around first errors. >> >> You may try to build kernel with `options ATA_CAM` to see if it helps. >> I've mostly tested this patch in that mode. > > I tried setting `options ATA_CAM` but that didn't fix the problem. I still got > continuous ATA error messages spewed out while probing the ATA devices. I'm > not able to capture the verbose output as the system never successfully boots > and I don't have a serial console attached to the system. It's strange. Can you at least show errors you received in that case? I suppose they should be different from the original. > For now, I plan to stay with the previous version of ata-intel.c since this is > my gateway system and I need for it to 'just work'. :( -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D860C9A.7020600>