linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Ilkka Naulapää" <digirigawa@gmail.com>
Cc: "Linux regression tracking (Thorsten Leemhuis)"
	<regressions@leemhuis.info>,
	Linux regressions mailing list <regressions@lists.linux.dev>,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org
Subject: Re: Bug in Kernel 6.8.x, 6.9.x Causing Trace/Panic During Shutdown/Reboot
Date: Tue, 18 Jun 2024 10:52:39 -0400	[thread overview]
Message-ID: <20240618105239.1feda53a@rorschach.local.home> (raw)
In-Reply-To: <CAE4VaRFwdxNuUWb=S+itDLZf1rOZx9px+xoLWCi+hdUaWJwj6Q@mail.gmail.com>

On Thu, 13 Jun 2024 10:32:24 +0300
Ilkka Naulapää <digirigawa@gmail.com> wrote:

> ok, so if you don't have any idea where this bug is after those debug
> patches, I'll try to find some time to bisect it as a last resort.
> Stay tuned.

FYI,

I just debugged a strange crash that was caused by my config having
something leftover from your config. Specifically, that was:

CONFIG_FORCE_NR_CPUS

Do you get any warning about nr cpus not matching at boot up?

Regardless, can you disable that and see if you still get the same
crash.

Thanks,

-- Steve

  parent reply	other threads:[~2024-06-18 14:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAE4VaREzY+a2PvQJYJbfh8DwB4OP7kucZG-e28H22xyWob1w_A@mail.gmail.com>
2024-05-24 10:50 ` Bug in Kernel 6.8.x, 6.9.x Causing Trace/Panic During Shutdown/Reboot Linux regression tracking (Thorsten Leemhuis)
2024-05-24 17:14   ` Steven Rostedt
2024-05-24 17:20   ` Steven Rostedt
2024-05-26 17:42     ` Ilkka Naulapää
2024-05-27 16:40       ` Ilkka Naulapää
2024-05-27 18:14         ` Greg KH
2024-05-27 21:44           ` Steven Rostedt
2024-05-28  4:08             ` Ilkka Naulapää
2024-05-27 22:31   ` Steven Rostedt
2024-05-28  4:51     ` Ilkka Naulapää
2024-05-28 18:47       ` Steven Rostedt
2024-05-29 18:36         ` Ilkka Naulapää
2024-05-29 18:47           ` Steven Rostedt
2024-05-29 19:48             ` Steven Rostedt
2024-05-30 13:02               ` Ilkka Naulapää
2024-05-30 13:59                 ` Steven Rostedt
2024-06-02  7:32                   ` Ilkka Naulapää
2024-06-12 13:36                     ` Linux regression tracking (Thorsten Leemhuis)
2024-06-12 15:56                       ` Steven Rostedt
2024-06-13  7:32                         ` Ilkka Naulapää
2024-06-13  7:48                           ` Linux regression tracking (Thorsten Leemhuis)
2024-06-18 14:52                           ` Steven Rostedt [this message]
2024-06-19 10:41                             ` Ilkka Naulapää

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=20240618105239.1feda53a@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=digirigawa@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).