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 218651] kernel 6.8.2 - Bluetooth bug/dump at boot
Date: Sun, 31 Mar 2024 16:56:09 +0000	[thread overview]
Message-ID: <bug-218651-62941-rBrGRweMD8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218651-62941@https.bugzilla.kernel.org/>

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

--- Comment #19 from wolf.seifert@web.de ---
(In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from
comment #18)
> If the kernel without the patch (In reply to wolf.seifert from comment #17)
> >
> > Although the git bisect gave the same git commit, the problem is probably
> > different and the suggested fix did not work.
> > 
> > See
> > https://bbs.archlinux.org/viewtopic.php?pid=2161135#p2161135
> > for details.
> 
> Spreading feedback over multiple places makes things hard.
> 
> And journalctl -k / dmesg would be helpful. 
> 
> Did your kernel threw that "kernel: BUG: kernel NULL pointer dereference"
> before the fix? If it did not, it was a different problem to begin with and
> worth its own ticket, as things otherwise get confusing. 
> 
> Or did the kernel throw that error and it's gone now, but things are not
> working? Then the patch helped -- but there might be another problem or the
> fix is not enough. Building a 6.8.2 kernel with the culprit removed could
> help to narrow things down.

Sorry for the confusion! In fact I never had this "kernel: BUG: kernel NULL
pointer dereference", but other people having this commented my original post,
so things got messed up.

Anyway, the git bisection is probably o.k., only the problem is different. I
will try to clarify and open a own ticket.

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

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

  parent reply	other threads:[~2024-03-31 16:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28  2:10 [Bug 218651] New: kernel 6.8.2 - Bluetooth bug/dump at boot bugzilla-daemon
2024-03-28  2:12 ` [Bug 218651] " bugzilla-daemon
2024-03-28  2:13 ` bugzilla-daemon
2024-03-28 11:00 ` bugzilla-daemon
2024-03-28 11:03 ` bugzilla-daemon
2024-03-28 11:08 ` bugzilla-daemon
2024-03-28 12:48 ` bugzilla-daemon
2024-03-28 12:49 ` bugzilla-daemon
2024-03-28 12:50 ` bugzilla-daemon
2024-03-28 12:52 ` bugzilla-daemon
2024-03-30  1:49 ` bugzilla-daemon
2024-03-30  1:50 ` bugzilla-daemon
2024-03-30 13:59 ` bugzilla-daemon
2024-03-30 15:50 ` bugzilla-daemon
2024-03-30 17:27 ` bugzilla-daemon
2024-03-30 19:34 ` bugzilla-daemon
2024-03-30 21:52 ` bugzilla-daemon
2024-03-31 15:48 ` bugzilla-daemon
2024-03-31 16:21 ` bugzilla-daemon
2024-03-31 16:56 ` bugzilla-daemon [this message]
2024-04-01 20:33 ` bugzilla-daemon
2024-04-02  6:47 ` bugzilla-daemon
2024-04-04  4:45 ` bugzilla-daemon
2024-04-04  5:38 ` bugzilla-daemon
2024-04-04  8:56 ` bugzilla-daemon
2024-04-05 16:35 ` bugzilla-daemon
2024-04-06  6:54 ` 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-218651-62941-rBrGRweMD8@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