Re: solved Re: 2.6.20 SATA error

2007-02-28 Thread Robert Hancock

Gerhard Mack wrote:

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


On Wed, 28 Feb 2007 13:25:00 -0500 (EST)
Gerhard Mack <[EMAIL PROTECTED]> 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 [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: solved Re: 2.6.20 SATA error

2007-02-28 Thread Robert Hancock

Gerhard Mack wrote:

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


On Wed, 28 Feb 2007 13:25:00 -0500 (EST)
Gerhard Mack [EMAIL PROTECTED] 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 [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/