LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* 2.6.20 SATA error
@ 2007-02-28 12:40 Gerhard Mack
  2007-02-28 16:14 ` Charles Shannon Hendrix
  0 siblings, 1 reply; 5+ messages in thread
From: Gerhard Mack @ 2007-02-28 12:40 UTC (permalink / raw)
  To: linux-kernel

hello, 

Can someone tell me what this means?
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x400000 action 0x2 frozen
ata1.00: cmd 35/00:00:40:a6:23/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288 
out
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1: soft resetting port
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: configured for UDMA/100
ata1: EH complete
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't 
support DPO
or FUA


--
Gerhard Mack

gmack@innerfire.net

<>< As a computer I find your faith in technology amusing.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.6.20 SATA error
  2007-02-28 12:40 2.6.20 SATA error Gerhard Mack
@ 2007-02-28 16:14 ` Charles Shannon Hendrix
  2007-02-28 18:25   ` Gerhard Mack
  0 siblings, 1 reply; 5+ messages in thread
From: Charles Shannon Hendrix @ 2007-02-28 16:14 UTC (permalink / raw)
  To: Gerhard Mack; +Cc: linux-kernel

On Wed, 28 Feb 2007 07:40:23 -0500 (EST)
Gerhard Mack <gmack@innerfire.net> wrote:

> hello, 
> 
> Can someone tell me what this means?
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x400000 action 0x2 frozen
> ata1.00: cmd 35/00:00:40:a6:23/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288 
> out
>          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata1: port is slow to respond, please be patient (Status 0xd0)
> ata1: port failed to respond (30 secs, Status 0xd0)
> ata1: soft resetting port
> ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata1.00: configured for UDMA/100

I am fairly certain this is a bug in the 2.6.20 kernel.

I never see it in 2.6.19*, just 2.6.20.

It is some kind of but in the SATA code paths, or at least that's all it
appears to affect on my system.

What chipset do you have?

I have an nforce4 chipset.

In another thread, I think they were saying it was either a SATA chipset
driver bug, or a problem in libata core.


-- 
shannon                      | governorrhea: 
                             | a contagious disease that spreads from
                             | the governor of a state downward through other 
                             | offices and his corporate sponsors

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.6.20 SATA error
  2007-02-28 16:14 ` Charles Shannon Hendrix
@ 2007-02-28 18:25   ` Gerhard Mack
       [not found]     ` <20070228163204.16c21f29@daydream.goid.lan>
  0 siblings, 1 reply; 5+ messages in thread
From: Gerhard Mack @ 2007-02-28 18:25 UTC (permalink / raw)
  To: Charles Shannon Hendrix; +Cc: linux-kernel

On Wed, 28 Feb 2007, Charles Shannon Hendrix wrote:

> On Wed, 28 Feb 2007 07:40:23 -0500 (EST)
> Gerhard Mack <gmack@innerfire.net> wrote:
> 
> > hello, 
> > 
> > Can someone tell me what this means?
> > ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x400000 action 0x2 frozen
> > ata1.00: cmd 35/00:00:40:a6:23/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288 
> > out
> >          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> > ata1: port is slow to respond, please be patient (Status 0xd0)
> > ata1: port failed to respond (30 secs, Status 0xd0)
> > ata1: soft resetting port
> > ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> > ata1.00: configured for UDMA/100
> 
> I am fairly certain this is a bug in the 2.6.20 kernel.
> 
> I never see it in 2.6.19*, just 2.6.20.
> 
> It is some kind of but in the SATA code paths, or at least that's all it
> appears to affect on my system.
> 
> What chipset do you have?
> 
> I have an nforce4 chipset.
> 
> In another thread, I think they were saying it was either a SATA chipset
> driver bug, or a problem in libata core.

I also have an nforce4.

	Gerhard


--
Gerhard Mack

gmack@innerfire.net

<>< As a computer I find your faith in technology amusing.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* solved Re: 2.6.20 SATA error
       [not found]     ` <20070228163204.16c21f29@daydream.goid.lan>
@ 2007-02-28 21:55       ` Gerhard Mack
  0 siblings, 0 replies; 5+ messages in thread
