From: Chris Ball <cjb@laptop.org>
To: Madhav Chauhan <madhav.imsec@gmail.com>
Cc: linux-mmc@vger.kernel.org
Subject: Re: MMC insert remove issue
Date: Tue, 18 May 2010 11:09:18 -0400 [thread overview]
Message-ID: <m3632lb61t.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <AANLkTimg_VbK2uPZNCn3Il8klv22JhF7iEe-MTCA5NYe@mail.gmail.com> (Madhav Chauhan's message of "Tue, 18 May 2010 20:02:32 +0530")
Hi,
> In one ARM based boards I am facing soft lock up issue while
> inserting/removing MMC/SD card continuously having 2K files. Can
> someone point me where should i look whether host controller
> driver or MMC block layer/Kernel block layer??
Could be any of the above, but perhaps most likely your host
controller driver -- which one are you using? Can you perform
alt-sysrq-t when the lockup happens, or get a kgdb backtrace?
- Chris.
--
Chris Ball <cjb@laptop.org>
One Laptop Per Child
next prev parent reply other threads:[~2010-05-18 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 14:32 MMC insert remove issue Madhav Chauhan
2010-05-18 15:09 ` Chris Ball [this message]
2010-05-19 13:29 ` Madhav Chauhan
2010-05-20 5:28 ` Madhav Chauhan
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=m3632lb61t.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=madhav.imsec@gmail.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