From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Linux kernel regressions list <regressions@lists.linux.dev>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] Oops during init in btintel_read_debug_features with today's mainline
Date: Tue, 26 Mar 2024 12:56:50 -0400 [thread overview]
Message-ID: <CABBYNZKDa9KR8A_4TbpPyiLWFFH22T=Z9jk7N=o6U+z1oB+7vg@mail.gmail.com> (raw)
In-Reply-To: <08275279-7462-4f4a-a0ee-8aa015f829bc@leemhuis.info>
Hi Thorsten,
On Tue, Mar 26, 2024 at 4:44 AM Thorsten Leemhuis <linux@leemhuis.info> wrote:
>
> Lo! Just booted 6.9 for the first time and noticed the Bluetooth code
> causes an Oops (see below) during boot that did not happen with 6.8 and
> earlier. This is on Fedora 40 with a vanilla kernel on a Lenovo Thinkpad
> T14s Gen1 AMD.
>
> Do I need to bisect this? Or is this known already? Or does anyone by
> chance an idea what might cause this? Or is there some other way to get
> down to the problem?
>
> Ciao, Thorsten
>
> [Full dmesg: https://www.leemhuis.info/files/misc/dmesg-6.9-btprob]
>
> [ 19.903869] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
> [ 19.903908] Bluetooth: hci0: Boot Address: 0x24800
> [ 19.903913] Bluetooth: hci0: Firmware Version: 255-255.255
> [ 19.906245] usb 6-4: USB disconnect, device number 3
> [ 19.906364] usb 2-2: Found UVC 1.50 device Integrated Camera (04f2:b6cb)
> [ 19.906583] Bluetooth: hci0: FW download error recovery failed (-19)
> [ 19.906649] Bluetooth: hci0: sending frame failed (-19)
> [ 19.906666] BUG: kernel NULL pointer dereference, address: 0000000000000070
> [ 19.906672] #PF: supervisor read access in kernel mode
> [ 19.906677] #PF: error_code(0x0000) - not-present page
> [ 19.906681] PGD 0 P4D 0
> [ 19.906688] Oops: 0000 [#1] PREEMPT SMP NOPTI
> [ 19.906701] Hardware name: LENOVO 20UH001HGE/20UH001HGE, BIOS R1CET77W(1.46 ) 10/26/2023
> [ 19.906706] Workqueue: hci0 hci_power_on [bluetooth]
> [ 19.906775] RIP: 0010:btintel_read_debug_features (/usr/src/debug/[...]/drivers/bluetooth/btintel.c:1306) btintel
Seem like the following could be reason:
https://patchwork.kernel.org/project/bluetooth/patch/20240326164317.1460864-1-luiz.dentz@gmail.com/
prev parent reply other threads:[~2024-03-26 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 8:44 [REGRESSION] Oops during init in btintel_read_debug_features with today's mainline Thorsten Leemhuis
2024-03-26 16:56 ` Luiz Augusto von Dentz [this message]
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='CABBYNZKDa9KR8A_4TbpPyiLWFFH22T=Z9jk7N=o6U+z1oB+7vg@mail.gmail.com' \
--to=luiz.dentz@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=marcel@holtmann.org \
--cc=regressions@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).