linux-kernel - Re: Kernel 2.6.30rc7 limits IDE to UDMA33

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 5 Jun 2009 16:02:43 +0200
From:	Grozdan <neutrino8@...il.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	hancockrwd@...il.com, linux-kernel@...r.kernel.org,
	linux-ide@...r.kernel.org
Subject: Re: Kernel 2.6.30rc7 limits IDE to UDMA33

2009/6/5 Alan Cox <alan@...rguk.ukuu.org.uk>:
>> older kernels have no problems setting the correct UDMA while 2.6.30
>> does have problems. Something must have definitely changed in this
>> latest kernel. I'll go dig in my BIOS to see if I may need to
>> change/force something.
>
> Unless you can actually work through the various kernels and release
> candidates to find the one it changes its basically impossible to tell
> what has occurred or why.
>

Well, I looked around in the BIOS and there isn't anything I can do to
force a specific UDMA - it only offers disable and auto detect.
Upgrading the BIOS firware won't do a thing since I'm already running
the latest version of it. The BIOS correctly reports that my first
disk is using Transfer Mode 6 and my second one Transfer Mode 5. I've
also noticed that some Ubuntu users have the same problem on kernel
2.6.27 (which works for me)

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285595

So if this can't be fixed in the kernel itself, I may need to resort
to kernel params if I experience the problem again in the future. I
may give all rc's of 2.6.30 a try and see which one introduces it...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/