Linux kernel 4.4.70 can't boot successfully about bpi-r2-bsp HOT 5 OPEN

Sometimes the boot will work, however then it crashes with the following error:

[ 7.195748] VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2): error -6
[ 7.203832] Please append a correct "root=" boot option; here are the available partitions:
[ 7.212340] 0100 4096 ram0 (driver?)
[ 7.217049] 0101 4096 ram1 (driver?)
[ 7.221771] 0102 4096 ram2 (driver?)
[ 7.226475] 0103 4096 ram3 (driver?)
[ 7.231195] 0104 4096 ram4 (driver?)
[ 7.241095] 0105 4096 ram5 (driver?)
[ 7.250895] 0106 4096 ram6 (driver?)
[ 7.260569] 0107 4096 ram7 (driver?)
[ 7.270123] 0108 4096 ram8 (driver?)
[ 7.279522] 0109 4096 ram9 (driver?)
[ 7.288835] 010a 4096 ram10 (driver?)
[ 7.298175] 010b 4096 ram11 (driver?)
[ 7.307491] 010c 4096 ram12 (driver?)
[ 7.316733] 010d 4096 ram13 (driver?)
[ 7.325908] 010e 4096 ram14 (driver?)
[ 7.334956] 010f 4096 ram15 (driver?)
[ 7.343895] b300 7634944 mmcblk0 driver: mmcblk
[ 7.353375] b318 512 mmcblk0rpmb (driver?)
[ 7.362750] b310 4096 mmcblk0boot1 (driver?)
[ 7.372226] b308 4096 mmcblk0boot0 (driver?)
[ 7.381596] b320 15711232 mmcblk1 driver: mmcblk
[ 7.390928] b321 262144 mmcblk1p1 017d4b90-01
[ 7.400193] b322 15346688 mmcblk1p2 017d4b90-02
[ 7.409331] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
[ 7.421638] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.4.70-BPI-R2-Kernel #1

Looks like mmcblk* numbers are inverted, AFAIK we should have mmcblk0p1/2 and mmcblk1boot0/1

from bpi-r2-bsp.

@dfiloni for the issue you encountered, because the MMC0(EMMC) was named as mmcblk0, but there is no avaialable file system on it, and the command line is "..... root=/dev/mmcblk0p2 ...", so it crashed.

There are two workarounds:

1. Change the command line in <SD/part1>/bananapi/bpoi-r2/linux/uEnv.txt to “..... root=/dev/mmcblk1p2 ......", or
2. Disable the MMC0(EMMC) in dts(mt7623n-bpi-r2.dts), rebuild the kernal, and then update the kernel image of SD .

Let me know if you have any problem.

from bpi-r2-bsp.

@garywangcn: I already applied the first workaround, it works fine after the uEnv.txt fix ;) Then it boots fine each time (looks like only the first boot triggers the issue described by you in this bug)

from bpi-r2-bsp.

@dfiloni Thanks for your information.
I think the issue you reported is not the same with the one I encountered.

from bpi-r2-bsp.

Hello,

I have exactly the same issue. Sometime after power outage I can not boot in OS. It stays on the same step as on the screenshot from the first post (Key type dns_resolver registered). I can only boot after several restarts (after 5-6 restarts OS will boot succesfully).

Thank you,

from bpi-r2-bsp.