From: Grozdan <neutrino8@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: hancockrwd@gmail.com, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: Kernel 2.6.30rc7 limits IDE to UDMA33
Date: Fri, 5 Jun 2009 16:02:43 +0200 [thread overview]
Message-ID: <c5bd819b0906050702o6051fa1dh3673e94119142f55@mail.gmail.com> (raw)
In-Reply-To: <20090605142153.1895fac5@lxorguk.ukuu.org.uk>
2009/6/5 Alan Cox <alan@lxorguk.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...
next prev parent reply other threads:[~2009-06-05 14:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c5bd819b0906021525l13ee9282j1fb270e141985f66@mail.gmail.com>
2009-06-03 4:05 ` Kernel 2.6.30rc7 limits IDE to UDMA33 Robert Hancock
2009-06-03 11:35 ` Grozdan
2009-06-03 12:14 ` Alan Cox
2009-06-03 12:52 ` Grozdan
2009-06-03 13:01 ` Alan Cox
2009-06-03 13:15 ` Grozdan
2009-06-03 13:39 ` Grozdan
2009-06-04 14:50 ` Grozdan
2009-06-05 9:05 ` Alan Cox
2009-06-05 10:35 ` Grozdan
2009-06-05 10:42 ` Alan Cox
2009-06-05 12:43 ` Grozdan
2009-06-05 13:21 ` Alan Cox
2009-06-05 14:02 ` Grozdan [this message]
2009-06-06 1:07 ` Robert Hancock
2009-06-06 14:56 ` Alan Cox
2009-06-06 18:16 ` Robert Hancock
2009-06-06 22:08 ` Alan Cox
2009-06-07 4:39 ` Grozdan
[not found] ` <4A2BF785.3020402@gmail.com>
2009-06-07 18:24 ` Grozdan
2009-06-07 18:46 ` Michael S. Zick
2009-06-07 19:54 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c5bd819b0906050702o6051fa1dh3673e94119142f55@mail.gmail.com \
--to=neutrino8@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox