From: Cory Maccarrone <darkstar6262@gmail.com>
To: linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: mmc omap BUG in mmc_omap_start_request on boot
Date: Fri, 28 May 2010 18:36:42 -0700 [thread overview]
Message-ID: <1275097002.9620.8.camel@runt.local> (raw)
Hey all,
I've been playing with the latest Linus tree kernel trying to get MMC
working on my device (an HTC Herald), and I've come up against a
problem.
In the function mmc_omap_start_request in drivers/mmc/host/omap.c, line
1160, I'm finding that this bug:
BUG_ON(irqs_disabled());
is triggering shortly after the MMC initializes on boot. I hadn't had
this problem before, but it's been a while since I've worked with this,
and I don't know what could have changed to cause this. If I comment
out that line, everything seems to run fine -- the mmc card comes up,
and I can boot from it perfectly.
I'm sure commenting it out isn't the right solution, but I don't know
the MMC subsystem well enough to understand why that function is called
while interrupts are disabled.
Can anyone point me in a direction that might allow me to resolve this?
Has anyone else had this problem recently?
For reference, this is on an HTC Herald (OMAP850-based OMAP1).
Thanks
Cory
reply other threads:[~2010-05-29 1:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1275097002.9620.8.camel@runt.local \
--to=darkstar6262@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@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;
as well as URLs for NNTP newsgroup(s).