From: Gerhard Mack @ 2007-02-28 21:55 UTC (permalink / raw)
  To: Charles Shannon Hendrix; +Cc: linux-kernel

On Wed, 28 Feb 2007, Charles Shannon Hendrix wrote:

> On Wed, 28 Feb 2007 13:25:00 -0500 (EST)
> Gerhard Mack <gmack@innerfire.net> wrote:
> 
>  
> > > In another thread, I think they were saying it was either a SATA chipset
> > > driver bug, or a problem in libata core.
> > 
> > I also have an nforce4.
> 
> On another mailing list, someone with an Intel chipset is reporting the same
> problem, and also that others without nforce chipsets are seeing it.

I was reaching inside my computer to check something and heared the thing 
click and got the same error message.

Turns out the adaptor that goes between SATA drive and the old style power 
connector was loose on the drive side.  Doesn't seem to me like it was 
very snug fitting to begin with.  I changed it to one of the proper SATA 
connectors comming off the power supply and it doesn't do that anymore.

Sorry for the false alarm, 

	Gerhard

--
Gerhard Mack

gmack@innerfire.net

<>< As a computer I find your faith in technology amusing.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: solved Re: 2.6.20 SATA error
       [not found]       ` <fa.Evhbh+iC4EjQWXsDSWHX9shqJXc@ifi.uio.no>
@ 2007-02-28 23:20         ` Robert Hancock
  0 siblings, 0 replies; 5+ messages in thread
From: Robert Hancock @ 2007-02-28 23:20 UTC (permalink / raw)
  To: Gerhard Mack, linux-kernel; +Cc: Charles Shannon Hendrix

Gerhard Mack wrote:
> On Wed, 28 Feb 2007, Charles Shannon Hendrix wrote:
> 
>> On Wed, 28 Feb 2007 13:25:00 -0500 (EST)
>> Gerhard Mack <gmack@innerfire.net> wrote:
>>
>>  
>>>> In another thread, I think they were saying it was either a SATA chipset
>>>> driver bug, or a problem in libata core.
>>> I also have an nforce4.
>> On another mailing list, someone with an Intel chipset is reporting the same
>> problem, and also that others without nforce chipsets are seeing it.
> 
> I was reaching inside my computer to check something and heared the thing 
> click and got the same error message.
> 
> Turns out the adaptor that goes between SATA drive and the old style power 
> connector was loose on the drive side.  Doesn't seem to me like it was 
> very snug fitting to begin with.  I changed it to one of the proper SATA 
> connectors comming off the power supply and it doesn't do that anymore.
> 
> Sorry for the false alarm, 

There is one thing that seems odd, if you do have an nForce4 chipset, 
the kernel should be running the SATA controller in ADMA mode in 2.6.20, 
but it doesn't seem like it is from your dmesg output. Can you post the 
output of "lspci -vvn"? Also what kind of motherboard is that?

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2007-02-28 23:20 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-02-28 12:40 2.6.20 SATA error Gerhard Mack
2007-02-28 16:14 ` Charles Shannon Hendrix
2007-02-28 18:25   ` Gerhard Mack
     [not found]     ` <20070228163204.16c21f29@daydream.goid.lan>
2007-02-28 21:55       ` solved " Gerhard Mack
     [not found] <fa./FMiSBkno9w078cQXK8Y1+afU50@ifi.uio.no>
     [not found] ` <fa.OO5sHloeJxxBmHwyt7Swo5eydUY@ifi.uio.no>
     [not found]   ` <fa.G7ZWCF8iZMzCCHcWS6votbmzA3U@ifi.uio.no>
     [not found]     ` <fa.GSOUb36DPlkk7gFXS5FtJVpQIq0@ifi.uio.no>
     [not found]       ` <fa.Evhbh+iC4EjQWXsDSWHX9shqJXc@ifi.uio.no>
2007-02-28 23:20         ` Robert Hancock

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).