Boot failure after upgrade to kernel 6.9

patrick_g · 2024-05-18 16:36:00

After updating my kernel from the 6.8 to the 6.9 version and rebooting, I'm stuck in the boot sequence.
I see an error :
"Framebuffer coreboot8: probe with driver framebuffer failed with error -17".

boot

Tried to Google this error but found nothing relevant. Any idea?

loqs · 2024-05-18 16:48:00

Please chroot in from the installation media then post the system journal from the boot with the issue to a pastebin and post the link to that.

patrick_g · 2024-05-18 18:21:44

I used the fallback option of my boot manager to boot.
It worked and I was able to log into my XFCE session...but I have no WiFi, I don't know why.

I then saved the result of "sudo dmesg" to a txt file and put it in a pastebin.

https://pastebin.com/wZWPHJFZ

Everytime I try to boot from the normal boot option (not the fallback one) I see the same boot error.

Last edited by patrick_g (2024-05-18 18:23:25)

loqs · 2024-05-18 20:11:25

Two drivers want to create /bus/platform/devices/simple-framebuffer:

[    8.004317] sysfs: cannot create duplicate filename '/bus/platform/devices/simple-framebuffer.0'
[    8.004323] CPU: 5 PID: 546 Comm: (udev-worker) Not tainted 6.9.1-arch1-1 #1 8721656fa781c58301f7268d475f3e6380e2b47c
[    8.004327] Hardware name: Notebook NS5x_NS7xPU/NS5x_NS7xPU, BIOS Dasharo (coreboot+UEFI) v1.7.2 12/21/2023
[    8.004329] Call Trace:
[    8.004331]  <TASK>
[    8.004333]  dump_stack_lvl+0x5d/0x80
[    8.004340]  sysfs_warn_dup.cold+0x17/0x23
[    8.004345]  sysfs_do_create_link_sd+0xcf/0xe0
[    8.004349]  bus_add_device+0x6b/0x130
[    8.004353]  device_add+0x3eb/0x8a0
[    8.004356]  platform_device_add+0xed/0x250
[    8.004361]  platform_device_register_full+0xbb/0x140
[    8.004366]  platform_device_register_resndata.constprop.0+0x54/0x80 [framebuffer_coreboot 42e734af8755849d8c844f9d1cd390543b9e9a3e]
[    8.004376]  framebuffer_probe+0x154/0x1a0 [framebuffer_coreboot 42e734af8755849d8c844f9d1cd390543b9e9a3e]
[    8.004384]  really_probe+0xdb/0x340
[    8.004389]  ? pm_runtime_barrier+0x54/0x90
[    8.004395]  ? __pfx___driver_attach+0x10/0x10
[    8.004399]  __driver_probe_device+0x78/0x110
[    8.004404]  driver_probe_device+0x1f/0xa0
[    8.004409]  __driver_attach+0xba/0x1c0
[    8.004414]  bus_for_each_dev+0x8c/0xe0
[    8.004418]  bus_add_driver+0x116/0x1f0
[    8.004422]  driver_register+0x72/0xd0
[    8.004425]  ? __pfx_framebuffer_driver_init+0x10/0x10 [framebuffer_coreboot 42e734af8755849d8c844f9d1cd390543b9e9a3e]
[    8.004433]  do_one_initcall+0x58/0x310
[    8.004439]  do_init_module+0x60/0x220
[    8.004445]  init_module_from_file+0x89/0xe0
[    8.004450]  idempotent_init_module+0x121/0x2b0
[    8.004454]  __x64_sys_finit_module+0x5e/0xb0
[    8.004456] mc: Linux media interface: v0.10
[    8.004459]  do_syscall_64+0x82/0x160
[    8.004462]  ? do_syscall_64+0x8e/0x160
[    8.004465]  ? do_syscall_64+0x8e/0x160
[    8.004468]  ? syscall_exit_to_user_mode+0x75/0x210
[    8.004470]  ? do_syscall_64+0x8e/0x160
[    8.004473]  ? do_syscall_64+0x8e/0x160
[    8.004476]  ? syscall_exit_to_user_mode+0x75/0x210
[    8.004478]  ? do_syscall_64+0x8e/0x160
[    8.004480]  ? exc_page_fault+0x81/0x190
[    8.004484]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[    8.004489] RIP: 0033:0x7ad61db27e9d
[    8.004509] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 63 de 0c 00 f7 d8 64 89 01 48
[    8.004512] RSP: 002b:00007fff36a1a7c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[    8.004517] RAX: ffffffffffffffda RBX: 00005dc608b40270 RCX: 00007ad61db27e9d
[    8.004520] RDX: 0000000000000004 RSI: 00007ad61e0f2376 RDI: 000000000000002a
[    8.004522] RBP: 00007ad61e0f2376 R08: 0000000000000003 R09: 00007fff36a1a810
[    8.004524] R10: 0000000000000007 R11: 0000000000000246 R12: 0000000000020000
[    8.004525] R13: 00005dc608b69d90 R14: 0000000000000000 R15: 00005dc608b3d200
[    8.004529]  </TASK>
[    8.004557] coreboot: could not register framebuffer
[    8.004561] framebuffer coreboot8: probe with driver framebuffer failed with error -17

