Re: sata NCQ blacklist entry

Re: sata NCQ blacklist entry

[Robert Hancock]

Tejun Heo wrote:
> Florian La Roche wrote:
>> Hello all,
>>
>> I've taking email addresses from the last NCQ blacklist changes going
>> into the kernel.
>> This Fujitsu drive also gives me spurious command completions. Detailed
>> output also available at https://bugzilla.redhat.com/show_bug.cgi?id=366181.
>>
>> Let me know if you need more info or anything else.
>>
>> --- drivers/ata/libata-core.c
>> +++ drivers/ata/libata-core.c
>> @@ -4222,6 +4222,7 @@
>>  	{ "WDC WD740ADFD-00NLR1", NULL,		ATA_HORKAGE_NONCQ, },
>>  	{ "WDC WD3200AAJS-00RYA0", "12.01B01",	ATA_HORKAGE_NONCQ, },
>>  	{ "FUJITSU MHV2080BH",	"00840028",	ATA_HORKAGE_NONCQ, },
>> +	{ "FUJITSU MHW2160BJ G2",       NULL,           ATA_HORKAGE_NONCQ },
>>  	{ "ST9120822AS",	"3.CLF",	ATA_HORKAGE_NONCQ, },
>>  	{ "ST9160821AS",	"3.CLF",	ATA_HORKAGE_NONCQ, },
>>  	{ "ST9160821AS",	"3.ALD",	ATA_HORKAGE_NONCQ, },
> 
> Thanks.  We're currently trying to find out what's actually going on
> with all these drives.  At first, drives which got blacklisted aren't
> many and made sense (had other problems with NCQ, etc..) but with new
> generation drives from many vendors showing the same symptom, we aren't
> too sure now.
> 
> I'll keep your email in my todo list and add the drive to the blacklist
> once the problem is verified.

I agree that something seems fishy with this. It seems unlikely that 
this many drives from multiple vendors would have the exact same, 
relatively obscure problem..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/

Re: sata NCQ blacklist entry

[Robert Hancock]

