From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Thanos Kyritsis <djart@linux.gr>
Cc: Mark Lord <liml@rtr.ca>, linux-ide@vger.kernel.org
Subject: Re: [PROBLEM]: hdparm strange behaviour for 2.6.21 and later
Date: Sat, 23 Jun 2007 20:28:58 +0200 [thread overview]
Message-ID: <200706232028.58193.bzolnier@gmail.com> (raw)
In-Reply-To: <200706201807.41646.djart@linux.gr>
Hi,
On Wednesday 20 June 2007, Thanos Kyritsis wrote:
> On Monday 18 June 2007, Mark Lord wrote:
> > Thanos Kyritsis wrote:
> [snip]
> > > /etc/rc.d/rc.local contains the following:
> > > /usr/sbin/hdparm -q -d1 -q -u1 -q -c1 -q -k1 /dev/hda
> > > /usr/sbin/hdparm -q -d1 -q -u1 -q -c1 -q -k1 /dev/hdb
> [snip]
>
> > Sounds like a (kernel) timing issue.
> > The "-q" option gets rid of some intermediary printf's,
> > and nothing else. So with -q, the ioctl() calls happen
> > much closer together in time. Without -q, the intermediary
> > printf's likely cause a resched, giving the kernel more time
> > to complete anything left over from the earlier call.
It could be that some assumptions that I've taken when
fixing DMA tuning locking were wrong...
> > ????
> >
> > Any difference with a modern version of hdparm?
>
> The same issue happens when using hdparm 7.4 as well as 7.5.
Adding a couple of printk-s to ide.c::set_using_dma() and
ide.c::ide_spin_wait_hwgroup() will for sure help in debugging
it further.
Also could you try running UP kernel without PREEMPT and see
if it makes difference?
Thanks,
Bart
next prev parent reply other threads:[~2007-06-23 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-16 16:58 [PROBLEM]: hdparm strange behaviour for 2.6.21 and later Thanos Kyritsis
2007-06-18 20:01 ` Mark Lord
2007-06-20 15:07 ` Thanos Kyritsis
2007-06-23 18:28 ` Bartlomiej Zolnierkiewicz [this message]
2007-06-24 17:47 ` Thanos Kyritsis
2007-06-27 19:46 ` PREEMPT bug? (was: Re: [PROBLEM]: hdparm strange behaviour for 2.6.21 and later) Bartlomiej Zolnierkiewicz
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=200706232028.58193.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=djart@linux.gr \
--cc=liml@rtr.ca \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).