From: "Heiko Stübner" <heiko@sntech.de>
To: Andrei Warkentin <andreiw@motorola.com>
Cc: linux-mmc@vger.kernel.org, Kyungmin Park <kmpark@infradead.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: irq flood with mmc boot partitions on s3c2416 with 3.0rc1
Date: Thu, 16 Jun 2011 22:14:10 +0200 [thread overview]
Message-ID: <201106162214.11084.heiko@sntech.de> (raw)
In-Reply-To: <BANLkTimzxUQnVn5VC8EOaJeHq=wifUhZ4A@mail.gmail.com>
Am Dienstag 14 Juni 2011, 22:32:41 schrieb Andrei Warkentin:
> Hi Heiko,
>
> On Tue, Jun 14, 2011 at 9:10 AM, Heiko Stübner <heiko@sntech.de> wrote:
> > nope, no updates yet. The flood also only starts when udev wants to
> > create its device nodes, meaning the initial detection seems not to
> > produce this problem
> >
> > But when I disable the whole boot partition stuff, it works as before
> > without irq storms.
> >
> > As there don't seem to exist reports from other emmc users about this
> > I guess the problem lays somewhere between the boot-partitions-patch
> > and the sdhci-s3c driver (for s3c2416 at least).
>
> Alright. Curious. Can you let me know what eMMC device you are
> connecting to the controller? What is the eMMC revision?
hmm ... how do I find these?
The real device providing the storage is a 2GB NAND Flash from Hynix.
And sadly both of your patches didn't change anything.
I made two interessting observations:
during boot the initial detection works ok - I can even mount the normal
partitions without hickup when I stop it before the udev stage.
The irq storm seems to be caused by something udev does during its population
of the /dev filesystem.
And second the mentioned irq storm never stops during the runtime of the
device. When I let it boot through it spews what must be millions of the irq
messages and does so until I shut it down.
Heiko
next prev parent reply other threads:[~2011-06-16 20:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 19:49 irq flood with mmc boot partitions on s3c2416 with 3.0rc1 Heiko Stübner
2011-06-02 23:48 ` Kyungmin Park
2011-06-03 5:31 ` Santosh Shilimkar
2011-06-03 7:56 ` Heiko Stübner
2011-06-14 0:09 ` Andrei Warkentin
2011-06-14 14:10 ` Heiko Stübner
2011-06-14 20:32 ` Andrei Warkentin
2011-06-16 20:14 ` Heiko Stübner [this message]
2011-06-16 20:35 ` Andrei Warkentin
2011-06-18 20:20 ` Heiko Stübner
2011-06-18 20:56 ` Daniel Mack
2011-06-19 14:23 ` Heiko Stübner
2011-06-20 19:34 ` Andrei Warkentin
-- strict thread matches above, loose matches on Subject: below --
2011-07-05 6:59 Heiko Stübner
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=201106162214.11084.heiko@sntech.de \
--to=heiko@sntech.de \
--cc=andreiw@motorola.com \
--cc=kmpark@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.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