Luca Tettamanti wrote:
> On Nov 7, 2007 1:55 PM, Tejun Heo <htejun@gmail.com> wrote:
>> Florian La Roche wrote:
>>> Hello all,
>>>
>>> I've taking email addresses from the last NCQ blacklist changes going
>>> into the kernel.
>>> This Fujitsu drive also gives me spurious command completions. Detailed
>>> output also available at https://bugzilla.redhat.com/show_bug.cgi?id=366181.
>>>
>>> Let me know if you need more info or anything else.
>>>
>>> --- drivers/ata/libata-core.c
>>> +++ drivers/ata/libata-core.c
>>> @@ -4222,6 +4222,7 @@
>>>       { "WDC WD740ADFD-00NLR1", NULL,         ATA_HORKAGE_NONCQ, },
>>>       { "WDC WD3200AAJS-00RYA0", "12.01B01",  ATA_HORKAGE_NONCQ, },
>>>       { "FUJITSU MHV2080BH",  "00840028",     ATA_HORKAGE_NONCQ, },
>>> +     { "FUJITSU MHW2160BJ G2",       NULL,           ATA_HORKAGE_NONCQ },
>>>       { "ST9120822AS",        "3.CLF",        ATA_HORKAGE_NONCQ, },
>>>       { "ST9160821AS",        "3.CLF",        ATA_HORKAGE_NONCQ, },
>>>       { "ST9160821AS",        "3.ALD",        ATA_HORKAGE_NONCQ, },
>> Thanks.  We're currently trying to find out what's actually going on
>> with all these drives.  At first, drives which got blacklisted aren't
>> many and made sense (had other problems with NCQ, etc..) but with new
>> generation drives from many vendors showing the same symptom, we aren't
>> too sure now.
> 
> Is there a way to tell whether Windows is using NCQ or not? I checked
> the system log (or whatever it's called) on my notebook and is clean
> but I'm not sure it's using NCQ (I don't even know if it'd log
> spurious completions somewhere).

Which driver is installed for the SATA controller in Windows, the 
chipset-manufacturer-provided AHCI driver or the default Microsoft 
driver? You'd need the AHCI driver installed for NCQ to be used.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/

Re: sata NCQ blacklist entry

[Luca Tettamanti]

On Nov 9, 2007 12:32 AM, Robert Hancock <hancockr@shaw.ca> wrote:
> Luca Tettamanti wrote:
> > On Nov 7, 2007 1:55 PM, Tejun Heo <htejun@gmail.com> wrote:
> >> Florian La Roche wrote:
> >>> Hello all,
> >>>
> >>> I've taking email addresses from the last NCQ blacklist changes going
> >>> into the kernel.
> >>> This Fujitsu drive also gives me spurious command completions. Detailed
> >>> output also available at https://bugzilla.redhat.com/show_bug.cgi?id=366181.
> >>>
> >>> Let me know if you need more info or anything else.
> >>>
> >>> --- drivers/ata/libata-core.c
> >>> +++ drivers/ata/libata-core.c
> >>> @@ -4222,6 +4222,7 @@
> >>>       { "WDC WD740ADFD-00NLR1", NULL,         ATA_HORKAGE_NONCQ, },
> >>>       { "WDC WD3200AAJS-00RYA0", "12.01B01",  ATA_HORKAGE_NONCQ, },
> >>>       { "FUJITSU MHV2080BH",  "00840028",     ATA_HORKAGE_NONCQ, },
> >>> +     { "FUJITSU MHW2160BJ G2",       NULL,           ATA_HORKAGE_NONCQ },
> >>>       { "ST9120822AS",        "3.CLF",        ATA_HORKAGE_NONCQ, },
> >>>       { "ST9160821AS",        "3.CLF",        ATA_HORKAGE_NONCQ, },
> >>>       { "ST9160821AS",        "3.ALD",        ATA_HORKAGE_NONCQ, },
> >> Thanks.  We're currently trying to find out what's actually going on
> >> with all these drives.  At first, drives which got blacklisted aren't
> >> many and made sense (had other problems with NCQ, etc..) but with new
> >> generation drives from many vendors showing the same symptom, we aren't
> >> too sure now.
> >
> > Is there a way to tell whether Windows is using NCQ or not? I checked
> > the system log (or whatever it's called) on my notebook and is clean
> > but I'm not sure it's using NCQ (I don't even know if it'd log
> > spurious completions somewhere).
>
> Which driver is installed for the SATA controller in Windows, the
> chipset-manufacturer-provided AHCI driver or the default Microsoft
> driver? You'd need the AHCI driver installed for NCQ to be used.

I'm aware of this. I'm using the AHCI driver (from Intel). Still, I
don't know if it's really used or limited like under Linux.

Luca

Re: sata NCQ blacklist entry

[Tejun Heo]

Florian La Roche wrote:
> Hello all,
> 
> I've taking email addresses from the last NCQ blacklist changes going
> into the kernel.
> This Fujitsu drive also gives me spurious command completions. Detailed
> output also available at https://bugzilla.redhat.com/show_bug.cgi?id=366181.
> 
> Let me know if you need more info or anything else.
> 
> --- drivers/ata/libata-core.c
> +++ drivers/ata/libata-core.c
> @@ -4222,6 +4222,7 @@
>  	{ "WDC WD740ADFD-00NLR1", NULL,		ATA_HORKAGE_NONCQ, },
>  	{ "WDC WD3200AAJS-00RYA0", "12.01B01",	ATA_HORKAGE_NONCQ, },
>  	{ "FUJITSU MHV2080BH",	"00840028",	ATA_HORKAGE_NONCQ, },
> +	{ "FUJITSU MHW2160BJ G2",       NULL,           ATA_HORKAGE_NONCQ },
>  	{ "ST9120822AS",	"3.CLF",	ATA_HORKAGE_NONCQ, },
>  	{ "ST9160821AS",	"3.CLF",	ATA_HORKAGE_NONCQ, },
>  	{ "ST9160821AS",	"3.ALD",	ATA_HORKAGE_NONCQ, },

Thanks.  We're currently trying to find out what's actually going on
with all these drives.  At first, drives which got blacklisted aren't
many and made sense (had other problems with NCQ, etc..) but with new
generation drives from many vendors showing the same symptom, we aren't
too sure now.

I'll keep your email in my todo list and add the drive to the blacklist
once the problem is verified.

Thanks.

-- 
tejun

Re: sata NCQ blacklist entry

[Luca Tettamanti]

On Nov 7, 2007 1:55 PM, Tejun Heo <htejun@gmail.com> wrote:
> Florian La Roche wrote:
> > Hello all,
> >
> > I've taking email addresses from the last NCQ blacklist changes going
> > into the kernel.
> > This Fujitsu drive also gives me spurious command completions. Detailed
> > output also available at https://bugzilla.redhat.com/show_bug.cgi?id=366181.
> >
> > Let me know if you need more info or anything else.
> >
> > --- drivers/ata/libata-core.c
> > +++ drivers/ata/libata-core.c
> > @@ -4222,6 +4222,7 @@
> >       { "WDC WD740ADFD-00NLR1", NULL,         ATA_HORKAGE_NONCQ, },
> >       { "WDC WD3200AAJS-00RYA0", "12.01B01",  ATA_HORKAGE_NONCQ, },
> >       { "FUJITSU MHV2080BH",  "00840028",     ATA_HORKAGE_NONCQ, },
> > +     { "FUJITSU MHW2160BJ G2",       NULL,           ATA_HORKAGE_NONCQ },
> >       { "ST9120822AS",        "3.CLF",        ATA_HORKAGE_NONCQ, },
> >       { "ST9160821AS",        "3.CLF",        ATA_HORKAGE_NONCQ, },
> >       { "ST9160821AS",        "3.ALD",        ATA_HORKAGE_NONCQ, },
>
> Thanks.  We're currently trying to find out what's actually going on
> with all these drives.  At first, drives which got blacklisted aren't
> many and made sense (had other problems with NCQ, etc..) but with new
> generation drives from many vendors showing the same symptom, we aren't
> too sure now.

Is there a way to tell whether Windows is using NCQ or not? I checked
the system log (or whatever it's called) on my notebook and is clean
but I'm not sure it's using NCQ (I don't even know if it'd log
spurious completions somewhere).

Luca

Re: sata NCQ blacklist entry

[Bjoern Olausson]

On 11/7/07, Tejun Heo <htejun@gmail.com> wrote:
>
> Thanks.  We're currently trying to find out what's actually going on
> with all these drives.  At first, drives which got blacklisted aren't
> many and made sense (had other problems with NCQ, etc..) but with new
> generation drives from many vendors showing the same symptom, we aren't
> too sure now.
>
> I'll keep your email in my todo list and add the drive to the blacklist
> once the problem is verified.
>
> Thanks.

Something new on the NCQ front?
Just asking if you need someone to test some of your ideas?

I got the "WDC WD740ADFD-00NLR1"

by the way, and OT, did the Plextor DVD-RW drive reach you, Tejun?

Re: sata NCQ blacklist entry

[Tejun Heo]

Bjoern Olausson wrote:
> On 11/7/07, Tejun Heo <htejun@gmail.com> wrote:
>> Thanks.  We're currently trying to find out what's actually going on
>> with all these drives.  At first, drives which got blacklisted aren't
>> many and made sense (had other problems with NCQ, etc..) but with new
>> generation drives from many vendors showing the same symptom, we aren't
>> too sure now.
>>
>> I'll keep your email in my todo list and add the drive to the blacklist
>> once the problem is verified.
>>
>> Thanks.
> 
> Something new on the NCQ front?
> Just asking if you need someone to test some of your ideas?
> 
> I got the "WDC WD740ADFD-00NLR1"

I now have affected drives on my desk and am gonna try reproduce it.  My
gut feeling says it's timing related problem on controller / driver
side.  Please wait a bit.

> by the way, and OT, did the Plextor DVD-RW drive reach you, Tejun?

No, not yet.  Do you have a tracking number or something?

Thanks.

-- 
tejun

Re: sata NCQ blacklist entry

[Bjoern Olausson]

On 11/29/07, Tejun Heo <htejun@gmail.com> wrote:
>
> I now have affected drives on my desk and am gonna try reproduce it.  My
> gut feeling says it's timing related problem on controller / driver
> side.  Please wait a bit.
>
Okay, no problem, I am just curious.

> > by the way, and OT, did the Plextor DVD-RW drive reach you, Tejun?
>
> No, not yet.  Do you have a tracking number or something?
>
No, I havn't... all I got is the bill... but that doesn't help because
we choosed to use shipment without enshurance... there is no tracking
number. Mhhh that sucks... i can't get rid of the bad feeling that it
got lost. But I'll try to make some checks.

CU
Bjoern

Re: sata NCQ blacklist entry

[Bjoern Olausson]

On 11/29/07, Tejun Heo <htejun@gmail.com> wrote:
>
> I now have affected drives on my desk and am gonna try reproduce it.  My
> gut feeling says it's timing related problem on controller / driver
> side.  Please wait a bit.
>

> > by the way, and OT, did the Plextor DVD-RW drive reach you, Tejun?
>
> No, not yet.  Do you have a tracking number or something?
>
> Thanks.

Re: sata NCQ blacklist entry

[Andrew Morton]

On Tue, 13 Nov 2007 21:55:15 +0100 Jan-Simon M__ller <dl9pf@gmx.de> wrote:

> Hi!

You removed from cc the guys who are most likely to fix this.  Please always
do reply-to-all.

> Just using kernel 2.6.24-rc2 (325d22df7b19e0116aff3391d3a03f73d0634ded).
> 
> When booting the system hangs, using the emergency-sync a couple of times gets 
> the system to go on at some point. 
> Its always around starting X/Firewall (can't actually say whats done in this 
> moment).
> 
> Looking at dmesg i found this (NCQ disabled ...)
> 
> dmesg output
> 
> ata1.00: exception Emask 0x2 SAct 0x4 SErr 0x0 action 0x2 frozen
> ata1.00: spurious completions during NCQ issue=0x0 SAct=0x4 
> FIS=004040a1:00000002
> ata1.00: cmd 61/08:10:bc:b2:5d/00:00:08:00:00/40 tag 2 cdb 0x0 data 4096 out
>          res 40/00:14:bc:b2:5d/00:00:08:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1: soft resetting link
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: configured for UDMA/133
> ata1: EH complete
> sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support 
> DPO or FUA
> ata1.00: NCQ disabled due to excessive errors
> ata1.00: exception Emask 0x2 SAct 0xfffd3 SErr 0x0 action 0x2 frozen
> ata1.00: spurious completions during NCQ issue=0x0 SAct=0xfffd3 
> FIS=004040a1:00000020
> ata1.00: cmd 60/10:00:14:05:69/00:00:06:00:00/40 tag 0 cdb 0x0 data 8192 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/08:08:cc:dd:12/00:00:04:00:00/40 tag 1 cdb 0x0 data 4096 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/18:20:84:54:a3/00:00:05:00:00/40 tag 4 cdb 0x0 data 12288 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/08:30:bc:b1:07/00:00:06:00:00/40 tag 6 cdb 0x0 data 4096 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/08:38:dc:b1:07/00:00:06:00:00/40 tag 7 cdb 0x0 data 4096 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/10:40:3c:b2:07/00:00:06:00:00/40 tag 8 cdb 0x0 data 8192 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/08:48:2c:cf:07/00:00:06:00:00/40 tag 9 cdb 0x0 data 4096 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/08:50:3c:cf:07/00:00:06:00:00/40 tag 10 cdb 0x0 data 4096 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/08:58:64:b4:12/00:00:04:00:00/40 tag 11 cdb 0x0 data 4096 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/28:60:6c:b4:12/00:00:04:00:00/40 tag 12 cdb 0x0 data 20480 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/f8:68:7c:e1:07/00:00:06:00:00/40 tag 13 cdb 0x0 data 126976 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/08:70:a4:04:69/00:00:06:00:00/40 tag 14 cdb 0x0 data 4096 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/18:78:b4:04:69/00:00:06:00:00/40 tag 15 cdb 0x0 data 12288 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/08:80:a4:5c:6a/00:00:06:00:00/40 tag 16 cdb 0x0 data 4096 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/20:88:2c:05:69/00:00:06:00:00/40 tag 17 cdb 0x0 data 16384 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/30:90:54:05:69/00:00:06:00:00/40 tag 18 cdb 0x0 data 24576 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/08:98:94:05:69/00:00:06:00:00/40 tag 19 cdb 0x0 data 4096 in
>          res 40/00:04:14:05:69/00:00:06:00:00/40 Emask 0x2 (HSM violation)
> ata1.00: status: { DRDY }
> ata1: soft resetting link
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: configured for UDMA/133
> ata1: EH complete
> sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support 
> DPO or FUA
> 
> 
> 
> hdparm -i /dev/sda
> 
> /dev/sda:
> 
>  Model=WDC WD2500BEVS-22UST0                   , FwRev=01.01A01, SerialNo=     
> WD-WXE807E07297
>  Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
>  RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50
>  BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=?16?
>  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
>  IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
>  PIO modes:  pio0 pio3 pio4
>  DMA modes:  mdma0 mdma1 mdma2
>  UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5
>  AdvancedPM=yes: disabled (255) WriteCache=enabled
>  Drive conforms to: Unspecified:  ATA/ATAPI-1,2,3,4,5,6,7
> 
>  * signifies the current active mode
> 

So is this problem (which in another email you attributed to smartd) also
present in 2.6.23?

And is is still present in 2.6.24-rc3?

Thanks.

Re: sata NCQ blacklist entry

[Jan-Simon Möller]

Am Freitag 23 November 2007 08:21:09 schrieb Andrew Morton:
> On Tue, 13 Nov 2007 21:55:15 +0100 Jan-Simon M__ller <dl9pf@gmx.de> wrote:
> > Hi!
>
> You removed from cc the guys who are most likely to fix this.  Please
> always do reply-to-all.
Sri, will remember that.
>
> > Just using kernel 2.6.24-rc2 (325d22df7b19e0116aff3391d3a03f73d0634ded).
> >
>
> So is this problem (which in another email you attributed to smartd) 
Even without smartd in my default runlevel it happens at some point.

> also 
> present in 2.6.23?
I compiled and tested 2.6.23.8. Smartd enabled, nothing noticed, dmesg is 
really clean:
dmesg | grep ata
ACPI: SSDT 7F6D3C3F, 02DD (r1 SataRe SataAhci     1000 INTL 20060912)
PERCPU: Allocating 46888 bytes of per cpu data
Memory: 2042960k/2087744k available (2062k kernel code, 44396k reserved, 982k 
data, 324k init)
ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
libata version 2.21 loaded.
ata1: SATA max UDMA/133 cmd 0xffffc2000034e100 ctl 0x0000000000000000 bmdma 
0x0000000000000000 irq 4347
ata2: SATA max UDMA/133 cmd 0xffffc2000034e180 ctl 0x0000000000000000 bmdma 
0x0000000000000000 irq 4347
ata3: SATA max UDMA/133 cmd 0xffffc2000034e200 ctl 0x0000000000000000 bmdma 
0x0000000000000000 irq 4347
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-8: WDC WD2500BEVS-22UST0, 01.01A01, max UDMA/133
ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
ata2: SATA link down (SStatus 0 SControl 300)
ata3: SATA link down (SStatus 0 SControl 300)
ata_piix 0000:00:1f.1: version 2.12
scsi3 : ata_piix
scsi4 : ata_piix
ata4: PATA max UDMA/100 cmd 0x00000000000101f0 ctl 0x00000000000103f6 bmdma 
0x0000000000011810 irq 14
ata5: PATA max UDMA/100 cmd 0x0000000000010170 ctl 0x0000000000010376 bmdma 
0x0000000000011818 irq 15
ata4.00: ATAPI: HL-DT-ST DVDRAM GSA-T20N, WW01, max UDMA/33
ata4.00: configured for UDMA/33
EXT3-fs: mounted filesystem with ordered data mode.



>
> And is is still present in 2.6.24-rc3?
Went back to 2.6.24-rc3 ...
Yes, but not at boot when smartd is started.

dmesg | grep ata
ACPI: SSDT 7F6D3C3F, 02DD (r1 SataRe SataAhci     1000 INTL 20060912)
PERCPU: Allocating 46968 bytes of per cpu data
Memory: 2048732k/2087744k available (2219k kernel code, 38624k reserved, 992k 
data, 344k init)
ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
libata version 3.00 loaded.
ata1: SATA max UDMA/133 abar m2048@0xfc404000 port 0xfc404100 irq 4347
ata2: SATA max UDMA/133 abar m2048@0xfc404000 port 0xfc404180 irq 4347
ata3: SATA max UDMA/133 abar m2048@0xfc404000 port 0xfc404200 irq 4347
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-8: WDC WD2500BEVS-22UST0, 01.01A01, max UDMA/133
ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
ata2: SATA link down (SStatus 0 SControl 300)
ata3: SATA link down (SStatus 0 SControl 300)
ata_piix 0000:00:1f.1: version 2.12
scsi3 : ata_piix
scsi4 : ata_piix
ata4: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x1810 irq 14
ata5: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x1818 irq 15
ata4.00: ATAPI: HL-DT-ST DVDRAM GSA-T20N, WW01, max UDMA/33
ata4.00: configured for UDMA/33
EXT3-fs: mounted filesystem with ordered data mode.
ata1.00: exception Emask 0x2 SAct 0x73 SErr 0x0 action 0x2 frozen
ata1.00: spurious completions during NCQ issue=0x0 SAct=0x73 
FIS=004040a1:00000008
ata1.00: cmd 60/10:00:d4:82:31/00:00:07:00:00/40 tag 0 cdb 0x0 data 8192 in
ata1.00: status: { DRDY }
ata1.00: cmd 60/08:08:9c:e5:cc/00:00:08:00:00/40 tag 1 cdb 0x0 data 4096 in
ata1.00: status: { DRDY }
ata1.00: cmd 60/10:20:24:61:25/00:00:09:00:00/40 tag 4 cdb 0x0 data 8192 in
ata1.00: status: { DRDY }
ata1.00: cmd 60/58:28:c4:65:25/00:00:09:00:00/40 tag 5 cdb 0x0 data 45056 in
ata1.00: status: { DRDY }
ata1.00: cmd 60/20:30:7c:f6:a3/00:00:05:00:00/40 tag 6 cdb 0x0 data 16384 in
ata1.00: status: { DRDY }
ata1: soft resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x2 SAct 0x187 SErr 0x0 action 0x2 frozen
ata1.00: spurious completions during NCQ issue=0x0 SAct=0x187 
FIS=004040a1:00000040
ata1.00: cmd 60/08:00:ec:af:10/00:00:04:00:00/40 tag 0 cdb 0x0 data 4096 in
ata1.00: status: { DRDY }
ata1.00: cmd 60/10:08:8c:e6:d8/00:00:04:00:00/40 tag 1 cdb 0x0 data 8192 in
ata1.00: status: { DRDY }
ata1.00: cmd 60/20:10:24:1a:da/00:00:04:00:00/40 tag 2 cdb 0x0 data 16384 in
ata1.00: status: { DRDY }
ata1.00: cmd 61/01:38:15:b3:30/00:00:07:00:00/40 tag 7 cdb 0x0 data 512 out
ata1.00: status: { DRDY }
ata1.00: cmd 61/10:40:1c:b3:30/00:00:07:00:00/40 tag 8 cdb 0x0 data 8192 out
ata1.00: status: { DRDY }
ata1: soft resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/133
ata1: EH complete


Thanks !
Best regards,
Jan-Simon

Re: sata NCQ blacklist entry

[Rafael J. Wysocki]

On Saturday, 24 of November 2007, Jan-Simon Möller wrote:
> Am Freitag 23 November 2007 08:21:09 schrieb Andrew Morton:
> > On Tue, 13 Nov 2007 21:55:15 +0100 Jan-Simon M__ller <dl9pf@gmx.de> wrote:
> > > Hi!
> >
> > You removed from cc the guys who are most likely to fix this.  Please
> > always do reply-to-all.
> Sri, will remember that.
> >
> > > Just using kernel 2.6.24-rc2 (325d22df7b19e0116aff3391d3a03f73d0634ded).
> > >
> >
> > So is this problem (which in another email you attributed to smartd) 
> Even without smartd in my default runlevel it happens at some point.
> 
> > also 
> > present in 2.6.23?
> I compiled and tested 2.6.23.8. Smartd enabled, nothing noticed, dmesg is 
> really clean:
> dmesg | grep ata
> ACPI: SSDT 7F6D3C3F, 02DD (r1 SataRe SataAhci     1000 INTL 20060912)
> PERCPU: Allocating 46888 bytes of per cpu data
> Memory: 2042960k/2087744k available (2062k kernel code, 44396k reserved, 982k 
> data, 324k init)
> ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
> ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
> libata version 2.21 loaded.
> ata1: SATA max UDMA/133 cmd 0xffffc2000034e100 ctl 0x0000000000000000 bmdma 
> 0x0000000000000000 irq 4347
> ata2: SATA max UDMA/133 cmd 0xffffc2000034e180 ctl 0x0000000000000000 bmdma 
> 0x0000000000000000 irq 4347
> ata3: SATA max UDMA/133 cmd 0xffffc2000034e200 ctl 0x0000000000000000 bmdma 
> 0x0000000000000000 irq 4347
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: ATA-8: WDC WD2500BEVS-22UST0, 01.01A01, max UDMA/133
> ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
> ata1.00: configured for UDMA/133
> ata2: SATA link down (SStatus 0 SControl 300)
> ata3: SATA link down (SStatus 0 SControl 300)
> ata_piix 0000:00:1f.1: version 2.12
> scsi3 : ata_piix
> scsi4 : ata_piix
> ata4: PATA max UDMA/100 cmd 0x00000000000101f0 ctl 0x00000000000103f6 bmdma 
> 0x0000000000011810 irq 14
> ata5: PATA max UDMA/100 cmd 0x0000000000010170 ctl 0x0000000000010376 bmdma 
> 0x0000000000011818 irq 15
> ata4.00: ATAPI: HL-DT-ST DVDRAM GSA-T20N, WW01, max UDMA/33
> ata4.00: configured for UDMA/33
> EXT3-fs: mounted filesystem with ordered data mode.
> 
> 
> 
> >
> > And is is still present in 2.6.24-rc3?
> Went back to 2.6.24-rc3 ...
> Yes, but not at boot when smartd is started.
> 
> dmesg | grep ata
> ACPI: SSDT 7F6D3C3F, 02DD (r1 SataRe SataAhci     1000 INTL 20060912)
> PERCPU: Allocating 46968 bytes of per cpu data
> Memory: 2048732k/2087744k available (2219k kernel code, 38624k reserved, 992k 
> data, 344k init)
> ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
> libata version 3.00 loaded.
> ata1: SATA max UDMA/133 abar m2048@0xfc404000 port 0xfc404100 irq 4347
> ata2: SATA max UDMA/133 abar m2048@0xfc404000 port 0xfc404180 irq 4347
> ata3: SATA max UDMA/133 abar m2048@0xfc404000 port 0xfc404200 irq 4347
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: ATA-8: WDC WD2500BEVS-22UST0, 01.01A01, max UDMA/133
> ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
> ata1.00: configured for UDMA/133
> ata2: SATA link down (SStatus 0 SControl 300)
> ata3: SATA link down (SStatus 0 SControl 300)
> ata_piix 0000:00:1f.1: version 2.12
> scsi3 : ata_piix
> scsi4 : ata_piix
> ata4: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x1810 irq 14
> ata5: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x1818 irq 15
> ata4.00: ATAPI: HL-DT-ST DVDRAM GSA-T20N, WW01, max UDMA/33
> ata4.00: configured for UDMA/33
> EXT3-fs: mounted filesystem with ordered data mode.
> ata1.00: exception Emask 0x2 SAct 0x73 SErr 0x0 action 0x2 frozen
> ata1.00: spurious completions during NCQ issue=0x0 SAct=0x73 
> FIS=004040a1:00000008
> ata1.00: cmd 60/10:00:d4:82:31/00:00:07:00:00/40 tag 0 cdb 0x0 data 8192 in
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/08:08:9c:e5:cc/00:00:08:00:00/40 tag 1 cdb 0x0 data 4096 in
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/10:20:24:61:25/00:00:09:00:00/40 tag 4 cdb 0x0 data 8192 in
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/58:28:c4:65:25/00:00:09:00:00/40 tag 5 cdb 0x0 data 45056 in
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/20:30:7c:f6:a3/00:00:05:00:00/40 tag 6 cdb 0x0 data 16384 in
> ata1.00: status: { DRDY }
> ata1: soft resetting link
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: configured for UDMA/133
> ata1: EH complete
> ata1.00: exception Emask 0x2 SAct 0x187 SErr 0x0 action 0x2 frozen
> ata1.00: spurious completions during NCQ issue=0x0 SAct=0x187 
> FIS=004040a1:00000040
> ata1.00: cmd 60/08:00:ec:af:10/00:00:04:00:00/40 tag 0 cdb 0x0 data 4096 in
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/10:08:8c:e6:d8/00:00:04:00:00/40 tag 1 cdb 0x0 data 8192 in
> ata1.00: status: { DRDY }
> ata1.00: cmd 60/20:10:24:1a:da/00:00:04:00:00/40 tag 2 cdb 0x0 data 16384 in
> ata1.00: status: { DRDY }
> ata1.00: cmd 61/01:38:15:b3:30/00:00:07:00:00/40 tag 7 cdb 0x0 data 512 out
> ata1.00: status: { DRDY }
> ata1.00: cmd 61/10:40:1c:b3:30/00:00:07:00:00/40 tag 8 cdb 0x0 data 8192 out
> ata1.00: status: { DRDY }
> ata1: soft resetting link
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: configured for UDMA/133
> ata1: EH complete

Please visit http://bugzilla.kernel.org/show_bug.cgi?id=9446 and provide the
information requested by Comment #1.

Thanks,
Rafael