FYI, after correctly setting both mce=off pci=noaer, I booted up ok. Just setting mce=off resulted in a crash. After booting up, I still see these messages in dmesg:
[ 14.818868] genirq: Flags mismatch irq 0. 00000000 (0000:06:00.1) vs. 00215a00 (timer) [ 17.518899] clocksource: Long readout interval, skipping watchdog check: cs_nsec: 2795340213 wd_nsec: 2795338094 [ 17.550967] i2c i2c-7: Successfully instantiated SPD at 0x56 [ 17.553505] i2c i2c-7: Successfully instantiated SPD at 0x57 [ 17.566615] ae4dma 0000:06:00.1: probe with driver ae4dma failed with error -16 [ 17.569676] Console: switching to colour dummy device 80x25 [ 17.571357] ae4dma 0000:21:00.1: enabling device (0000 -> 0002) [ 17.572644] ipmi_si IPI0001:00: IPMI kcs interface initialized [ 17.589639] ipmi_ssif: IPMI SSIF Interface driver [ 17.599321] genirq: Flags mismatch irq 0. 00000000 (0000:21:00.1) vs. 00215a00 (timer) [ 20.299338] workqueue: work_for_cpu_fn hogged CPU for >10000us 7 times, consider switching to WQ_UNBOUND [ 20.307939] ast 0000:63:00.0: vgaarb: deactivate vga console [ 20.313995] ast 0000:63:00.0: Using default configuration [ 20.314001] ast 0000:63:00.0: AST 2600 detected [ 20.314101] ast 0000:63:00.0: [drm] Using ASPEED DisplayPort transmitter [ 20.314106] ast 0000:63:00.0: [drm] dram MCLK=396 Mhz type=1 bus_width=16 [ 20.322326] ae4dma 0000:21:00.1: probe with driver ae4dma failed with error -16 [ 20.328255] ast 0000:63:00.0: [drm] Registered 1 planes with drm panic [ 20.328260] [drm] Initialized ast 0.1.0 for 0000:63:00.0 on minor 0 [ 20.329382] ae4dma 0000:45:00.1: enabling device (0000 -> 0002) [ 20.333122] fbcon: astdrmfb (fb0) is primary device [ 20.334660] genirq: Flags mismatch irq 0. 00000000 (0000:45:00.1) vs. 00215a00 (timer) [ 23.039505] ae4dma 0000:45:00.1: probe with driver ae4dma failed with error -16 [ 23.045129] RAPL PMU: API unit is 2^-32 Joules, 2 fixed counters, 163840 ms ovfl timer [ 23.045134] RAPL PMU: hw unit of domain package 2^-16 Joules [ 23.045136] RAPL PMU: hw unit of domain core 2^-16 Joules [ 23.071991] ae4dma 0000:64:00.1: enabling device (0000 -> 0002) [ 23.072689] genirq: Flags mismatch irq 0. 00000000 (0000:64:00.1) vs. 00215a00 (timer) [ 25.772704] workqueue: pci_pme_list_scan hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND [ 25.772793] Console: switching to colour frame buffer device 128x48 [ 25.789970] ast 0000:63:00.0: [drm] fb0: astdrmfb frame buffer device [ 25.808058] ae4dma 0000:64:00.1: probe with driver ae4dma failed with error -16 [ 25.808235] ae4dma 0000:82:00.1: enabling device (0000 -> 0002) [ 25.809150] genirq: Flags mismatch irq 0. 00000000 (0000:82:00.1) vs. 00215a00 (timer) [ 28.509161] workqueue: pci_pme_list_scan hogged CPU for >10000us 5 times, consider switching to WQ_UNBOUND [ 28.509169] workqueue: work_for_cpu_fn hogged CPU for >10000us 11 times, consider switching to WQ_UNBOUND [ 28.509671] ae4dma 0000:82:00.1: probe with driver ae4dma failed with error -16 [ 28.509869] ae4dma 0000:a2:00.1: enabling device (0000 -> 0002) [ 28.510461] genirq: Flags mismatch irq 0. 00000000 (0000:a2:00.1) vs. 00215a00 (timer) [ 31.211299] ae4dma 0000:a2:00.1: probe with driver ae4dma failed with error -16 [ 31.211528] ae4dma 0000:c1:00.1: enabling device (0000 -> 0002) [ 31.223058] genirq: Flags mismatch irq 0. 00000000 (0000:c1:00.1) vs. 00215a00 (timer) [ 33.923092] workqueue: pci_pme_list_scan hogged CPU for >10000us 7 times, consider switching to WQ_UNBOUND [ 33.923930] ae4dma 0000:c1:00.1: probe with driver ae4dma failed with error -16 [ 33.924148] ae4dma 0000:e1:00.1: enabling device (0000 -> 0002) [ 33.924710] genirq: Flags mismatch irq 0. 00000000 (0000:e1:00.1) vs. 00215a00 (timer) [ 33.989858] EXT4-fs (nvme10n1p2): mounted filesystem 7dd4edfe-c36f-4894-b4d2-46d56e949e25 r/w with ordered data mode. Quota mode: none. [ 36.641857] ae4dma 0000:e1:00.1: probe with driver ae4dma failed with error -16 ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2106553 Title: Epyc Genoa system unable to boot starting with Kernel 6.14.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106553/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
