------- Comment From daniel.axte...@ibm.com 2020-11-25 00:34 EDT------- Hi,
Looks like it fails to boot on a p9 qemu/kvm guest even out of grub: hangs trying to bring up SMP. That's probably what we saw in bare-metal too, the console probably just didn't catch up. I will continue investigating, but I'm not sure what kernel tree you're using: git://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/hirsute has something based on linux-5.8. What tree are you building from? Kind regards, Daniel Loading Linux 5.10.0-4-generic ... Loading initial ramdisk ... OF stdout device is: /vdevice/vty@30000000 Preparing to boot Linux version 5.10.0-4-generic (buildd@bos02-ppc64el-008) (gcc (Ubuntu 10.2.0-17ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #5-Ubuntu SMP Mon Nov 16 09:41:59 UTC 2020 (Ubuntu 5.10.0-4.5-generic 5.10.0-rc4) Detected machine type: 0000000000000101 command line: BOOT_IMAGE=/boot/vmlinux-5.10.0-4-generic root=UUID=19b72275-8385-4e0e-8001-62baacf410e3 ro console=hvc0 earlyprintk xmon=rw Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : 0000000000000000 (16 MB aligned) alloc_bottom : 0000000006570000 alloc_top : 0000000010000000 alloc_top_hi : 0000000400000000 rmo_top : 0000000010000000 ram_top : 0000000400000000 instantiating rtas at 0x000000000daf0000... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x0000000006580000 -> 0x0000000006580b32 Device tree struct 0x0000000006590000 -> 0x00000000065a0000 Quiescing Open Firmware ... Booting Linux via __start() @ 0x0000000002000000 ... [ 0.000000] radix-mmu: Page sizes from device-tree: [ 0.000000] radix-mmu: Page size shift = 12 AP=0x0 [ 0.000000] radix-mmu: Page size shift = 16 AP=0x5 [ 0.000000] radix-mmu: Page size shift = 21 AP=0x1 [ 0.000000] radix-mmu: Page size shift = 30 AP=0x2 [ 0.000000] radix-mmu: Activating Kernel Userspace Execution Prevention [ 0.000000] radix-mmu: Activating Kernel Userspace Access Prevention [ 0.000000] radix-mmu: Mapped 0x0000000000000000-0x0000000002000000 with 2.00 MiB pages (exec) [ 0.000000] radix-mmu: Mapped 0x0000000002000000-0x0000000400000000 with 2.00 MiB pages [ 0.000000] lpar: Using radix MMU under hypervisor [ 0.000000] Linux version 5.10.0-4-generic (buildd@bos02-ppc64el-008) (gcc (Ubuntu 10.2.0-17ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #5-Ubuntu SMP Mon Nov 16 09:41:59 UTC 2020 (Ubuntu 5.10.0-4.5-generic 5.10.0-rc4) [ 0.000000] Secure boot mode disabled [ 0.000000] Found initrd at 0xc000000004700000:0xc00000000656fbfa [ 0.000000] Using pSeries machine description [ 0.000000] printk: bootconsole [udbg0] enabled [ 0.000000] Partition configured for 24 cpus. [ 0.000000] CPU maps initialized for 1 thread per core [ 0.000000] ----------------------------------------------------- [ 0.000000] phys_mem_size = 0x400000000 [ 0.000000] dcache_bsize = 0x80 [ 0.000000] icache_bsize = 0x80 [ 0.000000] cpu_features = 0x0001c07b8f4f91a7 [ 0.000000] possible = 0x000ffbfbcf5fb1a7 [ 0.000000] always = 0x00000003800081a1 [ 0.000000] cpu_user_features = 0xdc0065c2 0xeff00000 [ 0.000000] mmu_features = 0xbc007441 [ 0.000000] firmware_features = 0x00000085455a445f [ 0.000000] vmalloc start = 0xc008000000000000 [ 0.000000] IO start = 0xc00a000000000000 [ 0.000000] vmemmap start = 0xc00c000000000000 [ 0.000000] ----------------------------------------------------- [ 0.000000] numa: NODE_DATA [mem 0x3ffd24900-0x3ffd2bfff] [ 0.000000] rfi-flush: fallback displacement flush available [ 0.000000] count-cache-flush: flush disabled. [ 0.000000] link-stack-flush: flush disabled. [ 0.000000] stf-barrier: eieio barrier available [ 0.000000] PCI host bridge /pci@800000020000000 ranges: [ 0.000000] IO 0x0000200000000000..0x000020000000ffff -> 0x0000000000000000 [ 0.000000] MEM 0x0000200080000000..0x00002000ffffffff -> 0x0000000080000000 [ 0.000000] MEM 0x0000210000000000..0x000021ffffffffff -> 0x0000210000000000 [ 0.000000] PPC64 nvram contains 65536 bytes [ 0.000000] barrier-nospec: using ORI speculation barrier [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x0000000000000000-0x00000003ffffffff] [ 0.000000] Device empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000000000000-0x00000003ffffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x00000003ffffffff] [ 0.000000] percpu: Embedded 11 pages/cpu s628760 r0 d92136 u720896 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 261888 [ 0.000000] Policy zone: Normal [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinux-5.10.0-4-generic root=UUID=19b72275-8385-4e0e-8001-62baacf410e3 ro console=hvc0 earlyprintk xmon=rw [ 0.000000] Dentry cache hash table entries: 2097152 (order: 8, 16777216 bytes, linear) [ 0.000000] Inode-cache hash table entries: 1048576 (order: 7, 8388608 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:on, heap free:off [ 0.000000] Memory: 16563392K/16777216K available (17728K kernel code, 3200K rwdata, 8320K rodata, 6528K init, 2230K bss, 213824K reserved, 0K cma-reserved) [ 0.000000] random: get_random_u64 called from kmem_cache_open+0x3c/0x330 with crng_init=0 [ 0.000000] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=24, Nodes=1 [ 0.000000] ftrace: allocating 44887 entries in 17 pages [ 0.000000] ftrace: allocated 17 pages with 2 groups [ 0.000000] rcu: Hierarchical RCU implementation. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=2048 to nr_cpu_ids=24. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] Rude variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=24 [ 0.000000] NR_IRQS: 512, nr_irqs: 512, preallocated irqs: 16 [ 0.000001] time_init: 32 bit decrementer (max: 7fffffff) [ 0.000554] clocksource: timebase: mask: 0xffffffffffffffff max_cycles: 0x761537d007, max_idle_ns: 440795202126 ns [ 0.001611] clocksource: timebase mult[1f40000] shift[24] registered [ 0.002314] Console: colour dummy device 80x25 [ 0.002772] printk: console [hvc0] enabled [ 0.002772] printk: console [hvc0] enabled [ 0.003215] printk: bootconsole [udbg0] disabled [ 0.003215] printk: bootconsole [udbg0] disabled [ 0.003753] pid_max: default: 32768 minimum: 301 [ 0.003862] LSM: Security Framework initializing [ 0.003933] Yama: becoming mindful. [ 0.003986] AppArmor: AppArmor initialized [ 0.004067] Mount-cache hash table entries: 32768 (order: 2, 262144 bytes, linear) [ 0.004141] Mountpoint-cache hash table entries: 32768 (order: 2, 262144 bytes, linear) [ 0.004799] POWER9 performance monitor hardware support registered [ 0.004874] rcu: Hierarchical SRCU implementation. [ 0.005741] smp: Bringing up secondary CPUs ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: Canonical requests to test the secure boot for the 5.10 kernel but kernel fails to boot with secure boot disabled. The 5.10 kernel can be found in: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap They can be installed by installing the linux-generic-wip package with this PPA enabled. As usual, they are only signed using a key specific to that PPA. This key can be retrieved from the signing tarballs for the kernels, e.g.: http://ppa.launchpad.net/canonical-kernel- team/bootstrap/ubuntu/dists/hirsute/main/signed/linux-5.10-ppc64el/5.10.0-2.3/signed.tar.gz Our tester installed the 5.10 kernel via aptitude. If booting directly from the bootmenu, it stucks at: "kexec_core: Starting new kernel" If booting recovery kernel for 5.10.0, it proceeds farther and after kexec_core, it failed at: " [ 0.029830] LSM: Security Framework initializing [ 0.029916] Yama: b " Two attempts with a different scenario; running with 5.8 kernel and boot via commandline for 5.10: kexec -l /boot/vmlinux-5.10.0-0-generic --initrd=/boot/initrd.img-5.10.0-0-generic --append="root=UUID=49d000cb-dba2-4d70-809e-38f2b31d0f09 ro quiet splash" kexec -e Both attempts also failed while rebooting, once with the same error as the error from booting with bootmenu; the other failure occurred a lot earlier. Wondering what new CONFIGs and/or features for the 5.10 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
