Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #84427 > unrolled thread
| Started by | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| First post | 2024-11-03 09:20 +0100 |
| Last post | 2024-11-09 19:10 +0100 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#1086638: linux-image-6.11.5: usbguard-daemon invalid opcode: 0000, usb's not usable Salvatore Bonaccorso <carnil@debian.org> - 2024-11-03 09:20 +0100
Bug#1086638: linux-image-6.11.5: usbguard-daemon invalid opcode: 0000, usb's not usable Salvatore Bonaccorso <carnil@debian.org> - 2024-11-09 17:00 +0100
Bug#1086638: linux-image-6.11.5: usbguard-daemon invalid opcode: 0000, usb's not usable Matias Fritz <fritzmatias@gmail.com> - 2024-11-09 19:10 +0100
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2024-11-03 09:20 +0100 |
| Subject | Bug#1086638: linux-image-6.11.5: usbguard-daemon invalid opcode: 0000, usb's not usable |
| Message-ID | <JEE01-6j3h-3@gated-at.bofh.it> |
On Sat, Nov 02, 2024 at 03:10:00PM -0300, matias wrote:
> Package: src:linux
> Version: 6.11.5-1
> Severity: critical
> Justification: breaks unrelated software
> X-Debbugs-Cc: fritzmatias@gmail.com
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
> * What led up to the situation?
> USB Mouse not working.
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
> usbguard & usbguard-dbus services looks like active but command
> usbguard list-devices is unresponsive.
> Restarting the services does not change the systemctl status,
> neither does the command to work.
>
> * What was the outcome of this action?
> usbguard list-devices | list-rules, locks unresponsive. Phisical
> USB mouse does not work.
> journal shows 'Device is not authorized for usage'
> * What outcome did you expect instead?
> usbgrub Normal response
> kernel not failure
>
> *** End of the template - remove these template lines ***
>
>
> -- Package-specific info:
> ** Version:
> Linux version 6.11.5-amd64 (debian-kernel@lists.debian.org) (x86_64-linux-gnu-gcc-14 (Debian 14.2.0-7) 14.2.0, GNU ld (GNU Binutils for Debian) 2.43.1) #1 SMP PREEMPT_DYNAMIC Debian 6.11.5-1 (2024-10-27)
>
> ** Command line:
> BOOT_IMAGE=/boot/vmlinuz-6.11.5-amd64 root=UUID=da91cf83-0c65-45cd-aac3-f809dd2a64b7 ro nvidia-drm.modeset=1 quiet
>
> ** Tainted: PDOE (12417)
> * proprietary module was loaded
> * kernel died recently, i.e. there was an OOPS or BUG
> * externally-built ("out-of-tree") module was loaded
> * unsigned module was loaded
>
> ** Kernel log:
> [ 22.043130] CR2: 0000560b839290c0 CR3: 000000018e4a8005 CR4: 0000000000f70ef0
> [ 22.043131] PKRU: 55555554
> [ 22.043132] Call Trace:
> [ 22.043133] <TASK>
> [ 22.043135] ? __die_body.cold+0x19/0x27
> [ 22.043137] ? die+0x2e/0x50
> [ 22.043139] ? do_trap+0xca/0x110
> [ 22.043141] ? do_error_trap+0x6a/0x90
> [ 22.043142] ? __list_del_entry_valid_or_report.cold+0x5c/0x6f
> [ 22.043144] ? exc_invalid_op+0x50/0x70
> [ 22.043146] ? __list_del_entry_valid_or_report.cold+0x5c/0x6f
> [ 22.043147] ? asm_exc_invalid_op+0x1a/0x20
> [ 22.043152] ? __list_del_entry_valid_or_report.cold+0x5c/0x6f
> [ 22.043154] ? __list_del_entry_valid_or_report.cold+0x5c/0x6f
> [ 22.043156] hci_unregister_dev+0x46/0x1f0 [bluetooth]
> [ 22.043183] btusb_disconnect+0x67/0x170 [btusb]
> [ 22.043186] usb_unbind_interface+0x90/0x290 [usbcore]
> [ 22.043220] device_release_driver_internal+0x19c/0x200
> [ 22.043224] bus_remove_device+0xc6/0x130
> [ 22.043225] device_del+0x161/0x3e0
> [ 22.043236] ? kobject_put+0xa0/0x1d0
> [ 22.043238] usb_disable_device+0xf4/0x210 [usbcore]
> [ 22.043249] usb_set_configuration+0x81/0x860 [usbcore]
> [ 22.043258] usb_deauthorize_device+0x3e/0x50 [usbcore]
> [ 22.043267] authorized_store+0x4f/0x90 [usbcore]
> [ 22.043277] kernfs_fop_write_iter+0x13e/0x1f0
> [ 22.043279] vfs_write+0x291/0x460
> [ 22.043282] ksys_write+0x6d/0xf0
> [ 22.043284] do_syscall_64+0x82/0x190
> [ 22.043286] ? do_syscall_64+0x8e/0x190
> [ 22.043287] ? do_syscall_64+0x8e/0x190
> [ 22.043288] ? do_syscall_64+0x8e/0x190
> [ 22.043290] ? clear_bhb_loop+0x25/0x80
> [ 22.043291] ? clear_bhb_loop+0x25/0x80
> [ 22.043292] ? clear_bhb_loop+0x25/0x80
> [ 22.043293] entry_SYSCALL_64_after_hwframe+0x76/0x7e
> [ 22.043307] RIP: 0033:0x7f972b30e24f
> [ 22.043335] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 e9 a1 f8 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 3c a2 f8 ff 48
> [ 22.043336] RSP: 002b:00007ffe63dfbc80 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
> [ 22.043337] RAX: ffffffffffffffda RBX: 00007ffe63dfbf50 RCX: 00007f972b30e24f
> [ 22.043338] RDX: 0000000000000001 RSI: 00007ffe63dfbf60 RDI: 000000000000001a
> [ 22.043339] RBP: 00007ffe63dfbf40 R08: 0000000000000000 R09: 0000000000000000
> [ 22.043340] R10: 0000000000000000 R11: 0000000000000293 R12: 00007ffe63dfbf30
> [ 22.043340] R13: 000000000000001a R14: 000055d5ba310ab0 R15: 000055d5ba310aa0
> [ 22.043342] </TASK>
> [ 22.043342] Modules linked in: xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat bridge stp llc nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c snd_seq_dummy snd_hrtimer snd_seq overlay qrtr bnep uinput nvidia_uvm(POE) sd_mod sg uas usb_storage scsi_mod scsi_common nvidia_drm(POE) btusb btrtl btintel btbcm btmtk bluetooth uvcvideo videobuf2_vmalloc uvc snd_usb_audio videobuf2_memops videobuf2_v4l2 videodev snd_usbmidi_lib snd_rawmidi videobuf2_common snd_seq_device usbhid mc nvidia_modeset(POE) binfmt_misc r8153_ecm cdc_ether usbnet nls_ascii nls_cp437 vfat fat r8152 mii nvidia(POE) joydev intel_uncore_frequency intel_uncore_frequency_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_sof_pci_intel_tgl snd_sof_pci_intel_cnl snd_sof_intel_hda_generic soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda_common kvm snd_sof_intel_hda_mlink snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof
> [ 22.043379] snd_sof_utils snd_soc_hdac_hda snd_soc_acpi_intel_match crct10dif_pclmul crc32_pclmul snd_soc_acpi soundwire_bus ghash_clmulni_intel sha512_ssse3 snd_soc_avs snd_hda_codec_realtek sha256_ssse3 sha1_ssse3 snd_hda_codec_generic snd_soc_hda_codec snd_hda_ext_core snd_hda_scodec_component snd_soc_core snd_hda_codec_hdmi snd_compress snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi aesni_intel snd_hda_codec asus_nb_wmi hid_multitouch gf128mul asus_wmi crypto_simd hid_generic cryptd platform_profile snd_hda_core iTCO_wdt intel_pmc_bxt ee1004 xhci_pci iTCO_vendor_support intel_rapl_msr r8169 watchdog rapl snd_hwdep processor_thermal_device_pci_legacy processor_thermal_device xhci_hcd snd_pcm processor_thermal_wt_hint processor_thermal_rfim realtek intel_cstate ucsi_acpi processor_thermal_rapl mdio_devres intel_rapl_common snd_timer typec_ucsi intel_lpss_pci intel_uncore rfkill wmi_bmof libphy usbcore thunderbolt pcspkr typec mei_hdcp processor_thermal_wt_req snd intel_lpss i2c_i801
> [ 22.043433] processor_thermal_power_floor idma64 soundcore i2c_hid_acpi processor_thermal_mbox roles i2c_smbus usb_common intel_soc_dts_iosf i2c_hid hid button battery int3403_thermal intel_pmc_core int340x_thermal_zone intel_vsec int3400_thermal intel_hid pmt_telemetry acpi_thermal_rel pmt_class acpi_pad ac asus_wireless sparse_keymap msr i2c_dev parport_pc ppdev lp parport nvme_fabrics configfs efi_pstore nfnetlink efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic nvme nvme_core i915 i2c_algo_bit drm_buddy ttm drm_display_helper drm_kms_helper mei_pxp drm mei_me mei cec evdev crc32c_intel serio_raw rc_core vmd fan video wmi
> [ 22.043478] ---[ end trace 0000000000000000 ]---
> [ 22.121721] RIP: 0010:__list_del_entry_valid_or_report.cold+0x5c/0x6f
> [ 22.121727] Code: e8 a8 5f fe ff 0f 0b 48 89 fe 48 89 ca 48 c7 c7 38 38 b4 95 e8 94 5f fe ff 0f 0b 48 89 fe 48 c7 c7 00 38 b4 95 e8 83 5f fe ff <0f> 0b 48 89 fe 48 c7 c7 d0 37 b4 95 e8 72 5f fe ff 0f 0b 4d 8b 4c
> [ 22.121728] RSP: 0018:ffffb3eb83017b58 EFLAGS: 00010246
> [ 22.121730] RAX: 000000000000004e RBX: ffff88e8c7e88000 RCX: 0000000000000000
> [ 22.121732] RDX: 0000000000000000 RSI: ffff88f80b521780 RDI: ffff88f80b521780
> [ 22.121732] RBP: ffff88e8c7e884d0 R08: 0000000000000000 R09: ffffb3eb830179e8
> [ 22.121733] R10: ffffffff962b41e8 R11: 0000000000000003 R12: ffff88e8c7e88000
> [ 22.121734] R13: ffffffffc58e3278 R14: ffffffffc58e3278 R15: ffff88e984720850
> [ 22.121735] FS: 00007f972a6b3ec0(0000) GS:ffff88f80b500000(0000) knlGS:0000000000000000
> [ 22.121736] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 22.121737] CR2: 0000560b839290c0 CR3: 000000018e4a8005 CR4: 0000000000f70ef0
> [ 22.121738] PKRU: 55555554
> [ 22.121739] note: usbguard-daemon[1034] exited with preempt_count 1
> [ 22.238667] usb 3-2: new full-speed USB device number 10 using xhci_hcd
> [ 22.366609] usb 3-2: device descriptor read/64, error -71
> [ 22.625513] usb 3-2: New USB device found, idVendor=0458, idProduct=6001, bcdDevice=10.01
> [ 22.625518] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> [ 22.625519] usb 3-2: Product: Wireless Device
> [ 22.625520] usb 3-2: Manufacturer: Genius
> [ 22.625795] usb 3-2: Device is not authorized for usage
> [ 24.699776] rfkill: input handler enabled
> [ 25.470003] rfkill: input handler disabled
> [ 29.213977] usb 3-2: USB disconnect, device number 10
> [ 34.058519] usb 3-2: new full-speed USB device number 11 using xhci_hcd
> [ 34.186454] usb 3-2: device descriptor read/64, error -71
> [ 34.444717] usb 3-2: New USB device found, idVendor=0458, idProduct=6001, bcdDevice=10.01
> [ 34.444721] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> [ 34.444722] usb 3-2: Product: Wireless Device
> [ 34.444724] usb 3-2: Manufacturer: Genius
> [ 34.445005] usb 3-2: Device is not authorized for usage
> [ 62.686674] usb 3-2: USB disconnect, device number 11
> [ 73.610243] usb 3-2: new full-speed USB device number 12 using xhci_hcd
> [ 73.738257] usb 3-2: device descriptor read/64, error -71
> [ 73.996766] usb 3-2: New USB device found, idVendor=0458, idProduct=6001, bcdDevice=10.01
> [ 73.996769] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> [ 73.996770] usb 3-2: Product: Wireless Device
> [ 73.996771] usb 3-2: Manufacturer: Genius
> [ 73.997031] usb 3-2: Device is not authorized for usage
> [ 198.185792] usb 3-14: USB disconnect, device number 7
> [ 373.344653] systemd-ssh-generator[6184]: Binding SSH to AF_UNIX socket /run/ssh-unix-local/socket.
> [ 373.344656] systemd-ssh-generator[6184]: \xe2\x86\x92 connect via 'ssh .host' locally
> [ 373.346907] systemd-sysv-generator[6187]: SysV service '/etc/init.d/cgroupfs-mount' lacks a native systemd unit file. ~ Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it safe, robust and future-proof. ! This compatibility logic is deprecated, expect removal soon. !
> [ 373.347701] systemd-sysv-generator[6187]: SysV service '/etc/init.d/speech-dispatcher' lacks a native systemd unit file. ~ Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it safe, robust and future-proof. ! This compatibility logic is deprecated, expect removal soon. !
> [ 373.599464] systemd-ssh-generator[6330]: Binding SSH to AF_UNIX socket /run/ssh-unix-local/socket.
> [ 373.599467] systemd-ssh-generator[6330]: \xe2\x86\x92 connect via 'ssh .host' locally
> [ 373.601526] systemd-sysv-generator[6333]: SysV service '/etc/init.d/cgroupfs-mount' lacks a native systemd unit file. ~ Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it safe, robust and future-proof. ! This compatibility logic is deprecated, expect removal soon. !
> [ 373.602300] systemd-sysv-generator[6333]: SysV service '/etc/init.d/speech-dispatcher' lacks a native systemd unit file. ~ Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it safe, robust and future-proof. ! This compatibility logic is deprecated, expect removal soon. !
> [ 373.937692] systemd-ssh-generator[6482]: Binding SSH to AF_UNIX socket /run/ssh-unix-local/socket.
> [ 373.937695] systemd-ssh-generator[6482]: \xe2\x86\x92 connect via 'ssh .host' locally
> [ 373.938837] systemd-sysv-generator[6484]: SysV service '/etc/init.d/cgroupfs-mount' lacks a native systemd unit file. ~ Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it safe, robust and future-proof. ! This compatibility logic is deprecated, expect removal soon. !
> [ 373.939575] systemd-sysv-generator[6484]: SysV service '/etc/init.d/speech-dispatcher' lacks a native systemd unit file. ~ Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it safe, robust and future-proof. ! This compatibility logic is deprecated, expect removal soon. !
The trace looks similar to what is in your earlier reported #1080201
but the log is slightly capped. Can you post the full log?
Regards,
Salvatore
[toc] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2024-11-09 17:00 +0100 |
| Message-ID | <JGW2t-7LSX-3@gated-at.bofh.it> |
| In reply to | #84427 |
Hi Matias, On Sun, Nov 03, 2024 at 07:01:20PM -0300, Matias Fritz wrote: > Hi Salvatore, first thanks for your time. > I' adding some journals with the usbguard error, from different boots just > to let you identify patterns. > In my search I found another one related to the kworker usbcore i think > could help to identify the issue. > > Finally I solved my issue booting with a kernel 6.10.12, where usbguard did > not break at all and was able to handle the allowance for the blocked mouse > and usbs. > I'm adding my dpkg package list and versions just to let you search for > libraries linked to the issue. > > Some things to have in mind. I have a mix of stable,testing and > experimental packages installed in pos to help to test/use some things > prematurely. > Let me know how I can become more useful. > > Best > PD: known error is mt7921e HW which worked fine on kernels 5.15* but does > not on 6.* Thanks for providing those. Now one further step, after we discussed this in the last kernel team meeting, even if the request might be strange at first, you have OOT modules (nvidia) which taint the kernel. Please try to reproduce the issue without those (upstream might reject a report if the kernel is tainted with OOT modules). In fact if it happens, then I would like to ask you to forward it to upstream, but let's first see if it happens *without* the OOT modules. Thanks, Regards, Salvatore
[toc] | [prev] | [next] | [standalone]
| From | Matias Fritz <fritzmatias@gmail.com> |
|---|---|
| Date | 2024-11-09 19:10 +0100 |
| Message-ID | <JGY4h-7NjT-9@gated-at.bofh.it> |
| In reply to | #84476 |
[Multipart message — attachments visible in raw view] — view raw
Hi Salvatore, sure I can run any test to help, but given I had fixed my original issue, first let's agree on how to prepare the environment to try to reproduce the original scenario and test it. 1 - Rollback fixes: This means block the devices previously allowed via usbguard. (I could try to do it with the 6.11.5 and see if it lock) or do it with kernel 6.10.12 which allowed me to fix it originally. Another change i should do, are some new udev rules added on my machine to avoid the mt7921e wifi be suspended. Details at ( https://github.com/fritzmatias/fritzmatias/blob/main/linux/kernel/mt7921e.md ) 2- Then try to reproduce the kernel crash running the 'usbguard list-devices' with kernel 6.11.5 as originally. (what to do if does not :O). 3- if step 2 is reproducible, Add mt7921e udev rules, and run 'usbguard list-devices'. This could validate my guess. 4- remove mt7921e udev rules. 5- If step 2 is confirmed, then uninstall OOT nvidia drivers. And run 'usbguard list-devices' with kernel 6.11.5. 6- independently of step 5's output. Install nvidia open kernel 545, and run 'usbguard list-devices' with kernel 6.11.5, to confirm/deny similarities as step 2. Let me know if that procedure is good enough or if you can improve it. My speculative guess, is related to the buggy hw mt7921e (wifi & bluetooth): when it fails because of a suspension call, the usb core locks, unable to handle that scenario. Open to suggestions Thanks in advance.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web