From: Mike Rapoport <rppt@kernel.org>
To: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Saarinen, Jani" <jani.saarinen@intel.com>,
"Kurmi, Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>
Subject: Re: Regression on linux-next (next-20250205)
Date: Fri, 14 Feb 2025 11:08:25 +0200 [thread overview]
Message-ID: <Z68ICeBI0_S9TEvl@kernel.org> (raw)
In-Reply-To: <SJ1PR11MB6129E21DBF1CA47BF29390D8B9FF2@SJ1PR11MB6129.namprd11.prod.outlook.com>
On Thu, Feb 13, 2025 at 05:30:24PM +0000, Borah, Chaitanya Kumar wrote:
>
> > -----Original Message-----
> > From: Mike Rapoport <rppt@kernel.org>
> > > Thank you for your reply.
> > >
> > > Unfortunately, the change makes it worse. Our local system seems to be in
> > continuous reboot.
> >
> > Are there any logs available?
>
> False alarm! The cyclic resets we are seeing may not be related to your
> change. Our systems are facing this even with the latest vanilla
> linux-next. We are looking into it.
>
> Good news is that if we take your change over the version which first
> detected the issue(next-20250205), it seems to resolve it. Can we expect
> a formal patch soon?
Here it is:
https://lore.kernel.org/all/20250214084531.3299390-1-rppt@kernel.org
> Regards
>
> Chaitanya
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2025-02-14 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 6:52 Regression on linux-next (next-20250205) Borah, Chaitanya Kumar
2025-02-11 7:50 ` Mike Rapoport
2025-02-11 12:30 ` Borah, Chaitanya Kumar
2025-02-12 6:45 ` Mike Rapoport
2025-02-13 17:30 ` Borah, Chaitanya Kumar
2025-02-14 9:08 ` Mike Rapoport [this message]
2025-02-11 8:44 ` ✗ Fi.CI.BUILD: failure for " Patchwork
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=Z68ICeBI0_S9TEvl@kernel.org \
--to=rppt@kernel.org \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=suresh.kumar.kurmi@intel.com \
--cc=x86@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