From: mhowe@cwlinux.com (Morgan Howe)
To: linux-arm-kernel@lists.infradead.org
Subject: mxcmmc driver hangs on sync
Date: Thu, 17 Jun 2010 16:33:40 +0800 [thread overview]
Message-ID: <20100617163340.69409a3f@morgan> (raw)
In-Reply-To: <20100615072237.GW17833@buzzloop.caiaq.de>
Daniel,
On Tue, 15 Jun 2010 09:22:37 +0200
Daniel Mack <daniel@caiaq.de> wrote:
> On Tue, Jun 15, 2010 at 03:20:51PM +0800, Morgan Howe wrote:
> > On Tue, 15 Jun 2010 08:31:43 +0200
> > Daniel Mack <daniel@caiaq.de> wrote:
> > > On Tue, Jun 15, 2010 at 11:29:36AM +0800, Morgan Howe wrote:
> > > > With the older kernel this would hang on sync after a few
> > > > thousand loops, and much sooner if you ran 2 or 3 of these
> > > > processes at a time. I tried last night with the newer kernel
> > > > and kicking off 3 processes and after ~100-150 loops per
> > > > process I get this:
> > >
> > > Which 'newer kernel' did you try?
> >
> > Hey Daniel,
> >
> > Sorry, I said current mainline, but actually it's 2.6.35-rc1.
>
> Could you try two things:
>
> a) build a kernel without MX2 DMA support
> b) try 2.6.34, as there were some updates to the mxcmmc driver after
> 2.6.34 which could be related
I have just been able to confirm using the final release of the 2.6.34
kernel that the problem also exists, with the same behavior as
described for 2.6.35.
Regards,
Morgan
next prev parent reply other threads:[~2010-06-17 8:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 3:29 mxcmmc driver hangs on sync Morgan Howe
2010-06-15 6:31 ` Daniel Mack
2010-06-15 7:20 ` Morgan Howe
2010-06-15 7:22 ` Daniel Mack
2010-06-15 10:32 ` Morgan Howe
2010-06-17 8:33 ` Morgan Howe [this message]
2010-06-17 18:51 ` Erik Oomen
2010-06-17 19:59 ` Daniel Mack
2010-06-17 20:43 ` Erik Oomen
2010-06-18 5:47 ` Morgan Howe
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=20100617163340.69409a3f@morgan \
--to=mhowe@cwlinux.com \
--cc=linux-arm-kernel@lists.infradead.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).