From: Thomas Pilarski <Thomas.Pilarski@arcor.de>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [Bug 12309] Large I/O operations result in slow performance and high iowait times
Date: Sat, 03 Apr 2010 21:19:48 +0200 [thread overview]
Message-ID: <1270322388.26420.56.camel@localhost> (raw)
In-Reply-To: <20100331002549.GB9925@khazad-dum.debian.net>
> > This problem is enormous increased, while the ultra bay disc is acceded
> > with udma2 instead of udma6 (caused by another bug),
>
> There is a thinkpad BIOS bug that could cause that: it will not signal a
> 80-wire cable when you hot-add an HD on a PATA ultrabay. Exists at least on
> all T4x, including the T43.
It's a SATA untrabay disk. There is a 40-wire message, but sometimes it
works and sometimes not. I could not figure out, when it does and when
not.
> The fix is to whitelist these thinkpads for high-speed UDMA even on 40-wire
> cables. The workaround is to add a kernel command line parameter (I forget
> which).
>
> Does that match your udma2 instead of udma6 problem?
Thanks. I will try it. But have to finish another project first.
next prev parent reply other threads:[~2010-04-03 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12309-14043@http.bugzilla.kernel.org/>
[not found] ` <201003162357.o2GNvkNF024562@demeter.kernel.org>
2010-03-30 7:44 ` [Bug 12309] Large I/O operations result in slow performance and high iowait times Thomas Pilarski
2010-03-31 0:25 ` Henrique de Moraes Holschuh
2010-04-03 19:19 ` Thomas Pilarski [this message]
2010-04-04 2:08 ` Henrique de Moraes Holschuh
[not found] <20091101134207.b97e4f5f.akpm@linux-foundation.org>
2009-11-02 15:56 ` Mike Galbraith
2009-11-02 20:26 ` Thomas Pilarski
2009-11-03 9:47 ` Mike Galbraith
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=1270322388.26420.56.camel@localhost \
--to=thomas.pilarski@arcor.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hmh@hmh.eng.br \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.