From: "Rogério Brito" <rbrito@ime.usp.br>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
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: Tue, 21 Apr 2009 02:32:58 -0300 [thread overview]
Message-ID: <20090421053258.GA18001@ime.usp.br> (raw)
In-Reply-To: <20090420221955.2c71bd26@lxorguk.ukuu.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
Hi Alan, Bart and Co.
On Apr 20 2009, Alan Cox wrote:
> > DISCLAIMER: I'm not handling this bugreport, this is best
> > done by pata_pdc202xx_old Maintainer or libata Maintainer.
>
> Be that as it may thanks - thats well spotted and definitely a bug.
Well, I just compiled the kernel both with libata and with the usual IDE
drivers.
Unfortunately, it seems that Bart's patch isn't enough. OTOH, when I use
the older IDE drive, it seems to work OK, as the attached dmesgs show
(BTW, you may notice that there's something fishy with X, but that's
another story).
Oh, just one observation: I tried to compile a 2.6.30-rc2 kernel, but I
only got errors during the compilation. This is why I used a 2.6.29
kernel.
Actually, I also had a compilation problem with the 2.6.30-rc2 kernel on
another box running x86_64. I can post them separately if needed.
Thanks for your valuable help so far, Rogério Brito.
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
[-- Attachment #2: dmesg-2.6.29-with-libata-patched.txt.bz2 --]
[-- Type: application/octet-stream, Size: 9881 bytes --]
[-- Attachment #3: dmesg-2.6.29-with-common-ide.txt.bz2 --]
[-- Type: application/octet-stream, Size: 9413 bytes --]
next prev parent reply other threads:[~2009-04-21 5:33 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 [this message]
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
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=20090421053258.GA18001@ime.usp.br \
--to=rbrito@ime.usp.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=mjt@tls.msk.ru \
/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