Message-ID: <46DEE617.4050004@rtr.ca>
Date: Wed, 05 Sep 2007 13:23:35 -0400
From: Mark Lord <liml@rtr.ca>
User-Agent: Thunderbird 2.0.0.6 (X11/20070728)
MIME-Version: 1.0
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Tejun Heo <htejun@gmail.com>, michal.k.k.piotrowski@gmail.com,
       bryan@arbores.ca, linux-kernel@vger.kernel.org,
       linux-ide@vger.kernel.org
Subject: Re: Stardom SATA HSM violation
References: <46CFA08E.6090604@arbores.ca>	<6bffcb0e0708261610g10d9c59ck5789fac6feca9f42@mail.gmail.com>	<46DBCB6C.8080206@gmail.com> <20070905095327.6277d054.akpm@linux-foundation.org>
In-Reply-To: <20070905095327.6277d054.akpm@linux-foundation.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 3624
Lines: 89

Andrew Morton wrote:
>> On Mon, 03 Sep 2007 17:53:00 +0900 Tejun Heo <htejun@gmail.com> wrote:
>> Michal Piotrowski wrote:
>>> Hi,
>>>
>>> [Adding linux-ide to CC]
>>>
>>> On 25/08/07, Bryan Woods <bryan@arbores.ca> wrote:
>>>> Hi KML
>>>>
>>>> I am installing gentoo 2007.0 (kernel 2.6.19) on a dual AMD Opteron server (total of 4 cores). The hard disk is a Stardom 2611-2S-S1 device: actually two 250GB drives in a RAID0 config managed by the device itself - it should appear to the kernel as one SATA drive. If it matters, the underlying HDs are "Seagate Barracuda 7200 10"s. Here's the device:
>>>>
>>>>  http://www.synetic.net/Synetic-Products/Stardoms/SR-2611-SA/Stardom-2611.htm
>>>>
>>>> During the install and at different points in the process I get an "HSM violation" and the system becomes unresponsive. It looks like a similar situation to:
>>>>
>>>>   http://lkml.org/lkml/2007/6/6/195
>>>>
>>>> Will more recent kernels work with this hardware (should I keep it and try the install again) or should I switch hardware to something more compatible (like an Adaptec card)?
>>>>
>>>> Thanks!
>>>> Bryan
>>>>
>>>> --
>>>> console output:
>>>>
>>>> tag 0 cmd 0x39 Emask 0x2 stat 0x58 err 0x0 (HSM violation)
>>>> exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
>>>>
>>>> --
>>>> Output from hdparm -I /dev/sda:
>>>>
>>>> /dev/sda:
>>>>
>>>> ATA device, with non-removable media
>>>>         Model Number:   STARDOM V.36.A0B
>>>>         Serial Number:
>>>>         Firmware Revision:      V.36.A0B
>>>> Standards:
>>>>         Used: ATA/ATAPI-6 T13 1410D revision 0
>>>>
>>>> [snip]
>>>>
>>>> Commands/features:
>>>>         Enabled Supported:
>>>>         *       SMART feature set
>>>>         *       Power Management feature set
>>>>         *       Advanced Power Management feature set
>>>>         *       48-bit Address feature set
>>>>         *       Mandatory FLUSH_CACHE
>>>>         *       SATA-I signaling speed (1.5 Gb/s)
>>>>         *       SATA-II signaling speed (3.0 Gb/s)
>>>>
>>>> --
>>>> Parts of dmesg:
>>>> libata version 2.00 loaded
>>>> sata_nv 0000:00:05.0: version 2.0
>>>> ata1: SATA max UDMA/133 cmd 0xD480 ctl 0xD402 bmdma 0xCC00 irq 21
>>>> ata2: SATA max UDMA/133 cmd 0xD080 ctl 0xD002 bmdma 0xCC08 irq 21
>>>> scsi0 : sata_nv
>>>> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>>>> ata1.00: ATA-6, max UDMA/133,976794112 sectors: LBA48
>>>> ata1.00: ata1: dev 0 multi count 1
>>>> ata1.00: applying bridge limits
>>>> ata1.00: configured for UDMA/100
>> Please post full dmesg and full 'hdparm -I' result.  Also, if possible,
>> please try 2.6.22.5.  Even if it doesn't fix the problem, it would
>> report error conditions better.
> 
> Presumably in the week and a half between Bryan's report and your request,
> Bryan has gone off and got an adaptec card.  Bryan, it would be helpful if
> you could rebuild the original systam and help us get to the bottom of this
> bug, thanks.

I reported a very similar bug back a few releases ago.
Anyone who wants to try it themselves, can do this with hdparm-7.7 (from sourceforge):

    hdparm --drq-hsm-error /dev/sda

Whether or not it hangs the machine does depend upon exactly which SATA LLD is used,
and what model/revision of drive is installed.  But if it hangs for you (eg. Tejun),
then you now have a way to reproduce a HSM error "on demand" for testing.  :)

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