From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 203535] Bluetooth: command tx timeout with Intel Corporation Wireless 7260 in A2DP mode
Date: Sat, 03 Oct 2020 08:28:24 +0000 [thread overview]
Message-ID: <bug-203535-62941-b1o6voXS7l@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203535-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203535
A. M. (de99like@mennucci.debian.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |de99like@mennucci.debian.ne
| |t
--- Comment #6 from A. M. (de99like@mennucci.debian.net) ---
hi
I have the same problem with a different chipset 8087:0029
I also got a kernel backtrace
kernel: kobject_add_internal failed for hci0:256 with -EEXIST, don't try to
register things with the same name in the same directory.
kernel: Bluetooth: hci0: failed to register connection device
kernel: Bluetooth: hci0: link tx timeout
kernel: Bluetooth: hci0: killing stalled connection 75:ab:d6:65:ea:56
kernel: BUG: unable to handle kernel NULL pointer dereference at
0000000000000020
kernel: IP: klist_next+0x1c/0x100
kernel: PGD 0 P4D 0
kernel: Oops: 0000 [#1] SMP NOPTI
kernel: Modules linked in: rfcomm pci_stub vboxpci(OE) vboxnetadp(OE)
vboxnetflt(OE) vboxdrv(OE) ccm cmac bnep binfmt_misc dm_crypt algif_skcipher
af_alg cdc_ether usbnet r8152 mii uvcvideo videobuf2_vmalloc videobuf2_memops
btusb videobuf2_v4l2 btrtl btbcm videobuf2_core btintel videodev bluetooth
media ecdh_generic snd_hda_codec_hdmi snd_hda_codec_realtek
snd_hda_codec_generic hid_multitouch arc4 dell_laptop intel_rapl
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm nls_iso8859_1
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_intel
aesni_intel snd_hda_codec aes_x86_64 snd_hda_core crypto_simd glue_helper
snd_hwdep cryptd intel_cstate snd_pcm intel_rapl_perf iwlmvm(OE) snd_seq_midi
snd_seq_midi_event dell_wmi mac80211(OE) joydev input_leds dell_smbios
snd_rawmidi
kernel: serio_raw dcdbas snd_seq iwlwifi(OE) snd_seq_device snd_timer
dell_wmi_descriptor wmi_bmof snd idma64 intel_wmi_thunderbolt virt_dma
cfg80211(OE) soundcore rtsx_pci_ms compat(OE) memstick ucsi_acpi intel_lpss_pci
intel_lpss typec_ucsi processor_thermal_device intel_soc_dts_iosf typec
int3403_thermal int340x_thermal_zone intel_hid mac_hid int3400_thermal
sparse_keymap acpi_thermal_rel acpi_pad sch_fq_codel parport_pc ppdev lp
parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq
libcrc32c raid1 raid0 multipath linear hid_generic usbhid i915 i2c_algo_bit
drm_kms_helper rtsx_pci_sdmmc syscopyarea psmouse thunderbolt sysfillrect
sysimgblt fb_sys_fops rtsx_pci drm wmi i2c_hid hid video
kernel: CPU: 3 PID: 17609 Comm: kworker/u17:3 Tainted: G W OE
4.15.0-1097-oem #107-Ubuntu
kernel: Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.6.0 07/07/2020
kernel: Workqueue: hci0 hci_rx_work [bluetooth]
kernel: RIP: 0010:klist_next+0x1c/0x100
kernel: RSP: 0018:ffffbf86c742fc80 EFLAGS: 00010282
kernel: RAX: 0000000000000000 RBX: ffff996fce487000 RCX: 0000000000000000
kernel: RDX: ffffffffc0f4b230 RSI: ffffbf86c742fcc0 RDI: 0000000000000000
kernel: RBP: ffffbf86c742fcb0 R08: 0000377d840d5913 R09: ffff996ffbf49818
kernel: R10: 0000000000000000 R11: 00007fe43cbf3014 R12: ffffbf86c742fcc0
kernel: R13: 0000000000000000 R14: ffff996ff532c000 R15: ffff996fce487000
kernel: FS: 0000000000000000(0000) GS:ffff99700e4c0000(0000)
knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: 0000000000000020 CR3: 00000001a320a002 CR4: 00000000003606e0
kernel: Call Trace:
kernel: ? bt_link_release+0x20/0x20 [bluetooth]
kernel: device_find_child+0x5c/0xb0
kernel: ? bt_link_release+0x20/0x20 [bluetooth]
kernel: hci_conn_del_sysfs+0x54/0xa0 [bluetooth]
kernel: hci_conn_cleanup+0x92/0x140 [bluetooth]
kernel: hci_conn_del+0xf1/0x1f0 [bluetooth]
kernel: hci_event_packet+0x1155/0x2d60 [bluetooth]
kernel: ? __switch_to_asm+0x35/0x70
kernel: ? __switch_to_asm+0x41/0x70
kernel: ? __switch_to_asm+0x35/0x70
kernel: ? __switch_to_asm+0x41/0x70
kernel: ? __switch_to_asm+0x35/0x70
kernel: hci_rx_work+0x199/0x390 [bluetooth]
kernel: ? hci_rx_work+0x199/0x390 [bluetooth]
kernel: process_one_work+0x1de/0x420
kernel: worker_thread+0x32/0x410
kernel: kthread+0x121/0x140
kernel: ? process_one_work+0x420/0x420
kernel: ? kthread_create_worker_on_cpu+0x70/0x70
kernel: ret_from_fork+0x1f/0x40
kernel: Code: 41 5c 41 5d 5d c3 66 0f 1f 84 00 00 00 00 00 55 48 89 e5 41 57 41
56 41 55 41 54 49 89 fc 53 48 83 ec 08 48 8b 3f 4d 8b 6c 24 08 <4c> 8b 77 20 e8
db 24 02 00 4d 85 ed 0f 84 84 00 00 00 49 8b 4d
kernel: RIP: klist_next+0x1c/0x100 RSP: ffffbf86c742fc80
kernel: CR2: 0000000000000020
kernel: ---[ end trace e0cb46d230eda351 ]---
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-10-03 8:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 0:23 [Bug 203535] New: Bluetooth: command tx timeout with Intel Corporation Wireless 7260 in A2DP mode bugzilla-daemon
2020-04-05 15:53 ` [Bug 203535] " bugzilla-daemon
2020-04-05 15:54 ` bugzilla-daemon
2020-05-25 10:30 ` bugzilla-daemon
2020-07-06 20:53 ` bugzilla-daemon
2020-10-03 8:28 ` bugzilla-daemon [this message]
2020-12-12 14:56 ` bugzilla-daemon
2020-12-14 20:15 ` bugzilla-daemon
2020-12-26 17:19 ` bugzilla-daemon
2021-01-02 7:19 ` bugzilla-daemon
2021-01-14 16:59 ` bugzilla-daemon
2022-11-30 17:35 ` bugzilla-daemon
2023-03-12 20:21 ` bugzilla-daemon
2023-03-23 0:08 ` bugzilla-daemon
2023-04-22 15:59 ` 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-203535-62941-b1o6voXS7l@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).