From: Andrew Morton <akpm@linux-foundation.org>
To: Zan Lynx <zlynx@acm.org>
Cc: linux-kernel@vger.kernel.org, linux-pcmcia@lists.infradead.org,
linux-ide@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: 2.6.24-rc4-mm1 and Very Slow PCMCIA Compact Flash
Date: Sat, 8 Dec 2007 20:04:15 -0800 [thread overview]
Message-ID: <20071208200415.611afb57.akpm@linux-foundation.org> (raw)
In-Reply-To: <1197169375.7352.4.camel@localhost>
On Sat, 08 Dec 2007 20:02:54 -0700 Zan Lynx <zlynx@acm.org> wrote:
>
> On Sat, 2007-12-08 at 02:07 -0800, Andrew Morton wrote:
> > On Fri, 07 Dec 2007 22:01:33 -0700 Zan Lynx <zlynx@acm.org> wrote:
> >
> > >
> > > On Fri, 2007-12-07 at 15:22 -0800, Andrew Morton wrote:
> > > > On Fri, 07 Dec 2007 23:09:43 +0000
> > > > Zan Lynx <zlynx@acm.org> wrote:
> > > [cut]
> > > > > > > Now with MM kernels 2.6.24 rc1-4 the PCMCIA adapter works again, but I
> > > > > > > only get read rates of 1.6 MB/s. When it used to work in 2.6.20 I got
> > > > > > > at least 16 MB/s. The card itself is capable of 30+ in the USB-2
> > > > > > > reader.
> [cut]
> > argh. OK. And Linus's current tree is OK, yes?
> >
> > In which case we should be OK for 2.6.24 and I guess we can hope like heck
> > that the dud patch doesn't leak into mainline. Hopefully Alan will get
> > some time to look into it before 2.6.25 opens.
>
> Linus' tree is also broken.
>
> I tried a Linus 2.6.24-rc4 and it acts the same way, with a very slow
> transfer rate.
shit
> I also tried 2.6.24-rc4 with the older not-libata PATA drivers and it is
> broken.
squared.
> dmesg had a line about the CF card detected as hda,
> but /sys/block did not have hda and /dev/hda did not function.
But these drivers did work in earlier kernels, yes? 2.6.20 worked, but
we don't know about intervening kernels.
Can you tell us which version(s)?
> I will try the patches you mentioned
Yes, that won't tell use anything.
> but I think I may also have to
> work backward through kernel versions until I find the last one where
> the PCMCIA hd{a,b,c,d,e} drivers worked.
That would be great - a git-bisect is often ideal.
http://www.kernel.org/doc/local/git-quick.html has details.
next prev parent reply other threads:[~2007-12-09 4:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1197059904.15428.15.camel@localhost>
[not found] ` <20071207150251.a0dbae23.akpm@linux-foundation.org>
[not found] ` <1197068983.15428.29.camel@localhost>
2007-12-07 23:22 ` 2.6.24-rc4-mm1 and Very Slow PCMCIA Compact Flash Andrew Morton
2007-12-07 23:39 ` Zan Lynx
2007-12-08 5:01 ` Zan Lynx
2007-12-08 10:07 ` Andrew Morton
2007-12-09 3:02 ` Zan Lynx
2007-12-09 4:04 ` Andrew Morton [this message]
[not found] <fa.9+cyQSoHqcg4p5BAdLi4beGvJ8E@ifi.uio.no>
[not found] ` <fa.es7DHARPOKbnzAqaEFBauYRpWjo@ifi.uio.no>
[not found] ` <fa.kwN53ZHLrpa2M5QIn+VR9hoaqjA@ifi.uio.no>
[not found] ` <fa.IgSJMFcov+qjLkhPpd1LhbCf93o@ifi.uio.no>
[not found] ` <fa.5knWxRyOEvQSAwZoz5fEa2Krvko@ifi.uio.no>
2007-12-08 4:47 ` Robert Hancock
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=20071208200415.611afb57.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=zlynx@acm.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).