* Regression on linux-next (next-20250205)
@ 2025-02-10 6:52 Borah, Chaitanya Kumar
2025-02-11 7:50 ` Mike Rapoport
2025-02-11 8:44 ` ✗ Fi.CI.BUILD: failure for " Patchwork
0 siblings, 2 replies; 7+ messages in thread
From: Borah, Chaitanya Kumar @ 2025-02-10 6:52 UTC (permalink / raw)
To: rppt@kernel.org
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
Saarinen, Jani, Kurmi, Suresh Kumar, x86@kernel.org,
De Marchi, Lucas
Hello Mike,
Hope you are doing well. I am Chaitanya from the linux graphics team in Intel.
This mail is regarding a regression we are seeing in our CI runs[1] on linux-next repository.
Since the version next-20250205 [2], we are seeing the following regression
`````````````````````````````````````````````````````````````````````````````````
<4>[ 314.781734] kmemleak: Found object by alias at 0xffffffffa0595000
<4>[ 314.781738] CPU: 11 UID: 0 PID: 6042 Comm: i915_selftest Tainted: G U 6.14.0-rc1-next-20250205-next-20250205-ged88b8b82c53+ #1
<4>[ 314.781741] Tainted: [U]=USER
<4>[ 314.781741] Hardware name: ASUS System Product Name/PRIME Z790-P WIFI, BIOS 0812 02/24/2023
<4>[ 314.781742] Call Trace:
<4>[ 314.781743] <TASK>
<4>[ 314.781744] dump_stack_lvl+0x91/0xf0
<4>[ 314.781749] dump_stack+0x10/0x20
<4>[ 314.781751] __lookup_object+0x90/0xa0
<4>[ 314.781755] __find_and_get_object+0x6c/0x190
<4>[ 314.781758] paint_ptr+0x1b/0xa0
<4>[ 314.781759] kmemleak_not_leak+0x33/0x70
<4>[ 314.781762] load_module+0xa20/0x2d10
`````````````````````````````````````````````````````````````````````````````````
Details log can be found in [3].
After bisecting the tree, the following patch [4] seems to be the first "bad"
commit
`````````````````````````````````````````````````````````````````````````````````````````````````````````
commit 64f6a4e10c05ed527f0f24b7954964255e0d3535
Author: Mike Rapoport (Microsoft) mailto:rppt@kernel.org
Date: Sun Jan 26 09:47:33 2025 +0200
x86: re-enable EXECMEM_ROX support
after rework of execmem ROX caches
Signed-off-by: "Mike Rapoport (Microsoft)" mailto:rppt@kernel.org
Signed-off-by: Peter Zijlstra (Intel) mailto:peterz@infradead.org
Link: https://lore.kernel.org/r/20250126074733.1384926-10-rppt@kernel.org
`````````````````````````````````````````````````````````````````````````````````````````````````````````
We also verified that if we revert the patch the issue is not seen.
Could you please check why the patch causes this regression and provide a fix if necessary?
Thank you.
Regards
Chaitanya
[1] https://intel-gfx-ci.01.org/tree/linux-next/combined-alt.html?
[2] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20250205
[3] https://intel-gfx-ci.01.org/tree/linux-next/next-20250205/bat-rpls-4/dmesg0.txt
[4] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20250205&id=64f6a4e10c05ed527f0f24b7954964255e0d3535
Regards
Chaitanya
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Regression on linux-next (next-20250205)
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-11 8:44 ` ✗ Fi.CI.BUILD: failure for " Patchwork
1 sibling, 1 reply; 7+ messages in thread
From: Mike Rapoport @ 2025-02-11 7:50 UTC (permalink / raw)
To: Borah, Chaitanya Kumar
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
Saarinen, Jani, Kurmi, Suresh Kumar, x86@kernel.org,
De Marchi, Lucas
Hello Chaitanya,
On Mon, Feb 10, 2025 at 06:52:35AM +0000, Borah, Chaitanya Kumar wrote:
> Hello Mike,
>
> Hope you are doing well. I am Chaitanya from the linux graphics team in Intel.
>
> This mail is regarding a regression we are seeing in our CI runs[1] on linux-next repository.
>
> Since the version next-20250205 [2], we are seeing the following regression
>
> `````````````````````````````````````````````````````````````````````````````````
> <4>[ 314.781734] kmemleak: Found object by alias at 0xffffffffa0595000
> <4>[ 314.781738] CPU: 11 UID: 0 PID: 6042 Comm: i915_selftest Tainted: G U 6.14.0-rc1-next-20250205-next-20250205-ged88b8b82c53+ #1
> <4>[ 314.781741] Tainted: [U]=USER
> <4>[ 314.781741] Hardware name: ASUS System Product Name/PRIME Z790-P WIFI, BIOS 0812 02/24/2023
> <4>[ 314.781742] Call Trace:
> <4>[ 314.781743] <TASK>
> <4>[ 314.781744] dump_stack_lvl+0x91/0xf0
> <4>[ 314.781749] dump_stack+0x10/0x20
> <4>[ 314.781751] __lookup_object+0x90/0xa0
> <4>[ 314.781755] __find_and_get_object+0x6c/0x190
> <4>[ 314.781758] paint_ptr+0x1b/0xa0
> <4>[ 314.781759] kmemleak_not_leak+0x33/0x70
> <4>[ 314.781762] load_module+0xa20/0x2d10
> `````````````````````````````````````````````````````````````````````````````````
> Details log can be found in [3].
Does this fix it for you?
diff --git a/kernel/module/main.c b/kernel/module/main.c
index 4a02503836d7..a598888e7072 100644
--- a/kernel/module/main.c
+++ b/kernel/module/main.c
@@ -1260,7 +1260,8 @@ static int module_memory_alloc(struct module *mod, enum mod_mem_type type)
* *do* eventually get freed, but let's just keep things simple
* and avoid *any* false positives.
*/
- kmemleak_not_leak(ptr);
+ if (!mod->mem[type].is_rox)
+ kmemleak_not_leak(ptr);
memset(ptr, 0, size);
mod->mem[type].base = ptr;
> [1] https://intel-gfx-ci.01.org/tree/linux-next/combined-alt.html?
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20250205
> [3] https://intel-gfx-ci.01.org/tree/linux-next/next-20250205/bat-rpls-4/dmesg0.txt
> [4] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20250205&id=64f6a4e10c05ed527f0f24b7954964255e0d3535
>
> Regards
> Chaitanya
--
Sincerely yours,
Mike.
^ permalink raw reply related [flat|nested] 7+ messages in thread
* ✗ Fi.CI.BUILD: failure for Regression on linux-next (next-20250205)
2025-02-10 6:52 Regression on linux-next (next-20250205) Borah, Chaitanya Kumar
2025-02-11 7:50 ` Mike Rapoport
@ 2025-02-11 8:44 ` Patchwork
1 sibling, 0 replies; 7+ messages in thread
From: Patchwork @ 2025-02-11 8:44 UTC (permalink / raw)
To: Mike Rapoport; +Cc: intel-gfx
== Series Details ==
Series: Regression on linux-next (next-20250205)
URL : https://patchwork.freedesktop.org/series/144645/
State : failure
== Summary ==
Error: patch https://patchwork.freedesktop.org/api/1.0/series/144645/revisions/1/mbox/ not applied
Applying: Regression on linux-next (next-20250205)
error: sha1 information is lacking or useless (kernel/module/main.c).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Regression on linux-next (next-20250205)
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Build failed, no error log produced
^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: Regression on linux-next (next-20250205)
2025-02-11 7:50 ` Mike Rapoport
@ 2025-02-11 12:30 ` Borah, Chaitanya Kumar
2025-02-12 6:45 ` Mike Rapoport
0 siblings, 1 reply; 7+ messages in thread
From: Borah, Chaitanya Kumar @ 2025-02-11 12:30 UTC (permalink / raw)
To: Mike Rapoport
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
Saarinen, Jani, Kurmi, Suresh Kumar, x86@kernel.org,
De Marchi, Lucas
Hello Mike,
> -----Original Message-----
> From: Mike Rapoport <rppt@kernel.org>
> Sent: Tuesday, February 11, 2025 1:21 PM
> To: Borah, Chaitanya Kumar <chaitanya.kumar.borah@intel.com>
> Cc: intel-gfx@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; De Marchi, Lucas
> <lucas.demarchi@intel.com>
> Subject: Re: Regression on linux-next (next-20250205)
>
> Hello Chaitanya,
>
> On Mon, Feb 10, 2025 at 06:52:35AM +0000, Borah, Chaitanya Kumar
> wrote:
> > Hello Mike,
> >
> > Hope you are doing well. I am Chaitanya from the linux graphics team in
> Intel.
> >
> > This mail is regarding a regression we are seeing in our CI runs[1] on linux-
> next repository.
> >
> > Since the version next-20250205 [2], we are seeing the following
> > regression
> >
> > ``````````````````````````````````````````````````````````````````````
> > ``````````` <4>[ 314.781734] kmemleak: Found object by alias at
> > 0xffffffffa0595000 <4>[ 314.781738] CPU: 11 UID: 0 PID: 6042 Comm:
> > i915_selftest Tainted: G U
> > 6.14.0-rc1-next-20250205-next-20250205-ged88b8b82c53+ #1 <4>[
> > 314.781741] Tainted: [U]=USER <4>[ 314.781741] Hardware name: ASUS
> > System Product Name/PRIME Z790-P WIFI, BIOS 0812 02/24/2023
> <4>[ 314.781742] Call Trace:
> > <4>[ 314.781743] <TASK>
> > <4>[ 314.781744] dump_stack_lvl+0x91/0xf0 <4>[ 314.781749]
> > dump_stack+0x10/0x20 <4>[ 314.781751] __lookup_object+0x90/0xa0
> <4>[
> > 314.781755] __find_and_get_object+0x6c/0x190 <4>[ 314.781758]
> > paint_ptr+0x1b/0xa0 <4>[ 314.781759] kmemleak_not_leak+0x33/0x70
> > <4>[ 314.781762] load_module+0xa20/0x2d10
> > ``````````````````````````````````````````````````````````````````````
> > ```````````
> > Details log can be found in [3].
>
> Does this fix it for you?
>
>
> diff --git a/kernel/module/main.c b/kernel/module/main.c index
> 4a02503836d7..a598888e7072 100644
> --- a/kernel/module/main.c
> +++ b/kernel/module/main.c
> @@ -1260,7 +1260,8 @@ static int module_memory_alloc(struct module
> *mod, enum mod_mem_type type)
> * *do* eventually get freed, but let's just keep things simple
> * and avoid *any* false positives.
> */
> - kmemleak_not_leak(ptr);
> + if (!mod->mem[type].is_rox)
> + kmemleak_not_leak(ptr);
>
> memset(ptr, 0, size);
> mod->mem[type].base = ptr;
>
>
Thank you for your reply.
Unfortunately, the change makes it worse. Our local system seems to be in continuous reboot.
Regards
Chaitanya
> > [1] https://intel-gfx-ci.01.org/tree/linux-next/combined-alt.html?
> > [2]
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/co
> > mmit/?h=next-20250205 [3]
> > https://intel-gfx-ci.01.org/tree/linux-next/next-20250205/bat-rpls-4/d
> > mesg0.txt [4]
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/co
> > mmit/?h=next-
> 20250205&id=64f6a4e10c05ed527f0f24b7954964255e0d3535
> >
> > Regards
> > Chaitanya
>
> --
> Sincerely yours,
> Mike.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Regression on linux-next (next-20250205)
2025-02-11 12:30 ` Borah, Chaitanya Kumar
@ 2025-02-12 6:45 ` Mike Rapoport
2025-02-13 17:30 ` Borah, Chaitanya Kumar
0 siblings, 1 reply; 7+ messages in thread
From: Mike Rapoport @ 2025-02-12 6:45 UTC (permalink / raw)
To: Borah, Chaitanya Kumar
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
Saarinen, Jani, Kurmi, Suresh Kumar, x86@kernel.org,
De Marchi, Lucas
On Tue, Feb 11, 2025 at 12:30:01PM +0000, Borah, Chaitanya Kumar wrote:
> Hello Mike,
>
> > -----Original Message-----
> > From: Mike Rapoport <rppt@kernel.org>
> > Sent: Tuesday, February 11, 2025 1:21 PM
> > To: Borah, Chaitanya Kumar <chaitanya.kumar.borah@intel.com>
> > Cc: intel-gfx@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; De Marchi, Lucas
> > <lucas.demarchi@intel.com>
> > Subject: Re: Regression on linux-next (next-20250205)
> >
> > Hello Chaitanya,
> >
> > On Mon, Feb 10, 2025 at 06:52:35AM +0000, Borah, Chaitanya Kumar
> > wrote:
> > > Hello Mike,
> > >
> > > Hope you are doing well. I am Chaitanya from the linux graphics team in
> > Intel.
> > >
> > > This mail is regarding a regression we are seeing in our CI runs[1] on linux-
> > next repository.
> > >
> > > Since the version next-20250205 [2], we are seeing the following
> > > regression
> > >
> > > ``````````````````````````````````````````````````````````````````````
> > > ``````````` <4>[ 314.781734] kmemleak: Found object by alias at
> > > 0xffffffffa0595000 <4>[ 314.781738] CPU: 11 UID: 0 PID: 6042 Comm:
> > > i915_selftest Tainted: G U
> > > 6.14.0-rc1-next-20250205-next-20250205-ged88b8b82c53+ #1 <4>[
> > > 314.781741] Tainted: [U]=USER <4>[ 314.781741] Hardware name: ASUS
> > > System Product Name/PRIME Z790-P WIFI, BIOS 0812 02/24/2023
> > <4>[ 314.781742] Call Trace:
> > > <4>[ 314.781743] <TASK>
> > > <4>[ 314.781744] dump_stack_lvl+0x91/0xf0 <4>[ 314.781749]
> > > dump_stack+0x10/0x20 <4>[ 314.781751] __lookup_object+0x90/0xa0
> > <4>[
> > > 314.781755] __find_and_get_object+0x6c/0x190 <4>[ 314.781758]
> > > paint_ptr+0x1b/0xa0 <4>[ 314.781759] kmemleak_not_leak+0x33/0x70
> > > <4>[ 314.781762] load_module+0xa20/0x2d10
> > > ``````````````````````````````````````````````````````````````````````
> > > ```````````
> > > Details log can be found in [3].
> >
> > Does this fix it for you?
> >
> >
> > diff --git a/kernel/module/main.c b/kernel/module/main.c index
> > 4a02503836d7..a598888e7072 100644
> > --- a/kernel/module/main.c
> > +++ b/kernel/module/main.c
> > @@ -1260,7 +1260,8 @@ static int module_memory_alloc(struct module
> > *mod, enum mod_mem_type type)
> > * *do* eventually get freed, but let's just keep things simple
> > * and avoid *any* false positives.
> > */
> > - kmemleak_not_leak(ptr);
> > + if (!mod->mem[type].is_rox)
> > + kmemleak_not_leak(ptr);
> >
> > memset(ptr, 0, size);
> > mod->mem[type].base = ptr;
> >
> >
>
> 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?
> Regards
>
> Chaitanya
>
> > > [1] https://intel-gfx-ci.01.org/tree/linux-next/combined-alt.html?
> > > [2]
> > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/co
> > > mmit/?h=next-20250205 [3]
> > > https://intel-gfx-ci.01.org/tree/linux-next/next-20250205/bat-rpls-4/d
> > > mesg0.txt [4]
> > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/co
> > > mmit/?h=next-
> > 20250205&id=64f6a4e10c05ed527f0f24b7954964255e0d3535
> > >
> > > Regards
> > > Chaitanya
> >
> > --
> > Sincerely yours,
> > Mike.
--
Sincerely yours,
Mike.
^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: Regression on linux-next (next-20250205)
2025-02-12 6:45 ` Mike Rapoport
@ 2025-02-13 17:30 ` Borah, Chaitanya Kumar
2025-02-14 9:08 ` Mike Rapoport
0 siblings, 1 reply; 7+ messages in thread
From: Borah, Chaitanya Kumar @ 2025-02-13 17:30 UTC (permalink / raw)
To: Mike Rapoport
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
Saarinen, Jani, Kurmi, Suresh Kumar, x86@kernel.org,
De Marchi, Lucas
> -----Original Message-----
> From: Mike Rapoport <rppt@kernel.org>
> Sent: Wednesday, February 12, 2025 12:15 PM
> To: Borah, Chaitanya Kumar <chaitanya.kumar.borah@intel.com>
> Cc: intel-gfx@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; De Marchi, Lucas
> <lucas.demarchi@intel.com>
> Subject: Re: Regression on linux-next (next-20250205)
>
> On Tue, Feb 11, 2025 at 12:30:01PM +0000, Borah, Chaitanya Kumar wrote:
> > Hello Mike,
> >
> > > -----Original Message-----
> > > From: Mike Rapoport <rppt@kernel.org>
> > > Sent: Tuesday, February 11, 2025 1:21 PM
> > > To: Borah, Chaitanya Kumar <chaitanya.kumar.borah@intel.com>
> > > Cc: intel-gfx@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; De Marchi, Lucas
> > > <lucas.demarchi@intel.com>
> > > Subject: Re: Regression on linux-next (next-20250205)
> > >
> > > Hello Chaitanya,
> > >
> > > On Mon, Feb 10, 2025 at 06:52:35AM +0000, Borah, Chaitanya Kumar
> > > wrote:
> > > > Hello Mike,
> > > >
> > > > Hope you are doing well. I am Chaitanya from the linux graphics
> > > > team in
> > > Intel.
> > > >
> > > > This mail is regarding a regression we are seeing in our CI
> > > > runs[1] on linux-
> > > next repository.
> > > >
> > > > Since the version next-20250205 [2], we are seeing the following
> > > > regression
> > > >
> > > > ``````````````````````````````````````````````````````````````````
> > > > ```` ``````````` <4>[ 314.781734] kmemleak: Found object by alias
> > > > at
> > > > 0xffffffffa0595000 <4>[ 314.781738] CPU: 11 UID: 0 PID: 6042 Comm:
> > > > i915_selftest Tainted: G U
> > > > 6.14.0-rc1-next-20250205-next-20250205-ged88b8b82c53+ #1 <4>[
> > > > 314.781741] Tainted: [U]=USER <4>[ 314.781741] Hardware name:
> > > > ASUS System Product Name/PRIME Z790-P WIFI, BIOS 0812 02/24/2023
> > > <4>[ 314.781742] Call Trace:
> > > > <4>[ 314.781743] <TASK>
> > > > <4>[ 314.781744] dump_stack_lvl+0x91/0xf0 <4>[ 314.781749]
> > > > dump_stack+0x10/0x20 <4>[ 314.781751] __lookup_object+0x90/0xa0
> > > <4>[
> > > > 314.781755] __find_and_get_object+0x6c/0x190 <4>[ 314.781758]
> > > > paint_ptr+0x1b/0xa0 <4>[ 314.781759] kmemleak_not_leak+0x33/0x70
> > > > <4>[ 314.781762] load_module+0xa20/0x2d10
> > > > ``````````````````````````````````````````````````````````````````
> > > > ````
> > > > ```````````
> > > > Details log can be found in [3].
> > >
> > > Does this fix it for you?
> > >
> > >
> > > diff --git a/kernel/module/main.c b/kernel/module/main.c index
> > > 4a02503836d7..a598888e7072 100644
> > > --- a/kernel/module/main.c
> > > +++ b/kernel/module/main.c
> > > @@ -1260,7 +1260,8 @@ static int module_memory_alloc(struct module
> > > *mod, enum mod_mem_type type)
> > > * *do* eventually get freed, but let's just keep things simple
> > > * and avoid *any* false positives.
> > > */
> > > - kmemleak_not_leak(ptr);
> > > + if (!mod->mem[type].is_rox)
> > > + kmemleak_not_leak(ptr);
> > >
> > > memset(ptr, 0, size);
> > > mod->mem[type].base = ptr;
> > >
> > >
> >
> > 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?
Regards
Chaitanya
>
> > Regards
> >
> > Chaitanya
> >
> > > > [1] https://intel-gfx-ci.01.org/tree/linux-next/combined-alt.html?
> > > > [2]
> > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.gi
> > > > t/co
> > > > mmit/?h=next-20250205 [3]
> > > > https://intel-gfx-ci.01.org/tree/linux-next/next-20250205/bat-rpls
> > > > -4/d
> > > > mesg0.txt [4]
> > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.gi
> > > > t/co
> > > > mmit/?h=next-
> > > 20250205&id=64f6a4e10c05ed527f0f24b7954964255e0d3535
> > > >
> > > > Regards
> > > > Chaitanya
> > >
> > > --
> > > Sincerely yours,
> > > Mike.
>
> --
> Sincerely yours,
> Mike.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Regression on linux-next (next-20250205)
2025-02-13 17:30 ` Borah, Chaitanya Kumar
@ 2025-02-14 9:08 ` Mike Rapoport
0 siblings, 0 replies; 7+ messages in thread
From: Mike Rapoport @ 2025-02-14 9:08 UTC (permalink / raw)
To: Borah, Chaitanya Kumar
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
Saarinen, Jani, Kurmi, Suresh Kumar, x86@kernel.org,
De Marchi, Lucas
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.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2025-02-14 9:08 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2025-02-11 8:44 ` ✗ Fi.CI.BUILD: failure for " Patchwork
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox