From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Alexander Elbs <alex@segv.de>, Nicolas Pitre <nico@fluxnic.net>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
bonbons@linux-vserver.org, Jason Cooper <jason@lakedaemon.net>,
Andrew Lunn <andrew@lunn.ch>,
Gregory CLEMENT <gregory.clement@free-electrons.com>
Subject: Re: mvsdio: unhandled interrupt, mmc writes queuing up
Date: Tue, 25 Mar 2014 23:16:53 +0100 [thread overview]
Message-ID: <53320055.9080307@gmail.com> (raw)
In-Reply-To: <20140325192759.GJ29769@segv.de>
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
next prev parent reply other threads:[~2014-03-25 22:16 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 [this message]
2014-03-26 0:07 ` Jason Cooper
2014-03-26 6:50 ` Bruno Prémont
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=53320055.9080307@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=alex@segv.de \
--cc=andrew@lunn.ch \
--cc=bonbons@linux-vserver.org \
--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=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).