hd limited to udma33, thinkpad t23

[EricDHH]

Binary package hint: linux-image-2.6.27-10-generic

Hello

maybe it's hardware specific. Thinkpad T23 with transscend TS8GSSD25-S solidstate disk. There is no hd cable in the machine. Intrepid i386 with kernel 2.6.27-10-generic installed.

lspci
IDE interface: Intel Corporation 82801CAM IDE U100 Controller (rev 02)

dmesg
[ 5.608855] ata_piix 0000:00:1f.1: setting latency timer to 64
[ 5.610726] scsi0 : ata_piix
[ 5.611088] scsi1 : ata_piix
[ 5.613696] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x1860 irq 14
[ 5.613704] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x1868 irq 15
[ 5.776372] ata1.00: ATA-8: TS8GSSD25-S, FW0625, max UDMA/100
[ 5.776382] ata1.00: 15604848 sectors, multi 0: LBA
[ 5.776408] ata1.00: limited to UDMA/33 due to 40-wire cable
[ 5.784318] ata1.00: configured for UDMA/33
[ 5.948405] ata2.00: ATAPI: SONY DVD+/-RW DW-D56A, PDTV, max UDMA/33
[ 5.964344] ata2.00: configured for UDMA/33

The problem is the limit to udma33 that did not occur when everything was running by hdX devices. The dvd drive are slowdowned and the powerful ssd is crawling at half speed. I found hope in a kernel parameter for libata but

