From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215347] btintel: AX200 (8087:0029): hci crashes and can't recover after repeated rfkill on/off
Date: Wed, 22 Dec 2021 22:56:34 +0000 [thread overview]
Message-ID: <bug-215347-62941-UBe6zE5fu8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215347-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215347
--- Comment #8 from Tedd An (tedd.an@intel.com) ---
It seems like kernel oops in the dmesg and it may causes the issue.
[ 46.401807] ------------[ cut here ]------------
[ 46.401808] kernel BUG at net/core/skbuff.c:113!
[ 46.401819] invalid opcode: 0000 [#1] PREEMPT SMP
[ 46.401826] CPU: 7 PID: 142 Comm: kworker/u33:0 Not tainted 5.16.0-rc1+ #1
[ 46.401831] Hardware name: LENOVO 20U8S0PQ00/20U8S0PQ00, BIOS R19ET36W (1.20
) 07/12/2021
[ 46.401835] Workqueue: hci0 hci_rx_work [bluetooth]
[ 46.401890] RIP: 0010:skb_panic+0x4c/0x4e
[ 46.401899] Code: 4f 70 50 8b 87 bc 00 00 00 50 8b 87 b8 00 00 00 50 ff b7
c8 00 00 00 4c 8b 8f c0 00 00 00 48 c7 c7 e8 00 a7 98 e8 46 11 fb ff <0f> 0b 48
8b 55 08 48 c7 c1 60 b1 71 98 e8 a2 ff ff ff 48 c7 c6 b0
[ 46.401903] RSP: 0018:ffffa22980aa3c60 EFLAGS: 00010246
[ 46.401908] RAX: 0000000000000088 RBX: 0000000000000000 RCX:
0000000000000000
[ 46.401911] RDX: 0000000000000000 RSI: ffffffff989a0551 RDI:
00000000ffffffff
[ 46.401914] RBP: ffffa22980aa3c80 R08: 0000000000000000 R09:
ffffa22980aa3a50
[ 46.401917] R10: 0000000000000001 R11: 0000000000000001 R12:
00000000000000a5
[ 46.401919] R13: 00000000000000a5 R14: ffff9409c4e7c300 R15:
00000000000000aa
[ 46.401923] FS: 0000000000000000(0000) GS:ffff940ccefc0000(0000)
knlGS:0000000000000000
[ 46.401927] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 46.401930] CR2: 00007fae7c01b398 CR3: 000000040c20f000 CR4:
0000000000350ee0
[ 46.401933] Call Trace:
[ 46.401937] <TASK>
[ 46.401942] skb_put.cold+0x10/0x10
[ 46.401947] mgmt_device_found+0x3c8/0x4c0 [bluetooth]
[ 46.402004] hci_extended_inquiry_result_evt+0x162/0x230 [bluetooth]
[ 46.402054] hci_event_packet+0x2cd/0x4b0 [bluetooth]
[ 46.402099] ? hci_remote_oob_data_request_evt+0x1f0/0x1f0 [bluetooth]
[ 46.402144] hci_rx_work+0x1b2/0x3d0 [bluetooth]
[ 46.402190] ? queue_delayed_work_on+0x3d/0x50
[ 46.402198] process_one_work+0x1ec/0x3c0
[ 46.402204] worker_thread+0x4d/0x3d0
[ 46.402210] kthread+0x17a/0x1a0
[ 46.402214] ? process_one_work+0x3c0/0x3c0
[ 46.402218] ? set_kthread_struct+0x40/0x40
[ 46.402223] ret_from_fork+0x22/0x30
[ 46.402232] </TASK>
[ 46.402234] Modules linked in: rfcomm bnep nls_iso8859_1 intel_rapl_msr
intel_rapl_common snd_ctl_led snd_hda_codec_realtek snd_hda_codec_generic
snd_hda_codec_hdmi snd_hda_intel edac_mce_amd snd_intel_dspcfg
snd_intel_sdw_acpi uvcvideo snd_hda_codec videobuf2_vmalloc snd_hda_core
videobuf2_memops btusb snd_hwdep videobuf2_v4l2 btrtl kvm_amd btbcm snd_pcm
input_leds btintel videobuf2_common kvm snd_seq_midi btmtk snd_seq_midi_event
bluetooth videodev snd_rawmidi joydev iwlmvm ecdh_generic think_lmi
thinkpad_acpi mc rapl ecc serio_raw firmware_attributes_class efi_pstore
wmi_bmof snd_seq nvram mac80211 platform_profile libarc4 ledtrig_audio
snd_seq_device iwlwifi snd_timer snd_rn_pci_acp3x ucsi_acpi ipmi_devintf snd
typec_ucsi snd_pci_acp3x cfg80211 k10temp ipmi_msghandler soundcore typec
mac_hid sch_fq_codel msr parport_pc ppdev lp parport sunrpc ip_tables x_tables
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy
async_pq async_xor async_tx xor raid6_pq
[ 46.402343] libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash
dm_log amdgpu iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper
syscopyarea sysfillrect rtsx_pci_sdmmc sysimgblt fb_sys_fops crc32c_intel
psmouse cec rc_core drm xhci_pci i2c_piix4 xhci_pci_renesas nvme rtsx_pci r8169
realtek nvme_core wmi video i2c_scmi
[ 46.402425] ---[ end trace e9aa209601e9071e ]---
--
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:[~2021-12-22 22:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 11:42 [Bug 215347] New: btintel: AX200 (8087:0029): hci crashed and can't recover after repeated rfkill on/off bugzilla-daemon
2021-12-17 11:43 ` [Bug 215347] btintel: AX200 (8087:0029): hci crashes " bugzilla-daemon
2021-12-18 0:02 ` bugzilla-daemon
2021-12-18 6:12 ` bugzilla-daemon
2021-12-18 6:13 ` bugzilla-daemon
2021-12-18 6:14 ` bugzilla-daemon
2021-12-18 6:15 ` bugzilla-daemon
2021-12-18 6:36 ` bugzilla-daemon
2021-12-18 6:46 ` bugzilla-daemon
2021-12-22 22:56 ` bugzilla-daemon [this message]
2021-12-22 23:45 ` bugzilla-daemon
2021-12-23 5:28 ` bugzilla-daemon
2021-12-23 13:42 ` bugzilla-daemon
2021-12-25 1:32 ` bugzilla-daemon
2022-01-20 1:22 ` bugzilla-daemon
2022-01-20 1:22 ` 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-215347-62941-UBe6zE5fu8@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 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.