Re: Cannot boot with rootfs from eMMC if maxcpus=1

2017-11-18 Thread Randy Dunlap
On 11/09/2017 08:14 AM, Richard Schmitt wrote: > Using a 4.9 kernel, trying to boot a kernel using an eMMC based rootfs will > result in a crash > > The message preceeding the crash is: > > [3.285566] VFS: Cannot open root device "mmcblk0p9" or > unknown-block(0,0): error -6 > [

Re: Cannot boot with rootfs from eMMC if maxcpus=1

2017-11-18 Thread Randy Dunlap
On 11/09/2017 08:14 AM, Richard Schmitt wrote: > Using a 4.9 kernel, trying to boot a kernel using an eMMC based rootfs will > result in a crash > > The message preceeding the crash is: > > [3.285566] VFS: Cannot open root device "mmcblk0p9" or > unknown-block(0,0): error -6 > [

Cannot boot with rootfs from eMMC if maxcpus=1

2017-11-09 Thread Richard Schmitt
Using a 4.9 kernel, trying to boot a kernel using an eMMC based rootfs will result in a crash The message preceeding the crash is: [3.285566] VFS: Cannot open root device "mmcblk0p9" or unknown-block(0,0): error -6 [3.293338] Please append a correct "root=" boot option; here are the

Cannot boot with rootfs from eMMC if maxcpus=1

2017-11-09 Thread Richard Schmitt
Using a 4.9 kernel, trying to boot a kernel using an eMMC based rootfs will result in a crash The message preceeding the crash is: [3.285566] VFS: Cannot open root device "mmcblk0p9" or unknown-block(0,0): error -6 [3.293338] Please append a correct "root=" boot option; here are the