[ 0.000000] Unknown boot option `libata.force=80c,udma4': ignoring
[ 5.371760] libata version 3.00 loaded.

this parameter seems to be forbidden or unknown. There must be a easy solution to workaround this limit or switch back to plain ata where this bug did not exists.

Regards
Eric

[EricDHH (ericdhh)]

Hello

som further informations

eric@vishnu:~$ uname -a
Linux vishnu 2.6.27-10-generic #1 SMP Fri Nov 21 12:00:22 UTC 2008 i686 GNU/Linux

Will attach a dmesg.log, there you can see the libata.force_cbl=80 kernel param that did not result anything. There is no cable on the mainboard, so a cable detection faults. We need an option to disable it.

http://pixca.net/2008/02/03/limited-to-udma33-due-to-40-wire-cable/http://ubuntuforums.org/showthread.php?t=689413

If we wait a few weeks, we can celebrate a birthday party to this bug

http://<email address hidden>/msg14508.html

Bye
Eric

[EricDHH (ericdhh)]

Hello

found a workaround by forcing the 80c. But the problem is already an existing bug in the kernel, the cable detection is messed up.

eric@vishnu:~$ cat /etc/modprobe.d/options
# XXX: Ignore HPA by default. Needs to be revisted in jaunty
#options libata ignore_hpa=1
options libata force=80c

[ 5.132296] ata_piix 0000:00:1f.1: version 2.12
[ 5.132320] ata_piix 0000:00:1f.1: enabling device (0005 -> 0007)
[ 5.132338] ata_piix 0000:00:1f.1: PCI INT A -> Link[LNKC] -> GSI 9 (level, low) -> IRQ 9
[ 5.132424] ata_piix 0000:00:1f.1: setting latency timer to 64
[ 5.140062] scsi0 : ata_piix
[ 5.140448] scsi1 : ata_piix
[ 5.142950] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x1860 irq 14
[ 5.142958] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x1868 irq 15
[ 5.304389] ata1: FORCE: cable set to 80c
[ 5.304425] ata1.00: ATA-8: TS8GSSD25-S, FW0625, max UDMA/100
[ 5.304432] ata1.00: 15604848 sectors, multi 0: LBA
[ 5.312346] ata1.00: configured for UDMA/100
[ 5.476344] ata2: FORCE: cable set to 80c

Now the expensive slc ssd runs at full speed.

root@vishnu:/home/eric# hdparm -tT /dev/sda5
/dev/sda5:
 Timing cached reads: 436 MB in 2.01 seconds = 217.37 MB/sec
 Timing buffered disk reads: 184 MB in 3.05 seconds = 60.40 MB/sec

Meantime i asked the transcend support if there is a known error with thinkpad bios, they dont know about such behaviour.

Bye
Eric

[Davias (davias)]

I modified /etc/modprobe.d/options as you suggested, with options libata force=80c

But still it does not work - dmesg:

4.156770] ata1.00: ATA-7: Maxtor 6Y080L0, YAR41BW0, max UDMA/133
[ 4.156779] ata1.00: 160086528 sectors, multi 16: LBA
[ 4.157250] ata1.01: ATA-7: Maxtor 6Y080L0, YAR41BW0, max UDMA/133
[ 4.157255] ata1.01: 160086528 sectors, multi 16: LBA
[ 4.157275] ata1.00: limited to UDMA/33 due to 40-wire cable
[ 4.157280] ata1.01: limited to UDMA/33 due to 40-wire cable
[ 4.172632] ata1.00: configured for UDMA/33
[ 4.188657] ata1.01: configured for UDMA/33
[ 4.352502] ata2.00: ATAPI: HL-DT-STDVD-RAM GH22NP20, 1.00, max UDMA/66
[ 4.352528] ata2.00: limited to UDMA/33 due to 40-wire cable
[ 4.368488] ata2.00: configured for UDMA/33
[ 4.368733] scsi 0:0:0:0: Direct-Access ATA Maxtor 6Y080L0 YAR4 PQ: 0 ANSI: 5
[ 4.368969] scsi 0:0:1:0: Direct-Access ATA Maxtor 6Y080L0 YAR4 PQ: 0 ANSI: 5
[ 4.370266] scsi 1:0:0:0: CD-ROM HL-DT-ST DVD-RAM GH22NP20 1.00 PQ: 0 ANSI: 5
[ 4.372144] usb 2-2: new full speed USB device using uhci_hcd and address 2

Can you help? (wires are ok) TIA

[Davias (davias)]

OK, it works!

I forgot to sudo update-initramfs -u
& reboot system

Now its at UDMA5 - great! Thanks!

[EricDHH (ericdhh)]

Same procedure on jaunty

Linux atalanta 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

[ 2.766449] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x1860 irq 14
[ 2.766456] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x1868 irq 15
[ 2.928316] ata1.00: ATA-8: TS8GSSD25-S, FW0625, max UDMA/100
[ 2.928322] ata1.00: 15604848 sectors, multi 0: LBA
[ 2.928371] ata1.00: limited to UDMA/33 due to 40-wire cable
[ 2.936272] ata1.00: configured for UDMA/33
[ 3.100305] ata2.00: ATAPI: SONY DVD+/-RW DW-D56A, PDTV, max UDMA/33
[ 3.116283] ata2.00: configured for UDMA/33
[ 3.116897] scsi 0:0:0:0: Direct-Access ATA TS8GSSD25-S FW06 PQ
: 0 ANSI: 5

But now my suggested bugfix /etc/modprobe.d/options
#options libata ignore_hpa=1
options libata force=80c

did not work anymore. The disk stays on udma33, the options did not exist under jaunty and when created they are ignored. Where to place the option now?

Bye
Eric

[Davias (davias)]

Eric you are in good company:
I confirm that upgrading to 9.04 brings back to UDMA2 -
This is really annoying... Ubuntu devs? Where are you ?

Now what we do?

[EricDHH (ericdhh)]

Hello,
found a suggest that the modprobe.d/options file is no more processed in jaunty. So i renamed it to .conf like the other working .conf files but this did not help. The file or the option seems to be ignored, permissions are same.

My t42 is not affected by this problem, only the t23 shows it. The board and chipset are companions, what maybe the difference?

[ 4.051289] scsi0 : ata_piix
[ 4.051688] scsi1 : ata_piix
[ 4.054534] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x1860 irq 14
[ 4.054543] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x1868 irq 15
[ 4.220197] ata1.00: ATA-7: MTRON MSD-PATA3025, 0.19R1H3, max UDMA/133
[ 4.220207] ata1.00: 31252480 sectors, multi 1: LBA
[ 4.240190] ata1.00: configured for UDMA/100

Bye
Eric

[Davias (davias)]

The board on my PC is an old MSI K7T with VIA Apollo 4 chipset, if this is of any help. I think that many have this problem, just that not many are aware of it.

Ubuntu devs should do something - at least as workaround like the libata force=80c that worked before.

GoodBye all
Dave

[kernel-janitor (kernel-janitor)]

Hi EricW@Hamburg,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/karmic .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 303429

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[EricDHH (ericdhh)]

kernel-janitor <email address hidden> wrote:

> Also, if you could test the latest upstream kernel available that would
> be great. It will allow additional upstream developers to examine the

The machine was sold 2 months ago, equipped with a hdd that did not
show this bug. If no other users confirm this bug ob newer kernels, it
can be closed.

Thanks
Eric

[Leann Ogasawara (leannogasawara)]

Having had no other response I'll go ahead and just close this bug for now. Thanks.

[Cloudlight (pnkellogg)]

Hello everyone,

Am experiencing the very same phenomenon on a Compaq Evo N440c under Karmic Koala 2.6.31-15-generic (#50-Ubuntu SMP Tue Nov 10 14:54:29 UTC 2009).

It would be great if this "bug" could find resolution.

sudo hdparm -v -i /dev/sda1 reveals:

/dev/sda1:
 multcount = 16 (on)
 IO_support = 1 (32-bit)
 readonly = 0 (off)
 readahead = 256 (on)
 geometry = 4864/255/63, sectors = 75923127, start = 63

 Model=WDC, FwRev=09.07D09, SerialNo=WD-WXEY04012112
 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50
 BuffType=unknown, BuffSize=2048kB, MaxMultSect=16, MultSect=16
 CurCHS=17475/15/63, CurSects=16513875, LBA=yes, LBAsects=78140160
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes: pio0 pio3 pio4
 DMA modes: mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 *udma2 udma3 udma4 udma5
 AdvancedPM=yes: unknown setting WriteCache=enabled
 Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6

 * signifies the current active mode

The drive is capable of UDMA/100. however it runs at UDMA/33.