From owner-svn-src-all@FreeBSD.ORG Sun Mar 20 14:19:47 2011 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A156B106564A; Sun, 20 Mar 2011 14:19:47 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id A0B5F8FC0C; Sun, 20 Mar 2011 14:19:46 +0000 (UTC) Received: by bwz12 with SMTP id 12so5020549bwz.13 for ; Sun, 20 Mar 2011 07:19:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=oCsp4KL+NK38BrE1m4PHGulEWMQJNm0aYwlMgphhIo4=; b=kTrkh3hwILrCkDgQxQjR9zmfz9ZPDRTwnPcSzzQHpIgyLzTR1xxR01Q+A6FgXwhkWE U7yMcWGaMPgSL0arVlcWLJVNb4uGuc2+MKtj/XzlUBcBZwzSgOgvBAfuXm4WxdmRYNct /QCZlNiKuZ7skRYic7nDwzKwPMTbPHh9NHOp0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=ozx54Y+lrTIRQVHFwTppkGQkFxOIPQbWv8TX6Q107dHM07OGSeEAuQiMxuhDGC5NSk ExC8GgbgYexhVVG6+XeDqZczgpJutoTiBB0gAbHNGj7aCRSwZSIslZEbHIHhizKLTlB/ mCmmCt/pWLTriuBgew4u3caEOLwJvoi8K/rsQ= Received: by 10.204.151.205 with SMTP id d13mr2745597bkw.117.1300630785499; Sun, 20 Mar 2011 07:19:45 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id v21sm3605483bkt.23.2011.03.20.07.19.43 (version=SSLv3 cipher=OTHER); Sun, 20 Mar 2011 07:19:44 -0700 (PDT) Sender: Alexander Motin Message-ID: <4D860C9A.7020600@FreeBSD.org> Date: Sun, 20 Mar 2011 16:18:02 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Bob Willcox References: <201102052134.p15LYRmw041695@svn.freebsd.org> <20110316135122.GB7185@rancor.immure.com> <4D814AAA.3070801@FreeBSD.org> <20110320141501.GB19338@rancor.immure.com> In-Reply-To: <20110320141501.GB19338@rancor.immure.com> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2011 14:19:47 -0000 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