patrick_g · 2024-05-18 20:17:00

loqs wrote:

Two drivers want to create /bus/platform/devices/simple-framebuffer:

Any idea about how to solve this?
Could it be related to the fact that this laptop use Coreboot as bios firmware?

boulders · 2024-05-19 02:20:49

Interesting, I'm having framebuffer issues too on my corebooted (libreboot) T430, with Intel HD4000 graphics.
Every time my system tries to open KDE, it works for a few seconds and then immediately Kwin restarts.

I get errors that say:

kwin_wayland_drm: Failed to create framebuffer: Input/output error

in journalctl.

My system was unusable in this state so I had to downgrade to kernel 6.8.9

seth · 2024-05-19 06:42:13

Can you boot when adding "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters ?

patrick_g · 2024-05-19 08:22:36

seth wrote:

Can you boot when adding "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters ?

Had a black screen after booting with this kernel parameter. I typed my LUKS password blindly and then the xfce session was up and running.
Still no WiFi.
Very strange.

If I look at errors In journalctl I see this.

journalctl

seth · 2024-05-19 10:51:41

It'll probably block both simpledrm devices - the wifi situation should be unrelated to that.
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Or "sudo journalctl -b > /tmp/journal.txt" and upload that.

patrick_g · 2024-05-20 17:56:10

When I'm blocked during the boot I have no other solution than a hard reset.
And then why I retry again to start the system everything is fine (so the boot problem is not systematic) and a "sudo journalctl -b > /tmp/journal.txt" would be useless because the second boot was successful.
Is there any solution to save a failed boot sequence that was interrupted by a hard reset?

Here is what I see when the boot sequence is blocked :

boot

Last edited by patrick_g (2024-05-20 17:56:43)

patrick_g · 2024-05-20 18:35:07

OK I played a little with journalctl and I found the boot sequence that was frozen and for witch I was forced to do a hard reset.
Here it is :

https://pastebin.com/B39vLTRz

loqs · 2024-05-20 18:52:35

Linked below is linux 6.9.arch1 built with the config from 6.8.9.arch1:
https://drive.google.com/file/d/1H80vq8 … sp=sharing linux-6.9.arch1-1.1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1Ytt0LX … sp=sharing linux-headers-6.9.arch1-1.1-x86_64.pkg.tar.zst
Does it have the issue?

patrick_g · 2024-05-20 20:15:52

