Slow disk performance with Seagate SATA disk and Sil3112 controller

Bug #48979 reported by RichardOs
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Invalid
Undecided
Chuck Short

Bug Description

Binary package hint: linux-source-2.6.15

The problem is described here:
http://ubuntuforums.org/showthread.php?t=81056

Althouh the thread is several months old, and I've switched to Dapper, the performance is the same.

There seems to be a proposed fix for the problem described here:
http://home-tj.org/wiki/index.php/Sil_m15w

Chuck Short (zulcss)
Changed in linux-source-2.6.15:
assignee: nobody → zulcss
Revision history for this message
Phil Bull (philbull) wrote :

Thanks for the report. Do you still have this issue?

Changed in linux-source-2.6.15:
status: Unconfirmed → Needs Info
Revision history for this message
RichardOs (richard-oszlanczi) wrote :

My Seagate hard drive died in december last year (mechanical problem I think, the computer didn't boot with the drive connected, and it made mechanical grinding sounds). The problem was not fixed then either (I was using Kubuntu Edgy).

I had it replaced with with a Maxtor DiamondMax10 (also 200Gb), which works normally with Sil3112 (I get 30-40 MB/s transfer speeds).

Revision history for this message
Andrew Fenn (andrewfenn) wrote :

I'm thinking this has been fixed? I'm using Gutsy and a Seagate SATA disk and I am getting the following.

sudo hdparm -tT /dev/sda
/dev/sda:
 Timing cached reads: 1770 MB in 2.00 seconds = 885.08 MB/sec
 Timing buffered disk reads: 172 MB in 3.02 seconds = 56.88 MB/sec

lsmod | grep sata
sata_nv 20612 3
libata 125168 2 ata_generic,sata_nv

I am not using a Sil3112 controller though so I am guessing that might be where your problem is?

Could you update this bug report if you're still having problems or close it, thanks.

Revision history for this message
RichardOs (richard-oszlanczi) wrote :

Hi.

As I said earlier, I don't have the Seagate disk anymore. So if no one seems to have this problem besides me, I think the bug can be closed.

Thanks,
Richard

Revision history for this message
Andrew Lowe (bugzrevenge) wrote :

Does not look like it is able to be reproduced by anyone other then the original submitter, who is, as mentioned, not able to reproduce any more due to a hardware change. I believe this bug is not valid any longer.

Changed in linux-source-2.6.15:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.