public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 216686] New: BUG: kernel NULL pointer dereference, address: 0000000000000680
Date: Sun, 13 Nov 2022 07:29:55 +0000	[thread overview]
Message-ID: <bug-216686-62941@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=216686

            Bug ID: 216686
           Summary: BUG: kernel NULL pointer dereference, address:
                    0000000000000680
           Product: Drivers
           Version: 2.5
    Kernel Version: 6.0.0, 6.0.3, 6.0.8, 6.1-rc3
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: frc.gabriel@gmail.com
        Regression: Yes

Hi, good morning,

I noticed few bluetooth crashes starting with kernel 6.0.0 release.

With 5.19.x I didn't see this oops and bluetooth works ok.

Kernel oops comes pretty randomly and/or takes some time to occur.

I noticed it happens more frequently when returning from suspend or when trying
to reconnect an already paired earphone headset.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021905 (kernel=6.0.0,
firmware-linux=20210818, bios=1.19)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023076 (kernel=6.0.3,
firmware-linux=20221012, bios=1.19)

This kernel oops is also appearing with 6.0.8 and 6.1-rc3 from debian
experimental + firmware-linux=20221012 and lenovo bios=1.21.

Have a nice day,
Gabriel Francisco

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2022-11-13  7:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13  7:29 bugzilla-daemon [this message]
2022-11-13  7:30 ` [Bug 216686] BUG: kernel NULL pointer dereference, address: 0000000000000680 bugzilla-daemon
2022-11-13  7:31 ` bugzilla-daemon
2022-11-13  7:31 ` bugzilla-daemon
2022-11-13  8:44 ` bugzilla-daemon
2022-11-13 10:12 ` bugzilla-daemon
2022-11-13 13:23 ` bugzilla-daemon
2022-11-13 13:38 ` bugzilla-daemon
2022-11-13 14:15 ` bugzilla-daemon
2022-11-14  5:39 ` bugzilla-daemon
2022-11-14  5:40 ` bugzilla-daemon
2022-11-14  5:45 ` bugzilla-daemon
2022-11-14  6:08 ` bugzilla-daemon
2022-11-14  6:09 ` bugzilla-daemon
2022-11-14  6:32 ` 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-216686-62941@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox