* Fwd: Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed to send headers (or body or access otp area)
@ 2023-08-18 10:16 Bagas Sanjaya
2023-08-21 5:02 ` Kalle Valo
0 siblings, 1 reply; 5+ messages in thread
From: Bagas Sanjaya @ 2023-08-18 10:16 UTC (permalink / raw)
To: Kalle Valo, Jeff Johnson, François Armand
Cc: Linux Kernel Mailing List, Linux ath11k, Linux Bluetooth
Hi,
I notice a bug report on Bugzilla [1]. Quoting from it:
> Hello,
>
> (Sorry by advance if it's not the correct place to discuss that, but I tried other place like my distro kernel forum (https://bbs.archlinux.org/viewtopic.php?id=286929), interactive chat, etc and nobody was able to help).
>
> [1] == Short summary ==
>
> I have a lenovo T14S AMD Gen 3 with a *Qualcomm NFA725A* Wi-Fi card (which is actually reported by lspci as QCNFA765) and bluetooth never worked on it, failing to load the rampatch with "failed to send header" or "failed to send body" or "Failed to access otp area (-71)".
>
> Other people reports bluetooth as working (https://wiki.archlinux.org/title/Lenovo_ThinkPad_T14s_(AMD)_Gen_3) and a work friend has a T16 AMD gen1 which seems to have exactly the same chipset and work flowlessly. So perhaps it's an hardware issue, but I don't know how to qualify it if so.
>
> => How can this be further qualified/debuged/workarounded?
>
> Any help, even RTFM pointing to corresponding manuals would be very much appreciated.
>
>
> [2] == logs and more details ==
>
> I have that laptop since october 2022 and use archlinux with the standard kernels. None made bluetooth wroked since then. First install was around linux 6.0.10 and current kernel: 6.4.10-arch1-10.
>
> There is nothing obvious in bios setting that could lead to that (bluetooth is enabled).
>
> # LSPCI
>
> lspci -k -s 01:00.0
> 01:00.0 Network controller: Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter (rev 01)
> Subsystem: Lenovo QCNFA765 Wireless Network Adapter
> Kernel driver in use: ath11k_pci
> Kernel modules: ath11k_pci
>
>
> # kernel boot log: "Failed to send headers (-71)"
>
> kernel: thinkpad_acpi: radio switch found; radios are enabled
> kernel: thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
> kernel: thinkpad_acpi: Disabling thinkpad-acpi brightness events by default
> ...
> kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
> ...
> rfkill[6774]: unblock set for type bluetooth sudo[6773]: pam_unix(sudo:session): session closed for user root
> kernel: usb 1-3.1: new full-speed USB device number 3 using xhci_hcd
> kernel: usb 1-3.1: New USB device found, idVendor=10ab, idProduct=9309, bcdDevice= 0.01 kernel: usb 1-3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 boltd[935]: probing: started [1000]
> kernel: Bluetooth: Core ver 2.22 kernel: NET: Registered PF_BLUETOOTH protocol family kernel: Bluetooth: HCI device and connection manager initialized
> kernel: Bluetooth: HCI socket layer initialized kernel: Bluetooth: L2CAP socket layer initialized
> kernel: Bluetooth: SCO socket layer initialized kernel: usbcore: registered new interface driver btusb
> systemd[1328]: Reached target Bluetooth.
> kernel: Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00130201.bin
> kernel: Bluetooth: hci0: QCA: patch rome 0x130201 build 0x5073, firmware rome 0x130201 build 0x38e6
> kernel: Bluetooth: hci0: Failed to send headers (-71)
> systemd[1]: Starting Bluetooth service...
> bluetoothd[6866]: Bluetooth daemon 5.66
> systemd[1]: Started Bluetooth service.
> systemd[1]: Reached target Bluetooth Support.
> bluetoothd[6866]: Starting SDP server bluetoothd[6866]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
>
> # rfkill status
>
> sudo rfkill
> ID TYPE DEVICE SOFT HARD
> 0 bluetooth tpacpi_bluetooth_sw blocked unblocked
> 1 wlan phy0 unblocked unblocked
>
> # when trying to unlock: "failed to send body at 40 of 142192 (-71)"
>
> rfkill[105640]: unblock set for type bluetooth
> sudo[105639]: pam_unix(sudo:session): session closed for user root
> kernel: usb 1-3.1: new full-speed USB device number 4 using xhci_hcd
> kernel: usb 1-3.1: New USB device found, idVendor=10ab, idProduct=9309, bcdDevice= 0.01
> kernel: usb 1-3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> kernel: Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00130201.bin
> kernel: Bluetooth: hci0: QCA: patch rome 0x130201 build 0x5073, firmware rome 0x130201 build 0x38e6
> kernel: Bluetooth: hci0: Failed to send body at 40 of 142192 (-71)
> kernel: usb 1-3.1: USB disconnect, device number 4
> boltd[935]: probing: started [1000]
> systemd[1328]: Reached target Bluetooth.
> systemd[1328]: Stopped target Bluetooth.
> systemd[1]: Reached target Bluetooth Support.
> systemd[1]: Stopped target Bluetooth Support.
>
> # unloading and loading back kernel related modules (`bluetooth`, `btusb`, etc) and modprobe them back, and I get the same kind of logs after `rfkill unblock bluetoot`:
>
> rfkill[106483]: unblock set for type bluetooth
> sudo[106482]: pam_unix(sudo:session): session closed for user root
> kernel: usb 1-3.1: new full-speed USB device number 5 using xhci_hcd
> kernel: usb 1-3.1: New USB device found, idVendor=10ab, idProduct=9309, bcdDevice= 0.01
> kernel: usb 1-3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> kernel: usb 1-3.1: Failed to access otp area (-71)
> kernel: usb 1-3.1: USB disconnect, device number 5
> boltd[935]: probing: started [1000]
> systemd[1328]: Reached target Bluetooth.
> systemd[1]: Reached target Bluetooth Support.
> systemd[1328]: Stopped target Bluetooth.
> systemd[1]: Stopped target Bluetooth Support.
> boltd[935]: probing: timeout, done: [3001068] (2000000)
>
> Have a nice day
See Bugzilla for the full thread.
FYI, this is a duplicate of his earlier report [2] that had not seen
any replies. I have added ath11k maintainers to the recipient list
so that this bug can be hopefully addressed.
Thanks.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217805
[2]: https://lore.kernel.org/all/977f687e-533f-ebce-a50c-2dde1e1adb99@gmail.com/
--
An old man doll... just what I always wanted! - Clara
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: Fwd: Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed to send headers (or body or access otp area) 2023-08-18 10:16 Fwd: Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed to send headers (or body or access otp area) Bagas Sanjaya @ 2023-08-21 5:02 ` Kalle Valo 2023-08-22 8:21 ` Bagas Sanjaya 0 siblings, 1 reply; 5+ messages in thread From: Kalle Valo @ 2023-08-21 5:02 UTC (permalink / raw) To: Bagas Sanjaya Cc: Jeff Johnson, François Armand, Linux Kernel Mailing List, Linux ath11k, Linux Bluetooth Bagas Sanjaya <bagasdotme@gmail.com> writes: > Hi, > > I notice a bug report on Bugzilla [1]. Quoting from it: > >> Hello, >> >> (Sorry by advance if it's not the correct place to discuss that, but >> I tried other place like my distro kernel forum >> (https://bbs.archlinux.org/viewtopic.php?id=286929), interactive >> chat, etc and nobody was able to help). >> >> [1] == Short summary == >> >> I have a lenovo T14S AMD Gen 3 with a *Qualcomm NFA725A* Wi-Fi card >> (which is actually reported by lspci as QCNFA765) and bluetooth >> never worked on it, failing to load the rampatch with "failed to >> send header" or "failed to send body" or "Failed to access otp area >> (-71)". >> >> Other people reports bluetooth as working >> (https://wiki.archlinux.org/title/Lenovo_ThinkPad_T14s_(AMD)_Gen_3) >> and a work friend has a T16 AMD gen1 which seems to have exactly the >> same chipset and work flowlessly. So perhaps it's an hardware issue, >> but I don't know how to qualify it if so. >> >> => How can this be further qualified/debuged/workarounded? >> >> Any help, even RTFM pointing to corresponding manuals would be very >> much appreciated. This looks like a bluetooth bug so not related to ath11k (which is a Wi-Fi driver). -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Fwd: Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed to send headers (or body or access otp area) 2023-08-21 5:02 ` Kalle Valo @ 2023-08-22 8:21 ` Bagas Sanjaya 2023-08-22 13:01 ` Kalle Valo 2023-08-28 7:08 ` François 0 siblings, 2 replies; 5+ messages in thread From: Bagas Sanjaya @ 2023-08-22 8:21 UTC (permalink / raw) To: Kalle Valo Cc: Jeff Johnson, François Armand, Linux Kernel Mailing List, Linux ath11k, Linux Bluetooth, Marcel Holtmann, Johan Hedberg, Luiz Augusto von Dentz On 21/08/2023 12:02, Kalle Valo wrote: > Bagas Sanjaya <bagasdotme@gmail.com> writes: > >> Hi, >> >> I notice a bug report on Bugzilla [1]. Quoting from it: >> >>> Hello, >>> >>> (Sorry by advance if it's not the correct place to discuss that, but >>> I tried other place like my distro kernel forum >>> (https://bbs.archlinux.org/viewtopic.php?id=286929), interactive >>> chat, etc and nobody was able to help). >>> >>> [1] == Short summary == >>> >>> I have a lenovo T14S AMD Gen 3 with a *Qualcomm NFA725A* Wi-Fi card >>> (which is actually reported by lspci as QCNFA765) and bluetooth >>> never worked on it, failing to load the rampatch with "failed to >>> send header" or "failed to send body" or "Failed to access otp area >>> (-71)". >>> >>> Other people reports bluetooth as working >>> (https://wiki.archlinux.org/title/Lenovo_ThinkPad_T14s_(AMD)_Gen_3) >>> and a work friend has a T16 AMD gen1 which seems to have exactly the >>> same chipset and work flowlessly. So perhaps it's an hardware issue, >>> but I don't know how to qualify it if so. >>> >>> => How can this be further qualified/debuged/workarounded? >>> >>> Any help, even RTFM pointing to corresponding manuals would be very >>> much appreciated. > > This looks like a bluetooth bug so not related to ath11k (which is a > Wi-Fi driver). > Oops, I really can't guess which driver is the culprit in this case unless the reporter also attaches lsmod output. To François: Can you show lsmod list as requested? Also Cc: bluetooth people. -- An old man doll... just what I always wanted! - Clara ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Fwd: Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed to send headers (or body or access otp area) 2023-08-22 8:21 ` Bagas Sanjaya @ 2023-08-22 13:01 ` Kalle Valo 2023-08-28 7:08 ` François 1 sibling, 0 replies; 5+ messages in thread From: Kalle Valo @ 2023-08-22 13:01 UTC (permalink / raw) To: Bagas Sanjaya Cc: Jeff Johnson, François Armand, Linux Kernel Mailing List, Linux ath11k, Linux Bluetooth, Marcel Holtmann, Johan Hedberg, Luiz Augusto von Dentz Bagas Sanjaya <bagasdotme@gmail.com> writes: > On 21/08/2023 12:02, Kalle Valo wrote: >> Bagas Sanjaya <bagasdotme@gmail.com> writes: >> >>> Hi, >>> >>> I notice a bug report on Bugzilla [1]. Quoting from it: >>> >>>> Hello, >>>> >>>> (Sorry by advance if it's not the correct place to discuss that, but >>>> I tried other place like my distro kernel forum >>>> (https://bbs.archlinux.org/viewtopic.php?id=286929), interactive >>>> chat, etc and nobody was able to help). >>>> >>>> [1] == Short summary == >>>> >>>> I have a lenovo T14S AMD Gen 3 with a *Qualcomm NFA725A* Wi-Fi card >>>> (which is actually reported by lspci as QCNFA765) and bluetooth >>>> never worked on it, failing to load the rampatch with "failed to >>>> send header" or "failed to send body" or "Failed to access otp area >>>> (-71)". >>>> >>>> Other people reports bluetooth as working >>>> (https://wiki.archlinux.org/title/Lenovo_ThinkPad_T14s_(AMD)_Gen_3) >>>> and a work friend has a T16 AMD gen1 which seems to have exactly the >>>> same chipset and work flowlessly. So perhaps it's an hardware issue, >>>> but I don't know how to qualify it if so. >>>> >>>> => How can this be further qualified/debuged/workarounded? >>>> >>>> Any help, even RTFM pointing to corresponding manuals would be very >>>> much appreciated. >> >> This looks like a bluetooth bug so not related to ath11k (which is a >> Wi-Fi driver). >> > > Oops, I really can't guess which driver is the culprit in this case unless > the reporter also attaches lsmod output. No worries, it's understandable that it's not always clear where the problem is. And most likely the reporter also has ath11k driver loaded as the same chip has both Wi-Fi and Bluetooth functionality. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Fwd: Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed to send headers (or body or access otp area) 2023-08-22 8:21 ` Bagas Sanjaya 2023-08-22 13:01 ` Kalle Valo @ 2023-08-28 7:08 ` François 1 sibling, 0 replies; 5+ messages in thread From: François @ 2023-08-28 7:08 UTC (permalink / raw) To: Bagas Sanjaya, Kalle Valo Cc: Jeff Johnson, Linux Kernel Mailing List, Linux ath11k, Linux Bluetooth, Marcel Holtmann, Johan Hedberg, Luiz Augusto von Dentz On 22/08/2023 10:21, Bagas Sanjaya wrote: > On 21/08/2023 12:02, Kalle Valo wrote: >> Bagas Sanjaya <bagasdotme@gmail.com> writes: >> >>> Hi, >>> >>> I notice a bug report on Bugzilla [1]. Quoting from it: >>> >>>> Hello, >>>> >>>> (Sorry by advance if it's not the correct place to discuss that, but >>>> I tried other place like my distro kernel forum >>>> (https://bbs.archlinux.org/viewtopic.php?id=286929), interactive >>>> chat, etc and nobody was able to help). >>>> >>>> [1] == Short summary == >>>> >>>> I have a lenovo T14S AMD Gen 3 with a *Qualcomm NFA725A* Wi-Fi card >>>> (which is actually reported by lspci as QCNFA765) and bluetooth >>>> never worked on it, failing to load the rampatch with "failed to >>>> send header" or "failed to send body" or "Failed to access otp area >>>> (-71)". >>>> >>>> Other people reports bluetooth as working >>>> (https://wiki.archlinux.org/title/Lenovo_ThinkPad_T14s_(AMD)_Gen_3) >>>> and a work friend has a T16 AMD gen1 which seems to have exactly the >>>> same chipset and work flowlessly. So perhaps it's an hardware issue, >>>> but I don't know how to qualify it if so. >>>> >>>> => How can this be further qualified/debuged/workarounded? >>>> >>>> Any help, even RTFM pointing to corresponding manuals would be very >>>> much appreciated. >> This looks like a bluetooth bug so not related to ath11k (which is a >> Wi-Fi driver). >> > Oops, I really can't guess which driver is the culprit in this case unless > the reporter also attaches lsmod output. To François: Can you show > lsmod list as requested? > > Also Cc: bluetooth people. Very sorry, I was AFK for a couple of days and totaly missed the request. # lsmod, just the ath11k part: ❯ lsmod | grep -i ath ath11k_pci 24576 0 ath11k 749568 1 ath11k_pci qmi_helpers 36864 1 ath11k mac80211 1527808 1 ath11k cfg80211 1286144 2 ath11k,mac80211 mhi 110592 2 ath11k_pci,qrtr_mhi # lsmod, just btusb ❯ lsmod | grep -i btusb btusb 81920 0 btrtl 28672 1 btusb btbcm 24576 1 btusb btintel 53248 1 btusb btmtk 12288 1 btusb bluetooth 1093632 14 btrtl,btmtk,btintel,btbcm,bnep,btusb # lsmod everything ❯ lsmod Module Size Used by bnep 36864 2 btusb 81920 0 btrtl 28672 1 btusb btbcm 24576 1 btusb btintel 53248 1 btusb btmtk 12288 1 btusb bluetooth 1093632 14 btrtl,btmtk,btintel,btbcm,bnep,btusb ecdh_generic 16384 1 bluetooth hid_logitech_hidpp 77824 0 hid_logitech_dj 40960 0 hid_jabra 16384 0 snd_usb_audio 438272 0 snd_usbmidi_lib 49152 1 snd_usb_audio snd_rawmidi 53248 1 snd_usbmidi_lib usbhid 77824 2 hid_logitech_dj,hid_logitech_hidpp tun 69632 2 snd_seq_dummy 12288 0 snd_hrtimer 12288 1 snd_seq 106496 7 snd_seq_dummy snd_seq_device 16384 2 snd_seq,snd_rawmidi ccm 20480 6 michael_mic 12288 1 qrtr_mhi 16384 0 iptable_nat 12288 0 nf_nat 61440 1 iptable_nat nf_conntrack 200704 1 nf_nat nf_defrag_ipv6 24576 1 nf_conntrack nf_defrag_ipv4 12288 1 nf_conntrack iptable_mangle 12288 0 iptable_filter 12288 0 uvcvideo 176128 0 videobuf2_vmalloc 20480 1 uvcvideo uvc 12288 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 40960 1 uvcvideo videodev 372736 2 videobuf2_v4l2,uvcvideo videobuf2_common 86016 4 videobuf2_vmalloc,videobuf2_v4l2,uvcvideo,videobuf2_memops mc 86016 5 videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common snd_acp6x_pdm_dma 16384 1 snd_soc_acp6x_mach 24576 4 snd_soc_dmic 12288 1 snd_sof_amd_rembrandt 16384 0 snd_sof_amd_renoir 16384 0 ext4 1150976 1 snd_sof_amd_acp 57344 2 snd_sof_amd_rembrandt,snd_sof_amd_renoir snd_sof_pci 24576 2 snd_sof_amd_rembrandt,snd_sof_amd_renoir snd_sof_xtensa_dsp 16384 1 snd_sof_amd_acp qrtr 57344 5 qrtr_mhi crc16 12288 2 bluetooth,ext4 snd_sof 409600 2 snd_sof_amd_acp,snd_sof_pci mbcache 16384 1 ext4 joydev 24576 0 ath11k_pci 24576 0 snd_sof_utils 16384 1 snd_sof mousedev 24576 0 jbd2 208896 1 ext4 ath11k 749568 1 ath11k_pci snd_soc_core 438272 4 snd_soc_acp6x_mach,snd_sof,snd_acp6x_pdm_dma,snd_soc_dmic snd_ctl_led 24576 0 snd_compress 28672 1 snd_soc_core intel_rapl_msr 20480 0 qmi_helpers 36864 1 ath11k ac97_bus 12288 1 snd_soc_core snd_hda_codec_realtek 192512 1 snd_pcm_dmaengine 16384 1 snd_soc_core intel_rapl_common 36864 1 intel_rapl_msr snd_hda_codec_generic 110592 1 snd_hda_codec_realtek snd_hda_codec_hdmi 94208 1 snd_pci_ps 20480 0 mac80211 1527808 1 ath11k edac_mce_amd 53248 0 snd_rpl_pci_acp6x 16384 0 snd_acp_pci 12288 0 snd_hda_intel 61440 10 snd_pci_acp6x 20480 0 snd_intel_dspcfg 32768 2 snd_hda_intel,snd_sof kvm_amd 204800 0 snd_pci_acp5x 16384 0 snd_intel_sdw_acpi 16384 1 snd_intel_dspcfg libarc4 12288 1 mac80211 snd_hda_codec 212992 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek kvm 1318912 1 kvm_amd ucsi_acpi 12288 0 hid_multitouch 32768 0 snd_rn_pci_acp3x 24576 0 cfg80211 1286144 2 ath11k,mac80211 snd_hda_core 139264 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_acp_config 16384 6 snd_rn_pci_acp3x,snd_pci_acp6x,snd_sof_amd_rembrandt,snd_acp_pci,snd_pci_ps,snd_sof_amd_renoir think_lmi 36864 0 typec_ucsi 61440 1 ucsi_acpi irqbypass 12288 1 kvm snd_soc_acpi 12288 2 snd_sof_amd_acp,snd_acp_config sp5100_tco 20480 0 snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec rapl 20480 0 psmouse 233472 0 typec 106496 1 typec_ucsi acpi_cpufreq 32768 0 firmware_attributes_class 12288 1 think_lmi wmi_bmof 12288 0 k10temp 16384 0 thunderbolt 495616 0 snd_pcm 196608 14 snd_sof_amd_acp,snd_hda_codec_hdmi,snd_pci_acp6x,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_sof,snd_acp6x_pdm_dma,snd_compress,snd_soc_core,snd_sof_utils,snd_hda_core,snd_pci_ps,snd_pcm_dmaengine snd_pci_acp3x 16384 0 i2c_piix4 32768 0 snd_timer 53248 3 snd_seq,snd_hrtimer,snd_pcm mhi 110592 2 ath11k_pci,qrtr_mhi roles 16384 1 typec_ucsi i2c_hid_acpi 12288 0 i2c_hid 40960 1 i2c_hid_acpi amd_pmc 36864 0 acpi_tad 20480 0 mac_hid 12288 0 vboxnetflt 40960 1 vboxnetadp 28672 0 vboxdrv 651264 4 vboxnetadp,vboxnetflt vfat 20480 1 fat 102400 1 vfat pkcs8_key_parser 12288 0 crypto_user 20480 0 fuse 204800 5 loop 40960 0 bpf_preload 20480 0 ip_tables 36864 3 iptable_filter,iptable_nat,iptable_mangle x_tables 61440 4 iptable_filter,ip_tables,iptable_nat,iptable_mangle btrfs 2035712 1 blake2b_generic 24576 0 libcrc32c 12288 3 nf_conntrack,nf_nat,btrfs crc32c_generic 12288 0 xor 20480 1 btrfs raid6_pq 122880 1 btrfs dm_crypt 65536 1 cbc 12288 0 encrypted_keys 28672 1 dm_crypt trusted 53248 2 encrypted_keys,dm_crypt asn1_encoder 12288 1 trusted tee 45056 1 trusted dm_mod 217088 3 dm_crypt serio_raw 16384 0 atkbd 40960 0 crct10dif_pclmul 12288 1 libps2 20480 2 atkbd,psmouse crc32_pclmul 12288 0 vivaldi_fmap 12288 1 atkbd crc32c_intel 16384 4 polyval_clmulni 12288 0 polyval_generic 12288 1 polyval_clmulni gf128mul 16384 1 polyval_generic nvme 65536 4 ghash_clmulni_intel 16384 0 sha512_ssse3 45056 0 thinkpad_acpi 200704 0 aesni_intel 360448 6 snd 147456 48 snd_ctl_led,snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_sof,snd_timer,snd_compress,thinkpad_acpi,snd_soc_core,snd_pcm,snd_rawmidi crypto_simd 16384 1 aesni_intel cryptd 28672 3 crypto_simd,ghash_clmulni_intel soundcore 16384 2 snd_ctl_led,snd xhci_pci 28672 0 nvme_core 237568 6 nvme ledtrig_audio 12288 3 snd_ctl_led,snd_hda_codec_generic,thinkpad_acpi ccp 155648 1 kvm_amd xhci_pci_renesas 24576 1 xhci_pci platform_profile 12288 1 thinkpad_acpi nvme_common 20480 1 nvme_core i8042 53248 0 rfkill 40960 6 bluetooth,thinkpad_acpi,cfg80211 serio 28672 7 amd_pmc,serio_raw,atkbd,psmouse,i8042 amdgpu 11882496 67 i2c_algo_bit 20480 1 amdgpu drm_ttm_helper 12288 1 amdgpu ttm 98304 2 amdgpu,drm_ttm_helper video 77824 2 thinkpad_acpi,amdgpu wmi 45056 3 video,wmi_bmof,think_lmi drm_suballoc_helper 12288 1 amdgpu drm_buddy 20480 1 amdgpu gpu_sched 53248 1 amdgpu drm_display_helper 204800 1 amdgpu cec 86016 1 drm_display_helper -- François ARMAND ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-08-28 7:09 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2023-08-18 10:16 Fwd: Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed to send headers (or body or access otp area) Bagas Sanjaya 2023-08-21 5:02 ` Kalle Valo 2023-08-22 8:21 ` Bagas Sanjaya 2023-08-22 13:01 ` Kalle Valo 2023-08-28 7:08 ` François
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox