All of lore.kernel.org
 help / color / mirror / Atom feed
From: mcuelenaere@gmail.com (Maurus Cuelenaere)
To: linux-arm-kernel@lists.infradead.org
Subject: S3C6410 SDHCI driver crash
Date: Mon, 28 Sep 2009 20:06:40 +0200	[thread overview]
Message-ID: <4AC0FB30.3080105@gmail.com> (raw)
In-Reply-To: <20090924190002.GG31920@trinity.fluff.org>

Op 24-09-09 21:00, Ben Dooks schreef:
 > On Thu, Sep 24, 2009 at 05:32:37PM +0200, Maurus Cuelenaere wrote:
 >> 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!
 >
 > Having a look at the code in mainline, this is being triggered in
 > sdhci_write_block_pio(), by the following code:
 >
 > 296     while (blksize) {
 > 297             if (!sg_miter_next(&host->sg_miter))
 > 298                     BUG();
 >
 > Which suggests that the size of the transfer was bigger than the sg list
 > passed to the transfer, which is worrying as this seems to suggest there
 > is a problem with the PIO code writing insufficient data to the card.
 >

An update on this: apparently this issue was caused by using the EXT4 driver
for loading an EXT3 FS, so it has nothing to do with the SDHCI driver...

Sorry for the false alarm.

I also want to mention that the ADMA patch from kki_ap/linux-2.6-samsung.git
seems to be working smoothly here.


Regards,

Maurus Cuelenaere

      reply	other threads:[~2009-09-28 18:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 15:32 S3C6410 SDHCI driver crash Maurus Cuelenaere
2009-09-24 19:00 ` Ben Dooks
2009-09-28 18:06   ` Maurus Cuelenaere [this message]

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=4AC0FB30.3080105@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.