From: Stephen Warren <swarren@wwwdotorg.org>
To: Chris Mason <chris.mason@fusionio.com>, Olof Johansson <olof@lixom.net>
Cc: Jens Axboe <axboe@kernel.dk>,
Tushar Behera <tushar.behera@linaro.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Kent Overstreet <kmo@daterainc.com>
Subject: Re: Boot failure on Arndale with next-20131105
Date: Tue, 05 Nov 2013 15:06:25 -0700 [thread overview]
Message-ID: <52796BE1.5010306@wwwdotorg.org> (raw)
In-Reply-To: <20131105205623.3802.5166@localhost.localdomain>
On 11/05/2013 01:56 PM, Chris Mason wrote:
> Quoting Olof Johansson (2013-11-05 15:38:33)
>> On Tue, Nov 5, 2013 at 12:33 PM, Chris Mason <chris.mason@fusionio.com> wrote:
>>> Quoting Olof Johansson (2013-11-05 15:23:51)
>>>> On Tue, Nov 5, 2013 at 11:33 AM, Jens Axboe <axboe@kernel.dk> wrote:
>>>
>>> [ horrible crashes fixed by removing my patch ]
>>>
...
> Ok, I think I see it. My guess is that you're hitting bounce buffers.
> __blk_queue_bounce is the only caller of the bio splitting code I can
> see that you might be hitting.
>
> My first patch exposed a lurking bug in bio_clone_biovec. Basically
> bio->bi_vcnt is being doubled instead of initialized.
>
> This patch is only compile tested, but I think it'll fix it.
Tested-by: Stephen Warren <swarren@nvidia.com>
(this fixes the issue on Tegra30/Beaver at least)
next prev parent reply other threads:[~2013-11-05 22:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 11:49 Boot failure on Arndale with next-20131105 Tushar Behera
2013-11-05 16:42 ` Tomasz Figa
2013-11-05 17:38 ` Stephen Warren
2013-11-05 21:25 ` Jens Axboe
2013-11-08 8:45 ` Stephen Rothwell
2013-11-05 19:59 ` Jens Axboe
2013-11-05 19:33 ` Jens Axboe
2013-11-05 20:23 ` Olof Johansson
2013-11-05 20:33 ` Chris Mason
2013-11-05 20:38 ` Olof Johansson
2013-11-05 20:56 ` Chris Mason
2013-11-05 21:27 ` Olof Johansson
2013-11-05 22:06 ` Stephen Warren [this message]
2013-11-05 22:41 ` Olof Johansson
2013-11-06 0:04 ` Chris Mason
2013-11-06 6:15 ` Tushar Behera
2013-11-05 20:34 ` Jens Axboe
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=52796BE1.5010306@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=axboe@kernel.dk \
--cc=chris.mason@fusionio.com \
--cc=kmo@daterainc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=tushar.behera@linaro.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