Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:2 as permitted sender) client-ip=2620:137:e000::3:2;
Message-ID: <bcf1998e-5efa-4505-a8d2-3381c16de885@gmail.com>
Date:   Wed, 4 Oct 2023 19:50:29 +0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: what to do on no reproducer case? (was Re: Fwd: Uhhuh. NMI
 received for unknown reason 3d/2d/ on CPU xx)
To:     Thorsten Leemhuis <regressions@leemhuis.info>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Regressions <regressions@lists.linux.dev>
References: <0e6de51b-da1d-43f0-ffae-fb521febbe07@gmail.com>
 <ZQo8hzP-eRjXvtXf@debian.me>
 <2a298145-b6ec-4b4e-bd45-0cddf62b6052@leemhuis.info>
Content-Language: en-US
From:   Bagas Sanjaya <bagasdotme@gmail.com>
In-Reply-To: <2a298145-b6ec-4b4e-bd45-0cddf62b6052@leemhuis.info>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 21/09/2023 15:10, Thorsten Leemhuis wrote:
> On 20.09.23 02:27, Bagas Sanjaya wrote:
>> This regression looks stalled: on Bugzilla, the reporter keeps asking to me,
>> for which I'm not the expert of involved subsystem. And apparently, he still
>> had not any reproducer yet (is it triggered by random chance?). Should I
>> mark this as inconclusive?
> 
> 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

-- 
An old man doll... just what I always wanted! - Clara