From: mcuelenaere@gmail.com (Maurus Cuelenaere)
To: linux-arm-kernel@lists.infradead.org
Subject: S3C6410 SDHCI driver crash
Date: Thu, 24 Sep 2009 17:32:37 +0200 [thread overview]
Message-ID: <4ABB9115.4030609@gmail.com> (raw)
Hi,
I'm currently experiencing an SDHCI bug in 2.6.31 and linux-next, which
didn't
seem to appear in 2.6.31-rc8.
This is on a new S3C6410 platform (SmartQ 7, see [1]) and it seems to be
consistently happening right after displaying "Loading hardware drivers" (in
user-space; Ubuntu-based).
The relevant kernel log lines are:
blk: request botched
kernel BUG at drivers/mmc/host/sdhci.c:298!
This is on 2.6.31-next-20090923, but I've also had this on regular
2.6.31, Ben
Dooks latest tree and linux-next with the ADMA patches applied.
Any ideas?
[1]
http://gitorious.org/mcuelenaere-smartq-kernel/mcuelenaere-smartq-kernel/commits/experimental-2.6.31
Regards,
Maurus Cuelenaere
next reply other threads:[~2009-09-24 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 15:32 Maurus Cuelenaere [this message]
2009-09-24 19:00 ` S3C6410 SDHCI driver crash Ben Dooks
2009-09-28 18:06 ` Maurus Cuelenaere
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=4ABB9115.4030609@gmail.com \
--to=mcuelenaere@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).