public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus@drzeus.cx>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Don Mullis <dwm@meer.net>,
	linux-kernel@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>
Subject: Re: 2.6.23-rc8-mm2: OOPS in mmc on boot
Date: Thu, 4 Oct 2007 09:28:41 +0200	[thread overview]
Message-ID: <20071004092841.322a3476@poseidon.drzeus.cx> (raw)
In-Reply-To: <20071003231659.f41df5ed.akpm@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]

On Wed, 3 Oct 2007 23:16:59 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:

> On Wed, 03 Oct 2007 23:11:02 -0700 Don Mullis <dwm@meer.net> wrote:
> 
> > OOPS followed by a 3 minute timeout, then completion of boot.
> > Not seen if card (Kingston microSD adapter) is ejected; not seen in
> > 2.6.23-rc8. Running on a Dell XPS M1330 laptop.
> > 

Impossible! My code is bug free!

> > [   13.709831] EIP is at blk_rq_map_sg+0xc0/0x160
> > [   13.711857] Call Trace:
> > [   13.711971]  [<f8c39e58>] mmc_queue_map_sg+0x28/0xc0 [mmc_block]
> > [   13.712085]  [<f8c396c9>] mmc_blk_issue_rq+0x199/0x780 [mmc_block]
> > [   13.712193]  [<f8c3a168>] mmc_queue_thread+0x78/0xe0 [mmc_block]

Seems to be in the handling of the bounce buffer. I don't see how any
of the parameters to blk_rq_map_sg() could be incorrect though, so I
suspect the problem is not in the mmc layer.

Don, is MMC_BLOCK_BOUNCE enabled? Could you try toggling it and see if
things change?

> 
> This could be due to git-block changes (or a lack of them ;))
> 

There are no pending patches, or recent changes that mess about in any
real way in there.

Don, when did this work last?

Rgds
Pierre

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2007-10-04  7:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04  6:11 2.6.23-rc8-mm2: OOPS in mmc on boot Don Mullis
2007-10-04  6:16 ` Andrew Morton
2007-10-04  7:25   ` Jens Axboe
2007-10-04  8:01     ` Pierre Ossman
2007-10-04  8:06       ` Jens Axboe
2007-10-04  8:46         ` Pierre Ossman
2007-10-04  9:30           ` Jens Axboe
2007-10-04 10:24             ` Pierre Ossman
2007-10-04 10:38               ` Jens Axboe
2007-10-04 10:46                 ` Pierre Ossman
2007-10-04 10:59                   ` Jens Axboe
2007-10-04 16:19     ` Don Mullis
2007-10-04 16:35       ` Pierre Ossman
2007-10-04 16:42         ` Jens Axboe
2007-10-04 16:46           ` Pierre Ossman
2007-10-04 17:06           ` Don Mullis
2007-10-04 18:10             ` Jens Axboe
2007-10-04  7:28   ` Pierre Ossman [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=20071004092841.322a3476@poseidon.drzeus.cx \
    --to=drzeus@drzeus.cx \
    --cc=akpm@linux-foundation.org \
    --cc=dwm@meer.net \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@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