From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Al Viro <viro@zeniv.linux.org.uk>,
brauner@kernel.org, Jan Kara <jack@suse.cz>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: 6.16.4-rc1 oopses under an Ubuntu at an AMD
Date: Wed, 27 Aug 2025 21:36:52 +0200 [thread overview]
Message-ID: <9dafd91d-3f90-4b01-ab02-34135c9b58fb@gmx.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 90 bytes --]
I got the attached oops while testing that rc at a tiny cloud instance.
--
Toralf
[-- Attachment #2: common-trace-full.log --]
[-- Type: chemical/x-gaussian-log, Size: 4728 bytes --]
reply other threads:[~2025-08-27 19:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9dafd91d-3f90-4b01-ab02-34135c9b58fb@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).