From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: exception Emask 0x0 SAct 0x1 / SErr 0x0 action 0x2 frozen Date: Mon, 29 Sep 2008 17:13:33 +0900 Message-ID: <48E08E2D.6050905@kernel.org> References: <3E6D0C24877245C3A5A327129A7B4CA7@909927SOSLA> <5A4A9A3B0AAA4A20A33BC2D578F5F75F@909927SOSLA> <5419A02543384E69AF2BA82FF6E66C14@909927SOSLA> <4B1ABD0393EF40FFB0A12242FE8356AF@909927SOSLA> <48DBAB81.8050900@tmr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from hera.kernel.org ([140.211.167.34]:56227 "EHLO hera.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751802AbYI2IPk (ORCPT ); Mon, 29 Sep 2008 04:15:40 -0400 In-Reply-To: <48DBAB81.8050900@tmr.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Bill Davidsen Cc: Gwendal Grignou , Justin Piszcz , Brian Rademacher , linux-ide@vger.kernel.org, linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org, Bruce Allen Bill Davidsen wrote: > Gwendal Grignou wrote: >> About ata1:0 problem, as reported in the bugzilla bug: I would try to >> disable NCQ to see if it helps. Your disks firmware might not fully >> support it. >> >> You can either add the parameter "libata.force=noncq" when loading >> your kernel, or set queue_depth to 1 for all the Seagate drives behind >> the Marvell MV88SX6081 controller. >> >> About ata5:0 , someone - in user space probably - is trying to do a >> SMART ENABLE operation, but the device ignores it. I don't know which >> device you are using, but I assume it does not support ATA SMART >> feature set. Timeout is an acceptable but not a nice way to answer, a >> cancel would have been better; check if there is a firmware upgrade >> for your device. >> > > You certainly called the SMART issue, I was wondering why a new > distribution install on some older hardware was getting all the errors, > clearly the Fedora "smartd" doesn't check SMART capability before trying > to enable the feature. Oddly the drive on which I see this does reply to > SMART requests, so the firmware must be "semi-functional." Not a > problem, in my case the drive is just used for testing handling of hot > swap, and has no data of any value. Can you post full kernel log including the boot messages and the error messages? Also, please attach the output of hdparm -I on the drive which fails the smart command. (cc'ing Bruce, hi!) Bruce, this is the second report I see about drive timing out SMART ENABLE OPERATIONS. Does anything ring a bell? Thanks. -- tejun