From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Alexander Elbs <alex@segv.de>, Nicolas Pitre <nico@fluxnic.net>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Lunn <andrew@lunn.ch>,
Gregory CLEMENT <gregory.clement@free-electrons.com>
Subject: Re: mvsdio: unhandled interrupt, mmc writes queuing up
Date: Wed, 26 Mar 2014 07:50:29 +0100 [thread overview]
Message-ID: <20140326075029.4fcc6675@pluto> (raw)
In-Reply-To: <20140326000735.GI28304@titan.lakedaemon.net>
Hi Jason,
Will try this out this evening when I'm back home (and have some time
to reboot the sheevaplug).
Note that the write-back stalls seem to be nilfs2 specific (I'm getting
them on usb-storage as well while ext4 filesystem on usb-storage
does not present the stall issue).
Bruno
On Tue, 25 Mar 2014 20:07:35 -0400 Jason Cooper wrote:
> On Tue, Mar 25, 2014 at 11:16:53PM +0100, Sebastian Hesselbarth wrote:
> > On 03/25/2014 08:27 PM, Alexander Elbs wrote:
> > >> On Wed, 19 Mar 2014, Bruno Prémont wrote:
> > >>> Since upgrading my Sheevaplug from 3.7.2 to 3.13.6 (FDT) I'm seeing
> > >>> mvsdio f1090000.mvsdio: unhandled interrupt status=0x8810 en=0x0000 pio=0
> > >>> at varied timings.
> > >
> > > I have the same problem on my sheevaplug.
> > >
> > >> It has been many years since I've looked at the code for this driver.
> > >> I'm therefore including Thomas Petazzoni to the CC list as he appears to
> > >> have been the most active since then.
> > >>
> > >> The reported status seems to indicate missing data in the context of a
> > >> transfer with CMD12, and a CRC error ensued of course.
> > >>
> > >> At this point I'd suggest testing intermediate kernels between 3.7 and
> > >> 3.13, and try bisection until you find the offending commit.
> > >>
> > >> [...]
> > >>> I get same results with 3.14-rc7.
> > >>
> > >> Excellent, that reduces the search space significantly. You can do a
> > >> git bisect directly.
> > >
> > > I did a git bisect.
> > > good: no message "unhandled interrupt"
> > > bad: message above appears
> > > skipped: unbootable kernel, usually stuck after the line "Uncompressing Linux".
> > >
> > > So far I am down to a few commits after 3.11.
> > >
> > > $ git bisect view --oneline
> > > 2326f04 (refs/bisect/bad) ARM: kirkwood: convert to DT irqchip and clocksource
> >
> > Can you please try the patches contained in [1]?
> >
> > They have been Acked-by Jason Cooper, but I guess we simply lost
> > track of them.
> >
> > Sebastian
> >
> > [1] https://lkml.org/lkml/2013/11/15/276
>
> Bruno,
>
> If these work for you, please send a Tested-by and I'll keep better
> track of them this time. I think these were sent before we had a
> process for shuttling things into irqchip...
>
> thx,
>
> Jason.
next prev parent reply other threads:[~2014-03-26 6:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 15:28 mvsdio: unhandled interrupt, mmc writes queuing up Bruno Prémont
2014-03-19 16:37 ` Nicolas Pitre
2014-03-25 19:27 ` Alexander Elbs
2014-03-25 22:16 ` Sebastian Hesselbarth
2014-03-26 0:07 ` Jason Cooper
2014-03-26 6:50 ` Bruno Prémont [this message]
2014-03-26 20:46 ` Bruno Prémont
2014-03-26 20:06 ` Alexander Elbs
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=20140326075029.4fcc6675@pluto \
--to=bonbons@linux-vserver.org \
--cc=alex@segv.de \
--cc=andrew@lunn.ch \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
/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).