Comments
gbcox
My problem was related to a grub.cfg cmdline changing karma.
I took a photo of the errors, here they are:
Jun 24 13:18:83 charon Bystemet 11535]: Failed to switch root: Specified switch root path /sysroot' does not seem to be an OS tree. os-release file is missing. Jun 24 13:18:83 charon systemd[1]: initrd-switch-root.service: Main process exited, code=exited, status=1/FAILURE
Jun 24 13:18:83 charon systemd[1]: initrd-switch-root.service: Failed with result 'exit-code". Jun 24 13:18:83 charon systemd[1]: Failed to start initrd-switch-root.service Switch Boot. Jun 24 13:18:83 charon systemd[1]: Startup finished in 236us (firmare) 129us (loader) 2.538s (kernel) 8 (initrd) 6.861s (userspace) = 9.3928.
Jun 24 13:18:83 charon systemd[1]: initrd-switch-root.service: Triggering OnFailure dependencies. Jun 24 13:18:83 charon systemd[1]: Started emergency.service- Emergency Shell.
Jun 24 13:18:83 charon systemd[1]: Reached target emergency.target - Emergency Mode.
9.371419) charon systemd[1]: Starting initrd-switch-root.service L 9.3771621 charon Bystemet1(535): Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree, os-release file is missing. L 9.3778141 charon systemd[1]: initrd-switch-root.service: Main process exited, code=exited, status=1/FAILURE
I
L 9.377965] charon systemd[1]: initrd-switch-root.service: Failed with result 'exit-code'. L 9.3883871 charon systemd[1]: Failed to start initrd-switch-root.service- Switch Root.
9.3922131 charon systemd[1]: Startup finished in 236us (firmare) 129us (loader) 2.538s (kernel) 8 (initrd) + 6.861s (userspace) = 9.392s. 9.3923861 charon systemd[1]: initrd-switch-root.service: Triggering OnFailure dependencies. I 9.1843781 charon systemd[1]: Started emergency.service- Emergency Shell.
I 9.184595] charon systemd[1]: Reached target emergency.target Emergency Mode. I 9.4284331 charon systemd[1]: Received SIGRIMIN-21 from PID 451 (plymouthd). 9.4384651 charon systemd[1]: Received SIGRTMIM+21 from PID 451 (plymouthd).
Just another note, looking at the other negative karma and the thing everyone has in common is that the are using AMD (including myself), so possibly this update is toxic to AMD.
Just another note, looking at the other negative karma and the thing everyone has in common is that the are using AMD (including myself), so possibly this update is toxic to AMD.
I got thrown into rescue maintenance mode when I booted. I looked at the journal and it reported errors about ostree, which was odd since I'm not running silverblue, I'm using normal workstation. I backed out to the previous kernel and all is working fine now. Unfortunately it appears that journal wasn't saved so I can't post any of the error messages. If I'm missing something on how to retrieve messages from that log, please advise, but it appears it wasn't retained.
Unfortuately system freeze with this kernel. Log shows: ? do_error_trap+0x6a/0x90 ...: 1 Time(s) BUG: soft lockup - CPU#3 stuck for 108s! [kw ...: 1 Time(s) BUG: soft lockup - CPU#3 stuck for 134s! [kw ...: 1 Time(s) BUG: soft lockup - CPU#3 stuck for 160s! [kw ...: 1 Time(s) BUG: soft lockup - CPU#3 stuck for 186s! [kw ...: 1 Time(s) BUG: soft lockup - CPU#3 stuck for 212s! [kw ...: 1 Time(s) BUG: soft lockup - CPU#3 stuck for 23s! [kwo ...: 1 Time(s) BUG: soft lockup - CPU#3 stuck for 250s! [kw ...: 1 Time(s) BUG: soft lockup - CPU#3 stuck for 49s! [kwo ...: 1 Time(s) BUG: soft lockup - CPU#3 stuck for 82s! [kwo ...: 1 Time(s) INFO: rcu_preempt self-detected stall on CPU ...: 2 Time(s)
Then:
watchdog: BUG: soft lockup - CPU#3 stuck for 250s! [kworker/3:1:106764] Jun 08 21:39:28 charon kernel: Modules linked in: uinput snd_seq_dummy snd_hrtimer nft_fib_inet nft_fib_ipv4 > Jun 08 21:39:28 charon kernel: snd_timer i2c_piix4 snd soundcore pktcdvd loop zram amdgpu iommu_v2 drm_buddy> Jun 08 21:39:28 charon kernel: CPU: 3 PID: 106764 Comm: kworker/3:1 Tainted: G D OEL 6.3.6-200.fc> Jun 08 21:39:28 charon kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./SABERTOOTH 990FX/> Jun 08 21:39:28 charon kernel: Workqueue: events async_free_zspage Jun 08 21:39:28 charon kernel: RIP: 0010:queued_read_lock_slowpath+0x51/0x130 Jun 08 21:39:28 charon kernel: Code: 0f 1f 44 00 00 48 8d 6b 04 31 c0 ba 01 00 00 00 f0 0f b1 53 04 0f 85 d2 > Jun 08 21:39:28 charon kernel: RSP: 0018:ffffb1ce84d8fdf0 EFLAGS: 00000286 Jun 08 21:39:28 charon kernel: RAX: 00000000000002ff RBX: ffff8afb15cbb318 RCX: ffffb1ce84d8fe48 Jun 08 21:39:28 charon kernel: RDX: 0000000000000001 RSI: ffff8afb15cbb2e8 RDI: ffff8afb15cbb318 Jun 08 21:39:28 charon kernel: RBP: ffff8afb15cbb31c R08: 0000000000000000 R09: ffff8afe871c3a34 Jun 08 21:39:28 charon kernel: R10: 0000000000000007 R11: 0000000000000030 R12: ffff8afb15cbb318 Jun 08 21:39:28 charon kernel: R13: dead000000000122 R14: dead000000000100 R15: ffff8afb15cbb2d0 Jun 08 21:39:28 charon kernel: FS: 0000000000000000(0000) GS:ffff8affdecc0000(0000) knlGS:0000000000000000 Jun 08 21:39:28 charon kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 08 21:39:28 charon kernel: CR2: 00005605c9196000 CR3: 000000047a022000 CR4: 00000000000406e0 Jun 08 21:39:28 charon kernel: Call Trace: Jun 08 21:39:28 charon kernel: <IRQ> Jun 08 21:39:28 charon kernel: ? watchdog_timer_fn+0x1a8/0x210 Jun 08 21:39:28 charon kernel: ? __pfx_watchdog_timer_fn+0x10/0x10 Jun 08 21:39:28 charon kernel: ? __hrtimer_run_queues+0x112/0x2b0 Jun 08 21:39:28 charon kernel: ? hrtimer_interrupt+0xf8/0x230 Jun 08 21:39:28 charon kernel: ? __sysvec_apic_timer_interrupt+0x61/0x130 Jun 08 21:39:28 charon kernel: ? sysvec_apic_timer_interrupt+0x6d/0x90 Jun 08 21:39:28 charon kernel: </IRQ> Jun 08 21:39:28 charon kernel: <TASK> Jun 08 21:39:28 charon kernel: ? asm_sysvec_apic_timer_interrupt+0x1a/0x20 Jun 08 21:39:28 charon kernel: ? queued_read_lock_slowpath+0x51/0x130 Jun 08 21:39:28 charon kernel: lock_zspage+0x1a/0x470 Jun 08 21:39:28 charon kernel: async_free_zspage+0x111/0x1f0 Jun 08 21:39:28 charon kernel: process_one_work+0x1c7/0x3d0 Jun 08 21:39:28 charon kernel: worker_thread+0x51/0x390 Jun 08 21:39:28 charon kernel: ? __pfx_worker_thread+0x10/0x10 Jun 08 21:39:28 charon kernel: kthread+0xde/0x110 Jun 08 21:39:28 charon kernel: ? __pfx_kthread+0x10/0x10 Jun 08 21:39:28 charon kernel: ret_from_fork+0x2c/0x50 Jun 08 21:39:28 charon kernel: </TASK>
Sorry, this was a mistake on my part. This update is not compatible with F37. I've opened a ticket to resolve.
Works! Thanks Adam for posting!
Thanks @ausil and @rombobeorn for the feedback.
resolves #2162496
@jforbes, I had originally found the bug via: https://forum.endeavouros.com/t/netgear-wifi-dongle-mt7612u-hangs-os-on-connect-as-of-kernel-6-1-1/35159/9 and then i misinterpreted the 6.1,6.1.1 missing the comma, thinking this was when it was fixed, not reported. Comment 9 thinks it may be in next weeks release (hopefully). Thanks for keeping an eye out for it.
Opened: https://bugzilla.redhat.com/show_bug.cgi?id=2162496 to report mt76x2u issue.
System freezes when USB Network adapter ALFA AWUS036ACM is inserted, which uses mt76x2u. I found this bug: https://bugzilla.kernel.org/show_bug.cgi?id=216839. but according to the report, it should have been included in 6.1.6 - if this is the case, then the issue isn't fixed.
Sorry, report above press the wrong thumbs up/ thumbs down.
System freezes when USB Network adapter ALFA AWUS036ACM is inserted, which uses mt76x2u. I found this bug: https://bugzilla.kernel.org/show_bug.cgi?id=216839. but according to the report, it should have been included in 6.1.6 - if this is the case, then the issue isn't fixed.
Thanks! Resolves regressions described in #2156259
Problem: package kf5-kimageformats-5.100.0-1.fc37.x86_64 requires libavif.so.14()(64bit), but none of the providers can be installed - cannot install both libavif-0.10.1-3.fc37.x86_64 and libavif-0.11.1-1.fc37.x86_64 - cannot install the best update candidate for package kf5-kimageformats-5.99.0-4.fc37.x86_64 - problem with installed package libavif-0.11.1-1.fc37.x86_64 ===========================================================================
works for me
works for me
works for me
Works