On 2/22/22 8:14 PM, Chaitanya Kulkarni wrote: > 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@xxxxxxxxx> > 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 Can you bisect between those two? Not sure what this might be... -- Jens Axboe
