linux-kernel - Re: exception Emask 0x0 SAct 0x1 / SErr 0x0 action 0x2 frozen

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 29 Sep 2008 17:13:33 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Bill Davidsen <davidsen@....com>
CC:	Gwendal Grignou <gwendal@...gle.com>,
	Justin Piszcz <jpiszcz@...idpixels.com>,
	Brian Rademacher <rad@...files.net>, linux-ide@...r.kernel.org,
	linux-raid@...r.kernel.org, linux-kernel@...r.kernel.org,
	Bruce Allen <ballen@...vity.phys.uwm.edu>
Subject: Re: exception Emask 0x0 SAct 0x1 / SErr 0x0 action 0x2 frozen

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/