AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Linux regressions mailing list" <regressions@lists.linux.dev>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Pan, Xinhui" <Xinhui.Pan@amd.com>,
	"David Airlie" <airlied@gmail.com>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Hawking Zhang" <Hawking.Zhang@amd.com>, "Le Ma" <le.ma@amd.com>,
	"Tao Zhou" <tao.zhou1@amd.com>,
	"YiPeng Chai" <YiPeng.Chai@amd.com>,
	"Jiadong.Zhu" <Jiadong.Zhu@amd.com>,
	"Yang Wang" <KevinYang.Wang@amd.com>,
	"Candice Li" <candice.li@amd.com>,
	"Xiaojian Du" <Xiaojian.Du@amd.com>,
	"Likun Gao" <Likun.Gao@amd.com>,
	"Linux AMDGPU" <amd-gfx@lists.freedesktop.org>,
	"Linux DRI Development" <dri-devel@lists.freedesktop.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Cc: "Azamat S. Kalimoulline" <turtle@bazon.ru>,
	max <kernel-ODwfxu5zp4@maxxor.org>
Subject: Re: Fwd: Kernel 5.11 crashes when it boots, it produces black screen.
Date: Wed, 10 May 2023 20:29:44 +0700	[thread overview]
Message-ID: <cfb6bcf7-a6c2-7e52-d7dd-3e054574942e@gmail.com> (raw)
In-Reply-To: <9cf29c20-5b82-89bb-0927-e6f66b3bd8d5@leemhuis.info>

On 5/10/23 16:51, Linux regression tracking (Thorsten Leemhuis) wrote:
> Bagas, thx for all your help with regression tracking, much appreciated
> (side note, as I'm curious for a while already: what is your motivation?
> Just want to help? But whatever, any help is great!).
> 

I did this when I was on "gabut" (an Indonesian slang term that means
doing nothing but get rewarded). In other words, I was finding a task
when there is no documentation review or issues that needs to be worked
on.

> That being said: I'm not sure if I like what you did in this particular
> case, as developers might start getting annoyed by regression tracking
> if we throw too many bug reports of lesser quality before their feet --
> and then they might start to ignore us, which we really need to prevent.
> 
> That's why I would not have forwarded that report at this point of time,
> mainly for these reasons:
> 
>  * The initial report is quite old already, as it fall through the
> cracks (not good, but happens; sorry Azamat!). Hence in this case it
> would definitely be better to *first* ask the reporter to check if the
> problem still happens with latest mainline (or at least latest stable)
> before involving the kernel developers, as it might have been fixed
> already.
> 

Oh dear, I have already seen the bug age (two years old, from Reported
date).

>  * This might not be a amdgpu bug at all; in fact the other bug the
> reporter mentioned was an iommu thing. Hence this might be one of those
> regressions where a bisection is the only way to get down to the
> problem. Sure, sending a few developers a quick inquiry along the lines
> of "do you maybe have an idea what's up there" is fine, but that's not
> what you did in your mail. Your list of recipients is also quite long;
> that's risky: if you do that too often, as then they might start
> ignoring mail from you.
> 

Oops, I was blindly copy-paste get_maintainer.pl list at that time.

Anyway, thanks for the reminder!

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


  reply	other threads:[~2023-05-11  6:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10  8:26 Fwd: Kernel 5.11 crashes when it boots, it produces black screen Bagas Sanjaya
2023-05-10  9:51 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-10 13:29   ` Bagas Sanjaya [this message]
2023-05-20 13:50 ` Bagas Sanjaya

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=cfb6bcf7-a6c2-7e52-d7dd-3e054574942e@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=Hawking.Zhang@amd.com \
    --cc=Jiadong.Zhu@amd.com \
    --cc=KevinYang.Wang@amd.com \
    --cc=Likun.Gao@amd.com \
    --cc=Xiaojian.Du@amd.com \
    --cc=Xinhui.Pan@amd.com \
    --cc=YiPeng.Chai@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=candice.li@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel-ODwfxu5zp4@maxxor.org \
    --cc=le.ma@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=tao.zhou1@amd.com \
    --cc=turtle@bazon.ru \
    /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