[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20231005152815.GA630707@angband.pl>
Date: Thu, 5 Oct 2023 17:28:15 +0200
From: Adam Borowski <kilobyte@...band.pl>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: Thorsten Leemhuis <regressions@...mhuis.info>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Regressions <regressions@...ts.linux.dev>
Subject: Re: what to do on no reproducer case? (was Re: Fwd: Uhhuh. NMI
received for unknown reason 3d/2d/ on CPU xx)
On Wed, Oct 04, 2023 at 07:50:29PM +0700, Bagas Sanjaya wrote:
> On 21/09/2023 15:10, Thorsten Leemhuis wrote:
> > Yes, without a reliable bisection result there sometimes is not much we
> > can do -- apart from prodding various developers directly and asking for
> > help or an idea. But in this case that's not worth it afaics, as
> > messages like
> > https://lore.kernel.org/all/e08e33d5-4f6d-91aa-f335-9404d16a983c@amd.com/
> > indicate that it might be a hardware problem and not really a
> > regression. Hence:
> >
> > #regzbot resolve: inconclusive: not bisected and might be a hardware
> > problem after all
> Thanks for the tip! Now to fix up:
>
> #regzbot inconclusive: regression not bisected - possibly hardware issue
This doesn't seem to be a regression, I'm seeing this (reason 2c/3c) since
forever (2019) on my box (2990WX), up to current -rc kernels.
Of course, it might be a different problem that results in same message,
but I don't pretend to have a clue about the cause -- just reporting.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Q: Is it ok to combine wired, wifi, and/or bluetooth connections
⢿⡄⠘⠷⠚⠋⠀ in wearable computing?
⠈⠳⣄⠀⠀⠀⠀ A: No, that would be mixed fabric, which Lev19:19 forbids.
Powered by blists - more mailing lists