From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: block: potential bug on linux-block/for-next
Date: Wed, 23 Feb 2022 03:14:52 +0000 [thread overview]
Message-ID: <3386f561-604f-ff9d-51ca-77ff90835376@nvidia.com> (raw)
In-Reply-To: <3610d58a-ef1d-a460-4bb7-de3d0297dae2@kernel.dk>
On 2/22/22 18:58, Jens Axboe wrote:
> On 2/22/22 7:49 PM, Chaitanya Kulkarni wrote:
>> Hi,
>>
>> After today's pull on linux-block/for-next test QEMU is not able to
>> boot, any information about how to solve this will be helpful as
>> it is blocking blktest testing, here is dmsg :-
>>
>> [ 1.304698] ata1.00: Read log 0x00 page 0x00 failed, Emask 0x1
>> [ 1.305587] ata1.01: Read log 0x00 page 0x00 failed, Emask 0x1
>> [ 1.455959] systemd[1]: Cannot be run in a chroot() environment.
>> [ 1.456743] systemd[1]: Freezing execution.
>
> What was the previous one you tried? What are the changes between the
> two?
>
This is the one tried and can boot normally:-
root@dev linux-block ((HEAD detached at 03546d43eb84)) # git log -1
commit 03546d43eb841d5fd66203822c2bb290a46464c9 (HEAD)
Merge: a102cd383c4a 55143a783f07
Author: Jens Axboe <axboe@kernel.dk>
Date: Wed Feb 16 19:38:35 2022 -0700
Merge branch 'for-5.18/drivers' into for-next
* for-5.18/drivers:
null_blk: remove hardcoded alloc_cmd() parameter
-ck
next prev parent reply other threads:[~2022-02-23 3:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 2:49 block: potential bug on linux-block/for-next Chaitanya Kulkarni
2022-02-23 2:58 ` Jens Axboe
2022-02-23 3:14 ` Chaitanya Kulkarni [this message]
2022-02-23 3:18 ` Jens Axboe
2022-02-23 4:13 ` Chaitanya Kulkarni
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=3386f561-604f-ff9d-51ca-77ff90835376@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=linux-block@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