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
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
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 hou
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
>
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
>
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
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
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
: 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
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
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
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
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
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 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
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
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
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
: 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
: 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
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
> 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 Hi
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
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
0: 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:
: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
: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
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
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 d
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
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
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
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=00404
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
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
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):
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:
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
> 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
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
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
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
[
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
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
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
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
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
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
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
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
: 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
: 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
52 matches
Mail list logo
