From: Martin Schlemmer <azarah@gentoo.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Catalin BOIE <util@deuroconsult.ro>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: libata driver update posted
Date: 19 Jul 2003 23:18:14 +0200 [thread overview]
Message-ID: <1058649494.23174.43.camel@nosferatu.lan> (raw)
In-Reply-To: <3F19A651.2080503@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]
On Sat, 2003-07-19 at 22:13, Jeff Garzik wrote:
> Martin Schlemmer wrote:
> > On Fri, 2003-07-18 at 17:43, Jeff Garzik wrote:
> >
> > Slower this side. The Maxtor 40GB (ata133) is however just set to
> > udma33, where the Seagate 20GB (ata100) driver is set correctly to
> > udma100.
>
> Yeah, that's expected: Parallel ATA (PATA) requires cable detection to
> go beyond UDMA/33, and my driver doesn't do that yet [since I'm
> concentrating on SATA].
>
Ok, make sense. Nothing like the ide's 'hdx=foo' param?
>
> > The Seagate start off ok (about 35mb/s), but then after doing some heavy
> > disk io, it also just drops to the 20mb/s region.
>
> That's definitely interesting. Is "heavy disk I/O" the hdparm stuff you
> described, or something else too?
>
Nope, its unpacking, compiling and installing glibc. Sure, not _that_
extensive, but it does make it work a bit. Might be some other
weirdness, as I did not try to reproduce it more than twice.
And then something else - gnome did not want to start due to missing
icons. They are there however, and rebooting to old kernel without
libata worked fine (same kernel, just do not have the patch applied
or the normal ata driver disabled).
I will give it a go some more. Currently I am having some issues with
getting latest cvs glibc & nptl to play nice, so I will not take it too
serious for now. If anything obvious might cause it and you want me
to test, ask. Otherwise I will give it a good run in the next few
weeks and get a more complete report.
Thanks,
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-19 21:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 21:14 libata driver update posted Jeff Garzik
2003-07-18 6:24 ` Catalin BOIE
2003-07-18 13:13 ` Jeff Garzik
2003-07-18 15:39 ` Martin Schlemmer
2003-07-18 15:43 ` Jeff Garzik
2003-07-19 0:30 ` Martin Schlemmer
2003-07-19 0:38 ` Alan Cox
2003-07-19 0:52 ` Martin Schlemmer
2003-07-19 0:45 ` Andre Tomt
2003-07-19 0:45 ` Andre Tomt
2003-07-19 20:08 ` Martin Schlemmer
2003-07-19 20:13 ` Jeff Garzik
2003-07-19 21:18 ` Martin Schlemmer [this message]
2003-07-20 2:27 ` James H. Cloos Jr.
2003-07-20 2:51 ` Jeff Garzik
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=1058649494.23174.43.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=util@deuroconsult.ro \
--cc=vojtech@suse.cz \
/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.