From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: "Rogério Brito" <rbrito@users.sf.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jeff Garzik <jeff@garzik.org>, Michael Tokarev <mjt@tls.msk.ru>,
Mark Lord <lkml@rtr.ca>,
linux-kernel@vger.kernel.org
Subject: Re: Quick question about libata and hdparm
Date: Fri, 1 May 2009 13:20:57 +0200 [thread overview]
Message-ID: <200905011320.57491.bzolnier@gmail.com> (raw)
In-Reply-To: <20090501091804.GB29466@ime.usp.br>
On Friday 01 May 2009 11:18:04 Rogério Brito wrote:
> Hi, Bart and other people.
>
> On Apr 24 2009, Rogério Brito wrote:
> > On 4/23/09, Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> > > You can try booting with "libata.force=1.00:mwdma2" kernel paramater
> > > to force use of "regular" MWDMA2 transfer mode instead of UDMA ones
> > > so we are sure that the issue is specific to pata_pdc202xx_old +
> > > UDMA.
> >
> > This *did* work. I see no other error messages, while using multword
> > dma. So I think that this serves for us to rule out some unknown
> > variables.
>
> Is there anything that I can do right now? Just to remember, the
> original IDE driver works without any problems, but I would like to
> migrate everything to libata (and many distributions are already using
> libata by default, even with IDE devices).
DISCLAIMER was there for a reason...
Please ping pata_pdc202xx_old maintainer, libata maintainer or said
distributions about it, not me.
Don't get me wrong. I would like to help but such problems usually
take really long time to debug (you have to know both stacks, both
drivers and be able to track subtle differences between all of them)
and you have absolutely no guarantee that it will yield any results.
[ Tejun has spent few days on trying to fix pata_ali MWDMA regression
and he is one of people who really know what they are doing. ]
I don't have such time and my motivation to help is seriously effected
by behaviors like that seen in:
http://bugzilla.kernel.org/show_bug.cgi?id=12734
Thanks,
Bart
next prev parent reply other threads:[~2009-05-01 11:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 0:22 Quick question about libata and hdparm Rogério Brito
2009-04-19 6:31 ` Robert Hancock
2009-04-19 12:33 ` Mark Lord
2009-04-19 12:44 ` Michael Tokarev
2009-04-19 12:57 ` Jeff Garzik
2009-04-19 13:06 ` Michael Tokarev
2009-04-19 20:11 ` Rogério Brito
2009-04-19 21:27 ` Jeff Garzik
2009-04-20 17:35 ` Rogério Brito
2009-04-20 18:40 ` Alan Cox
2009-04-20 20:41 ` Rogério Brito
2009-04-20 21:16 ` Alan Cox
2009-04-20 20:31 ` Bartlomiej Zolnierkiewicz
2009-04-20 20:45 ` Rogério Brito
2009-04-20 21:19 ` Alan Cox
2009-04-20 22:57 ` Rogério Brito
2009-04-21 5:32 ` Rogério Brito
2009-04-21 12:59 ` Bartlomiej Zolnierkiewicz
2009-04-23 5:56 ` Rogério Brito
2009-04-23 21:31 ` Bartlomiej Zolnierkiewicz
2009-04-24 3:00 ` Rogério Brito
2009-05-01 9:18 ` Rogério Brito
2009-05-01 10:31 ` Alan Cox
2009-05-01 11:50 ` Rogério Brito
2009-05-01 13:16 ` Alan Cox
2009-05-01 14:19 ` Rogério Brito
2009-05-01 11:20 ` Bartlomiej Zolnierkiewicz [this message]
2009-05-11 18:34 ` Jeff Garzik
2009-04-19 20:03 ` Rogério Brito
2009-04-19 23:41 ` Mark Lord
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=200905011320.57491.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=mjt@tls.msk.ru \
--cc=rbrito@users.sf.net \
/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