Well my bad for saying packages do not require Linux kernel as a dependency explicitly, as for partial upgrades , I would say they are not advisable but can be utilised for stability and usability if a recent kernel version causes issues.
And just to add to it which I should have said way earlier, holding the kernel package like this is only safe (mostly) for a few months (6-8 months max) at best. After which one should give a new kernel version a try. Doing this for years or longer can and WILL cause issues.
Kinda feel ashamed that I forgot to say this earlier.
2-3 months is the sweet spot in IMO if one has the NECESSITY of the ABSOLUTE NEED to freeze the kernel package.
Again comes to my experience, I have held kernel updates a few time mostly for a month or two at best and can say I have never faced issues. LTS is the kernel version which I have used for long and held updates for.
NOTE FOR NEW USERS:
To freeze the updates for kernel packages, add their package name to the IgnorePkg line in /etc/pacman.conf and remove the # at the starting of the line.
So you will have IgnorePkg = linux linux-headers or something similar.
@BluishHumility , I have added a note to all my replys and tried to fix the mess I unknowingly made. Sorry to everyone.
After I updated to Plasma 6.2 and some other bluetooth apps and libraries, I get the same freezing issue every time I pluig / unplug USB dongles. I started to think this is more of a bluetooth driver issue than latest kernel problem. I am typing from 6.11.2 with Plasma 6.2, but I know as soon as I plug in a new USB device, my PC will freeze up.
Here is the output of journalctl:
— 20241010-1308 —
Here is the output of dmesg:
╰─λ sudo dmesg | grep -i bluetooth
So, do I have to wait another USB / bluetooth driver update ?
Isao
Idk about things but you gotta put the output in code blocks man, it is really difficult to decipher anything otherwise , select the text output and click on the code icon in edit mode: </> this one to put it in code blocks for you.
Sorry, I am still new to this new forum system.
I can’t snap back to the working image anymore, since it’s not the new kernel that’s affecting the system anymore.
Here is something I got from dmesg:
[ 18.338100] warning: `kdeconnectd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[ 25.918790] Bluetooth: hci0: Device setup in 20439837 usecs
[ 25.918795] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[ 26.197792] Bluetooth: hci0: AOSP extensions version v1.00
[ 26.197797] Bluetooth: hci0: AOSP quality report is supported
[ 26.217427] Bluetooth: MGMT ver 1.23
[ 26.221214] NET: Registered PF_ALG protocol family
[ 26.240069] Bluetooth: RFCOMM TTY layer initialized
[ 26.240073] Bluetooth: RFCOMM socket layer initialized
[ 26.240075] Bluetooth: RFCOMM ver 1.11
[ 32.175635] xhci_hcd 0000:15:00.0: xHC error in resume, USBSTS 0x401, Reinit
[ 32.175640] usb usb1: root hub lost power or was reset
[ 32.175642] usb usb2: root hub lost power or was reset
[ 32.550608] usb 1-12: reset high-speed USB device number 2 using xhci_hcd
[ 32.780523] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240716163633
[ 43.064039] Bluetooth: hci0: Execution of wmt command timed out
[ 43.064046] Bluetooth: hci0: Failed to send wmt patch dwnld (-110)
[ 43.064072] Bluetooth: hci0: Failed to set up firmware (-110)
[ 43.064074] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[ 45.116450] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[ 45.117444] Bluetooth: hci0: command 0xfd30 tx timeout
[ 45.117465] Bluetooth: hci0: AOSP get vendor capabilities (-110)
[ 45.245739] Oops: general protection fault, probably for non-canonical address 0xdead000000000122: 0000 [#1] PREEMPT SMP NOPTI
[ 45.245747] CPU: 30 UID: 0 PID: 328 Comm: kworker/30:1 Not tainted 6.11.2-zen1-1-zen #1 d30fef8841e6fc6d439846897474034e8403afe5
[ 45.245751] Hardware name: ASRock X670E Pro RS/X670E Pro RS, BIOS 3.08 09/18/2024
[ 45.245754] Workqueue: events __usb_queue_reset_device
[ 45.245760] RIP: 0010:hci_unregister_dev+0x45/0x230 [bluetooth]
[ 45.245786] Code: 89 ef e8 6e 5c bc cf f0 80 8b e9 0e 00 00 08 48 89 ef e8 be 47 bc cf 48 c7 c7 e8 1e da c0 e8 d2 c1 bc cf 48 8b 43 08 48 8b 13 <48> 3b 18 0f 85 6e a3 07 00 48 3b 5a 08 0f 85 64 a3 07 00 48 89 42
[ 45.245789] RSP: 0018:ffffa7ff06463d30 EFLAGS: 00010246
[ 45.245793] RAX: dead000000000122 RBX: ffff9af640fb4000 RCX: 0000000000000002
[ 45.245796] RDX: dead000000000100 RSI: ffff9af6478f3550 RDI: ffffffffc0da1ee8
[ 45.245798] RBP: ffff9af640fb44d0 R08: 0000000000000000 R09: 0000000000000001
[ 45.245801] R10: ffff9af640209e18 R11: 0000000000000040 R12: ffff9af640fb4000
[ 45.245803] R13: ffffffffc109e258 R14: ffffffffc109e258 R15: ffff9af641a77c50
[ 45.245806] FS: 0000000000000000(0000) GS:ffff9afd5e700000(0000) knlGS:0000000000000000
[ 45.245810] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 45.245813] CR2: 0000713a7938d4d4 CR3: 00000001c8622000 CR4: 0000000000f50ef0
[ 45.245817] PKRU: 55555554
[ 45.245820] Call Trace:
[ 45.245825] <TASK>
[ 45.245830] ? die_addr.cold+0x8/0xd
[ 45.245839] ? exc_general_protection+0x38a/0x4f0
[ 45.245852] ? srso_alias_return_thunk+0x5/0xfbef5
[ 45.245873] ? asm_exc_general_protection+0x26/0x30
[ 45.245889] ? hci_unregister_dev+0x45/0x230 [bluetooth d8126f1cd857657cd30c5ab37a29ea8077cf397c]
[ 45.245967] btusb_disconnect+0x67/0x170 [btusb 7b8fccfa22d7425ead7fb9564bf32c0e1306028b]
[ 45.245984] usb_unbind_interface+0x92/0x290
[ 45.245998] device_release_driver_internal+0x2ed/0x320
[ 45.246009] usb_forced_unbind_intf+0x75/0xb0
[ 45.246020] usb_reset_device+0x124/0x290
[ 45.246031] __usb_queue_reset_device+0x39/0x60
[ 45.246042] process_one_work+0x18f/0x350
[ 45.246056] worker_thread+0x24c/0x380
[ 45.246067] ? __pfx_worker_thread+0x10/0x10
[ 45.246075] kthread+0xcf/0x100
[ 45.246081] ? __pfx_kthread+0x10/0x10
[ 45.246087] ret_from_fork+0x31/0x50
[ 45.246093] ? __pfx_kthread+0x10/0x10
[ 45.246099] ret_from_fork_asm+0x1a/0x30
[ 45.246111] </TASK>
[ 45.246115] Modules linked in: uhid rfcomm cmac algif_hash algif_skcipher af_alg snd_seq_dummy snd_hrtimer snd_seq snd_seq_device qrtr bnep vfat fat snd_hda_codec_realtek intel_rapl_msr amd_atl amdgpu snd_hda_codec_generic mt7921e intel_rapl_common snd_hda_scodec_component mt7921_common snd_hda_codec_hdmi mt792x_lib mt76_connac_lib snd_hda_intel amdxcp mt76 snd_intel_dspcfg drm_exec btusb gpu_sched snd_intel_sdw_acpi btrtl mac80211 btintel drm_buddy snd_hda_codec i2c_algo_bit btbcm btmtk drm_suballoc_helper kvm_amd snd_hda_core drm_ttm_helper libarc4 mousedev bluetooth snd_hwdep kvm r8169 ttm spd5118 cfg80211 snd_pcmjoydev realtek drm_display_helper snd_timer gpio_amdpt mdio_devres i2c_piix4 snd cec rfkill libphy soundcore crc16 gpio_generic k10temp i2c_smbus rapl wmi_bmof mac_hid loop dm_mod nfnetlink zram ip_tables x_tables hid_generic usbhid crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel nvme gf128mul crypto_simd nvme_core cryptd
[ 45.246250] ccp sp5100_tco nvme_auth xhci_pci xhci_pci_renesas video wmi btrfs blake2b_generic libcrc32c crc32c_generic crc32c_intel xor raid6_pq uinput i2c_dev crypto_user
[ 45.246267] ---[ end trace 0000000000000000 ]---
I think either kdeconnect or bluedevil app is causing the issue, including the system freeze.
Isao
Might wanna downgrade again, downgrading packages and keeping them like so for a month in regard to linux-zen wont hurt your system’s stability or you can try the linux-lts kernel, these kind of issues were common at one time due to a kernel update as I saw on EndeavourOS forum and the fix was to be downgraded at the time.
So perhaps add your kernel to the IgnorePkg and downgrade it to the last version which worked fine for you and keep it like so for a month or so until a new update fixes things.
Once a newer version comes out which fixes your issue, you can remove the packages from IgnorePkg and get on with updates and keep slaying !
Also you might wanna read my last reply to @BluishHumility which can give you a general idea of stability if you hold packages and how to avoid breakages if you downgrade(only in the context of sole kernel packages).
Yep, I read that already.
If the kernel acts up really unstable, that would be the only option, like waiting out a storm.
I snapped back to 6.11.2 before this morning’s Plasma 6.2 update, yet still bluetooth was acting up. I tried manually reloading btusb driver and bluetooth and system stability came back. I really don’t know what’s going on…
1 Like
tbg
10 October 2024 22:10
50
If you feel blue devil is part of your issue you could always try replacing it with an alternate power manager such as:
https://wiki.archlinux.org/title/TLP
https://wiki.archlinux.org/title/Powertop
For further information see:
https://wiki.archlinux.org/title/Power_management
I would try replacing blue devil with TLP first, as this suggestion solved an issue with a crashing system a little while back.
You could also try replacing the Bluetooth management utility bluez with blueman to see if there is any improvement. This switch can also sometimes help with severe Bluetooth complications.
To install the blueman package, issue the command:
sudo pacman -S blueman
3 Likes
Thanks for the links and info, tbg.
I am closing this thread as the cause of the problem is shifting towards bluetooth, USB, and Plasma 6.2.
Here is a portion of journalctl from the unstable reboot:
╰─λ journalctl -p 3 -x -b -1 | grep -i error
Oct 10 13:50:23 isao-dsktp05 org_kde_powerdevil[4589]: busno=11, sleep-multiplier = 2.00. Testing for supported feature 0x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: EREMOTEIO(10)]
░░ This usually indicates a programming error in the crashing program and
░░ This usually indicates a programming error in the crashing program and
Oct 10 14:10:28 isao-dsktp05 systemd[3904]: plasma-kactivitymanagerd.service: Unexpected error response from GetNameOwner(): Connection terminated
Oct 10 14:10:28 isao-dsktp05 systemd[3904]: plasma-kglobalaccel.service: Unexpected error response from GetNameOwner(): Connection terminated
Oct 10 14:10:28 isao-dsktp05 systemd[3904]: plasma-xdg-desktop-portal-kde.service: Unexpected error response from GetNameOwner(): Connection terminated
Oct 10 14:10:28 isao-dsktp05 systemd[3904]: plasma-plasmashell.service: Unexpected error response from GetNameOwner(): Connection terminated
Oct 10 14:10:28 isao-dsktp05 systemd[3904]: at-spi-dbus-bus.service: Unexpected error response from GetNameOwner(): Connection terminated
Oct 10 14:10:28 isao-dsktp05 systemd[3904]: plasma-ksystemstats.service: Unexpected error response from GetNameOwner(): Connection terminated
Oct 10 14:10:28 isao-dsktp05 systemd[3904]: plasma-powerdevil.service: Unexpected error response from GetNameOwner(): Connection terminated
Oct 10 14:10:28 isao-dsktp05 systemd[3904]: xdg-permission-store.service: Unexpected error response from GetNameOwner(): Connection terminated
Oct 10 14:10:28 isao-dsktp05 systemd[3904]: xdg-desktop-portal-gtk.service: Unexpected error response from GetNameOwner(): Connection terminated
Oct 10 14:10:28 isao-dsktp05 systemd[3904]: xdg-desktop-portal.service: Unexpected error response from GetNameOwner(): Connection terminated
Oct 10 14:10:28 isao-dsktp05 systemd[3904]: plasma-polkit-agent.service: Unexpected error response from GetNameOwner(): Connection terminated
Oct 10 14:10:28 isao-dsktp05 systemd[3904]: xdg-document-portal.service: Unexpected error response from GetNameOwner(): Connection terminated
Oct 10 14:10:28 isao-dsktp05 systemd[3904]: plasma-ksmserver.service: Unexpected error response from GetNameOwner(): Connection terminated
Oct 10 14:10:28 isao-dsktp05 systemd[3904]: plasma-kded6.service: Unexpected error response from GetNameOwner(): Connection terminated
Oct 10 14:10:28 isao-dsktp05 systemd[3904]: plasma-kwin_wayland.service: Unexpected error response from GetNameOwner(): Connection terminated
Oct 10 14:10:28 isao-dsktp05 systemd[3904]: kde-baloo.service: Unexpected error response from GetNameOwner(): Connection terminated
I believe the following 3 things fixed the problems:
Unplugging unnecessary USB devices.
Waited out to 6.11.2.
Double reboot cleared up something that was sticking.
Thanks everyone who gave me all the info.
Isao
1 Like
system
13 October 2024 12:41
52
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.