From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/9] kernel-yocto: consolidated pull request
Date: Tue, 22 Aug 2017 22:56:55 +0100 [thread overview]
Message-ID: <1503439015.32591.138.camel@linuxfoundation.org> (raw)
In-Reply-To: <30e270c4-3369-b602-a1de-f8bd92038626@windriver.com>
On Tue, 2017-08-22 at 16:34 -0400, Bruce Ashfield wrote:
> On 08/22/2017 12:07 PM, Richard Purdie wrote:
> I found the commit that is causing the problem (after three hours
> of bisecting). That's the good news. The bad news is it isn't
> something
> I can revert .. or easily fix, since the commit is large and is
> pretty
> much tree wide. There's a lot of commits stacked on top if that
> change,
> so it can't be reverted.
>
> ------------
>
> commit 82ed4db499b8598f16f8871261bff088d6b0597f
> Author: Christoph Hellwig <hch@lst.de>
> Date: Fri Jan 27 09:46:29 2017 +0100
>
> block: split scsi_request out of struct request
>
> And require all drivers that want to support BLOCK_PC to
> allocate it
> as the first thing of their private data. To support this the
> legacy
> IDE and BSG code is switched to set cmd_size on their queues to
> let
> the block layer allocate the additional space.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Jens Axboe <axboe@fb.com>
>
> ---------
>
> I was able to boot with the following in the command line:
>
> -drive
> file=tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-
> 20170822200708.iso,if=virtio,media=cdrom
>
> --------
>
> IMHO we need to stop using the ancient IDE support, since it
> continually
> is broken (not usually this badly .. but often in more subtle ways).
>
> So switching to a virtio backed CDROM, while the issue is reported
> upstream is probably the best bet.
That seems reasonable to me and should be a simple change to the
runqemu script. The hint above should let me test that so I'll try and
and see how the builds work out. Thanks for the help in figuring a
workaround!
Cheers,
Richard
next prev parent reply other threads:[~2017-08-22 21:56 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 2:58 [PATCH 0/9] kernel-yocto: consolidated pull request Bruce Ashfield
2017-08-21 2:58 ` [PATCH 1/9] kernel-yocto: configuration updates: x86 features Bruce Ashfield
2017-08-21 2:58 ` [PATCH 2/9] linux-yocto/4.1: fix fsl-ls10xx sdhci Bruce Ashfield
2017-08-21 2:58 ` [PATCH 3/9] linux-yocto: add usb-net configs by default Bruce Ashfield
2017-08-21 2:58 ` [PATCH 4/9] linux-yocto: introduce 4.12 recipes Bruce Ashfield
2017-08-21 2:58 ` [PATCH 5/9] linux-yocto: remove 4.1 recipes Bruce Ashfield
2017-08-21 2:58 ` [PATCH 6/9] libc-headers: update to 4.12 Bruce Ashfield
2017-08-21 2:58 ` [PATCH 7/9] qemu: bump default version " Bruce Ashfield
2017-08-21 2:58 ` [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built Bruce Ashfield
2017-08-21 15:00 ` Peter Kjellerstedt
2017-08-21 15:03 ` Bruce Ashfield
2017-08-21 15:13 ` Bruce Ashfield
2017-08-21 15:16 ` Peter Kjellerstedt
2017-08-21 15:18 ` Bruce Ashfield
2017-08-23 3:40 ` Khem Raj
2017-08-23 12:37 ` Bruce Ashfield
2017-08-23 14:40 ` Khem Raj
2017-08-23 14:42 ` Bruce Ashfield
2017-08-23 14:58 ` Richard Purdie
2017-08-23 15:00 ` Bruce Ashfield
2017-08-23 15:07 ` Khem Raj
2017-08-23 18:31 ` Denys Dmytriyenko
2017-08-23 18:56 ` Bruce Ashfield
2017-08-21 2:58 ` [PATCH 9/9] linux-yocto/4.10: CVE & misc fixes Bruce Ashfield
2017-08-21 3:05 ` ✗ patchtest: failure for kernel-yocto: consolidated pull request Patchwork
2017-08-21 11:42 ` [PATCH 0/9] " Richard Purdie
2017-08-21 12:11 ` Bruce Ashfield
2017-08-21 13:01 ` Bruce Ashfield
2017-08-21 15:55 ` Richard Purdie
2017-08-21 15:57 ` Bruce Ashfield
2017-08-21 16:12 ` Bruce Ashfield
2017-08-22 14:24 ` Richard Purdie
2017-08-22 14:54 ` Bruce Ashfield
2017-08-22 15:28 ` Richard Purdie
2017-08-22 15:34 ` Bruce Ashfield
2017-08-22 16:00 ` Richard Purdie
2017-08-22 16:04 ` Bruce Ashfield
2017-08-22 16:07 ` Richard Purdie
2017-08-22 16:20 ` Bruce Ashfield
2017-08-22 17:13 ` Bruce Ashfield
2017-08-22 20:34 ` Bruce Ashfield
2017-08-22 21:56 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-14 13:46 Bruce Ashfield
2018-03-06 18:11 Bruce Ashfield
2018-06-07 2:07 Bruce Ashfield
2020-02-05 23:12 bruce.ashfield
2020-02-06 9:03 ` Richard Purdie
2020-02-06 13:25 ` Bruce Ashfield
2021-05-17 22:16 Bruce Ashfield
2022-09-19 14:28 bruce.ashfield
2022-09-20 9:45 ` Richard Purdie
2022-09-20 12:21 ` Richard Purdie
2022-09-20 12:53 ` Bruce Ashfield
2022-09-20 12:55 ` Richard Purdie
2022-09-20 20:29 ` Bruce Ashfield
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=1503439015.32591.138.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.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