libata patches in 2.6.7bk6 Hang Maxtor on SP bridge

libata patches in 2.6.7bk6 Hang Maxtor on SP bridge

[hab]

[-- Attachment #1: Type: text/plain, Size: 247 bytes --]

Sir
    I resolved problem by baking out scsi portion of patches, athough
some general configs such as FC2 development still introduce
the same problem as identified in the attached message.
Please assist me in resolving this problem.
Hubert Bahr

[-- Attachment #2: Sata-Sil bk6-bk8 hangs Maxtor with S-P bridge --]
[-- Type: message/rfc822, Size: 941 bytes --]

From: hab <hab@hbahr.org>
To: linux-kernel@vger.kernel.org
Subject: Sata-Sil bk6-bk8 hangs Maxtor with S-P bridge
Date: Sat, 26 Jun 2004 13:53:53 -0500
Message-ID: <40DDC641.1070403@hbahr.org>

With Bk6 and beyond I recieve a
command 0x25 Timeout Stat 0x50 host-stat 0x4  and then a hang in init.
I can cntl alt del to reboot.
This is with a Maxtor 6y160po  YAR4,  I also have a Maxtor 6y250P0

Earlier in the boot sequence I recieve a screaming interupt message and
interupt turned off message for the interupt used by the controller.

These work for 2.6.7 and 2.6.7 bk5.
It works for the ide implementation with the thousands of

sata_error = 0x00000000, watchdog = 0, siimage_mmio_ide_dma_test_irq

messages.

thanks  Hubert

Re: libata patches in 2.6.7bk6 Hang Maxtor on SP bridge

[Jeff Garzik]

On Mon, Jun 28, 2004 at 05:07:50PM -0500, hab wrote:
> Sir
>    I resolved problem by baking out scsi portion of patches, athough
> some general configs such as FC2 development still introduce
> the same problem as identified in the attached message.

Use sata_sil not siimage.  And certainly not _both_ drivers.

	Jeff

Re: libata patches in 2.6.7bk6 Hang Maxtor on SP bridge

[hab]

Jeff Garzik wrote:

>On Mon, Jun 28, 2004 at 05:07:50PM -0500, hab wrote:
>  
>
>>Sir
>>   I resolved problem by baking out scsi portion of patches, athough
>>some general configs such as FC2 development still introduce
>>the same problem as identified in the attached message.
>>    
>>
>
>Use sata_sil not siimage.  And certainly not _both_ drivers.
>
>	Jeff
>
>  
>
Can you think of any others that might cause a conflict.  I had 
inadvertantly left
siimage from a previous compile and starting with a make clean solved 
it.  However
if I take the redhat FC2 development config for i686 even if I leave 
siimage unchecked it
still has the same problem.  siimage was not compiled so it isn't the 
problem.
I will report this to redhat as well.
Thanks
Hubert

>-
>To unsubscribe from this list: send the line "unsubscribe linux-ide" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>  
>