Re: Patch : drivers/md/dm-verity-target.c

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Mon, 6 Nov 2023, Aaditya Raj Barnwal wrote:

> thanks for  reply ,  
>
> yes we already have 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=035641b01e72af4f6c6cf22a4bdb5d7dfc4e8e8e 
> and kernel cmdline is with wait for /dev/dm-0 where i could make out 
> from the logs it was able to get /dev/dm-0 but still failed to get the 
> data-devices adding the logs below
> 
>    9.785204][    T9] mmc0: CQHCI version 5.10
> [    9.826746][    T9] mmc0: SDHCI controller on 8804000.sdhci [8804000.sdhci] using ADMA 64-bit
> [    9.835559][    T9] sdhci_msm 8804000.sdhci: mmc0: CQE init: success
> [    9.842578][    T1] device-mapper: init: waiting for device /dev/dm-0 ...

You should wait for /dev/mmcblk0 here, not for /dev/dm-0.

> [    9.849605][    T1] device-mapper: init:  exiting after  /dev/dm-0  <<<<<got  dev/dm-0 

Where does this 'exiting after' message come from? I grepped the kernel 
for it and didn't find it.

> [    9.856689][    T1] device-mapper: init: all devices available
> [    9.863061][    T1] device-mapper: table: 252:0: verity: Data device lookup failed
> [    9.870868][    T1] device-mapper: ioctl: error adding target to table
> [    9.895539][   T37] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
> [    9.898825][    T1] gcc-sdxpinn 80000.clock-controller: sync-state
> [    9.905125][   T37] cfg80211: failed to load regulatory.db
> [    9.911731][    T1] ALSA device list:
> [    9.920911][    T1]   No soundcards found.
> [    9.925133][    T1] TAP version 14
> [    9.928642][    T1] 1..0
> [    9.931645][    T1] md: Waiting for all devices to be available before autodetect
> [    9.931829][   T85] mmc0: Command Queue Engine enabled
> [    9.939343][    T1] md: If you don't use raid, use raid=noautodetect
> [    9.944631][   T85] mmc0: new HS400 MMC card at address 0001
> [    9.951158][    T1] md: Autodetecting RAID arrays.
> [    9.957520][   T85] mmcblk0: mmc0:0001 S0J35A 7.28 GiB
> [    9.961908][    T1] md: autorun ...
> [    9.961912][    T1] md: ... autorun DONE.
> [    9.970173][   T85]  mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 p29 p30 p31 p32 p33 p34 p35 p36
> p37 p38 p39 p40 p41 p42 p43 p44 p45 p46
> [    9.971004][    T1] Waiting for root device /dev/dm-0...
> [    9.979384][   T85] mmcblk0boot0: mmc0:0001 S0J35A 31.5 MiB
> [   10.005842][   T85] mmcblk0boot1: mmc0:0001 S0J35A 31.5 MiB
> [   10.012536][   T85] mmcblk0rpmb: mmc0:0001 S0J35A 4.00 MiB, chardev (500:0)
> [   10.901495][   T85] msm-dwc3 a600000.ssusb: DWC3 in low power mode
> << no rootfs and no further bootup  blocked at this point same as the above path >>

I see that you also use md - please describe the full storage stack that 
you use.

Mikulas

[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux