Re: Spurious completions during NCQ
Hugo Mills wrote: I'm getting these on my Dell Latitude D830: Feb 15 13:06:00 willow kernel: ata1.00: exception Emask 0x2 SAct 0x4 SErr 0x0 action 0x2 frozen Feb 15 13:06:00 willow kernel: ata1.00: spurious completions during NCQ issue=0x0 SAct=0x4 FIS=004040a1:0002 Feb 15 13:06:00 willow kernel: ata1.00: cmd 61/10:10:26:fb:c4/00:00:02:00:00/40 tag 2 cdb 0x0 data 8192 out Feb 15 13:06:00 willow kernel: res 40/00:10:26:fb:c4/00:00:02:00:00/40 Emask 0x2 (HSM violation) Feb 15 13:06:00 willow kernel: ata1: soft resetting port Feb 15 13:06:00 willow kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 15 13:06:00 willow kernel: ata1.00: configured for UDMA/133 Feb 15 13:06:00 willow kernel: ata1: EH complete Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] Write Protect is off Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA In some cases, there are several cmd/res lines listed. It's happening about once an hour or so (not correlated with any other event that I can see). It doesn't seem to be affecting operation of the machine, but it's making me nervous. Can anyone set my mind at rest? (Or suggest a fix?) .. Tejun, have the spurious completion fixes been backported to 2.6.23 / 2.6.22 yet ? Those kernels will be in common use for some time to come, and this fix is more or less essential. ??? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Spurious completions during NCQ
Hugo Mills wrote: I'm getting these on my Dell Latitude D830: Feb 15 13:06:00 willow kernel: ata1.00: exception Emask 0x2 SAct 0x4 SErr 0x0 action 0x2 frozen Feb 15 13:06:00 willow kernel: ata1.00: spurious completions during NCQ issue=0x0 SAct=0x4 FIS=004040a1:0002 Feb 15 13:06:00 willow kernel: ata1.00: cmd 61/10:10:26:fb:c4/00:00:02:00:00/40 tag 2 cdb 0x0 data 8192 out Feb 15 13:06:00 willow kernel: res 40/00:10:26:fb:c4/00:00:02:00:00/40 Emask 0x2 (HSM violation) Feb 15 13:06:00 willow kernel: ata1: soft resetting port Feb 15 13:06:00 willow kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 15 13:06:00 willow kernel: ata1.00: configured for UDMA/133 Feb 15 13:06:00 willow kernel: ata1: EH complete Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] Write Protect is off Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA In some cases, there are several cmd/res lines listed. It's happening about once an hour or so (not correlated with any other event that I can see). It doesn't seem to be affecting operation of the machine, but it's making me nervous. Can anyone set my mind at rest? (Or suggest a fix?) .. Tejun, have the spurious completion fixes been backported to 2.6.23 / 2.6.22 yet ? Those kernels will be in common use for some time to come, and this fix is more or less essential. ??? -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Spurious completions during NCQ
Hugo Mills wrote: > On Fri, Feb 15, 2008 at 10:00:00AM -0500, Calvin Walton wrote: >> On Fri, 2008-02-15 at 13:46 +, Hugo Mills wrote: >>> I'm getting these on my Dell Latitude D830: >>> >>> Feb 15 13:06:00 willow kernel: ata1.00: exception Emask 0x2 SAct 0x4 SErr >>> 0x0 action 0x2 frozen >>> Feb 15 13:06:00 willow kernel: ata1.00: spurious completions during NCQ >>> issue=0x0 SAct=0x4 FIS=004040a1:0002 >>>In some cases, there are several cmd/res lines listed. It's >>> happening about once an hour or so (not correlated with any other >>> event that I can see). It doesn't seem to be affecting operation of >>> the machine, but it's making me nervous. JFYI: Most probably it is correlated with smartd asking the device for it's SMART status. /mjt -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Spurious completions during NCQ
On Fri, Feb 15, 2008 at 10:00:00AM -0500, Calvin Walton wrote: > On Fri, 2008-02-15 at 13:46 +, Hugo Mills wrote: > > I'm getting these on my Dell Latitude D830: > > > > Feb 15 13:06:00 willow kernel: ata1.00: exception Emask 0x2 SAct 0x4 SErr > > 0x0 action 0x2 frozen > > Feb 15 13:06:00 willow kernel: ata1.00: spurious completions during NCQ > > issue=0x0 SAct=0x4 FIS=004040a1:0002 > > >In some cases, there are several cmd/res lines listed. It's > > happening about once an hour or so (not correlated with any other > > event that I can see). It doesn't seem to be affecting operation of > > the machine, but it's making me nervous. > > > >Can anyone set my mind at rest? (Or suggest a fix?) > > You didn't mention which SATA chipset your laptop has, but some quick > googling says that it's AHCI. Until 2.6.24, the AHCI driver has a > problem where it'll report superious NCQ completions due to a bug in the > driver logic. > > > uname -a reports: > > Linux willow 2.6.23.1-hrt3 #1 SMP Sun Nov 4 14:51:20 GMT 2007 x86_64 > > GNU/Linux > > The fix is simple, upgrade your kernel to 2.6.24 :) Excellent. Thank you for clearing this up for me. I'll head off and do the upgrade now. Hugo. -- === Hugo Mills: [EMAIL PROTECTED] carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- All mushrooms are edible, but some are only edible once. --- signature.asc Description: Digital signature
Re: Spurious completions during NCQ
On Fri, 2008-02-15 at 13:46 +, Hugo Mills wrote: > I'm getting these on my Dell Latitude D830: > > Feb 15 13:06:00 willow kernel: ata1.00: exception Emask 0x2 SAct 0x4 SErr 0x0 > action 0x2 frozen > Feb 15 13:06:00 willow kernel: ata1.00: spurious completions during NCQ > issue=0x0 SAct=0x4 FIS=004040a1:0002 >In some cases, there are several cmd/res lines listed. It's > happening about once an hour or so (not correlated with any other > event that I can see). It doesn't seem to be affecting operation of > the machine, but it's making me nervous. > >Can anyone set my mind at rest? (Or suggest a fix?) You didn't mention which SATA chipset your laptop has, but some quick googling says that it's AHCI. Until 2.6.24, the AHCI driver has a problem where it'll report superious NCQ completions due to a bug in the driver logic. > uname -a reports: > Linux willow 2.6.23.1-hrt3 #1 SMP Sun Nov 4 14:51:20 GMT 2007 x86_64 GNU/Linux The fix is simple, upgrade your kernel to 2.6.24 :) >It's a kernel.org kernel with the patch for tickless operation on > amd64. Handily, the 2.6.24 kernel.org kernel includes amd64 tickless support already. -- Calvin Walton <[EMAIL PROTECTED]> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Spurious completions during NCQ
I'm getting these on my Dell Latitude D830:
Feb 15 13:06:00 willow kernel: ata1.00: exception Emask 0x2 SAct 0x4 SErr 0x0
action 0x2 frozen
Feb 15 13:06:00 willow kernel: ata1.00: spurious completions during NCQ
issue=0x0 SAct=0x4 FIS=004040a1:0002
Feb 15 13:06:00 willow kernel: ata1.00: cmd 61/10:10:26:fb:c4/00:00:02:00:00/40
tag 2 cdb 0x0 data 8192 out
Feb 15 13:06:00 willow kernel: res 40/00:10:26:fb:c4/00:00:02:00:00/40
Emask 0x2 (HSM violation)
Feb 15 13:06:00 willow kernel: ata1: soft resetting port
Feb 15 13:06:00 willow kernel: ata1: SATA link up 3.0 Gbps (SStatus 123
SControl 300)
Feb 15 13:06:00 willow kernel: ata1.00: configured for UDMA/133
Feb 15 13:06:00 willow kernel: ata1: EH complete
Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] 312581808 512-byte hardware
sectors (160042 MB)
Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] Write cache: enabled, read
cache: enabled, doesn't support DPO or FUA
In some cases, there are several cmd/res lines listed. It's
happening about once an hour or so (not correlated with any other
event that I can see). It doesn't seem to be affecting operation of
the machine, but it's making me nervous.
Can anyone set my mind at rest? (Or suggest a fix?)
uname -a reports:
Linux willow 2.6.23.1-hrt3 #1 SMP Sun Nov 4 14:51:20 GMT 2007 x86_64 GNU/Linux
It's a kernel.org kernel with the patch for tickless operation on
amd64.
hdparm -i reports:
/dev/sda:
Model=ST9160823AS , FwRev=3.ADC , SerialNo=
5NK0C448
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=?8?
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 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5
AdvancedPM=yes: unknown setting WriteCache=enabled
Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
Hugo.
--
=== Hugo Mills: [EMAIL PROTECTED] carfax.org.uk | darksatanic.net | lug.org.uk
===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- w.w.w. : England's batting scorecard ---
signature.asc
Description: Digital signature
Spurious completions during NCQ
I'm getting these on my Dell Latitude D830:
Feb 15 13:06:00 willow kernel: ata1.00: exception Emask 0x2 SAct 0x4 SErr 0x0
action 0x2 frozen
Feb 15 13:06:00 willow kernel: ata1.00: spurious completions during NCQ
issue=0x0 SAct=0x4 FIS=004040a1:0002
Feb 15 13:06:00 willow kernel: ata1.00: cmd 61/10:10:26:fb:c4/00:00:02:00:00/40
tag 2 cdb 0x0 data 8192 out
Feb 15 13:06:00 willow kernel: res 40/00:10:26:fb:c4/00:00:02:00:00/40
Emask 0x2 (HSM violation)
Feb 15 13:06:00 willow kernel: ata1: soft resetting port
Feb 15 13:06:00 willow kernel: ata1: SATA link up 3.0 Gbps (SStatus 123
SControl 300)
Feb 15 13:06:00 willow kernel: ata1.00: configured for UDMA/133
Feb 15 13:06:00 willow kernel: ata1: EH complete
Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] 312581808 512-byte hardware
sectors (160042 MB)
Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 15 13:06:00 willow kernel: sd 0:0:0:0: [sda] Write cache: enabled, read
cache: enabled, doesn't support DPO or FUA
In some cases, there are several cmd/res lines listed. It's
happening about once an hour or so (not correlated with any other
event that I can see). It doesn't seem to be affecting operation of
the machine, but it's making me nervous.
Can anyone set my mind at rest? (Or suggest a fix?)
uname -a reports:
Linux willow 2.6.23.1-hrt3 #1 SMP Sun Nov 4 14:51:20 GMT 2007 x86_64 GNU/Linux
It's a kernel.org kernel with the patch for tickless operation on
amd64.
hdparm -i reports:
/dev/sda:
Model=ST9160823AS , FwRev=3.ADC , SerialNo=
5NK0C448
Config={ HardSect NotMFM HdSw15uSec Fixed DTR10Mbs RotSpdTol.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=?8?
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 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5
AdvancedPM=yes: unknown setting WriteCache=enabled
Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
Hugo.
--
=== Hugo Mills: [EMAIL PROTECTED] carfax.org.uk | darksatanic.net | lug.org.uk
===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- w.w.w. : England's batting scorecard ---
signature.asc
Description: Digital signature
Re: Spurious completions during NCQ
On Fri, 2008-02-15 at 13:46 +, Hugo Mills wrote: I'm getting these on my Dell Latitude D830: Feb 15 13:06:00 willow kernel: ata1.00: exception Emask 0x2 SAct 0x4 SErr 0x0 action 0x2 frozen Feb 15 13:06:00 willow kernel: ata1.00: spurious completions during NCQ issue=0x0 SAct=0x4 FIS=004040a1:0002 In some cases, there are several cmd/res lines listed. It's happening about once an hour or so (not correlated with any other event that I can see). It doesn't seem to be affecting operation of the machine, but it's making me nervous. Can anyone set my mind at rest? (Or suggest a fix?) You didn't mention which SATA chipset your laptop has, but some quick googling says that it's AHCI. Until 2.6.24, the AHCI driver has a problem where it'll report superious NCQ completions due to a bug in the driver logic. uname -a reports: Linux willow 2.6.23.1-hrt3 #1 SMP Sun Nov 4 14:51:20 GMT 2007 x86_64 GNU/Linux The fix is simple, upgrade your kernel to 2.6.24 :) It's a kernel.org kernel with the patch for tickless operation on amd64. Handily, the 2.6.24 kernel.org kernel includes amd64 tickless support already. -- Calvin Walton [EMAIL PROTECTED] -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Spurious completions during NCQ
On Fri, Feb 15, 2008 at 10:00:00AM -0500, Calvin Walton wrote: On Fri, 2008-02-15 at 13:46 +, Hugo Mills wrote: I'm getting these on my Dell Latitude D830: Feb 15 13:06:00 willow kernel: ata1.00: exception Emask 0x2 SAct 0x4 SErr 0x0 action 0x2 frozen Feb 15 13:06:00 willow kernel: ata1.00: spurious completions during NCQ issue=0x0 SAct=0x4 FIS=004040a1:0002 In some cases, there are several cmd/res lines listed. It's happening about once an hour or so (not correlated with any other event that I can see). It doesn't seem to be affecting operation of the machine, but it's making me nervous. Can anyone set my mind at rest? (Or suggest a fix?) You didn't mention which SATA chipset your laptop has, but some quick googling says that it's AHCI. Until 2.6.24, the AHCI driver has a problem where it'll report superious NCQ completions due to a bug in the driver logic. uname -a reports: Linux willow 2.6.23.1-hrt3 #1 SMP Sun Nov 4 14:51:20 GMT 2007 x86_64 GNU/Linux The fix is simple, upgrade your kernel to 2.6.24 :) Excellent. Thank you for clearing this up for me. I'll head off and do the upgrade now. Hugo. -- === Hugo Mills: [EMAIL PROTECTED] carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- All mushrooms are edible, but some are only edible once. --- signature.asc Description: Digital signature
Re: Spurious completions during NCQ
Hugo Mills wrote: On Fri, Feb 15, 2008 at 10:00:00AM -0500, Calvin Walton wrote: On Fri, 2008-02-15 at 13:46 +, Hugo Mills wrote: I'm getting these on my Dell Latitude D830: Feb 15 13:06:00 willow kernel: ata1.00: exception Emask 0x2 SAct 0x4 SErr 0x0 action 0x2 frozen Feb 15 13:06:00 willow kernel: ata1.00: spurious completions during NCQ issue=0x0 SAct=0x4 FIS=004040a1:0002 In some cases, there are several cmd/res lines listed. It's happening about once an hour or so (not correlated with any other event that I can see). It doesn't seem to be affecting operation of the machine, but it's making me nervous. JFYI: Most probably it is correlated with smartd asking the device for it's SMART status. /mjt -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: western digital WD1500ADFD: spurious completions during NCQ
Jeff Garrett wrote: > Several threads that suggest this message is related to poor NCQ > support, but I did not see any for this drive. It's a Western Digital > WD1500ADFD-00NLR1. Is this the same thing, and should this drive be > blacklisted? How reproducible is the problem? -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: western digital WD1500ADFD: spurious completions during NCQ
Jeff Garrett wrote: Several threads that suggest this message is related to poor NCQ support, but I did not see any for this drive. It's a Western Digital WD1500ADFD-00NLR1. Is this the same thing, and should this drive be blacklisted? How reproducible is the problem? -- tejun - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: "spurious completions during NCQ" with 2.6.23.1 and DVD Multi-Recorder on Thinkpad T61
Alan Cox wrote: On Mon, 22 Oct 2007 09:56:10 +0800 Federico Sevilla III <[EMAIL PROTECTED]> wrote: Hi, Using the 2.6.23.1 kernel and Debian Etch on a Lenovo Thinkpad T61 7659A21, I am getting two weird errors, as follows: Turn off bluetooth and you may find the stuck IRQ goes away - at least on some thinkpads there are weird extra IRQs when bluetooth is running which break stuff. There was an old American Music/Comedy show called "Hee Haw!" which had a recurring skit consisting of a farmer running into the doctor's office and saying "Doctor, doctor! It hurts when I do this!" followed by some unlikely activity. The doctor always replied "Then don't do that." Turning off bluetooth is a useful diagnostic test, but for some systems it's not a practical operating configuration. Any thoughts on making bluetooth work in these cases? Most laptops make a unit like the Logitech MX5000 BT keyboard desirable for extended use. -- Bill Davidsen <[EMAIL PROTECTED]> "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: spurious completions during NCQ with 2.6.23.1 and DVD Multi-Recorder on Thinkpad T61
Alan Cox wrote: On Mon, 22 Oct 2007 09:56:10 +0800 Federico Sevilla III [EMAIL PROTECTED] wrote: Hi, Using the 2.6.23.1 kernel and Debian Etch on a Lenovo Thinkpad T61 7659A21, I am getting two weird errors, as follows: Turn off bluetooth and you may find the stuck IRQ goes away - at least on some thinkpads there are weird extra IRQs when bluetooth is running which break stuff. There was an old American Music/Comedy show called Hee Haw! which had a recurring skit consisting of a farmer running into the doctor's office and saying Doctor, doctor! It hurts when I do this! followed by some unlikely activity. The doctor always replied Then don't do that. Turning off bluetooth is a useful diagnostic test, but for some systems it's not a practical operating configuration. Any thoughts on making bluetooth work in these cases? Most laptops make a unit like the Logitech MX5000 BT keyboard desirable for extended use. -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: "spurious completions during NCQ" with 2.6.23.1 and DVD Multi-Recorder on Thinkpad T61
On Mon, 22 Oct 2007 09:56:10 +0800 Federico Sevilla III <[EMAIL PROTECTED]> wrote: > Hi, > > Using the 2.6.23.1 kernel and Debian Etch on a Lenovo Thinkpad T61 > 7659A21, I am getting two weird errors, as follows: Turn off bluetooth and you may find the stuck IRQ goes away - at least on some thinkpads there are weird extra IRQs when bluetooth is running which break stuff. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: spurious completions during NCQ with 2.6.23.1 and DVD Multi-Recorder on Thinkpad T61
On Mon, 22 Oct 2007 09:56:10 +0800 Federico Sevilla III [EMAIL PROTECTED] wrote: Hi, Using the 2.6.23.1 kernel and Debian Etch on a Lenovo Thinkpad T61 7659A21, I am getting two weird errors, as follows: Turn off bluetooth and you may find the stuck IRQ goes away - at least on some thinkpads there are weird extra IRQs when bluetooth is running which break stuff. Alan - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
"spurious completions during NCQ" with 2.6.23.1 and DVD Multi-Recorder on Thinkpad T61
Hi, Using the 2.6.23.1 kernel and Debian Etch on a Lenovo Thinkpad T61 7659A21, I am getting two weird errors, as follows: ata1.00: exception Emask 0x2 SAct 0x1c SErr 0x0 action 0x2 frozen ata1.00: spurious completions during NCQ issue=0x0 SAct=0x1c FIS=005040a1:0002 ata1.00: cmd 60/17:10:28:01:00/00:00:00:00:00/40 tag 2 cdb 0x0 data 11776 in res 50/00:30:bf:01:00/00:00:00:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 60/80:18:3f:01:00/00:00:00:00:00/40 tag 3 cdb 0x0 data 65536 in res 50/00:30:bf:01:00/00:00:00:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 60/30:20:bf:01:00/00:00:00:00:00/40 tag 4 cdb 0x0 data 24576 in res 50/00:30:bf:01:00/00:00:00:00:00/40 Emask 0x2 (HSM violation) ... irq 19: nobody cared (try booting with the "irqpoll" option) Call Trace: [] __report_bad_irq+0x1e/0x80 [] note_interrupt+0x29d/0x2e0 [] handle_fasteoi_irq+0xdd/0x110 [] call_softirq+0x1c/0x30 [] do_IRQ+0x7b/0x100 [] ret_from_intr+0x0/0xa handlers: [] (usb_hcd_irq+0x0/0x60) Disabling IRQ #19 I have tried booting with the irqpoll option, but this results in the automounter doing weird things with the optical drive. Specifically, it sporadically mounts an audio disc with weird negative-sized tracks, even if there is no disc inserted in the drive. Also, regardless of whether I boot with irqpoll or not, chrony frequently uses up 100% of one CPU. The chrony measurements.log, statistics.log and tracking.log all show normal activity (ie: a "normal" volume of entries, vis a vis chrony on other machines where CPU usage is normal). I don't know if this is related. Any clues? I have attached the following: 1. Kernel configuration 2. dmesg output 3. lspci output 4. chrony.conf (if it matters) Please cc me with replies, as I am not on the list. Thank you very much. Cheers! -- Federico Sevilla III F S 3 Consulting Inc. http://www.fs3.ph Linux version 2.6.23.1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Fri Oct 19 01:01:42 PHT 2007 Command line: root=/dev/mapper/humanitas-root rw vga=871 BIOS-provided physical RAM map: BIOS-e820: - 0009d800 (usable) BIOS-e820: 0009d800 - 000a (reserved) BIOS-e820: 000d2000 - 000d4000 (reserved) BIOS-e820: 000e - 0010 (reserved) BIOS-e820: 0010 - 3e6b (usable) BIOS-e820: 3e6b - 3e6cc000 (ACPI data) BIOS-e820: 3e6cc000 - 3e70 (ACPI NVS) BIOS-e820: 3e70 - 3f00 (reserved) BIOS-e820: f000 - f400 (reserved) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fed0 - fed00400 (reserved) BIOS-e820: fed14000 - fed1a000 (reserved) BIOS-e820: fed1c000 - fed9 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: ff00 - 0001 (reserved) Entering add_active_range(0, 0, 157) 0 entries of 256 used Entering add_active_range(0, 256, 255664) 1 entries of 256 used end_pfn_map = 1048576 DMI present. ACPI: RSDP 000F68D0, 0024 (r2 LENOVO) ACPI: XSDT 3E6BB8FD, 0094 (r1 LENOVO TP-7L1210 LTP0) ACPI: FACP 3E6BBA00, 00F4 (r3 LENOVO TP-7L1210 LNVO1) ACPI Warning (tbfadt-0442): Optional field "Gpe1Block" has zero address or length: 102C/0 [20070126] ACPI: DSDT 3E6BBE0C, FD64 (r1 LENOVO TP-7L1210 MSFT 300) ACPI: FACS 3E6E4000, 0040 ACPI: SSDT 3E64, 0258 (r1 LENOVO TP-7L1210 MSFT 300) ACPI: ECDT 3E6CBB70, 0052 (r1 LENOVO TP-7L1210 LNVO1) ACPI: TCPA 3E6CBBC2, 0032 (r2 LENOVO TP-7L1210 LNVO1) ACPI: APIC 3E6CBBF4, 0068 (r1 LENOVO TP-7L1210 LNVO1) ACPI: MCFG 3E6CBC5C, 003C (r1 LENOVO TP-7L1210 LNVO1) ACPI: HPET 3E6CBC98, 0038 (r1 LENOVO TP-7L1210 LNVO1) ACPI: SLIC 3E6CBDF0, 0176 (r1 LENOVO TP-7L1210 LTP0) ACPI: BOOT 3E6CBF66, 0028 (r1 LENOVO TP-7L1210 LTP1) ACPI: ASF! 3E6CBF8E, 0072 (r16 LENOVO TP-7L1210 PTL 1) ACPI: SSDT 3E6E2697, 025F (r1 LENOVO TP-7L1210 INTL 20050513) ACPI: SSDT 3E6E28F6, 00A6 (r1 LENOVO TP-7L1210 INTL 20050513) ACPI: SSDT 3E6E299C, 04F7 (r1 LENOVO TP-7L1210 INTL 20050513) ACPI: SSDT 3E6E2E93, 01D8 (r1 LENOVO TP-7L1210 INTL 20050513) Entering add_active_range(0, 0, 157) 0 entries of 256 used Entering add_active_range(0, 256, 255664) 1 entries of 256 used Zone PFN ranges: DMA 0 -> 4096 DMA324096 -> 1048576 Normal1048576 -> 1048576 Movable zone start PFN for each node early_node_map[2] active PFN r
spurious completions during NCQ with 2.6.23.1 and DVD Multi-Recorder on Thinkpad T61
Hi, Using the 2.6.23.1 kernel and Debian Etch on a Lenovo Thinkpad T61 7659A21, I am getting two weird errors, as follows: ata1.00: exception Emask 0x2 SAct 0x1c SErr 0x0 action 0x2 frozen ata1.00: spurious completions during NCQ issue=0x0 SAct=0x1c FIS=005040a1:0002 ata1.00: cmd 60/17:10:28:01:00/00:00:00:00:00/40 tag 2 cdb 0x0 data 11776 in res 50/00:30:bf:01:00/00:00:00:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 60/80:18:3f:01:00/00:00:00:00:00/40 tag 3 cdb 0x0 data 65536 in res 50/00:30:bf:01:00/00:00:00:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 60/30:20:bf:01:00/00:00:00:00:00/40 tag 4 cdb 0x0 data 24576 in res 50/00:30:bf:01:00/00:00:00:00:00/40 Emask 0x2 (HSM violation) ... irq 19: nobody cared (try booting with the irqpoll option) Call Trace: IRQ [80269f4e] __report_bad_irq+0x1e/0x80 [8026a24d] note_interrupt+0x29d/0x2e0 [8026adbd] handle_fasteoi_irq+0xdd/0x110 [8020d3cc] call_softirq+0x1c/0x30 [8020f44b] do_IRQ+0x7b/0x100 [8020c751] ret_from_intr+0x0/0xa EOI handlers: [8049e5f0] (usb_hcd_irq+0x0/0x60) Disabling IRQ #19 I have tried booting with the irqpoll option, but this results in the automounter doing weird things with the optical drive. Specifically, it sporadically mounts an audio disc with weird negative-sized tracks, even if there is no disc inserted in the drive. Also, regardless of whether I boot with irqpoll or not, chrony frequently uses up 100% of one CPU. The chrony measurements.log, statistics.log and tracking.log all show normal activity (ie: a normal volume of entries, vis a vis chrony on other machines where CPU usage is normal). I don't know if this is related. Any clues? I have attached the following: 1. Kernel configuration 2. dmesg output 3. lspci output 4. chrony.conf (if it matters) Please cc me with replies, as I am not on the list. Thank you very much. Cheers! -- Federico Sevilla III F S 3 Consulting Inc. http://www.fs3.ph Linux version 2.6.23.1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Fri Oct 19 01:01:42 PHT 2007 Command line: root=/dev/mapper/humanitas-root rw vga=871 BIOS-provided physical RAM map: BIOS-e820: - 0009d800 (usable) BIOS-e820: 0009d800 - 000a (reserved) BIOS-e820: 000d2000 - 000d4000 (reserved) BIOS-e820: 000e - 0010 (reserved) BIOS-e820: 0010 - 3e6b (usable) BIOS-e820: 3e6b - 3e6cc000 (ACPI data) BIOS-e820: 3e6cc000 - 3e70 (ACPI NVS) BIOS-e820: 3e70 - 3f00 (reserved) BIOS-e820: f000 - f400 (reserved) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fed0 - fed00400 (reserved) BIOS-e820: fed14000 - fed1a000 (reserved) BIOS-e820: fed1c000 - fed9 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: ff00 - 0001 (reserved) Entering add_active_range(0, 0, 157) 0 entries of 256 used Entering add_active_range(0, 256, 255664) 1 entries of 256 used end_pfn_map = 1048576 DMI present. ACPI: RSDP 000F68D0, 0024 (r2 LENOVO) ACPI: XSDT 3E6BB8FD, 0094 (r1 LENOVO TP-7L1210 LTP0) ACPI: FACP 3E6BBA00, 00F4 (r3 LENOVO TP-7L1210 LNVO1) ACPI Warning (tbfadt-0442): Optional field Gpe1Block has zero address or length: 102C/0 [20070126] ACPI: DSDT 3E6BBE0C, FD64 (r1 LENOVO TP-7L1210 MSFT 300) ACPI: FACS 3E6E4000, 0040 ACPI: SSDT 3E64, 0258 (r1 LENOVO TP-7L1210 MSFT 300) ACPI: ECDT 3E6CBB70, 0052 (r1 LENOVO TP-7L1210 LNVO1) ACPI: TCPA 3E6CBBC2, 0032 (r2 LENOVO TP-7L1210 LNVO1) ACPI: APIC 3E6CBBF4, 0068 (r1 LENOVO TP-7L1210 LNVO1) ACPI: MCFG 3E6CBC5C, 003C (r1 LENOVO TP-7L1210 LNVO1) ACPI: HPET 3E6CBC98, 0038 (r1 LENOVO TP-7L1210 LNVO1) ACPI: SLIC 3E6CBDF0, 0176 (r1 LENOVO TP-7L1210 LTP0) ACPI: BOOT 3E6CBF66, 0028 (r1 LENOVO TP-7L1210 LTP1) ACPI: ASF! 3E6CBF8E, 0072 (r16 LENOVO TP-7L1210 PTL 1) ACPI: SSDT 3E6E2697, 025F (r1 LENOVO TP-7L1210 INTL 20050513) ACPI: SSDT 3E6E28F6, 00A6 (r1 LENOVO TP-7L1210 INTL 20050513) ACPI: SSDT 3E6E299C, 04F7 (r1 LENOVO TP-7L1210 INTL 20050513) ACPI: SSDT 3E6E2E93, 01D8 (r1 LENOVO TP-7L1210 INTL 20050513) Entering add_active_range(0, 0, 157) 0 entries of 256 used Entering add_active_range(0, 256, 255664) 1 entries of 256 used Zone PFN ranges: DMA 0 - 4096 DMA324096 - 1048576 Normal1048576 - 1048576
western digital WD1500ADFD: spurious completions during NCQ
Several threads that suggest this message is related to poor NCQ support, but I did not see any for this drive. It's a Western Digital WD1500ADFD-00NLR1. Is this the same thing, and should this drive be blacklisted? ata1.00: exception Emask 0x2 SAct 0x1f1 SErr 0x0 action 0x2 frozen ata1.00: spurious completions during NCQ issue=0x0 SAct=0x1f1 FIS=004040a1:0008 ata1.00: cmd 61/10:00:90:d3:e8/00:00:0a:00:00/40 tag 0 cdb 0x0 data 8192 out res 40/00:08:80:fc:34/00:00:04:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/40:20:8e:2e:b8/00:00:06:00:00/40 tag 4 cdb 0x0 data 32768 out res 40/00:08:80:fc:34/00:00:04:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/40:28:ce:2e:b8/00:00:06:00:00/40 tag 5 cdb 0x0 data 32768 out res 40/00:08:80:fc:34/00:00:04:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/40:30:0e:2f:b8/00:00:06:00:00/40 tag 6 cdb 0x0 data 32768 out res 40/00:08:80:fc:34/00:00:04:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/40:38:4e:2f:b8/00:00:06:00:00/40 tag 7 cdb 0x0 data 32768 out res 40/00:08:80:fc:34/00:00:04:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/40:40:8e:2f:b8/00:00:06:00:00/40 tag 8 cdb 0x0 data 32768 out res 40/00:08:80:fc:34/00:00:04:00:00/40 Emask 0x2 (HSM violation) ata1: soft resetting port ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: configured for UDMA/133 ata1: EH complete I've attached hdparm -I output. Thanks, Jeff Garrett /dev/sda: ATA device, with non-removable media Model Number: WDC WD1500ADFD-00NLR1 Serial Number: WD-WMAP41106896 Firmware Revision: 20.07P20 Standards: Used: ATA/ATAPI-7 published, ANSI INCITS 397-2005 Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBAuser addressable sectors: 268435455 LBA48 user addressable sectors: 293046768 device size with M = 1024*1024: 143089 MBytes device size with M = 1000*1000: 150039 MBytes (150 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 128, current value: 254 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * NOP cmd * DOWNLOAD_MICROCODE Power-Up In Standby feature set * SET_FEATURES required to spinup after power up * SET_MAX security extension * Automatic Acoustic Management feature set * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * General Purpose Logging feature set * 64-bit World wide name * SATA-I signaling speed (1.5Gb/s) * Native Command Queueing (NCQ) * Phy event counters DMA Setup Auto-Activate optimization * Software settings preservation * SMART Command Transport (SCT) feature set * SCT Long Sector Access (AC1) * SCT LBA Segment Access (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[12] Security: Master password revision code = 65534 supported not enabled not locked frozen not expired: security count not supported: enhanced erase Checksum: correct
western digital WD1500ADFD: spurious completions during NCQ
Several threads that suggest this message is related to poor NCQ support, but I did not see any for this drive. It's a Western Digital WD1500ADFD-00NLR1. Is this the same thing, and should this drive be blacklisted? ata1.00: exception Emask 0x2 SAct 0x1f1 SErr 0x0 action 0x2 frozen ata1.00: spurious completions during NCQ issue=0x0 SAct=0x1f1 FIS=004040a1:0008 ata1.00: cmd 61/10:00:90:d3:e8/00:00:0a:00:00/40 tag 0 cdb 0x0 data 8192 out res 40/00:08:80:fc:34/00:00:04:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/40:20:8e:2e:b8/00:00:06:00:00/40 tag 4 cdb 0x0 data 32768 out res 40/00:08:80:fc:34/00:00:04:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/40:28:ce:2e:b8/00:00:06:00:00/40 tag 5 cdb 0x0 data 32768 out res 40/00:08:80:fc:34/00:00:04:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/40:30:0e:2f:b8/00:00:06:00:00/40 tag 6 cdb 0x0 data 32768 out res 40/00:08:80:fc:34/00:00:04:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/40:38:4e:2f:b8/00:00:06:00:00/40 tag 7 cdb 0x0 data 32768 out res 40/00:08:80:fc:34/00:00:04:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/40:40:8e:2f:b8/00:00:06:00:00/40 tag 8 cdb 0x0 data 32768 out res 40/00:08:80:fc:34/00:00:04:00:00/40 Emask 0x2 (HSM violation) ata1: soft resetting port ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: configured for UDMA/133 ata1: EH complete I've attached hdparm -I output. Thanks, Jeff Garrett /dev/sda: ATA device, with non-removable media Model Number: WDC WD1500ADFD-00NLR1 Serial Number: WD-WMAP41106896 Firmware Revision: 20.07P20 Standards: Used: ATA/ATAPI-7 published, ANSI INCITS 397-2005 Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBAuser addressable sectors: 268435455 LBA48 user addressable sectors: 293046768 device size with M = 1024*1024: 143089 MBytes device size with M = 1000*1000: 150039 MBytes (150 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 128, current value: 254 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * NOP cmd * DOWNLOAD_MICROCODE Power-Up In Standby feature set * SET_FEATURES required to spinup after power up * SET_MAX security extension * Automatic Acoustic Management feature set * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * General Purpose Logging feature set * 64-bit World wide name * SATA-I signaling speed (1.5Gb/s) * Native Command Queueing (NCQ) * Phy event counters DMA Setup Auto-Activate optimization * Software settings preservation * SMART Command Transport (SCT) feature set * SCT Long Sector Access (AC1) * SCT LBA Segment Access (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[12] Security: Master password revision code = 65534 supported not enabled not locked frozen not expired: security count not supported: enhanced erase Checksum: correct
Re: Hitachi disk: spurious completions during NCQ
On 10/15/07, Don Mullis <[EMAIL PROTECTED]> wrote: > > > ata3.00: spurious completions during NCQ issue=0x0 SAct=0x407fd > > FIS=005040a1:0002 > > ata3.00: cmd 61/08:00:c7:5a:82/00:00:1b:00:00/40 tag 0 cdb 0x0 data 4096 out > > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > > > This has been seen with several Hitachi drives. There's speculation > that it's due to a bug in the drive firmware: Yes, I'm aware of this. That's why I was suggesting to blacklist this drive. thanks, Luca - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Hitachi disk: spurious completions during NCQ
> ata3.00: spurious completions during NCQ issue=0x0 SAct=0x407fd > FIS=005040a1:0002 > ata3.00: cmd 61/08:00:c7:5a:82/00:00:1b:00:00/40 tag 0 cdb 0x0 data 4096 out > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) This has been seen with several Hitachi drives. There's speculation that it's due to a bug in the drive firmware: http://groups.google.it/group/linux.kernel/browse_thread/thread/a4bd3c19565a2009/389817602f0cd551?hl=it=st=hitachi+hsm+violation=3#389817602f0cd551 https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/137470 A workaround: Index: /etc/rc.local === --- .orig/etc/rc.local 2007-10-13 14:57:10.0 -0700 +++ /etc/rc.local 2007-10-13 14:59:21.0 -0700 @@ -11,4 +11,7 @@ # # By default this script does nothing. +# See https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/137470/ +echo 1 > /sys/block/sda/device/queue_depth + exit 0 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Hitachi disk: spurious completions during NCQ
ata3.00: spurious completions during NCQ issue=0x0 SAct=0x407fd FIS=005040a1:0002 ata3.00: cmd 61/08:00:c7:5a:82/00:00:1b:00:00/40 tag 0 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) This has been seen with several Hitachi drives. There's speculation that it's due to a bug in the drive firmware: http://groups.google.it/group/linux.kernel/browse_thread/thread/a4bd3c19565a2009/389817602f0cd551?hl=itlnk=stq=hitachi+hsm+violationrnum=3#389817602f0cd551 https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/137470 A workaround: Index: /etc/rc.local === --- .orig/etc/rc.local 2007-10-13 14:57:10.0 -0700 +++ /etc/rc.local 2007-10-13 14:59:21.0 -0700 @@ -11,4 +11,7 @@ # # By default this script does nothing. +# See https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/137470/ +echo 1 /sys/block/sda/device/queue_depth + exit 0 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Hitachi disk: spurious completions during NCQ
On 10/15/07, Don Mullis [EMAIL PROTECTED] wrote: ata3.00: spurious completions during NCQ issue=0x0 SAct=0x407fd FIS=005040a1:0002 ata3.00: cmd 61/08:00:c7:5a:82/00:00:1b:00:00/40 tag 0 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) This has been seen with several Hitachi drives. There's speculation that it's due to a bug in the drive firmware: Yes, I'm aware of this. That's why I was suggesting to blacklist this drive. thanks, Luca - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Hitachi disk: spurious completions during NCQ
On 10/13/07, Andrew Morton <[EMAIL PROTECTED]> wrote: > On Wed, 10 Oct 2007 21:03:43 +0200 > Luca Tettamanti <[EMAIL PROTECTED]> wrote: > > > Hello, > > sometimes kernel complains about spurious completions on my new > > notebook: > > > > ata3.00: exception Emask 0x2 SAct 0x407fd SErr 0x0 action 0x2 frozen > > ata3.00: spurious completions during NCQ issue=0x0 SAct=0x407fd > > FIS=005040a1:0002 > > ata3.00: cmd 61/08:00:c7:5a:82/00:00:1b:00:00/40 tag 0 cdb 0x0 data 4096 out > > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > > ata3.00: cmd 61/08:10:3f:5b:fa/00:00:18:00:00/40 tag 2 cdb 0x0 data 4096 out > > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > > ata3.00: cmd 61/08:18:5f:5b:fa/00:00:18:00:00/40 tag 3 cdb 0x0 data 4096 out > > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > > ata3.00: cmd 61/18:20:6f:5b:fa/00:00:18:00:00/40 tag 4 cdb 0x0 data 12288 > > out > > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > > ata3.00: cmd 61/08:28:e7:19:fd/00:00:18:00:00/40 tag 5 cdb 0x0 data 4096 out > > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > > ata3.00: cmd 61/08:30:df:59:ae/00:00:1a:00:00/40 tag 6 cdb 0x0 data 4096 out > > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > > ata3.00: cmd 61/08:38:3f:5a:ae/00:00:1a:00:00/40 tag 7 cdb 0x0 data 4096 out > > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > > ata3.00: cmd 61/08:40:6f:62:ae/00:00:1a:00:00/40 tag 8 cdb 0x0 data 4096 out > > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > > ata3.00: cmd 61/28:48:d7:59:7e/00:00:1b:00:00/40 tag 9 cdb 0x0 data 20480 > > out > > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > > ata3.00: cmd 61/10:50:07:5b:82/00:00:1b:00:00/40 tag 10 cdb 0x0 data 8192 > > out > > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > > ata3.00: cmd 61/30:90:f7:5a:fa/00:00:18:00:00/40 tag 18 cdb 0x0 data 24576 > > out > > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > > ata3: soft resetting port > > ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > > ata3.00: configured for UDMA/133 > > ata3: EH complete > > sd 2:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB) > > sd 2:0:0:0: [sda] Write Protect is off > > sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 > > sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't > > support DPO or FUA > > > > (this is a very recent 2.6.23-git, SMP, x86_64) > > The latest kernel, a serious-looking problem, sent to the correct mailing > lists. After two days nobody has bothered replying. > > > The disk is: > > > > ATA device, with non-removable media > > Model Number: Hitachi HTS542525K9SA00 > > Firmware Revision: BBFOC31P > > > > The controller is: > > > > 00:1f.2 SATA controller: Intel Corporation Mobile SATA AHCI Controller (rev > > 03) (prog-if 01 [AHCI 1.0]) > > Subsystem: ASUSTeK Computer Inc. Unknown device 14e7 > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > > Stepping- SERR- FastB2B- > > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > > SERR- > Latency: 0 > > Interrupt: pin B routed to IRQ 1272 > > Region 0: I/O ports at ec00 [size=8] > > Region 1: I/O ports at e880 [size=4] > > Region 2: I/O ports at e800 [size=8] > > Region 3: I/O ports at e480 [size=4] > > Region 4: I/O ports at e400 [size=32] > > Region 5: Memory at febff800 (32-bit, non-prefetchable) [size=2K] > > Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- > > Queue=0/2 Enable+ > > Address: fee0300c Data: 41b9 > > Capabilities: [70] Power Management version 3 > > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA > > PME(D0-,D1-,D2-,D3hot+,D3cold-) > > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > > Capabilities: [a8] #12 [0010] > > > > and I'm using AHCI driver. > > > > I see that similar disks are already blacklisted, probably this one is > > bugged too - though the error is pretty rare :( > > > > Does this cause any other symptoms? ie: does the system otherwise work OK? The system is stable, the EH seems to be doing its job. Luca - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Spurious completions during NCQ
Hi, I think that my drives should be NCQ blacklisted too. That's what I'm getting in my /var/log/messages: --- Oct 13 13:55:52 ko kernel: ata1.00: exception Emask 0x2 SAct 0x3f9 SErr 0x0 action 0x2 frozen Oct 13 13:55:53 ko kernel: ata1.00: (spurious completions during NCQ issue=0x0 SAct=0x3f9 FIS=004040a1:0004) Oct 13 13:55:53 ko kernel: ata1.00: cmd 61/08:00:d0:5e:8f/00:00:0f:00:00/40 tag 0 cdb 0x0 data 4096 out Oct 13 13:55:53 ko kernel: res 40/00:48:38:63:8f/00:00:0f:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:55:53 ko kernel: ata1.00: cmd 61/08:18:f8:7f:50/00:00:0d:00:00/40 tag 3 cdb 0x0 data 4096 out Oct 13 13:55:53 ko kernel: res 40/00:48:38:63:8f/00:00:0f:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:55:53 ko kernel: ata1.00: cmd 61/10:20:10:80:50/00:00:0d:00:00/40 tag 4 cdb 0x0 data 8192 out Oct 13 13:55:53 ko kernel: res 40/00:48:38:63:8f/00:00:0f:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:55:53 ko kernel: ata1.00: cmd 61/08:28:a0:4a:5c/00:00:0d:00:00/40 tag 5 cdb 0x0 data 4096 out Oct 13 13:55:53 ko kernel: res 40/00:48:38:63:8f/00:00:0f:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:55:53 ko kernel: ata1.00: cmd 61/08:30:b8:d7:5c/00:00:0d:00:00/40 tag 6 cdb 0x0 data 4096 out Oct 13 13:55:53 ko kernel: res 40/00:48:38:63:8f/00:00:0f:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:55:53 ko kernel: ata1.00: cmd 61/08:38:30:5e:8f/00:00:0f:00:00/40 tag 7 cdb 0x0 data 4096 out Oct 13 13:55:53 ko kernel: res 40/00:48:38:63:8f/00:00:0f:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:55:53 ko kernel: ata1.00: cmd 61/08:40:e8:61:8f/00:00:0f:00:00/40 tag 8 cdb 0x0 data 4096 out Oct 13 13:55:53 ko kernel: res 40/00:48:38:63:8f/00:00:0f:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:55:53 ko kernel: ata1.00: cmd 61/08:48:38:63:8f/00:00:0f:00:00/40 tag 9 cdb 0x0 data 4096 out Oct 13 13:55:53 ko kernel: res 40/00:48:38:63:8f/00:00:0f:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:55:53 ko kernel: ata1: soft resetting port Oct 13 13:55:53 ko kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 13 13:55:53 ko kernel: ata1.00: configured for UDMA/133 Oct 13 13:55:53 ko kernel: ata1: EH complete Oct 13 13:55:53 ko kernel: sd 0:0:0:0: [sda] 490234752 512-byte hardware sectors (251000 MB) Oct 13 13:55:53 ko kernel: sd 0:0:0:0: [sda] Write Protect is off Oct 13 13:55:53 ko kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 13:57:56 ko kernel: ata2.00: exception Emask 0x2 SAct 0x1fff7 SErr 0x0 action 0x2 frozen Oct 13 13:57:56 ko kernel: ata2.00: (spurious completions during NCQ issue=0x0 SAct=0x1fff7 FIS=004040a1:0004) Oct 13 13:57:56 ko kernel: ata2.00: cmd 61/08:00:40:1b:b3/00:00:08:00:00/40 tag 0 cdb 0x0 data 4096 out Oct 13 13:57:56 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:56 ko kernel: ata2.00: cmd 61/08:08:e8:1d:27/00:00:0d:00:00/40 tag 1 cdb 0x0 data 4096 out Oct 13 13:57:56 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:56 ko kernel: ata2.00: cmd 61/08:10:40:1c:4b/00:00:0d:00:00/40 tag 2 cdb 0x0 data 4096 out Oct 13 13:57:56 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:56 ko kernel: ata2.00: cmd 61/08:20:60:1b:f7/00:00:06:00:00/40 tag 4 cdb 0x0 data 4096 out Oct 13 13:57:56 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:56 ko kernel: ata2.00: cmd 61/08:28:80:1b:07/00:00:07:00:00/40 tag 5 cdb 0x0 data 4096 out Oct 13 13:57:56 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:56 ko kernel: ata2.00: cmd 61/08:30:50:1b:2f/00:00:07:00:00/40 tag 6 cdb 0x0 data 4096 out Oct 13 13:57:56 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:56 ko kernel: ata2.00: cmd 61/08:38:30:1b:3b/00:00:07:00:00/40 tag 7 cdb 0x0 data 4096 out Oct 13 13:57:56 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:57 ko kernel: ata2.00: cmd 61/08:40:38:1b:43/00:00:07:00:00/40 tag 8 cdb 0x0 data 4096 out Oct 13 13:57:57 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:57 ko kernel: ata2.00: cmd 61/08:48:58:1b:67/00:00:07:00:00/40 tag 9 cdb 0x0 data 4096 out Oct 13 13:57:57 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:57 ko kernel: ata2.00: cmd 61/08:50:38:1b:6b/00:00:07:00:00/40 tag 10 cdb 0x0 data 4096 out Oct 13 13:57:57 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:57 ko kernel: ata2.00: cmd 61/08:58:90:1b:97/00:00:07:00:00/40 tag 11 cdb 0x0 data 4096 out Oct 13 13:57:57 ko
Spurious completions during NCQ
Hi, I think that my drives should be NCQ blacklisted too. That's what I'm getting in my /var/log/messages: --- Oct 13 13:55:52 ko kernel: ata1.00: exception Emask 0x2 SAct 0x3f9 SErr 0x0 action 0x2 frozen Oct 13 13:55:53 ko kernel: ata1.00: (spurious completions during NCQ issue=0x0 SAct=0x3f9 FIS=004040a1:0004) Oct 13 13:55:53 ko kernel: ata1.00: cmd 61/08:00:d0:5e:8f/00:00:0f:00:00/40 tag 0 cdb 0x0 data 4096 out Oct 13 13:55:53 ko kernel: res 40/00:48:38:63:8f/00:00:0f:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:55:53 ko kernel: ata1.00: cmd 61/08:18:f8:7f:50/00:00:0d:00:00/40 tag 3 cdb 0x0 data 4096 out Oct 13 13:55:53 ko kernel: res 40/00:48:38:63:8f/00:00:0f:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:55:53 ko kernel: ata1.00: cmd 61/10:20:10:80:50/00:00:0d:00:00/40 tag 4 cdb 0x0 data 8192 out Oct 13 13:55:53 ko kernel: res 40/00:48:38:63:8f/00:00:0f:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:55:53 ko kernel: ata1.00: cmd 61/08:28:a0:4a:5c/00:00:0d:00:00/40 tag 5 cdb 0x0 data 4096 out Oct 13 13:55:53 ko kernel: res 40/00:48:38:63:8f/00:00:0f:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:55:53 ko kernel: ata1.00: cmd 61/08:30:b8:d7:5c/00:00:0d:00:00/40 tag 6 cdb 0x0 data 4096 out Oct 13 13:55:53 ko kernel: res 40/00:48:38:63:8f/00:00:0f:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:55:53 ko kernel: ata1.00: cmd 61/08:38:30:5e:8f/00:00:0f:00:00/40 tag 7 cdb 0x0 data 4096 out Oct 13 13:55:53 ko kernel: res 40/00:48:38:63:8f/00:00:0f:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:55:53 ko kernel: ata1.00: cmd 61/08:40:e8:61:8f/00:00:0f:00:00/40 tag 8 cdb 0x0 data 4096 out Oct 13 13:55:53 ko kernel: res 40/00:48:38:63:8f/00:00:0f:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:55:53 ko kernel: ata1.00: cmd 61/08:48:38:63:8f/00:00:0f:00:00/40 tag 9 cdb 0x0 data 4096 out Oct 13 13:55:53 ko kernel: res 40/00:48:38:63:8f/00:00:0f:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:55:53 ko kernel: ata1: soft resetting port Oct 13 13:55:53 ko kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 13 13:55:53 ko kernel: ata1.00: configured for UDMA/133 Oct 13 13:55:53 ko kernel: ata1: EH complete Oct 13 13:55:53 ko kernel: sd 0:0:0:0: [sda] 490234752 512-byte hardware sectors (251000 MB) Oct 13 13:55:53 ko kernel: sd 0:0:0:0: [sda] Write Protect is off Oct 13 13:55:53 ko kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 13:57:56 ko kernel: ata2.00: exception Emask 0x2 SAct 0x1fff7 SErr 0x0 action 0x2 frozen Oct 13 13:57:56 ko kernel: ata2.00: (spurious completions during NCQ issue=0x0 SAct=0x1fff7 FIS=004040a1:0004) Oct 13 13:57:56 ko kernel: ata2.00: cmd 61/08:00:40:1b:b3/00:00:08:00:00/40 tag 0 cdb 0x0 data 4096 out Oct 13 13:57:56 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:56 ko kernel: ata2.00: cmd 61/08:08:e8:1d:27/00:00:0d:00:00/40 tag 1 cdb 0x0 data 4096 out Oct 13 13:57:56 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:56 ko kernel: ata2.00: cmd 61/08:10:40:1c:4b/00:00:0d:00:00/40 tag 2 cdb 0x0 data 4096 out Oct 13 13:57:56 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:56 ko kernel: ata2.00: cmd 61/08:20:60:1b:f7/00:00:06:00:00/40 tag 4 cdb 0x0 data 4096 out Oct 13 13:57:56 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:56 ko kernel: ata2.00: cmd 61/08:28:80:1b:07/00:00:07:00:00/40 tag 5 cdb 0x0 data 4096 out Oct 13 13:57:56 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:56 ko kernel: ata2.00: cmd 61/08:30:50:1b:2f/00:00:07:00:00/40 tag 6 cdb 0x0 data 4096 out Oct 13 13:57:56 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:56 ko kernel: ata2.00: cmd 61/08:38:30:1b:3b/00:00:07:00:00/40 tag 7 cdb 0x0 data 4096 out Oct 13 13:57:56 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:57 ko kernel: ata2.00: cmd 61/08:40:38:1b:43/00:00:07:00:00/40 tag 8 cdb 0x0 data 4096 out Oct 13 13:57:57 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:57 ko kernel: ata2.00: cmd 61/08:48:58:1b:67/00:00:07:00:00/40 tag 9 cdb 0x0 data 4096 out Oct 13 13:57:57 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:57 ko kernel: ata2.00: cmd 61/08:50:38:1b:6b/00:00:07:00:00/40 tag 10 cdb 0x0 data 4096 out Oct 13 13:57:57 ko kernel: res 40/00:10:40:1c:4b/00:00:0d:00:00/40 Emask 0x2 (HSM violation) Oct 13 13:57:57 ko kernel: ata2.00: cmd 61/08:58:90:1b:97/00:00:07:00:00/40 tag 11 cdb 0x0 data 4096 out Oct 13 13:57:57 ko
Re: Hitachi disk: spurious completions during NCQ
On 10/13/07, Andrew Morton [EMAIL PROTECTED] wrote: On Wed, 10 Oct 2007 21:03:43 +0200 Luca Tettamanti [EMAIL PROTECTED] wrote: Hello, sometimes kernel complains about spurious completions on my new notebook: ata3.00: exception Emask 0x2 SAct 0x407fd SErr 0x0 action 0x2 frozen ata3.00: spurious completions during NCQ issue=0x0 SAct=0x407fd FIS=005040a1:0002 ata3.00: cmd 61/08:00:c7:5a:82/00:00:1b:00:00/40 tag 0 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:10:3f:5b:fa/00:00:18:00:00/40 tag 2 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:18:5f:5b:fa/00:00:18:00:00/40 tag 3 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/18:20:6f:5b:fa/00:00:18:00:00/40 tag 4 cdb 0x0 data 12288 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:28:e7:19:fd/00:00:18:00:00/40 tag 5 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:30:df:59:ae/00:00:1a:00:00/40 tag 6 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:38:3f:5a:ae/00:00:1a:00:00/40 tag 7 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:40:6f:62:ae/00:00:1a:00:00/40 tag 8 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/28:48:d7:59:7e/00:00:1b:00:00/40 tag 9 cdb 0x0 data 20480 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/10:50:07:5b:82/00:00:1b:00:00/40 tag 10 cdb 0x0 data 8192 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/30:90:f7:5a:fa/00:00:18:00:00/40 tag 18 cdb 0x0 data 24576 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3: soft resetting port ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: configured for UDMA/133 ata3: EH complete sd 2:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB) sd 2:0:0:0: [sda] Write Protect is off sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (this is a very recent 2.6.23-git, SMP, x86_64) The latest kernel, a serious-looking problem, sent to the correct mailing lists. After two days nobody has bothered replying. The disk is: ATA device, with non-removable media Model Number: Hitachi HTS542525K9SA00 Firmware Revision: BBFOC31P The controller is: 00:1f.2 SATA controller: Intel Corporation Mobile SATA AHCI Controller (rev 03) (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. Unknown device 14e7 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin B routed to IRQ 1272 Region 0: I/O ports at ec00 [size=8] Region 1: I/O ports at e880 [size=4] Region 2: I/O ports at e800 [size=8] Region 3: I/O ports at e480 [size=4] Region 4: I/O ports at e400 [size=32] Region 5: Memory at febff800 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/2 Enable+ Address: fee0300c Data: 41b9 Capabilities: [70] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a8] #12 [0010] and I'm using AHCI driver. I see that similar disks are already blacklisted, probably this one is bugged too - though the error is pretty rare :( Does this cause any other symptoms? ie: does the system otherwise work OK? The system is stable, the EH seems to be doing its job. Luca - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Hitachi disk: spurious completions during NCQ
On Wed, 10 Oct 2007 21:03:43 +0200 Luca Tettamanti <[EMAIL PROTECTED]> wrote: > Hello, > sometimes kernel complains about spurious completions on my new > notebook: > > ata3.00: exception Emask 0x2 SAct 0x407fd SErr 0x0 action 0x2 frozen > ata3.00: spurious completions during NCQ issue=0x0 SAct=0x407fd > FIS=005040a1:0002 > ata3.00: cmd 61/08:00:c7:5a:82/00:00:1b:00:00/40 tag 0 cdb 0x0 data 4096 out > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > ata3.00: cmd 61/08:10:3f:5b:fa/00:00:18:00:00/40 tag 2 cdb 0x0 data 4096 out > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > ata3.00: cmd 61/08:18:5f:5b:fa/00:00:18:00:00/40 tag 3 cdb 0x0 data 4096 out > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > ata3.00: cmd 61/18:20:6f:5b:fa/00:00:18:00:00/40 tag 4 cdb 0x0 data 12288 out > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > ata3.00: cmd 61/08:28:e7:19:fd/00:00:18:00:00/40 tag 5 cdb 0x0 data 4096 out > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > ata3.00: cmd 61/08:30:df:59:ae/00:00:1a:00:00/40 tag 6 cdb 0x0 data 4096 out > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > ata3.00: cmd 61/08:38:3f:5a:ae/00:00:1a:00:00/40 tag 7 cdb 0x0 data 4096 out > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > ata3.00: cmd 61/08:40:6f:62:ae/00:00:1a:00:00/40 tag 8 cdb 0x0 data 4096 out > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > ata3.00: cmd 61/28:48:d7:59:7e/00:00:1b:00:00/40 tag 9 cdb 0x0 data 20480 out > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > ata3.00: cmd 61/10:50:07:5b:82/00:00:1b:00:00/40 tag 10 cdb 0x0 data 8192 out > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > ata3.00: cmd 61/30:90:f7:5a:fa/00:00:18:00:00/40 tag 18 cdb 0x0 data 24576 out > res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) > ata3: soft resetting port > ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > ata3.00: configured for UDMA/133 > ata3: EH complete > sd 2:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB) > sd 2:0:0:0: [sda] Write Protect is off > sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 > sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support > DPO or FUA > > (this is a very recent 2.6.23-git, SMP, x86_64) The latest kernel, a serious-looking problem, sent to the correct mailing lists. After two days nobody has bothered replying. > The disk is: > > ATA device, with non-removable media > Model Number: Hitachi HTS542525K9SA00 > Firmware Revision: BBFOC31P > > The controller is: > > 00:1f.2 SATA controller: Intel Corporation Mobile SATA AHCI Controller (rev > 03) (prog-if 01 [AHCI 1.0]) > Subsystem: ASUSTeK Computer Inc. Unknown device 14e7 > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > SERR- Latency: 0 > Interrupt: pin B routed to IRQ 1272 > Region 0: I/O ports at ec00 [size=8] > Region 1: I/O ports at e880 [size=4] > Region 2: I/O ports at e800 [size=8] > Region 3: I/O ports at e480 [size=4] > Region 4: I/O ports at e400 [size=32] > Region 5: Memory at febff800 (32-bit, non-prefetchable) [size=2K] > Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- > Queue=0/2 Enable+ > Address: fee0300c Data: 41b9 > Capabilities: [70] Power Management version 3 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA > PME(D0-,D1-,D2-,D3hot+,D3cold-) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Capabilities: [a8] #12 [0010] > > and I'm using AHCI driver. > > I see that similar disks are already blacklisted, probably this one is > bugged too - though the error is pretty rare :( > Does this cause any other symptoms? ie: does the system otherwise work OK? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Hitachi disk: spurious completions during NCQ
On Wed, 10 Oct 2007 21:03:43 +0200 Luca Tettamanti [EMAIL PROTECTED] wrote: Hello, sometimes kernel complains about spurious completions on my new notebook: ata3.00: exception Emask 0x2 SAct 0x407fd SErr 0x0 action 0x2 frozen ata3.00: spurious completions during NCQ issue=0x0 SAct=0x407fd FIS=005040a1:0002 ata3.00: cmd 61/08:00:c7:5a:82/00:00:1b:00:00/40 tag 0 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:10:3f:5b:fa/00:00:18:00:00/40 tag 2 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:18:5f:5b:fa/00:00:18:00:00/40 tag 3 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/18:20:6f:5b:fa/00:00:18:00:00/40 tag 4 cdb 0x0 data 12288 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:28:e7:19:fd/00:00:18:00:00/40 tag 5 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:30:df:59:ae/00:00:1a:00:00/40 tag 6 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:38:3f:5a:ae/00:00:1a:00:00/40 tag 7 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:40:6f:62:ae/00:00:1a:00:00/40 tag 8 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/28:48:d7:59:7e/00:00:1b:00:00/40 tag 9 cdb 0x0 data 20480 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/10:50:07:5b:82/00:00:1b:00:00/40 tag 10 cdb 0x0 data 8192 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/30:90:f7:5a:fa/00:00:18:00:00/40 tag 18 cdb 0x0 data 24576 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3: soft resetting port ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: configured for UDMA/133 ata3: EH complete sd 2:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB) sd 2:0:0:0: [sda] Write Protect is off sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (this is a very recent 2.6.23-git, SMP, x86_64) The latest kernel, a serious-looking problem, sent to the correct mailing lists. After two days nobody has bothered replying. The disk is: ATA device, with non-removable media Model Number: Hitachi HTS542525K9SA00 Firmware Revision: BBFOC31P The controller is: 00:1f.2 SATA controller: Intel Corporation Mobile SATA AHCI Controller (rev 03) (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. Unknown device 14e7 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin B routed to IRQ 1272 Region 0: I/O ports at ec00 [size=8] Region 1: I/O ports at e880 [size=4] Region 2: I/O ports at e800 [size=8] Region 3: I/O ports at e480 [size=4] Region 4: I/O ports at e400 [size=32] Region 5: Memory at febff800 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/2 Enable+ Address: fee0300c Data: 41b9 Capabilities: [70] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a8] #12 [0010] and I'm using AHCI driver. I see that similar disks are already blacklisted, probably this one is bugged too - though the error is pretty rare :( Does this cause any other symptoms? ie: does the system otherwise work OK? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Hitachi disk: spurious completions during NCQ
Hello, sometimes kernel complains about spurious completions on my new notebook: ata3.00: exception Emask 0x2 SAct 0x407fd SErr 0x0 action 0x2 frozen ata3.00: spurious completions during NCQ issue=0x0 SAct=0x407fd FIS=005040a1:0002 ata3.00: cmd 61/08:00:c7:5a:82/00:00:1b:00:00/40 tag 0 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:10:3f:5b:fa/00:00:18:00:00/40 tag 2 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:18:5f:5b:fa/00:00:18:00:00/40 tag 3 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/18:20:6f:5b:fa/00:00:18:00:00/40 tag 4 cdb 0x0 data 12288 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:28:e7:19:fd/00:00:18:00:00/40 tag 5 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:30:df:59:ae/00:00:1a:00:00/40 tag 6 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:38:3f:5a:ae/00:00:1a:00:00/40 tag 7 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:40:6f:62:ae/00:00:1a:00:00/40 tag 8 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/28:48:d7:59:7e/00:00:1b:00:00/40 tag 9 cdb 0x0 data 20480 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/10:50:07:5b:82/00:00:1b:00:00/40 tag 10 cdb 0x0 data 8192 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/30:90:f7:5a:fa/00:00:18:00:00/40 tag 18 cdb 0x0 data 24576 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3: soft resetting port ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: configured for UDMA/133 ata3: EH complete sd 2:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB) sd 2:0:0:0: [sda] Write Protect is off sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (this is a very recent 2.6.23-git, SMP, x86_64) The disk is: ATA device, with non-removable media Model Number: Hitachi HTS542525K9SA00 Firmware Revision: BBFOC31P The controller is: 00:1f.2 SATA controller: Intel Corporation Mobile SATA AHCI Controller (rev 03) (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. Unknown device 14e7 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Hitachi disk: spurious completions during NCQ
Hello, sometimes kernel complains about spurious completions on my new notebook: ata3.00: exception Emask 0x2 SAct 0x407fd SErr 0x0 action 0x2 frozen ata3.00: spurious completions during NCQ issue=0x0 SAct=0x407fd FIS=005040a1:0002 ata3.00: cmd 61/08:00:c7:5a:82/00:00:1b:00:00/40 tag 0 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:10:3f:5b:fa/00:00:18:00:00/40 tag 2 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:18:5f:5b:fa/00:00:18:00:00/40 tag 3 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/18:20:6f:5b:fa/00:00:18:00:00/40 tag 4 cdb 0x0 data 12288 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:28:e7:19:fd/00:00:18:00:00/40 tag 5 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:30:df:59:ae/00:00:1a:00:00/40 tag 6 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:38:3f:5a:ae/00:00:1a:00:00/40 tag 7 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/08:40:6f:62:ae/00:00:1a:00:00/40 tag 8 cdb 0x0 data 4096 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/28:48:d7:59:7e/00:00:1b:00:00/40 tag 9 cdb 0x0 data 20480 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/10:50:07:5b:82/00:00:1b:00:00/40 tag 10 cdb 0x0 data 8192 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3.00: cmd 61/30:90:f7:5a:fa/00:00:18:00:00/40 tag 18 cdb 0x0 data 24576 out res 50/00:10:07:5b:82/00:00:1b:00:00/40 Emask 0x2 (HSM violation) ata3: soft resetting port ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: configured for UDMA/133 ata3: EH complete sd 2:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB) sd 2:0:0:0: [sda] Write Protect is off sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (this is a very recent 2.6.23-git, SMP, x86_64) The disk is: ATA device, with non-removable media Model Number: Hitachi HTS542525K9SA00 Firmware Revision: BBFOC31P The controller is: 00:1f.2 SATA controller: Intel Corporation Mobile SATA AHCI Controller (rev 03) (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. Unknown device 14e7 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin B routed to IRQ 1272 Region 0: I/O ports at ec00 [size=8] Region 1: I/O ports at e880 [size=4] Region 2: I/O ports at e800 [size=8] Region 3: I/O ports at e480 [size=4] Region 4: I/O ports at e400 [size=32] Region 5: Memory at febff800 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/2 Enable+ Address: fee0300c Data: 41b9 Capabilities: [70] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a8] #12 [0010] and I'm using AHCI driver. I see that similar disks are already blacklisted, probably this one is bugged too - though the error is pretty rare :( Luca -- Di tutte le perversioni sessuali, la castita` e` la piu` strana. Anatole France - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Spurious completions during NCQ with ahci/WDC WD1600BEVS-2
This happens with all kernel from 2.6.21 up to today Linus's git. >From time to time, i am getting the following error in dmesg (more information follows): ata1.00: exception Emask 0x2 SAct 0xffc SErr 0x0 action 0x2 frozen ata1.00: spurious completions during NCQ issue=0x0 SAct=0xffc FIS=004040a1:0004 ata1.00: cmd 61/10:10:c8:c4:c8/00:00:11:00:00/40 tag 2 cdb 0x0 data 8192 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/08:18:e0:c4:c8/00:00:11:00:00/40 tag 3 cdb 0x0 data 4096 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/08:20:b0:8c:c9/00:00:11:00:00/40 tag 4 cdb 0x0 data 4096 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/08:28:d0:8c:c9/00:00:11:00:00/40 tag 5 cdb 0x0 data 4096 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/08:30:f8:fa:c9/00:00:11:00:00/40 tag 6 cdb 0x0 data 4096 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/08:38:90:c4:fc/00:00:11:00:00/40 tag 7 cdb 0x0 data 4096 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/08:40:e8:c4:fc/00:00:11:00:00/40 tag 8 cdb 0x0 data 4096 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/08:48:f8:c4:fc/00:00:11:00:00/40 tag 9 cdb 0x0 data 4096 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/10:50:f0:c6:80/00:00:12:00:00/40 tag 10 cdb 0x0 data 8192 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/08:58:50:c7:80/00:00:12:00:00/40 tag 11 cdb 0x0 data 4096 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1: soft resetting port 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] 312581808 512-byte hardware sectors (160042 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 $ sdparm -a -v /dev/sda: /dev/sda: ATA WDC WD1600BEVS-2 04.0 Read write error recovery [0x1] mode page [PS=0]: AWRE1 ARRE1 TB 0 RC 0 EER 0 PER 0 DTE 0 DCR 0 RRC 0 COR_S 0 HOC 0 DSOC0 WRC 0 RTL 0 >> Disconnect-reconnect (SPC + transports) mode page [0x2] not supported >> Format (SBC) mode page [0x3] not supported >> Rigid disk (SBC) mode page [0x4] not supported >> Verify error recovery (SBC) mode page [0x7] not supported Caching (SBC) [0x8] mode page [PS=0]: IC 0 ABPF0 CAP 0 DISC0 SIZE0 WCE 1 MF 0 RCD 0 DRRP0 WRP 0 DPTL0 MIPF0 MAPF0 MAPFC 0 FSW 0 LBCSS 0 DRA 0 NV_DIS 0 NCS 0 CSS 0 Control [0xa] mode page [PS=0]: TST 0 TMF_ONLY0 D_SENSE 0 GLTSD 1 RLEC0 QAM 0 QERR0 RAC 0 UA_INTLCK 0 SWP 0 ATO 0 TAS 0 AUTOLOAD0 BTP-1 ESTCT 30 >> Control extension mode subpage [0xa,0x1] not supported >> SAT pATA control mode subpage [0xa,0xf1] not supported >> Power condition - old version mode page [0xd] not supported >> XOR control (SBC) mode page [0x10] not supported >> Protocol specific logical unit mode page [0x18] not supported >> Protocol specific port mode page [0x19] not supported >> Power condition mode page [0x1a] not supported >> Informational exceptions control mode page [0x1c] not supported >> Background control (SBC) mode subpage [0x1c,0x1] not supported $ lspci -vv -nn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile Memory Controller Hub [8086:2a00] (rev 03) Subsystem: Acer Incorporated [ALI] Unknown device [1025:011f] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- Capabilities: [40] Express Root Port (Slot+) IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s unlimited, L1 unlimited Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 1
Spurious completions during NCQ with ahci/WDC WD1600BEVS-2
This happens with all kernel from 2.6.21 up to today Linus's git. From time to time, i am getting the following error in dmesg (more information follows): ata1.00: exception Emask 0x2 SAct 0xffc SErr 0x0 action 0x2 frozen ata1.00: spurious completions during NCQ issue=0x0 SAct=0xffc FIS=004040a1:0004 ata1.00: cmd 61/10:10:c8:c4:c8/00:00:11:00:00/40 tag 2 cdb 0x0 data 8192 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/08:18:e0:c4:c8/00:00:11:00:00/40 tag 3 cdb 0x0 data 4096 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/08:20:b0:8c:c9/00:00:11:00:00/40 tag 4 cdb 0x0 data 4096 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/08:28:d0:8c:c9/00:00:11:00:00/40 tag 5 cdb 0x0 data 4096 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/08:30:f8:fa:c9/00:00:11:00:00/40 tag 6 cdb 0x0 data 4096 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/08:38:90:c4:fc/00:00:11:00:00/40 tag 7 cdb 0x0 data 4096 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/08:40:e8:c4:fc/00:00:11:00:00/40 tag 8 cdb 0x0 data 4096 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/08:48:f8:c4:fc/00:00:11:00:00/40 tag 9 cdb 0x0 data 4096 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/10:50:f0:c6:80/00:00:12:00:00/40 tag 10 cdb 0x0 data 8192 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/08:58:50:c7:80/00:00:12:00:00/40 tag 11 cdb 0x0 data 4096 out res 40/00:5c:50:c7:80/00:00:12:00:00/40 Emask 0x2 (HSM violation) ata1: soft resetting port 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] 312581808 512-byte hardware sectors (160042 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 $ sdparm -a -v /dev/sda: /dev/sda: ATA WDC WD1600BEVS-2 04.0 Read write error recovery [0x1] mode page [PS=0]: AWRE1 ARRE1 TB 0 RC 0 EER 0 PER 0 DTE 0 DCR 0 RRC 0 COR_S 0 HOC 0 DSOC0 WRC 0 RTL 0 Disconnect-reconnect (SPC + transports) mode page [0x2] not supported Format (SBC) mode page [0x3] not supported Rigid disk (SBC) mode page [0x4] not supported Verify error recovery (SBC) mode page [0x7] not supported Caching (SBC) [0x8] mode page [PS=0]: IC 0 ABPF0 CAP 0 DISC0 SIZE0 WCE 1 MF 0 RCD 0 DRRP0 WRP 0 DPTL0 MIPF0 MAPF0 MAPFC 0 FSW 0 LBCSS 0 DRA 0 NV_DIS 0 NCS 0 CSS 0 Control [0xa] mode page [PS=0]: TST 0 TMF_ONLY0 D_SENSE 0 GLTSD 1 RLEC0 QAM 0 QERR0 RAC 0 UA_INTLCK 0 SWP 0 ATO 0 TAS 0 AUTOLOAD0 BTP-1 ESTCT 30 Control extension mode subpage [0xa,0x1] not supported SAT pATA control mode subpage [0xa,0xf1] not supported Power condition - old version mode page [0xd] not supported XOR control (SBC) mode page [0x10] not supported Protocol specific logical unit mode page [0x18] not supported Protocol specific port mode page [0x19] not supported Power condition mode page [0x1a] not supported Informational exceptions control mode page [0x1c] not supported Background control (SBC) mode subpage [0x1c,0x1] not supported $ lspci -vv -nn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile Memory Controller Hub [8086:2a00] (rev 03) Subsystem: Acer Incorporated [ALI] Unknown device [1025:011f] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- Latency: 0 Capabilities: [e0] Vendor Specific Information 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile Integrated Graphics Controller [8086:2a02] (rev 03) (prog-if 00 [VGA]) Subsystem: Acer Incorporated [ALI] Unknown device [1025:011f] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at fc00 (64-bit, non-prefetchable) [size=1M] Region 2: Memory at d000 (64-bit, prefetchable) [size=256M
Re: spurious completions during NCQ?
Massimiliano Hofer wrote: > On Friday 8 June 2007, Alan Cox wrote: > >>> Model Number: HITACHI HTS541680J9SA00 >>> Serial Number: SB**I57L4A >> This one is already blacklisted in the windows drivers. > > I have the same problem with this drive (shipped with a Thinkpad Z61m): > > Model Number: HITACHI HTS541612J9SA00 > Firmware Revision: SBDIC7JP > > It reported several dozen spurious completions over a few days, but I can't > find any corruption. Is it really dangerous? I understand this clearly is a > firmware bug, but I'm not sure how to interpret the drive behavior. > I can perform any test you like, if you find it useful. It has _slight_ change of being dangerous and is just in violation of the protocol. No real data corruption case reported yet tho. Till now most drives which report such problems had stinky NCQ implementation anyway - slow, buggy, blacklisted in the other OS, etc... I'll submit a patch to blacklist the drive. Thanks. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: spurious completions during NCQ?
Massimiliano Hofer wrote: On Friday 8 June 2007, Alan Cox wrote: Model Number: HITACHI HTS541680J9SA00 Serial Number: SB**I57L4A This one is already blacklisted in the windows drivers. I have the same problem with this drive (shipped with a Thinkpad Z61m): Model Number: HITACHI HTS541612J9SA00 Firmware Revision: SBDIC7JP It reported several dozen spurious completions over a few days, but I can't find any corruption. Is it really dangerous? I understand this clearly is a firmware bug, but I'm not sure how to interpret the drive behavior. I can perform any test you like, if you find it useful. It has _slight_ change of being dangerous and is just in violation of the protocol. No real data corruption case reported yet tho. Till now most drives which report such problems had stinky NCQ implementation anyway - slow, buggy, blacklisted in the other OS, etc... I'll submit a patch to blacklist the drive. Thanks. -- tejun - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: spurious completions during NCQ?
On Friday 8 June 2007, Alan Cox wrote: > > Model Number: HITACHI HTS541680J9SA00 > > Serial Number: SB**I57L4A > > This one is already blacklisted in the windows drivers. I have the same problem with this drive (shipped with a Thinkpad Z61m): Model Number: HITACHI HTS541612J9SA00 Firmware Revision: SBDIC7JP It reported several dozen spurious completions over a few days, but I can't find any corruption. Is it really dangerous? I understand this clearly is a firmware bug, but I'm not sure how to interpret the drive behavior. I can perform any test you like, if you find it useful. -- Saluti, Massimiliano Hofer - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: spurious completions during NCQ?
On Friday 8 June 2007, Alan Cox wrote: Model Number: HITACHI HTS541680J9SA00 Serial Number: SB**I57L4A This one is already blacklisted in the windows drivers. I have the same problem with this drive (shipped with a Thinkpad Z61m): Model Number: HITACHI HTS541612J9SA00 Firmware Revision: SBDIC7JP It reported several dozen spurious completions over a few days, but I can't find any corruption. Is it really dangerous? I understand this clearly is a firmware bug, but I'm not sure how to interpret the drive behavior. I can perform any test you like, if you find it useful. -- Saluti, Massimiliano Hofer - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: spurious completions during NCQ?
> Model Number: HITACHI HTS541680J9SA00 > Serial Number: SB**I57L4A This one is already blacklisted in the windows drivers. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: spurious completions during NCQ?
On Fri, Jun 08, 2007 at 09:55:58PM +0900, Tejun Heo wrote:
> Florin Iucha wrote:
> >> It means the drive reported command tags were completed that were not
> >> outstanding. What kind of drive is this?
> >
> > [ 29.033142] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors
> > = 156
> > 301488
> > [ 29.033146] ata1.00: ATA-7: HITACHI HTS541680J9SA00, SB2IC7EP, max
> > UDMA/100
> > [ 29.033149] ata1.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 31/32)
> > [ 29.034230] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors
> > = 156
> > 301488
>
> Please report the result of 'hdparm -I /dev/sda'. We'll probably have
> to blacklist it for NCQ.
Here it is: I only jumbled the serial number a bit.
/dev/sda:
ATA device, with non-removable media
Model Number: HITACHI HTS541680J9SA00
Serial Number: SB**I57L4A
Firmware Revision: SB2IC7EP
Standards:
Used: ATA/ATAPI-7 T13 1532D revision 1
Supported: 7 6 5 4
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBAuser addressable sectors: 156301488
LBA48 user addressable sectors: 156301488
device size with M = 1024*1024: 76319 MBytes
device size with M = 1000*1000: 80026 MBytes (80 GB)
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Vendor, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: 128 (0x80)
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
*SMART feature set
Security Mode feature set
*Power Management feature set
*Write cache
*Look-ahead
*Host Protected Area feature set
*WRITE_BUFFER command
*READ_BUFFER command
*NOP cmd
*DOWNLOAD_MICROCODE
*Advanced Power Management feature set
SET_MAX security extension
Automatic Acoustic Management feature set
*48-bit Address feature set
*Device Configuration Overlay feature set
*Mandatory FLUSH_CACHE
*FLUSH_CACHE_EXT
*SMART error logging
*SMART self-test
*General Purpose Logging feature set
*WRITE_{DMA|MULTIPLE}_FUA_EXT
*64-bit World wide name
*IDLE_IMMEDIATE with UNLOAD
*SATA-I signaling speed (1.5Gb/s)
*Native Command Queueing (NCQ)
*Host-initiated interface power management
*Phy event counters
Non-Zero buffer offsets in DMA Setup FIS
DMA Setup Auto-Activate optimization
Device-initiated interface power management
In-order data delivery
*Software settings preservation
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
42min for SECURITY ERASE UNIT.
Checksum: correct
florin
--
Bruce Schneier expects the Spanish Inquisition.
http://geekz.co.uk/schneierfacts/fact/163
signature.asc
Description: Digital signature
Re: spurious completions during NCQ?
Florin Iucha wrote: > On Wed, Jun 06, 2007 at 08:28:07AM -0600, Robert Hancock wrote: >>> This is on a Thinkpad T60 with 2 GB RAM, running Ubuntu 7.04 (kernel >>> 2.6.20-16-generic). No proprietary drivers (ok, maybe the Intel >>> Wi-Fi - but that should not count). >>> >>> The laptop came with Windows but I blew that away - did I mess some >>> thing up regarding HPA and its ilk? >> It means the drive reported command tags were completed that were not >> outstanding. What kind of drive is this? > > [ 29.033142] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors = > 156 > 301488 > [ 29.033146] ata1.00: ATA-7: HITACHI HTS541680J9SA00, SB2IC7EP, max UDMA/100 > [ 29.033149] ata1.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 31/32) > [ 29.034230] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors = > 156 > 301488 Please report the result of 'hdparm -I /dev/sda'. We'll probably have to blacklist it for NCQ. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: spurious completions during NCQ?
On Fri, Jun 08, 2007 at 09:55:58PM +0900, Tejun Heo wrote:
Florin Iucha wrote:
It means the drive reported command tags were completed that were not
outstanding. What kind of drive is this?
[ 29.033142] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors
= 156
301488
[ 29.033146] ata1.00: ATA-7: HITACHI HTS541680J9SA00, SB2IC7EP, max
UDMA/100
[ 29.033149] ata1.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 29.034230] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors
= 156
301488
Please report the result of 'hdparm -I /dev/sda'. We'll probably have
to blacklist it for NCQ.
Here it is: I only jumbled the serial number a bit.
/dev/sda:
ATA device, with non-removable media
Model Number: HITACHI HTS541680J9SA00
Serial Number: SB**I57L4A
Firmware Revision: SB2IC7EP
Standards:
Used: ATA/ATAPI-7 T13 1532D revision 1
Supported: 7 6 5 4
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBAuser addressable sectors: 156301488
LBA48 user addressable sectors: 156301488
device size with M = 1024*1024: 76319 MBytes
device size with M = 1000*1000: 80026 MBytes (80 GB)
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Vendor, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: 128 (0x80)
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
*SMART feature set
Security Mode feature set
*Power Management feature set
*Write cache
*Look-ahead
*Host Protected Area feature set
*WRITE_BUFFER command
*READ_BUFFER command
*NOP cmd
*DOWNLOAD_MICROCODE
*Advanced Power Management feature set
SET_MAX security extension
Automatic Acoustic Management feature set
*48-bit Address feature set
*Device Configuration Overlay feature set
*Mandatory FLUSH_CACHE
*FLUSH_CACHE_EXT
*SMART error logging
*SMART self-test
*General Purpose Logging feature set
*WRITE_{DMA|MULTIPLE}_FUA_EXT
*64-bit World wide name
*IDLE_IMMEDIATE with UNLOAD
*SATA-I signaling speed (1.5Gb/s)
*Native Command Queueing (NCQ)
*Host-initiated interface power management
*Phy event counters
Non-Zero buffer offsets in DMA Setup FIS
DMA Setup Auto-Activate optimization
Device-initiated interface power management
In-order data delivery
*Software settings preservation
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
42min for SECURITY ERASE UNIT.
Checksum: correct
florin
--
Bruce Schneier expects the Spanish Inquisition.
http://geekz.co.uk/schneierfacts/fact/163
signature.asc
Description: Digital signature
Re: spurious completions during NCQ?
Florin Iucha wrote: On Wed, Jun 06, 2007 at 08:28:07AM -0600, Robert Hancock wrote: This is on a Thinkpad T60 with 2 GB RAM, running Ubuntu 7.04 (kernel 2.6.20-16-generic). No proprietary drivers (ok, maybe the Intel Wi-Fi - but that should not count). The laptop came with Windows but I blew that away - did I mess some thing up regarding HPA and its ilk? It means the drive reported command tags were completed that were not outstanding. What kind of drive is this? [ 29.033142] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors = 156 301488 [ 29.033146] ata1.00: ATA-7: HITACHI HTS541680J9SA00, SB2IC7EP, max UDMA/100 [ 29.033149] ata1.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 29.034230] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors = 156 301488 Please report the result of 'hdparm -I /dev/sda'. We'll probably have to blacklist it for NCQ. -- tejun - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: spurious completions during NCQ?
Model Number: HITACHI HTS541680J9SA00 Serial Number: SB**I57L4A This one is already blacklisted in the windows drivers. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: spurious completions during NCQ?
On Wed, Jun 06, 2007 at 08:28:07AM -0600, Robert Hancock wrote: > >This is on a Thinkpad T60 with 2 GB RAM, running Ubuntu 7.04 (kernel > >2.6.20-16-generic). No proprietary drivers (ok, maybe the Intel > >Wi-Fi - but that should not count). > > > >The laptop came with Windows but I blew that away - did I mess some > >thing up regarding HPA and its ilk? > > It means the drive reported command tags were completed that were not > outstanding. What kind of drive is this? [ 29.033142] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors = 156 301488 [ 29.033146] ata1.00: ATA-7: HITACHI HTS541680J9SA00, SB2IC7EP, max UDMA/100 [ 29.033149] ata1.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 29.034230] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors = 156 301488 florin -- Bruce Schneier expects the Spanish Inquisition. http://geekz.co.uk/schneierfacts/fact/163 signature.asc Description: Digital signature
Re: spurious completions during NCQ?
On Wed, Jun 06, 2007 at 08:28:07AM -0600, Robert Hancock wrote: This is on a Thinkpad T60 with 2 GB RAM, running Ubuntu 7.04 (kernel 2.6.20-16-generic). No proprietary drivers (ok, maybe the Intel Wi-Fi - but that should not count). The laptop came with Windows but I blew that away - did I mess some thing up regarding HPA and its ilk? It means the drive reported command tags were completed that were not outstanding. What kind of drive is this? [ 29.033142] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors = 156 301488 [ 29.033146] ata1.00: ATA-7: HITACHI HTS541680J9SA00, SB2IC7EP, max UDMA/100 [ 29.033149] ata1.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 29.034230] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors = 156 301488 florin -- Bruce Schneier expects the Spanish Inquisition. http://geekz.co.uk/schneierfacts/fact/163 signature.asc Description: Digital signature
Re: spurious completions during NCQ?
Florin Iucha wrote: Hello, I was working on a I/O heavy workload (parsing 100K spam messages to extract certain structures) when I got this in the kernel log: .. This is on a Thinkpad T60 with 2 GB RAM, running Ubuntu 7.04 (kernel 2.6.20-16-generic). No proprietary drivers (ok, maybe the Intel Wi-Fi - but that should not count). The laptop came with Windows but I blew that away - did I mess some thing up regarding HPA and its ilk? It means the drive reported command tags were completed that were not outstanding. What kind of drive is this? -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [EMAIL PROTECTED] Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: spurious completions during NCQ?
Florin Iucha wrote: Hello, I was working on a I/O heavy workload (parsing 100K spam messages to extract certain structures) when I got this in the kernel log: .. This is on a Thinkpad T60 with 2 GB RAM, running Ubuntu 7.04 (kernel 2.6.20-16-generic). No proprietary drivers (ok, maybe the Intel Wi-Fi - but that should not count). The laptop came with Windows but I blew that away - did I mess some thing up regarding HPA and its ilk? It means the drive reported command tags were completed that were not outstanding. What kind of drive is this? -- Robert Hancock Saskatoon, SK, Canada To email, remove nospam from [EMAIL PROTECTED] Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
spurious completions during NCQ?
Hello, I was working on a I/O heavy workload (parsing 100K spam messages to extract certain structures) when I got this in the kernel log: [ 2320.132893] ata1.00: exception Emask 0x2 SAct 0x701f SErr 0x0 action 0x2 frozen [ 2320.132899] ata1.00: (spurious completions during NCQ issue=0x0 SAct=0x701f FIS=005040a1:0800) [ 2320.132905] ata1.00: cmd 61/10:00:59:fc:d0/00:00:07:00:00/40 tag 0 cdb 0x0 data 8192 out [ 2320.132906] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132911] ata1.00: cmd 61/10:08:69:fc:d0/00:00:07:00:00/40 tag 1 cdb 0x0 data 8192 out [ 2320.132913] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132918] ata1.00: cmd 61/08:10:19:4c:d1/00:00:07:00:00/40 tag 2 cdb 0x0 data 4096 out [ 2320.132919] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132924] ata1.00: cmd 61/01:18:fb:27:0f/00:00:08:00:00/40 tag 3 cdb 0x0 data 512 out [ 2320.132925] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132930] ata1.00: cmd 61/08:20:11:28:0f/00:00:08:00:00/40 tag 4 cdb 0x0 data 4096 out [ 2320.132932] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132937] ata1.00: cmd 61/08:28:91:92:17/00:00:08:00:00/40 tag 5 cdb 0x0 data 4096 out [ 2320.132938] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132943] ata1.00: cmd 61/08:30:99:b3:17/00:00:08:00:00/40 tag 6 cdb 0x0 data 4096 out [ 2320.132944] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132949] ata1.00: cmd 61/01:38:5b:56:4b/00:00:05:00:00/40 tag 7 cdb 0x0 data 512 out [ 2320.132950] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132956] ata1.00: cmd 61/08:40:71:56:4b/00:00:05:00:00/40 tag 8 cdb 0x0 data 4096 out [ 2320.132957] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132962] ata1.00: cmd 61/08:48:09:cf:5a/00:00:05:00:00/40 tag 9 cdb 0x0 data 4096 out [ 2320.132963] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132968] ata1.00: cmd 61/01:50:3b:af:8b/00:00:05:00:00/40 tag 10 cdb 0x0 data 512 out [ 2320.132969] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132974] ata1.00: cmd 61/08:58:51:af:8b/00:00:05:00:00/40 tag 11 cdb 0x0 data 4096 out [ 2320.132976] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132981] ata1.00: cmd 61/08:60:d9:f1:8d/00:00:05:00:00/40 tag 12 cdb 0x0 data 4096 out [ 2320.132982] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132987] ata1.00: cmd 61/08:68:49:bd:8e/00:00:05:00:00/40 tag 13 cdb 0x0 data 4096 out [ 2320.132988] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132993] ata1.00: cmd 61/08:70:d9:63:d1/00:00:05:00:00/40 tag 14 cdb 0x0 data 4096 out [ 2320.132995] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133000] ata1.00: cmd 61/08:78:91:39:0f/00:00:06:00:00/40 tag 15 cdb 0x0 data 4096 out [ 2320.133001] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133006] ata1.00: cmd 61/08:80:49:30:97/00:00:06:00:00/40 tag 16 cdb 0x0 data 4096 out [ 2320.133007] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133013] ata1.00: cmd 61/08:88:41:c0:d0/00:00:06:00:00/40 tag 17 cdb 0x0 data 4096 out [ 2320.133014] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133019] ata1.00: cmd 61/08:90:b9:8c:d1/00:00:06:00:00/40 tag 18 cdb 0x0 data 4096 out [ 2320.133020] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133025] ata1.00: cmd 61/01:98:1b:cf:ce/00:00:07:00:00/40 tag 19 cdb 0x0 data 512 out [ 2320.133027] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133032] ata1.00: cmd 61/08:a0:31:cf:ce/00:00:07:00:00/40 tag 20 cdb 0x0 data 4096 out [ 2320.133033] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133038] ata1.00: cmd 61/10:e0:41:af:8b/00:00:05:00:00/40 tag 28 cdb 0x0 data 8192 out [ 2320.133039] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133044] ata1.00: cmd 61/01:e8:ba:12:8d/00:00:06:00:00/40 tag 29 cdb 0x0 data 512 out [ 2320.133046] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133051] ata1.00: cmd 61/10:f0:c1:12:8d/00:00:06:00:00/40 tag 30 cdb 0x0 data 8192 out [ 2320.133052] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.378387] ata1: soft resetting port [ 2320.442169] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 2320.460012] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors = 156301488 [ 2320.461395] ata1.00: ata_hpa_resize
spurious completions during NCQ?
Hello, I was working on a I/O heavy workload (parsing 100K spam messages to extract certain structures) when I got this in the kernel log: [ 2320.132893] ata1.00: exception Emask 0x2 SAct 0x701f SErr 0x0 action 0x2 frozen [ 2320.132899] ata1.00: (spurious completions during NCQ issue=0x0 SAct=0x701f FIS=005040a1:0800) [ 2320.132905] ata1.00: cmd 61/10:00:59:fc:d0/00:00:07:00:00/40 tag 0 cdb 0x0 data 8192 out [ 2320.132906] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132911] ata1.00: cmd 61/10:08:69:fc:d0/00:00:07:00:00/40 tag 1 cdb 0x0 data 8192 out [ 2320.132913] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132918] ata1.00: cmd 61/08:10:19:4c:d1/00:00:07:00:00/40 tag 2 cdb 0x0 data 4096 out [ 2320.132919] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132924] ata1.00: cmd 61/01:18:fb:27:0f/00:00:08:00:00/40 tag 3 cdb 0x0 data 512 out [ 2320.132925] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132930] ata1.00: cmd 61/08:20:11:28:0f/00:00:08:00:00/40 tag 4 cdb 0x0 data 4096 out [ 2320.132932] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132937] ata1.00: cmd 61/08:28:91:92:17/00:00:08:00:00/40 tag 5 cdb 0x0 data 4096 out [ 2320.132938] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132943] ata1.00: cmd 61/08:30:99:b3:17/00:00:08:00:00/40 tag 6 cdb 0x0 data 4096 out [ 2320.132944] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132949] ata1.00: cmd 61/01:38:5b:56:4b/00:00:05:00:00/40 tag 7 cdb 0x0 data 512 out [ 2320.132950] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132956] ata1.00: cmd 61/08:40:71:56:4b/00:00:05:00:00/40 tag 8 cdb 0x0 data 4096 out [ 2320.132957] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132962] ata1.00: cmd 61/08:48:09:cf:5a/00:00:05:00:00/40 tag 9 cdb 0x0 data 4096 out [ 2320.132963] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132968] ata1.00: cmd 61/01:50:3b:af:8b/00:00:05:00:00/40 tag 10 cdb 0x0 data 512 out [ 2320.132969] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132974] ata1.00: cmd 61/08:58:51:af:8b/00:00:05:00:00/40 tag 11 cdb 0x0 data 4096 out [ 2320.132976] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132981] ata1.00: cmd 61/08:60:d9:f1:8d/00:00:05:00:00/40 tag 12 cdb 0x0 data 4096 out [ 2320.132982] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132987] ata1.00: cmd 61/08:68:49:bd:8e/00:00:05:00:00/40 tag 13 cdb 0x0 data 4096 out [ 2320.132988] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.132993] ata1.00: cmd 61/08:70:d9:63:d1/00:00:05:00:00/40 tag 14 cdb 0x0 data 4096 out [ 2320.132995] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133000] ata1.00: cmd 61/08:78:91:39:0f/00:00:06:00:00/40 tag 15 cdb 0x0 data 4096 out [ 2320.133001] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133006] ata1.00: cmd 61/08:80:49:30:97/00:00:06:00:00/40 tag 16 cdb 0x0 data 4096 out [ 2320.133007] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133013] ata1.00: cmd 61/08:88:41:c0:d0/00:00:06:00:00/40 tag 17 cdb 0x0 data 4096 out [ 2320.133014] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133019] ata1.00: cmd 61/08:90:b9:8c:d1/00:00:06:00:00/40 tag 18 cdb 0x0 data 4096 out [ 2320.133020] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133025] ata1.00: cmd 61/01:98:1b:cf:ce/00:00:07:00:00/40 tag 19 cdb 0x0 data 512 out [ 2320.133027] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133032] ata1.00: cmd 61/08:a0:31:cf:ce/00:00:07:00:00/40 tag 20 cdb 0x0 data 4096 out [ 2320.133033] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133038] ata1.00: cmd 61/10:e0:41:af:8b/00:00:05:00:00/40 tag 28 cdb 0x0 data 8192 out [ 2320.133039] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133044] ata1.00: cmd 61/01:e8:ba:12:8d/00:00:06:00:00/40 tag 29 cdb 0x0 data 512 out [ 2320.133046] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.133051] ata1.00: cmd 61/10:f0:c1:12:8d/00:00:06:00:00/40 tag 30 cdb 0x0 data 8192 out [ 2320.133052] res 50/00:08:31:cf:ce/00:00:07:00:00/40 Emask 0x2 (HSM violation) [ 2320.378387] ata1: soft resetting port [ 2320.442169] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 2320.460012] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors = 156301488 [ 2320.461395] ata1.00: ata_hpa_resize
Intel AHCI generating spurious completions during NCQ errors
Hi, I'm going through the process of setting up a new mythtv box. I decided to let it record for a few days to see how it goes under a constant workload and am seeing an occasional error in the logs about NCQ problems. They are not happening with any regularity, maybe once every 3-4 hours. This is git from yesterday or so with the mv-ahci patch that was posted a few days ago included. However those drives aren't actually mounted right now. They are detected and spun up though. drive detection/errors/lspci attached. -pee drives from dmesg ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ata_hpa_resize 1: sectors = 312581808, hpa_sectors = 312581808 ata1.00: ATA-7: ST3160815AS, 3.AAC, max UDMA/133 ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32) ata1.00: ata_hpa_resize 1: sectors = 312581808, hpa_sectors = 312581808 ata1.00: configured for UDMA/133 ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ata_hpa_resize 1: sectors = 312581808, hpa_sectors = 312581808 ata2.00: ATA-7: ST3160815AS, 3.AAC, max UDMA/133 ata2.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32) ata2.00: ata_hpa_resize 1: sectors = 312581808, hpa_sectors = 312581808 ata2.00: configured for UDMA/133 ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata3.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133 ata3.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32) ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata3.00: configured for UDMA/133 ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata4.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata4.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133 ata4.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32) ata4.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata4.00: configured for UDMA/133 scsi 0:0:0:0: Direct-Access ATA ST3160815AS 3.AA PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 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 sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 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 sda: sda1 sda2 sda3 sda4 sd 0:0:0:0: [sda] Attached SCSI disk sd 0:0:0:0: Attached scsi generic sg0 type 0 scsi 1:0:0:0: Direct-Access ATA ST3160815AS 3.AA PQ: 0 ANSI: 5 sd 1:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB) sd 1:0:0:0: [sdb] Write Protect is off sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 1:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB) sd 1:0:0:0: [sdb] Write Protect is off sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdb: sdb1 sdb2 sdb3 sdb4 sd 1:0:0:0: [sdb] Attached SCSI disk sd 1:0:0:0: Attached scsi generic sg1 type 0 scsi 2:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) sd 2:0:0:0: [sdc] Write Protect is off sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) sd 2:0:0:0: [sdc] Write Protect is off sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdc: sdc1 sd 2:0:0:0: [sdc] Attached SCSI disk sd 2:0:0:0: Attached scsi generic sg2 type 0 scsi 3:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) sd 3:0:0:0: [sdd] Write Protect is off sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) sd 3:0:0:0: [sdd] Write Protect is off sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdd: sdd1 sd 3:0:0:0: [sdd] Attached SCSI disk sd 3:0:0:0: Attached scsi generic sg3 type 0 First few errors ata1.00: exception Emask 0x2 SAct 0x28 SErr 0x0 action 0x2 frozen ata1.00: (spurious completions during NCQ issue=0x0 SAct=0x28 FIS=004040a1:0010) ata1.00: cmd 61/08:18:24:25:7e/00:00:01:00:00/40 tag 3 cdb 0x0 data 4096 out res 40/00:28:2c:25:7e/00:00:01:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/10:28:2c:25:7e/00:00:01:00:00/40 tag 5 cdb 0x0 data 8192 out res 40/00:28:2c:25:7e/00:00:01:00:00/40 Emask 0x2 (HSM
Intel AHCI generating spurious completions during NCQ errors
Hi, I'm going through the process of setting up a new mythtv box. I decided to let it record for a few days to see how it goes under a constant workload and am seeing an occasional error in the logs about NCQ problems. They are not happening with any regularity, maybe once every 3-4 hours. This is git from yesterday or so with the mv-ahci patch that was posted a few days ago included. However those drives aren't actually mounted right now. They are detected and spun up though. drive detection/errors/lspci attached. -pee drives from dmesg ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: ata_hpa_resize 1: sectors = 312581808, hpa_sectors = 312581808 ata1.00: ATA-7: ST3160815AS, 3.AAC, max UDMA/133 ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32) ata1.00: ata_hpa_resize 1: sectors = 312581808, hpa_sectors = 312581808 ata1.00: configured for UDMA/133 ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ata_hpa_resize 1: sectors = 312581808, hpa_sectors = 312581808 ata2.00: ATA-7: ST3160815AS, 3.AAC, max UDMA/133 ata2.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32) ata2.00: ata_hpa_resize 1: sectors = 312581808, hpa_sectors = 312581808 ata2.00: configured for UDMA/133 ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata3.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133 ata3.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32) ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata3.00: configured for UDMA/133 ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata4.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata4.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133 ata4.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32) ata4.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata4.00: configured for UDMA/133 scsi 0:0:0:0: Direct-Access ATA ST3160815AS 3.AA PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 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 sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 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 sda: sda1 sda2 sda3 sda4 sd 0:0:0:0: [sda] Attached SCSI disk sd 0:0:0:0: Attached scsi generic sg0 type 0 scsi 1:0:0:0: Direct-Access ATA ST3160815AS 3.AA PQ: 0 ANSI: 5 sd 1:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB) sd 1:0:0:0: [sdb] Write Protect is off sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 1:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB) sd 1:0:0:0: [sdb] Write Protect is off sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdb: sdb1 sdb2 sdb3 sdb4 sd 1:0:0:0: [sdb] Attached SCSI disk sd 1:0:0:0: Attached scsi generic sg1 type 0 scsi 2:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) sd 2:0:0:0: [sdc] Write Protect is off sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) sd 2:0:0:0: [sdc] Write Protect is off sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdc: sdc1 sd 2:0:0:0: [sdc] Attached SCSI disk sd 2:0:0:0: Attached scsi generic sg2 type 0 scsi 3:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) sd 3:0:0:0: [sdd] Write Protect is off sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) sd 3:0:0:0: [sdd] Write Protect is off sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdd: sdd1 sd 3:0:0:0: [sdd] Attached SCSI disk sd 3:0:0:0: Attached scsi generic sg3 type 0 First few errors ata1.00: exception Emask 0x2 SAct 0x28 SErr 0x0 action 0x2 frozen ata1.00: (spurious completions during NCQ issue=0x0 SAct=0x28 FIS=004040a1:0010) ata1.00: cmd 61/08:18:24:25:7e/00:00:01:00:00/40 tag 3 cdb 0x0 data 4096 out res 40/00:28:2c:25:7e/00:00:01:00:00/40 Emask 0x2 (HSM violation) ata1.00: cmd 61/10:28:2c:25:7e/00:00:01:00:00/40 tag 5 cdb 0x0 data 8192 out res 40/00:28:2c:25:7e/00:00:01:00:00/40 Emask 0x2 (HSM
