Linux-Next discussions
 help / color / mirror / Atom feed
From: Bert Karwatzki <spasswolf@web.de>
To: linux-kernel@vger.kernel.org, Rafal Ostrowski <rafal.ostrowski@amd.com>
Cc: linux-next@vger.kernel.org, linux-rt-devel@lists.linux.dev,
	 amd-gfx@lists.freedesktop.org,
	Alex Deucher <alexander.deucher@amd.com>,
	 Mario Limonciello <mario.limonciello@amd.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Thomas Gleixner	 <tglx@linutronix.de>,
	spasswolf@web.de
Subject: Re: [Re] kernel panic during shutdown in  next-20260722
Date: Fri, 24 Jul 2026 00:51:19 +0200	[thread overview]
Message-ID: <4d7c2dd588cd77d1d112da473f2a262d22051d57.camel@web.de> (raw)
In-Reply-To: <1a0800888c2fcd42f1fcd661d8f6f50580ac2fd4.camel@web.de>

Am Donnerstag, dem 23.07.2026 um 18:17 +0200 schrieb Bert Karwatzki:
> Am Donnerstag, dem 23.07.2026 um 15:23 +0200 schrieb Bert Karwatzki:
> > Am Donnerstag, dem 23.07.2026 um 15:10 +0200 schrieb Bert Karwatzki:
> > > I was able to gather the panic error message from a failed shutdown via netconsole,
> > > this time the kernel used was v7.2-rc3:
> > > #
> > > Bert Karwatzki
> > 
> > Unfortunatetly I can now reproduce these kernel panics in v7.1:
> > 
> > 
> > So now I'm going to use memtest86+ on my machine and then look at the changes I had in
> > my userspace as the first error occured on 22.7.2026. Let's hope this does not escalate ...
> > 
> > Bert Karwatzki
> 
> 
> But I found out an exciting thing:
> I can only reproduce the crashes in v7.2-rc4 when watching the reboot via netconsole,
> without netconsole no crash occurs!(This also explains why I had not seen this crashes before ...) 
> 
Actually this is not cause by netconsole, but by rebooting right after a crash. Some
broken state seems to be preserved across reboots. Switching off the power supply after
a crash or even a ~30s wait after switching off the crashed machine seems to be enough
to get around this.
 Also the hang when rebooting next-20260722 also occurs when compiling without PREEMPT_RT.

Bert Karwatzki


      reply	other threads:[~2026-07-23 22:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260723124353.13040-1-spasswolf@web.de>
2026-07-23 13:10 ` [Re] kernel panic during shutdown in v7.2-rc{3,4} and next-20260722 with PREEMPT_RT Bert Karwatzki
2026-07-23 13:23   ` Bert Karwatzki
2026-07-23 16:17     ` Bert Karwatzki
2026-07-23 22:51       ` Bert Karwatzki [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=4d7c2dd588cd77d1d112da473f2a262d22051d57.camel@web.de \
    --to=spasswolf@web.de \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=mario.limonciello@amd.com \
    --cc=rafal.ostrowski@amd.com \
    --cc=tglx@linutronix.de \
    /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