Re: libata driver update posted

Martin Schlemmer
2003-07-19T21:03:14Z

[-- 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 --]