Hi
I have reported this bug quite a while but it was marked as Won't fix
However, I have a patch that you can test and which I am using since then.
Is no big deal and maybe it can be included in new builds. All builds (last
2.6.22-15.40) have the same bug and I have to replace modules after each
update.
Adrian
P.S. If you had the time to read up to this point, I can explain in a few
words what's the issue.
In libata-core.c:
Cable detection (40/80 wire) is now made on each attached drive and this is
not what the standards say. If a drive does not offer detection support or
says "don't care", it will be downgraded with no reason. The patch is doing
the detection by port plus all (one or two) attached HD, using the ATA
standard table to decide if the cable (for ALL drives) is to be declared 40
or 80 wire.
In pata_sis.c
There is a parameter missing in the udma table. It was originaly build for
ATA64 and then included for ATA100_old too. The entry for UDMA100 is
missing, garbage data is used to setup drive parameters and a bunch of
errors will occur until the system decides to downgrade the drive to UDMA64.
That's all
----- Original Message -----
From: "Adi POPA" <adrianp@xxxxxxxxxxxx>
To: <adrianp@xxxxxxxxxxxx>
Sent: Monday, November 19, 2007 11:21 AM
Subject: [Bug 163753] Strange ATA HD configuration
Public bug reported:
Binary package hint: linux-source-2.6.22
Ubuntu 2.6.22-14.46-server (Ubuntu 4.1.2-16ubuntu2) Sun Oct 14 23:34:23 GMT
2007
MB chipset SIS 730. IDE interface SIS 5513.
Two HDD an the same ATA cable (master/slave by jumpers), ATA 133/100
detected by AMIBIOS and set to ATA100 (max board cap)
One CDROM on IDE2 (checked with both ATA and IDE-40wire cables), UDMA33 by
BIOS
libata 2.21, pata_sis version 0.5.1 detects HD as UDMA/100 and CDROM as
UDMA/33 --> OK
and sis900.c - v1.08.10 loads
--> ata1.00: ... 16Sec max UDMA/133
--> ata1.01: ... 8Sec max UDMA/100
--> ata2.00: ... max UDMA/33
....
ata1.00: configured for UDMA/100 --> normal, board limit
ata1.01: limited to UDMA/33 due to 40-wire cable --> why? same cable!?
ata1.01: configured for UDMA/33 --> is this a bug?
ata2.00: configured for UDMA/33
.... some long (30 sec) stops on ata1.00 exception ... (timeout)
and then ata1.00 is limited even lower
ata1.00 configured for UDMA/66
** Affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
Strange ATA HD configuration
https://bugs.launchpad.net/bugs/163753
You received this bug notification because you are a direct subscriber
of the bug.
Attachment:
aag_source.diff
Description: Binary data
