Re[2]: Sata Sil3512 bug?

[MisterE <MisterE2002@zonnet.nl>]

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

Hello Tejun,

I made some new logs. Probably to many :)
The number corresponded with the directory in the archive.

1:
Much errors. I aborted the transfer after a while.

2:
First i copied a movie (multiple archives) with winscp. After a while i got a time-out and
the transfer stopped. And winscp crashed. After that i did some
concurrent transfers; 3 movies at the same time with samba.

4:
I had tried slot changing and insertion of videocard before. Now it
looks to work. Don't know why it now works, probably a bios setting i
changed in combination with the right slot.
After it recognized the sda i did test for corruption. It looks if it gives
more errors than the other board (when the videocard is also
inserted). Probably amount of errors comparable with intel 1 withhout
videocard.



According to lshw is motherboard 1 vAAA10378-405 and motherboard 2
vAAA10378-402. I must say that i also had sometimes problems with the first intel not
finding the hard drive. So, i really don't trust the motherboard
anymore. And i had it with those boards.... :(

Tomorrow i will stress-test the 2 sata controllers with the Asus
board with 4 wd's sata drives connected. If it gives any corruption i
will let you know...

I would like to thank you all for helping me... :)


Thursday, October 4, 2007, 3:27:18 AM, you wrote:

> Hello,

> MisterE wrote:
>> I build another setup with almost the same hardware.
>> This motherboard had already the latest bios.
>> I notice that the computer does almost never find the hard drive
>> although the controller is found every time (with lspci).

> What do you mean by "almost never"?  Does it find the harddisk
> sometimes?  Also, please post kernel boot log after disk detection
> failure.  lspci result just indicates only that the PCI device is present.

>> So i get no
>> drive (sda) assigned. I don't always see the "bios" screen from the
>> controller at startup. And in the past it showed the hard drive.
>> So i could not experiment with this motherboard.

> Can you re-seat the controller or move it to another slot and see
> whether things change?

>> After that i installed Windows XP and used the orginal (sweex)
>> drivers with the first motherboard. This also makes the data corrupt.
>> So it seems not to be an linux problem. So there is something wrong with
>> the motherboard or the 3512 controller.
>> 
>> After that i plugged both hard drives (ide with windows and sata disk)
>> to the Asus board. No data corruption. So the hard disks are'nt the
>> problem either.

> Hmmm... It's relieving to know that the problem isn't caused by sata_sil
> but I don't have much idea than it seems like something goes wrong on
> the PCI bus.  :-(

>> I'm thinking of replacing both 3512 controllers with a Promise SATA300
>> TX4. Do you know if there are problems with this device?

> I see occasional bug reports on sata_promise but AFAIK there haven't
> been any data corruption report.  Mikael knows much better about promise
> controllers.

> Thanks.




-- 
Best regards,
 MisterE                            mailto:MisterE2002@zonnet.nl

[-- Attachment #2: LOGS.rar --]
[-- Type: APPLICATION/OCTET-STREAM, Size: 264822 bytes --]