From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 218297] Kernel Panic and crash
Date: Fri, 12 Jan 2024 05:33:12 +0000 [thread overview]
Message-ID: <bug-218297-28872-qMmZRa2FV4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218297-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218297
Rajesh Goel (rgoel.bangalore@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rgoel.bangalore@gmail.com
--- Comment #3 from Rajesh Goel (rgoel.bangalore@gmail.com) ---
(In reply to Artem S. Tashkinov from comment #2)
> Please try to repro it in vanilla kernel 5.4.265.
>
> If earlier kernels aren't affected, please do regression testing:
>
> https://docs.kernel.org/admin-guide/bug-bisect.html
We are actually using the same kernel, with very few minute changes which are
not going to affect the working the way vanilla kernel is being used.
In our setups we cannot use the vanilla kernel directly.
The main reason for this bug report is to understand if similar issues were
seen in the past and any possible fixes has been suggested.
We see similar forum where same issue was reported, but patch suggest here is
already integrated in our builds.
Is there more information you can share, which can help us understand this
problem in more depth.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-01-12 5:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 4:53 [Bug 218297] New: Kernel Panic and crash bugzilla-daemon
2023-12-21 7:26 ` [Bug 218297] " bugzilla-daemon
2023-12-21 7:27 ` bugzilla-daemon
2024-01-12 5:33 ` bugzilla-daemon [this message]
2024-01-23 5:23 ` bugzilla-daemon
2024-02-01 4:36 ` 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-218297-28872-qMmZRa2FV4@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=kvm@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).