Bug 8133

Summary:	libata pata via module detects 2 UDMA 100 hard drives, but sets the first to UDMA33
Product:	IO/Storage	Reporter:	Plamen Petrov (plamen.sisi)
Component:	Serial ATA	Assignee:	Alan (alan)
Status:	CLOSED PATCH_ALREADY_AVAILABLE
Severity:	low
Priority:	P2
Hardware:	i386
OS:	Linux
Kernel Version:	all after 2.6.20-git11	Subsystem:
Regression:	---	Bisected commit-id:
Attachments:	kernel config used for 2.6.21-rc2-git3 dmesg output with 2.6.21-rc2-git3 hdparm output for the drive being set at UDMA33 lspci output rotated messages file from /var/log

Description Plamen Petrov 2007-03-06 02:42:24 UTC

Most recent kernel where this bug did *NOT* occur:
 2.6.20-git11
Distribution:
 Slackware 11
Hardware Environment:
 Duron 1300 MHz, VIA KT333 based ECS K7VTA3 v3, 384 MB DDR266,
 1x Seagate ST3160812A 160GB HDD, 1x MAXTOR 4K080H4 80GB HDD,
 1x HL-DT-ST CD-RW GCE-8523B, 1x HL-DT-ST DVDRAM GSA-4163B, 
 hard drives on the primary channel, optical drives on the secondary
Software Environment:
 standart for Slackware 11; kernel configured with built-in
 libata pata-via module;
Problem Description:
 all kernels after 2.6.20-git11 set the ATA-7 Seagate at UDMA33,
 and the ATA-5 Maxtor at UDMA100

Comment 1 Plamen Petrov 2007-03-06 02:47:30 UTC

Created attachment 10618 [details]
kernel config used for 2.6.21-rc2-git3

Comment 2 Plamen Petrov 2007-03-06 02:48:30 UTC

Created attachment 10619 [details]
dmesg output with 2.6.21-rc2-git3

Comment 3 Plamen Petrov 2007-03-06 02:49:52 UTC

Created attachment 10620 [details]
hdparm output for the drive being set at UDMA33

Comment 4 Plamen Petrov 2007-03-06 02:51:10 UTC

Created attachment 10621 [details]
lspci output

Comment 5 Plamen Petrov 2007-03-06 02:54:05 UTC

Created attachment 10622 [details]
rotated messages file from /var/log

in the logfile you can see the output of 2.6.20-git11, and later,
the newer kernels I compiled, that actually misconfigure the
primary master Seagate HDD at UDMA33

Comment 6 Plamen Petrov 2007-03-30 07:21:55 UTC

the bug was still present in linux-2.6.21-rc5,
just downloaded patch-2.6.21-rc5-git6 and will test
it as soon as possible...

Comment 7 Plamen Petrov 2007-04-04 08:03:24 UTC

linux-2.6.21-rc5-git6 solved the issue for me...