All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeremy Lainé" <jeremy.laine@m4x.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: linux-bluetooth@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: Bluetooth kernel BUG with Intel AX211 (regression in 6.1.83)
Date: Mon, 22 Apr 2024 01:17:10 +0200	[thread overview]
Message-ID: <CADRbXaD5Fsy0dxjrVG2JAn1PA36hpoTe6=23=zbhx8NWNf_9mg@mail.gmail.com> (raw)
In-Reply-To: <8eeb980a-f04a-4e94-8065-25566cfef4dd@molgen.mpg.de>

Hi Paul,

On Sun, Apr 21, 2024 at 11:01 PM Paul Menzel <pmenzel@molgen.mpg.de> wrote:
>
> Would you be so kind to go the extra mail, and bisect the commit between
> 6.1.82 and 6.1.83 [1]?
>

Thanks for the link to the instructions, here's the bisect log:

git bisect start
# status: waiting for both good and bad commits
# good: [d7543167affd372819a94879b8b1e8b9b12547d9] Linux 6.1.82
git bisect good d7543167affd372819a94879b8b1e8b9b12547d9
# status: waiting for bad commit, 1 good commit known
# bad: [e5cd595e23c1a075359a337c0e5c3a4f2dc28dd1] Linux 6.1.83
git bisect bad e5cd595e23c1a075359a337c0e5c3a4f2dc28dd1
# bad: [440e278cb53b8dd6627c32e84950350083c39d35] net: kcm: fix
incorrect parameter validation in the kcm_getsockopt) function
git bisect bad 440e278cb53b8dd6627c32e84950350083c39d35
# good: [a4116bd6ee5e1c1b65a61ed9221657615a2f45bf] arm64: dts:
imx8mm-kontron: Disable pull resistors for SD card signals on BL OSM-S
board
git bisect good a4116bd6ee5e1c1b65a61ed9221657615a2f45bf
# good: [e16c33dd9967b7f20987bf653acc4f605836127b] net: mctp: copy skb
ext data when fragmenting
git bisect good e16c33dd9967b7f20987bf653acc4f605836127b
# bad: [6083089ab00631617f9eac678df3ab050a9d837a] Bluetooth: hci_conn:
Consolidate code for aborting connections
git bisect bad 6083089ab00631617f9eac678df3ab050a9d837a
# good: [934212a623cbab851848b6de377eb476718c3e4c] SUNRPC: fix some
memleaks in gssx_dec_option_array
git bisect good 934212a623cbab851848b6de377eb476718c3e4c
# good: [8499af0616cf76e6cbe811107e3f5b33bd472041] igb: Fix missing
time sync events
git bisect good 8499af0616cf76e6cbe811107e3f5b33bd472041
# good: [653a17a99d752ffde175d4bc96154f2a3642f400] Bluetooth: Remove
superfluous call to hci_conn_check_pending()
git bisect good 653a17a99d752ffde175d4bc96154f2a3642f400
# good: [1023de27cd1d0d692e70fe6d6d5cee9fff9b9c84] Bluetooth: Cancel
sync command before suspend and power off
git bisect good 1023de27cd1d0d692e70fe6d6d5cee9fff9b9c84
# good: [ac7a47aaa7944efc94e4fc23cc438b7bd9cc222c] Bluetooth:
hci_sync: Only allow hci_cmd_sync_queue if running
git bisect good ac7a47aaa7944efc94e4fc23cc438b7bd9cc222c
# first bad commit: [6083089ab00631617f9eac678df3ab050a9d837a]
Bluetooth: hci_conn: Consolidate code for aborting connections


> You can pipe the output through `scripts/decodecode` and it should show
> more information.

This was the output of running the dmesg snippet through `scripts/decodecode`:

All code
========
   0:   fe                      (bad)
   1:   ff 0f                   decl   (%rdi)
   3:   0b 48 89                or     -0x77(%rax),%ecx
   6:   f2 48 89 fe             repnz mov %rdi,%rsi
   a:   48 c7 c7 48 18 7a 9f    mov    $0xffffffff9f7a1848,%rdi
  11:   e8 14 a1 fe ff          call   0xfffffffffffea12a
  16:   0f 0b                   ud2
  18:   48 89 fe                mov    %rdi,%rsi
  1b:   48 89 ca                mov    %rcx,%rdx
  1e:   48 c7 c7 10 18 7a 9f    mov    $0xffffffff9f7a1810,%rdi
  25:   e8 00 a1 fe ff          call   0xfffffffffffea12a
  2a:*  0f 0b                   ud2             <-- trapping instruction
  2c:   48 89 fe                mov    %rdi,%rsi
  2f:   48 c7 c7 d8 17 7a 9f    mov    $0xffffffff9f7a17d8,%rdi
  36:   e8 ef a0 fe ff          call   0xfffffffffffea12a
  3b:   0f 0b                   ud2
  3d:   48 89 fe                mov    %rdi,%rsi

Code starting with the faulting instruction
===========================================
   0:   0f 0b                   ud2
   2:   48 89 fe                mov    %rdi,%rsi
   5:   48 c7 c7 d8 17 7a 9f    mov    $0xffffffff9f7a17d8,%rdi
   c:   e8 ef a0 fe ff          call   0xfffffffffffea100
  11:   0f 0b                   ud2
  13:   48 89 fe                mov    %rdi,%rsi

Best regards,
Jeremy

  reply	other threads:[~2024-04-21 23:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-21 13:54 Bluetooth kernel BUG with Intel AX211 (regression in 6.1.83) Jeremy Lainé
2024-04-21 21:00 ` Paul Menzel
2024-04-21 23:17   ` Jeremy Lainé [this message]
2024-04-22  5:41     ` Linux regression tracking (Thorsten Leemhuis)
2024-04-22  8:27       ` Jeremy Lainé
2024-04-22  9:56 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-29 10:24   ` Linux regression tracking (Thorsten Leemhuis)
2024-04-29 18:28     ` Jeremy Lainé
2024-04-29 18:46       ` Linux regression tracking (Thorsten Leemhuis)

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='CADRbXaD5Fsy0dxjrVG2JAn1PA36hpoTe6=23=zbhx8NWNf_9mg@mail.gmail.com' \
    --to=jeremy.laine@m4x.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --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 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.