mirror of https://lore.kernel.org/lkml/
 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 v7.2-rc{3,4} and next-20260722 with PREEMPT_RT
Date: Thu, 23 Jul 2026 18:17:02 +0200	[thread overview]
Message-ID: <1a0800888c2fcd42f1fcd661d8f6f50580ac2fd4.camel@web.de> (raw)
In-Reply-To: <d24a136539c5931984f4855ad6596ca7aee8ebe2.camel@web.de>

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

So I've run memtest86+ for ~2.5h (2.6 complete runs) and found no error. Even if my memory
contained an error, if it's that hard to trigger it would not cause frequent crashes.

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 ...) 
In next-20260722 the crash is reproducible without netconsole.
So I'm going back to bisecting from v7.2-rc4 to next-20260722. Once I'm finished with
that I'm going to look at the "netconsole triggerred" crashes.
 Does anyone have an idea what's going on?

Bert Karwatzki

  reply	other threads:[~2026-07-23 16:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 12:34 kernel panic during shutdown in v7.2-rc4 " Bert Karwatzki
2026-07-23 12:43 ` [Re] " Bert Karwatzki
2026-07-23 13:10   ` [Re] kernel panic during shutdown in v7.2-rc{3,4} " Bert Karwatzki
2026-07-23 13:23     ` Bert Karwatzki
2026-07-23 16:17       ` Bert Karwatzki [this message]
2026-07-23 22:51         ` [Re] kernel panic during shutdown in next-20260722 Bert Karwatzki
2026-07-24 15:08           ` Bert Karwatzki
2026-07-25 19:58             ` Bert Karwatzki
2026-07-25 23:16               ` Bert Karwatzki
2026-07-26 18:47                 ` Bert Karwatzki
2026-07-26 22:52                   ` Bert Karwatzki
2026-07-27 10:06                     ` [Re] kernel panic during shutdown in v7.1+ with PREEMPT_RT Bert Karwatzki
2026-07-27 10:35                       ` Ostrowski, Rafal
2026-07-27 10:50                         ` [PATCH] drm/amd/display: fix usage of DC_FPU_{BEGIN,END} " Bert Karwatzki
2026-07-27 11:11                           ` sashiko-bot
2026-07-28  0:51                           ` mikhail.v.gavrilov
2026-07-29 12:35                             ` Bert Karwatzki
2026-07-29 14:39                               ` Mikhail Gavrilov
2026-07-29 17:46                                 ` Bert Karwatzki
2026-08-01  7:17                                   ` Bert Karwatzki
2026-08-01  7:35                                     ` sashiko-bot
2026-08-01 10:17                                     ` Mikhail Gavrilov
2026-08-07 12:58                                       ` Bert Karwatzki
2026-08-07 13:31                                         ` sashiko-bot
2026-08-06  3:47                                     ` kernel test robot
2026-08-06  4:29                                     ` kernel test robot
2026-08-07 12:49                                       ` [PATCH v7.2-rc6] " Bert Karwatzki
2026-08-07 13:13                                         ` sashiko-bot
2026-08-07 14:00                                         ` Greg KH

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=1a0800888c2fcd42f1fcd661d8f6f50580ac2fd4.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

all inboxes | Powered by JetHome®