From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219294] NULL dereference pointer in Bluetooth at boot
Date: Fri, 13 Dec 2024 09:20:12 +0000 [thread overview]
Message-ID: <bug-219294-62941-U81rBR5AjB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219294-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219294
Julian Stecklina (js@alien8.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |js@alien8.de
--- Comment #5 from Julian Stecklina (js@alien8.de) ---
I also see this occasionally on boot on my Framework 13 laptop running Linux
6.12.3. The result is a hang after the GDM login screen and the user session
doesn't start. I think it also happened on 6.12.1.
Dec 13 10:11:46 avalon kernel: Bluetooth: RFCOMM TTY layer initialized
Dec 13 10:11:46 avalon kernel: Bluetooth: RFCOMM socket layer initialized
Dec 13 10:11:46 avalon kernel: Bluetooth: RFCOMM ver 1.11
Dec 13 10:11:49 avalon kernel: BUG: kernel NULL pointer dereference, address:
0000000000000000
Dec 13 10:11:49 avalon kernel: #PF: supervisor read access in kernel mode
Dec 13 10:11:49 avalon kernel: #PF: error_code(0x0000) - not-present page
Dec 13 10:11:49 avalon kernel: PGD 0 P4D 0
Dec 13 10:11:49 avalon kernel: Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI
Dec 13 10:11:49 avalon kernel: CPU: 12 UID: 0 PID: 196 Comm: kworker/12:1 Not
tainted 6.12.3 #1-NixOS
Dec 13 10:11:49 avalon kernel: Hardware name: Framework Laptop 13 (AMD Ryzen
7040Series)/FRANMDCP07, BIOS 03.05 03/29/2024
Dec 13 10:11:49 avalon kernel: Workqueue: pm pm_runtime_work
Dec 13 10:11:49 avalon kernel: RIP: 0010:btusb_suspend+0x161/0x200 [btusb]
Dec 13 10:11:49 avalon kernel: Code: 00 00 01 e9 fb fe ff ff 48 89 fa 48 c7 c6
3f f2 32 c2 48 c7 c7 58 a3 32 c2 e8 7b f6 c1 e0 81 e5 00 04 00 00 0f 84 c6 fe
ff ff <48> 8b 13 8b 82 bc 09 00 00 03 82 b8 09 00 00 03 82 c4 09 00 00 03
Dec 13 10:11:49 avalon kernel: RSP: 0018:ffffae7ac066fca0 EFLAGS: 00010206
Dec 13 10:11:49 avalon kernel: RAX: ffffffffc2322a30 RBX: 0000000000000000 RCX:
0000000000000003
Dec 13 10:11:49 avalon kernel: RDX: ffff94f941331000 RSI: 0000000000000402 RDI:
ffff94f941344800
Dec 13 10:11:49 avalon kernel: RBP: 0000000000000400 R08: 0000000000000000 R09:
0000000000000000
Dec 13 10:11:49 avalon kernel: R10: 0000000000000000 R11: 0000000000000000 R12:
0000000000000402
Dec 13 10:11:49 avalon kernel: R13: 0000000000000003 R14: 0000000000000000 R15:
ffff94f954df0000
Dec 13 10:11:49 avalon kernel: FS: 0000000000000000(0000)
GS:ffff95009e600000(0000) knlGS:0000000000000000
Dec 13 10:11:49 avalon kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Dec 13 10:11:49 avalon kernel: CR2: 0000000000000000 CR3: 0000000036e22000 CR4:
0000000000f50ef0
Dec 13 10:11:49 avalon kernel: PKRU: 55555554
Dec 13 10:11:49 avalon kernel: Call Trace:
Dec 13 10:11:49 avalon kernel: <TASK>
Dec 13 10:11:49 avalon kernel: ? __die+0x23/0x80
Dec 13 10:11:49 avalon kernel: ? page_fault_oops+0x173/0x5b0
Dec 13 10:11:49 avalon kernel: ? page_counter_uncharge+0x21/0x50
Dec 13 10:11:49 avalon kernel: ? exc_page_fault+0x71/0x160
Dec 13 10:11:49 avalon kernel: ? asm_exc_page_fault+0x26/0x30
Dec 13 10:11:49 avalon kernel: ? __pfx_btusb_suspend+0x10/0x10 [btusb]
Dec 13 10:11:49 avalon kernel: ? btusb_suspend+0x161/0x200 [btusb]
Dec 13 10:11:49 avalon kernel: usb_suspend_both+0x94/0x290
Dec 13 10:11:49 avalon kernel: usb_runtime_suspend+0x2e/0x80
Dec 13 10:11:49 avalon kernel: ? __pfx_usb_runtime_suspend+0x10/0x10
Dec 13 10:11:49 avalon kernel: __rpm_callback+0x41/0x170
Dec 13 10:11:49 avalon kernel: ? __pfx_usb_runtime_suspend+0x10/0x10
Dec 13 10:11:49 avalon kernel: rpm_callback+0x59/0x70
Dec 13 10:11:49 avalon kernel: ? __pfx_usb_runtime_suspend+0x10/0x10
Dec 13 10:11:49 avalon kernel: rpm_suspend+0xe8/0x5e0
Dec 13 10:11:49 avalon kernel: ? psi_task_switch+0xfb/0x200
Dec 13 10:11:49 avalon kernel: ? finish_task_switch.isra.0+0x9c/0x2f0
Dec 13 10:11:49 avalon kernel: __pm_runtime_suspend+0x3c/0xd0
Dec 13 10:11:49 avalon kernel: ? __pfx_usb_runtime_idle+0x10/0x10
Dec 13 10:11:49 avalon kernel: usb_runtime_idle+0x39/0x50
Dec 13 10:11:49 avalon kernel: rpm_idle+0xbd/0x280
Dec 13 10:11:49 avalon kernel: pm_runtime_work+0x84/0xb0
Dec 13 10:11:49 avalon kernel: process_one_work+0x18f/0x3b0
Dec 13 10:11:49 avalon kernel: worker_thread+0x230/0x340
Dec 13 10:11:49 avalon kernel: ? __pfx_worker_thread+0x10/0x10
Dec 13 10:11:49 avalon kernel: ? __pfx_worker_thread+0x10/0x10
Dec 13 10:11:49 avalon kernel: kthread+0xcd/0x100
Dec 13 10:11:49 avalon kernel: ? __pfx_kthread+0x10/0x10
Dec 13 10:11:49 avalon kernel: ret_from_fork+0x31/0x50
Dec 13 10:11:49 avalon kernel: ? __pfx_kthread+0x10/0x10
Dec 13 10:11:49 avalon kernel: ret_from_fork_asm+0x1a/0x30
Dec 13 10:11:49 avalon kernel: </TASK>
Dec 13 10:11:49 avalon kernel: Modules linked in: rfcomm snd_seq_dummy
snd_hrtimer snd_seq qrtr cmac algif_hash algif_skcipher af_alg af_packet
xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp
nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4
nf_tables bnep msr nls_>
Dec 13 10:11:49 avalon kernel: hid_sensor_trigger snd_rpl_pci_acp6x
snd_hda_intel industrialio_triggered_buffer kfifo_buf snd_acp_pci
hid_sensor_iio_common snd_intel_dspcfg sch_fq_codel cros_ec_dev industrialio
snd_usb_audio spd5118 snd_intel_sdw_acpi snd_acp_legacy_common cfg80211
uvcvideo sp5100_tco snd_hda_codec>
Dec 13 10:11:49 avalon kernel: tpm_tis i2c_hid_acpi tpm_tis_core tap button
i2c_hid macvlan evdev mac_hid amd_pmc serio_raw bridge stp llc kvm_amd ccp kvm
fuse efi_pstore configfs nfnetlink zram 842_decompress 842_compress
lz4hc_compress lz4_compress efivarfs dmi_sysfs ip_tables x_tables autofs4 xfs
libcrc32c crc32>
Dec 13 10:11:49 avalon kernel: CR2: 0000000000000000
Dec 13 10:11:49 avalon kernel: ---[ end trace 0000000000000000 ]---
--
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-12-13 9:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 20:39 [Bug 219294] New: NULL dereference pointer in Bluetooth at boot bugzilla-daemon
2024-09-20 20:40 ` [Bug 219294] " bugzilla-daemon
2024-09-20 20:41 ` bugzilla-daemon
2024-09-25 13:54 ` bugzilla-daemon
2024-09-25 15:05 ` bugzilla-daemon
2024-09-26 9:21 ` bugzilla-daemon
2024-12-13 9:20 ` bugzilla-daemon [this message]
2024-12-13 9:29 ` bugzilla-daemon
2024-12-20 17:40 ` bugzilla-daemon
2024-12-27 21:55 ` 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-219294-62941-U81rBR5AjB@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.