From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 218416] hci0: command 0xfc05 tx timeout in kernel 6.7.1
Date: Thu, 04 Apr 2024 22:50:41 +0000 [thread overview]
Message-ID: <bug-218416-62941-A43KFKJBGv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218416-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218416
Robert Holt (robert@robertholt.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |robert@robertholt.net
--- Comment #17 from Robert Holt (robert@robertholt.net) ---
(In reply to Luiz Von Dentz from comment #16)
> Can you guys try with the following change:
>
> https://patchwork.kernel.org/project/bluetooth/patch/20240401193515.2525201-
> 1-luiz.dentz@gmail.com/
I have the same issue and applied this patch to my kernel, but it seems to have
broken the btintel module. I get a null pointer deref on boot and bluetooth is
broken:
[ 2.317366] BUG: kernel NULL pointer dereference, address: 0000000000000070
[ 2.317699] #PF: supervisor read access in kernel mode
[ 2.317993] #PF: error_code(0x0000) - not-present page
[ 2.318280] PGD 0 P4D 0
[ 2.318283] Oops: 0000 [#1] PREEMPT SMP NOPTI
[ 2.318842] CPU: 3 PID: 185 Comm: kworker/u33:0 Not tainted
6.8.3-gentoo-dist #1
[ 2.318844] Hardware name: AZW SER/SER, BIOS SER7PRO_P5C8V30 09/15/2023
[ 2.318845] Workqueue: hci0 hci_alloc_dev_priv [bluetooth]
[ 2.319426] RIP: 0010:btintel_configure_setup+0x245/0x970 [btintel]
[ 2.320365] Code: 85 ff 75 a1 f0 41 80 8e 51 06 00 00 02 f0 41 80 8e 51 06
00 00 04 f0 41 80 8e 51 06 00 00 08 49 c7 86 38 17 00 00 b0 63 66 c1 <83> 7b 70
0a 75 7b 48 8b 83 d0 00 00 00 80 78 01 37 75 6e 0f 1f 44
[ 2.320691] RSP: 0018:ffffa215005cfd48 EFLAGS: 00010202
[ 2.321452] RAX: 0000000000000000 RBX: 0000000000000000 RCX:
0000000080200006
[ 2.321760] RDX: 0000000080200007 RSI: ffffd3238404d700 RDI:
0000000000000000
[ 2.322437] RBP: ffff91a940ccc6c8 R08: 0000000080200007 R09:
0000000080200006
[ 2.322438] R10: 0000000000000001 R11: 0000000000000000 R12:
ffff91a940ccc6d0
[ 2.322439] R13: ffff91a947f50c00 R14: ffff91a940ccc000 R15:
ffff91a940ccca88
[ 2.322441] FS: 0000000000000000(0000) GS:ffff91af820c0000(0000)
knlGS:0000000000000000
[ 2.323737] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2.323739] CR2: 0000000000000070 CR3: 000000010dfa2000 CR4:
0000000000f50ef0
[ 2.323740] PKRU: 55555554
[ 2.323740] Call Trace:
[ 2.323743] <TASK>
[ 2.326248] ? __die_body+0x68/0xb0
[ 2.326253] ? page_fault_oops+0x3a3/0x400
[ 2.326256] ? exc_page_fault+0x60/0xf0
[ 2.326265] ? asm_exc_page_fault+0x26/0x30
[ 2.326269] ? btintel_configure_setup+0x245/0x970 [btintel]
[ 2.328091] ? btintel_configure_setup+0x16c/0x970 [btintel]
[ 2.328093] ? __ia32_compat_sys_sysinfo+0x230/0x270
[ 2.329006] hci_dev_open_sync+0x166/0x1610 [bluetooth]
[ 2.329013] ? srso_alias_return_thunk+0x5/0xfbef5
[ 2.329015] ? srso_alias_return_thunk+0x5/0xfbef5
[ 2.329016] ? srso_alias_return_thunk+0x5/0xfbef5
[ 2.329018] hci_alloc_dev_priv+0x164e/0x1bc0 [bluetooth]
[ 2.329023] process_scheduled_works+0x24b/0x450
[ 2.329026] worker_thread+0x2c3/0x420
[ 2.329028] ? __pfx_worker_thread+0x10/0x10
[ 2.329030] kthread+0xe8/0x110
[ 2.329032] ? __pfx_kthread+0x10/0x10
[ 2.329033] ret_from_fork+0x37/0x50
[ 2.329036] ? __pfx_kthread+0x10/0x10
[ 2.329038] ret_from_fork_asm+0x1b/0x30
[ 2.329043] </TASK>
[ 2.329043] Modules linked in: amdxcp(+) ac97_bus(+) iwlwifi(+)
snd_hda_codec(+) btusb snd_pcm_dmaengine gpu_sched vfat btbcm snd_pci_ps
drm_suballoc_helper btintel i2c_algo_bit fat snd_rpl_pci_acp6x kvm(+)
drm_ttm_helper snd_hda_core snd_acp_pci btrtl ttm snd_acp_legacy_common btmtk
snd_pci_acp6x irqbypass drm_exec snd_hwdep snd_pci_acp5x snd_pcm
drm_display_helper bluetooth snd_rn_pci_acp3x wmi_bmof cfg80211 snd_timer
snd_acp_config rapl cec snd_soc_acpi snd pcspkr drm_buddy soundcore i2c_piix4
k10temp snd_pci_acp3x rfkill amd_pmc fuse loop nfnetlink crct10dif_pclmul
crc32_pclmul crc32c_intel nvme polyval_clmulni polyval_generic
ghash_clmulni_intel thunderbolt sha512_ssse3 sha256_ssse3 sha1_ssse3 nvme_core
amd_sfh ccp sp5100_tco r8169 nvme_auth realtek video wmi i2c_hid_acpi i2c_hid
serio_raw
[ 2.329083] CR2: 0000000000000070
[ 2.329085] ---[ end trace 0000000000000000 ]---
[ 2.329087] RIP: 0010:btintel_configure_setup+0x245/0x970 [btintel]
[ 2.329089] Code: 85 ff 75 a1 f0 41 80 8e 51 06 00 00 02 f0 41 80 8e 51 06
00 00 04 f0 41 80 8e 51 06 00 00 08 49 c7 86 38 17 00 00 b0 63 66 c1 <83> 7b 70
0a 75 7b 48 8b 83 d0 00 00 00 80 78 01 37 75 6e 0f 1f 44
[ 2.329090] RSP: 0018:ffffa215005cfd48 EFLAGS: 00010202
[ 2.329091] RAX: 0000000000000000 RBX: 0000000000000000 RCX:
0000000080200006
[ 2.329092] RDX: 0000000080200007 RSI: ffffd3238404d700 RDI:
0000000000000000
[ 2.329093] RBP: ffff91a940ccc6c8 R08: 0000000080200007 R09:
0000000080200006
[ 2.329093] R10: 0000000000000001 R11: 0000000000000000 R12:
ffff91a940ccc6d0
[ 2.329094] R13: ffff91a947f50c00 R14: ffff91a940ccc000 R15:
ffff91a940ccca88
[ 2.329095] FS: 0000000000000000(0000) GS:ffff91af820c0000(0000)
knlGS:0000000000000000
[ 2.329096] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2.329096] CR2: 0000000000000070 CR3: 000000010dfa2000 CR4:
0000000000f50ef0
[ 2.329097] PKRU: 55555554
[ 2.329098] note: kworker/u33:0[185] exited with irqs disabled
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-04-04 22:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 14:29 [Bug 218416] New: hci0: command 0xfc05 tx timeout in kernel 6.7.1 bugzilla-daemon
2024-01-24 23:39 ` [Bug 218416] " bugzilla-daemon
2024-01-30 14:21 ` bugzilla-daemon
2024-01-30 17:05 ` bugzilla-daemon
2024-02-04 10:31 ` bugzilla-daemon
2024-02-10 23:07 ` bugzilla-daemon
2024-02-11 20:32 ` bugzilla-daemon
2024-02-15 20:43 ` bugzilla-daemon
2024-03-09 16:52 ` bugzilla-daemon
2024-03-25 9:38 ` bugzilla-daemon
2024-03-29 8:52 ` bugzilla-daemon
2024-03-29 16:16 ` bugzilla-daemon
2024-03-29 18:31 ` bugzilla-daemon
2024-03-29 18:33 ` bugzilla-daemon
2024-03-29 20:02 ` bugzilla-daemon
2024-03-30 13:44 ` bugzilla-daemon
2024-04-03 12:32 ` bugzilla-daemon
2024-04-03 18:28 ` bugzilla-daemon
2024-04-04 22:50 ` bugzilla-daemon [this message]
2024-04-09 12:18 ` bugzilla-daemon
2024-04-09 13:04 ` bugzilla-daemon
2024-04-09 13:45 ` bugzilla-daemon
2024-04-09 13:46 ` bugzilla-daemon
2024-04-09 14:31 ` bugzilla-daemon
2024-04-09 15:12 ` bugzilla-daemon
2024-04-09 19:57 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-218416-62941-A43KFKJBGv@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.