I used the "downgrade" tool (https://aur.archlinux.org/packages/downgrade) to roll back my kernel from 6.9 to 6.8.9.
It seems to have resolved the problem. I booted 6 times in a row without any issue.

It's a little bit disappointing to not have been able to identify the root cause but I think I'll wait patiently for future versions of the kernel to see if the problem was solved.

Thanks to Loqs, Boulder and Seth for the help!

seth · 2024-05-20 21:01:51

The journal in #11 is from a boot w/o initcall_blacklist=simpledrm_platform_driver_init and the problem here is that we're not getting rid of the simplydumb device.

mai 20 19:45:08 archlinux systemd[1]: TPM2 PCR Barrier (Initialization) was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
mai 20 19:45:08 archlinux systemd-udevd[519]: 0000:00:02.0: Worker [552] terminated by signal 9 (KILL).
mai 20 19:45:08 archlinux kernel: resource: Trying to free nonexistent resource <0x0000000090000000-0x00000000907e8fff>
mai 20 19:45:08 archlinux kernel: BUG: unable to handle page fault for address: 0000000300000031
mai 20 19:45:08 archlinux kernel: #PF: supervisor read access in kernel mode
mai 20 19:45:08 archlinux kernel: #PF: error_code(0x0000) - not-present page
mai 20 19:45:08 archlinux kernel: PGD 0 P4D 0
mai 20 19:45:08 archlinux kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
mai 20 19:45:08 archlinux kernel: CPU: 14 PID: 552 Comm: (udev-worker) Not tainted 6.9.1-arch1-1 #1 8721656fa781c58301f7268d475f3e6380e2b47c
mai 20 19:45:08 archlinux kernel: Hardware name: Notebook NS5x_NS7xPU/NS5x_NS7xPU, BIOS Dasharo (coreboot+UEFI) v1.7.2 12/21/2023
mai 20 19:45:08 archlinux kernel: RIP: 0010:__release_resource+0x1c/0x90
mai 20 19:45:08 archlinux kernel: Code: 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 48 8b 47 28 48 8d 50 38 48 8b 40 38 48 85 c0 75 0f eb 52 48 8d 50 30 <48> 8b 40 30 48 85 c0 74 45 48 39 c7 75 ee 40 84 f6 75 45 48 8b 4f
mai 20 19:45:08 archlinux kernel: RSP: 0018:ffffa70dc3df79c8 EFLAGS: 00010296
mai 20 19:45:08 archlinux kernel: RAX: 0000000300000001 RBX: ffff9469c2654900 RCX: ffff9469c2425f80
mai 20 19:45:08 archlinux kernel: RDX: 0000000300000031 RSI: 0000000000000001 RDI: ffff9469c2654900
mai 20 19:45:08 archlinux kernel: RBP: ffff9469c14fcc00 R08: ffff9469c2423b70 R09: 0000000000000000
mai 20 19:45:08 archlinux kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff9469c1480000
mai 20 19:45:08 archlinux kernel: R13: 0000000000000000 R14: ffff9469c14800c8 R15: ffff9469c1480000
mai 20 19:45:08 archlinux kernel: FS:  000076112e00f640(0000) GS:ffff94711fb00000(0000) knlGS:0000000000000000
mai 20 19:45:08 archlinux kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
mai 20 19:45:08 archlinux kernel: CR2: 0000000300000031 CR3: 0000000104c64000 CR4: 0000000000f50ef0
mai 20 19:45:08 archlinux kernel: PKRU: 55555554
mai 20 19:45:08 archlinux kernel: Call Trace:
mai 20 19:45:08 archlinux kernel:  <TASK>
mai 20 19:45:08 archlinux kernel:  ? __die_body.cold+0x19/0x27
mai 20 19:45:08 archlinux kernel:  ? page_fault_oops+0x15a/0x2b0
mai 20 19:45:08 archlinux kernel:  ? exc_page_fault+0x81/0x190
mai 20 19:45:08 archlinux kernel:  ? asm_exc_page_fault+0x26/0x30
mai 20 19:45:08 archlinux kernel:  ? __release_resource+0x1c/0x90
mai 20 19:45:08 archlinux kernel:  release_resource+0x26/0x40
mai 20 19:45:08 archlinux kernel:  platform_device_del+0x51/0x90
mai 20 19:45:08 archlinux kernel:  platform_device_unregister+0x12/0x30
mai 20 19:45:08 archlinux kernel:  sysfb_disable+0x2f/0x80
mai 20 19:45:08 archlinux kernel:  aperture_remove_conflicting_pci_devices+0x8c/0xa0
mai 20 19:45:08 archlinux kernel:  i915_driver_probe+0x7d2/0xad0 [i915 92b0667587a9a10999b37a12d9e3db1fe5c34000]
mai 20 19:45:08 archlinux kernel:  local_pci_probe+0x42/0x90
mai 20 19:45:08 archlinux kernel:  pci_device_probe+0xbd/0x290
mai 20 19:45:08 archlinux kernel:  ? sysfs_do_create_link_sd+0x6e/0xe0
mai 20 19:45:08 archlinux kernel:  really_probe+0xdb/0x340
mai 20 19:45:08 archlinux kernel:  ? __pfx___driver_attach+0x10/0x10
mai 20 19:45:08 archlinux kernel:  __driver_probe_device+0x78/0x110
mai 20 19:45:08 archlinux kernel:  driver_probe_device+0x1f/0xa0
mai 20 19:45:08 archlinux kernel:  __driver_attach+0xba/0x1c0
mai 20 19:45:08 archlinux kernel:  bus_for_each_dev+0x8c/0xe0
mai 20 19:45:08 archlinux kernel:  bus_add_driver+0x116/0x1f0
mai 20 19:45:08 archlinux kernel:  driver_register+0x72/0xd0
mai 20 19:45:08 archlinux kernel:  i915_init+0x23/0x90 [i915 92b0667587a9a10999b37a12d9e3db1fe5c34000]
mai 20 19:45:08 archlinux kernel:  ? __pfx_i915_init+0x10/0x10 [i915 92b0667587a9a10999b37a12d9e3db1fe5c34000]
mai 20 19:45:08 archlinux kernel:  do_one_initcall+0x58/0x310
mai 20 19:45:08 archlinux kernel:  do_init_module+0x60/0x220
mai 20 19:45:08 archlinux kernel:  init_module_from_file+0x89/0xe0
mai 20 19:45:08 archlinux kernel:  idempotent_init_module+0x121/0x2b0
mai 20 19:45:08 archlinux kernel:  __x64_sys_finit_module+0x5e/0xb0
mai 20 19:45:08 archlinux kernel:  do_syscall_64+0x82/0x160
mai 20 19:45:08 archlinux kernel:  ? sched_clock+0x10/0x30
mai 20 19:45:08 archlinux kernel:  ? sched_clock_cpu+0xf/0x1d0
mai 20 19:45:08 archlinux kernel:  ? irqtime_account_irq+0x3e/0xc0
mai 20 19:45:08 archlinux kernel:  ? __irq_exit_rcu+0x4a/0xb0
mai 20 19:45:08 archlinux kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
mai 20 19:45:08 archlinux kernel: RIP: 0033:0x76112db27e9d
mai 20 19:45:08 archlinux kernel: Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 63 de 0c 00 f7 d8 64 89 01 48
mai 20 19:45:08 archlinux kernel: RSP: 002b:00007fff55a1ece8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
mai 20 19:45:08 archlinux kernel: RAX: ffffffffffffffda RBX: 000058410f5b80e0 RCX: 000076112db27e9d
mai 20 19:45:08 archlinux kernel: RDX: 0000000000000004 RSI: 000076112e0fe376 RDI: 0000000000000031
mai 20 19:45:08 archlinux kernel: RBP: 000076112e0fe376 R08: 0000000000000001 R09: 00007fff55a1ed30
mai 20 19:45:08 archlinux kernel: R10: 0000000000000050 R11: 0000000000000246 R12: 0000000000020000
mai 20 19:45:08 archlinux kernel: R13: 000058410f5b8550 R14: 0000000000000000 R15: 000058410f5bb230
mai 20 19:45:08 archlinux kernel:  </TASK>
mai 20 19:45:08 archlinux kernel: Modules linked in: snd_soc_acpi_intel_match soundwire_generic_allocation snd_soc_acpi soundwire_bus intel_rapl_msr intel_rapl_common snd_soc_avs intel_uncore_frequency intel_uncore_frequency_common snd_soc_hda_codec intel_tcc_cooling snd_hda_ext_core x86_pkg_temp_thermal intel_powerclamp snd_soc_core snd_compress iwlmvm(+) coretemp ac97_bus kvm_intel snd_pcm_dmaengine mac80211 uvcvideo i915(+) snd_hda_intel snd_intel_dspcfg videobuf2_vmalloc snd_intel_sdw_acpi kvm libarc4 uvc btusb snd_hda_codec ptp videobuf2_memops pps_core btrtl snd_hda_core videobuf2_v4l2 btintel snd_hwdep rapl iTCO_wdt btbcm hid_multitouch(+) videodev drm_buddy btmtk vfat intel_pmc_bxt snd_pcm intel_cstate memconsole_coreboot i2c_algo_bit iwlwifi videobuf2_common ledtrig_netdev ee1004 iTCO_vendor_support fat framebuffer_coreboot cbmem memconsole bluetooth spi_nor r8169 mc ttm snd_timer cfg80211 intel_pmc_mux drm_display_helper ecdh_generic intel_uncore mtd realtek intel_lpss_pci snd psmouse mousedev typec mdio_devres i2c_i801 cec
mai 20 19:45:08 archlinux kernel:  pcspkr intel_lpss libphy i2c_smbus soundcore intel_pmc_core roles intel_gtt thunderbolt idma64 rfkill i2c_hid_acpi igen6_edac video intel_vsec pmt_telemetry i2c_hid intel_hid pmt_class intel_scu_pltdrv wmi pinctrl_tigerlake coreboot_table sparse_keymap mac_hid pkcs8_key_parser crypto_user loop nfnetlink ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_generic usbhid dm_crypt cbc encrypted_keys trusted asn1_encoder tee dm_mod crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 sdhci_pci sha256_ssse3 cqhci sha1_ssse3 serio_raw atkbd aesni_intel sdhci nvme libps2 vivaldi_fmap nvme_core crypto_simd mmc_core xhci_pci nvme_auth spi_intel_pci cryptd i8042 xhci_pci_renesas spi_intel serio
mai 20 19:45:08 archlinux kernel: CR2: 0000000300000031
mai 20 19:45:08 archlinux kernel: ---[ end trace 0000000000000000 ]---

For the boots w/ "initcall_blacklist=simpledrm_platform_driver_init", https://wiki.archlinux.org/title/Keyboa … el_(SysRq) doesn't work either??

marretics · 2024-05-21 16:09:41

Thank you, seth and loqs for your input. I have had the same problem as patrick_g. Just for reference I have uploaded the output of journalctl -b here.
For me, adding the kernel option initcall_blacklist=simpledrm_platform_driver_init worked well and my system boots up properly.

It seems however, that during bootup, I do now not see much of an output until my display manager appears.

Now since I am still quite a linux noob I would like to better understand what that option actually does. Reading through https://www.kernel.org/doc/html/v4.14/gpu/tinydrm.html it seems quite cryptic to me. My only question would be: What are the functional impacts of this change?

seth · 2024-05-21 16:48:40

https://www.phoronix.com/news/Linux-5.1 … l-DRM-Misc and the option blocks it's init function, so the module cannot be activated.
You've a device w/ a kms capable driver (like 99.67545% of all users), so the device is close to useless for you and mainly serves as a fallback to get you a graphical wayland session if the i915 module has a hiccup - like the vesa driver would on X11 and just like that I don't like the approach because in reality people will just miss that they're running a software emulation - we had that in spades w/ the mesa split and the intel DDX driver /rant

I do now not see much of an output until my display manager appears.

May 21 04:26:02 archlinux kernel: Linux version 6.9.1-arch1-1 (linux@archlinux) (gcc (GCC) 14.1.1 20240507, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Fri, 17 May 2024 16:56:38 +0000
May 21 04:26:06 mario-starbook kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access

https://wiki.archlinux.org/title/Kernel … _KMS_start ?

loqs · 2024-05-21 23:52:00

@seth do you think this is a kernel regression?

seth · 2024-05-22 00:46:26

(Internal) edid isn't applied: https://bbs.archlinux.org/viewtopic.php?id=296012
Blocking the simpledrm device breaks the boot: https://bbs.archlinux.org/viewtopic.php?id=295911 (hybrid system)
Not sure whether this SLI issue ties in: https://bbs.archlinux.org/viewtopic.php?id=295987

There's certainly something going on around the simpledrm device and the journal in #15 doesn't even have the release failures - there's just the sysfs warning.

rootinthemood · 2024-06-06 05:06:07

Anybody has a solution for this yet? I'm having exactly the same issue since 6.9.1, still persistent in 6.9.3.
I have to power cycle a few times until it boots correctly.

seth · 2024-06-06 06:53:29

marretics wrote:

For me, adding the kernel option initcall_blacklist=simpledrm_platform_driver_init worked well and my system boots up properly.

rootinthemood · 2024-06-06 07:13:11

seth wrote:

marretics wrote:
For me, adding the kernel option initcall_blacklist=simpledrm_platform_driver_init worked well and my system boots up properly.

Yes I tried that before but did not work for me.
However just an early KMS start of the i915 driver did it for me(without the kernel blacklist option). Tried a bunch of restarts and so far so good.

patrick_g · 2024-06-06 08:05:59

rootinthemood wrote:

Yes I tried that before but did not work for me.
However just an early KMS start of the i915 driver did it for me(without the kernel blacklist option). Tried a bunch of restarts and so far so good.

I still see this issue even after upgrading to 6.9.3.
I would like to try your solution. How do you set an early KMS start of the i915 driver?

rootinthemood · 2024-06-06 08:16:17

patrick_g wrote:

rootinthemood wrote:
Yes I tried that before but did not work for me.
However just an early KMS start of the i915 driver did it for me(without the kernel blacklist option). Tried a bunch of restarts and so far so good.
I still see this issue even after upgrading to 6.9.3.
I would like to try your solution. How do you set an early KMS start of the i915 driver?

https://wiki.archlinux.org/title/Kernel … _KMS_start

So put 'i915' in MODULES and regenerate initramfs.

patrick_g · 2024-06-06 14:10:15

Thank you rootinthemood.
I modified my /etc/mkinitcpio.conf to put i915 in MODULES and regenerated initramfs and now the problem appears to be solved.
After 12 boots I haven't seen any boot failure (previously it was approximately one failure for 3 or 4 boots).

rootinthemood · 2024-06-06 16:38:05

Yeah this definitely fixes it. No errors about framebuffer in journalctl and dmesg anymore. Also slow shutdowns I was experiencing are also gone but that maybe unrelated.

Arch Linux

#1 2024-05-18 16:36:00

Boot failure after upgrade to kernel 6.9

#2 2024-05-18 16:48:00

Re: Boot failure after upgrade to kernel 6.9

#3 2024-05-18 18:21:44

Re: Boot failure after upgrade to kernel 6.9

#4 2024-05-18 20:11:25

Re: Boot failure after upgrade to kernel 6.9

#5 2024-05-18 20:17:00

Re: Boot failure after upgrade to kernel 6.9

#6 2024-05-19 02:20:49

Re: Boot failure after upgrade to kernel 6.9

#7 2024-05-19 06:42:13

Re: Boot failure after upgrade to kernel 6.9

#8 2024-05-19 08:22:36

Re: Boot failure after upgrade to kernel 6.9

#9 2024-05-19 10:51:41

Re: Boot failure after upgrade to kernel 6.9

#10 2024-05-20 17:56:10

Re: Boot failure after upgrade to kernel 6.9

#11 2024-05-20 18:35:07

Re: Boot failure after upgrade to kernel 6.9

#12 2024-05-20 18:52:35

Re: Boot failure after upgrade to kernel 6.9

#13 2024-05-20 20:15:52

Re: Boot failure after upgrade to kernel 6.9

#14 2024-05-20 21:01:51

Re: Boot failure after upgrade to kernel 6.9

#15 2024-05-21 16:09:41

Re: Boot failure after upgrade to kernel 6.9

#16 2024-05-21 16:48:40

Re: Boot failure after upgrade to kernel 6.9

#17 2024-05-21 23:52:00

Re: Boot failure after upgrade to kernel 6.9

#18 2024-05-22 00:46:26

Re: Boot failure after upgrade to kernel 6.9

#19 2024-06-06 05:06:07

Re: Boot failure after upgrade to kernel 6.9

#20 2024-06-06 06:53:29

Re: Boot failure after upgrade to kernel 6.9

#21 2024-06-06 07:13:11

Re: Boot failure after upgrade to kernel 6.9

#22 2024-06-06 08:05:59

Re: Boot failure after upgrade to kernel 6.9

#23 2024-06-06 08:16:17

Re: Boot failure after upgrade to kernel 6.9

#24 2024-06-06 14:10:15

Re: Boot failure after upgrade to kernel 6.9

#25 2024-06-06 16:38:05

Re: Boot failure after upgrade to kernel 6.9

Board footer