From: Bill Davidsen <davidsen@tmr.com>
To: Tejun Heo <tj@kernel.org>
Cc: Gwendal Grignou <gwendal@google.com>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
Brian Rademacher <rad@radfiles.net>,
linux-ide@vger.kernel.org, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bruce Allen <ballen@gravity.phys.uwm.edu>
Subject: Re: exception Emask 0x0 SAct 0x1 / SErr 0x0 action 0x2 frozen
Date: Wed, 01 Oct 2008 11:09:18 -0400 [thread overview]
Message-ID: <48E3929E.7060501@tmr.com> (raw)
In-Reply-To: <48E08E2D.6050905@kernel.org>
Tejun Heo wrote:
> 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.
>
Belatedly, the drive was retired after I got thinking about it, I'm just
calling it an old bad drive and leaving it at that. I'm not goinf to
re-install a dubious 20GB drive, it's out of the hot-swap carrier,
cleared with dban, and in the recycle bin. You seem to have far better
examples of the issue, so I don't feel I would hold up progress. :-)
> (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.
>
>
--
Bill Davidsen <davidsen@tmr.com>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
next prev parent reply other threads:[~2008-10-01 15:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3E6D0C24877245C3A5A327129A7B4CA7@909927SOSLA>
[not found] ` <alpine.DEB.1.10.0809220404400.18908@p34.internal.lan>
[not found] ` <5A4A9A3B0AAA4A20A33BC2D578F5F75F@909927SOSLA>
[not found] ` <alpine.DEB.1.10.0809220828490.23159@p34.internal.lan>
[not found] ` <5419A02543384E69AF2BA82FF6E66C14@909927SOSLA>
[not found] ` <alpine.DEB.1.10.0809220903400.23159@p34.internal.lan>
[not found] ` <4B1ABD0393EF40FFB0A12242FE8356AF@909927SOSLA>
2008-09-22 13:19 ` exception Emask 0x0 SAct 0x1 / SErr 0x0 action 0x2 frozen Justin Piszcz
2008-09-22 13:26 ` Justin Piszcz
2008-09-22 13:26 ` Justin Piszcz
2008-09-23 18:14 ` Gwendal Grignou
2008-09-23 20:59 ` Brian Rademacher
2008-09-23 20:59 ` Brian Rademacher
2008-09-25 15:17 ` Bill Davidsen
2008-09-29 8:13 ` Tejun Heo
2008-09-30 20:47 ` Tom Mortensen
2008-09-30 21:18 ` Justin Piszcz
2008-10-01 3:50 ` Mr. James W. Laferriere
2008-10-01 8:06 ` Justin Piszcz
2008-10-01 11:12 ` Justin Piszcz
2008-10-04 2:27 ` Tejun Heo
2008-10-04 8:11 ` Justin Piszcz
2008-10-05 0:23 ` Justin Piszcz
2008-10-05 0:29 ` berk walker
2008-10-05 0:29 ` berk walker
2008-10-10 19:13 ` Justin Piszcz
2008-10-10 19:27 ` Alan Cox
2008-10-01 15:09 ` Bill Davidsen [this message]
2008-09-30 22:04 Christian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48E3929E.7060501@tmr.com \
--to=davidsen@tmr.com \
--cc=ballen@gravity.phys.uwm.edu \
--cc=gwendal@google.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=rad@radfiles.net \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.