From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Conor Dooley <conor@kernel.org>, Jakub Kicinski <kuba@kernel.org>
Cc: "Fuxbrumer, Devora" <devora.fuxbrumer@intel.com>,
regressions@lists.linux.dev, intel-wired-lan@lists.osuosl.org,
Ivan Smirnov <isgsmirnov@gmail.com>,
"Ruinskiy, Dima" <dima.ruinskiy@intel.com>,
"Avivi, Amir" <amir.avivi@intel.com>
Subject: Re: [Intel-wired-lan] igc kernel module crashes on new hardware (Intel Ethernet I225-V)
Date: Sun, 20 Nov 2022 11:32:36 +0100 [thread overview]
Message-ID: <8117aac8-947e-49ca-c2b1-ef45c2914975@leemhuis.info> (raw)
In-Reply-To: <Y3gTdsg4l71L0vz9@spud>
On 19.11.22 00:21, Conor Dooley wrote:
> On Fri, Nov 18, 2022 at 02:54:43PM -0800, Jakub Kicinski wrote:
>> On Fri, 18 Nov 2022 22:43:29 +0000 Conor Dooley wrote:
>>>> Is there any update for the community? More and more folks are asking. We
>>>> are all techies and happy to help debug.
>>>
>>> Vested interest since I am suffering from the same issue (X670E-F
>>> Gaming), but is it okay to add this to regzbot? Not sure whether it
>>> counts as a regression or not since it's new hw with the existing driver,
>>> but this seems to be falling through the cracks without a response for
>>> several weeks.
>>
>> Dunno, Thorsten's will decide. The line has to be drawn somewhere
>> on "vendor doesn't care about Linux support" vs "we broke uAPI".
>> This is the kind of situation I was alluding to in my line of
>> questioning at the maintainer summit: https://lwn.net/Articles/908324/
>
> Yeah & it is /regression/ tracking which I don't (or rather didn't)
> consider this situation to be.
Yeah, looks like this is not something that look track-worthy for
regzbot -- at least for now, maybe it one day makes sense to use and
improved regzbot for bug reports as well, but I'd like to focus on
establishing regression tracking properly first, which still requires a
lot of work.
> I'm generally a little unsure as to when
> I should trigger regzbot in general:
> - immediately when I find something?
Yes, ideally, as documented here:
https://docs.kernel.org/admin-guide/reporting-regressions.html
> - only if it goes a while with nothing constructive?
But that is fine as well. But FWIW, we all don't want bureaucracy. Even
I don't add each and every regression I see to the tracking yet.
> - is it okay to use it outside of "this used to work and now doesnt"?
Guess I should clarify that this is unwanted in above doc.
Ciao, Thorsten
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Conor Dooley <conor@kernel.org>, Jakub Kicinski <kuba@kernel.org>
Cc: Ivan Smirnov <isgsmirnov@gmail.com>,
"Neftin, Sasha" <sasha.neftin@intel.com>,
"Fuxbrumer, Devora" <devora.fuxbrumer@intel.com>,
intel-wired-lan@lists.osuosl.org, "Ruinskiy,
Dima" <dima.ruinskiy@intel.com>,
"Avivi, Amir" <amir.avivi@intel.com>,
regressions@lists.linux.dev
Subject: Re: [Intel-wired-lan] igc kernel module crashes on new hardware (Intel Ethernet I225-V)
Date: Sun, 20 Nov 2022 11:32:36 +0100 [thread overview]
Message-ID: <8117aac8-947e-49ca-c2b1-ef45c2914975@leemhuis.info> (raw)
In-Reply-To: <Y3gTdsg4l71L0vz9@spud>
On 19.11.22 00:21, Conor Dooley wrote:
> On Fri, Nov 18, 2022 at 02:54:43PM -0800, Jakub Kicinski wrote:
>> On Fri, 18 Nov 2022 22:43:29 +0000 Conor Dooley wrote:
>>>> Is there any update for the community? More and more folks are asking. We
>>>> are all techies and happy to help debug.
>>>
>>> Vested interest since I am suffering from the same issue (X670E-F
>>> Gaming), but is it okay to add this to regzbot? Not sure whether it
>>> counts as a regression or not since it's new hw with the existing driver,
>>> but this seems to be falling through the cracks without a response for
>>> several weeks.
>>
>> Dunno, Thorsten's will decide. The line has to be drawn somewhere
>> on "vendor doesn't care about Linux support" vs "we broke uAPI".
>> This is the kind of situation I was alluding to in my line of
>> questioning at the maintainer summit: https://lwn.net/Articles/908324/
>
> Yeah & it is /regression/ tracking which I don't (or rather didn't)
> consider this situation to be.
Yeah, looks like this is not something that look track-worthy for
regzbot -- at least for now, maybe it one day makes sense to use and
improved regzbot for bug reports as well, but I'd like to focus on
establishing regression tracking properly first, which still requires a
lot of work.
> I'm generally a little unsure as to when
> I should trigger regzbot in general:
> - immediately when I find something?
Yes, ideally, as documented here:
https://docs.kernel.org/admin-guide/reporting-regressions.html
> - only if it goes a while with nothing constructive?
But that is fine as well. But FWIW, we all don't want bureaucracy. Even
I don't add each and every regression I see to the tracking yet.
> - is it okay to use it outside of "this used to work and now doesnt"?
Guess I should clarify that this is unwanted in above doc.
Ciao, Thorsten
next prev parent reply other threads:[~2022-11-20 10:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPAtJa_o5q-sU+AD=G3y43H_5pBKnOZTQGXM99uszPXNkn8Z9A@mail.gmail.com>
2022-11-01 0:05 ` [Intel-wired-lan] igc kernel module crashes on new hardware (Intel Ethernet I225-V) Jakub Kicinski
2022-11-01 16:20 ` Neftin, Sasha
2022-11-02 16:54 ` Ivan Smirnov
2022-11-02 17:53 ` Ivan Smirnov
2022-11-10 11:44 ` Ivan Smirnov
2022-11-16 22:23 ` Ivan Smirnov
2022-11-18 22:43 ` Conor Dooley
2022-11-18 22:43 ` Conor Dooley
2022-11-18 22:54 ` Jakub Kicinski
2022-11-18 22:54 ` Jakub Kicinski
2022-11-18 23:21 ` Conor Dooley
2022-11-18 23:21 ` Conor Dooley
2022-11-19 18:06 ` Neftin, Sasha
2022-11-19 18:06 ` Neftin, Sasha
2022-11-20 19:55 ` Conor Dooley
2022-11-20 19:55 ` Conor Dooley
2022-12-21 17:30 ` Conor Dooley
2022-12-21 17:30 ` Conor Dooley
2022-12-31 15:02 ` Conor Dooley
2022-12-31 15:02 ` Conor Dooley
2023-01-02 11:09 ` Conor Dooley
2023-01-02 11:09 ` Conor Dooley
2022-11-20 10:32 ` Thorsten Leemhuis [this message]
2022-11-20 10:32 ` Thorsten Leemhuis
2022-11-20 18:40 ` Conor Dooley
2022-11-20 18:40 ` Conor Dooley
2022-11-23 11:47 ` Ruinskiy, Dima
2022-11-24 6:20 ` Ivan Smirnov
2022-11-24 13:55 ` Ruinskiy, Dima
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=8117aac8-947e-49ca-c2b1-ef45c2914975@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=amir.avivi@intel.com \
--cc=conor@kernel.org \
--cc=devora.fuxbrumer@intel.com \
--cc=dima.ruinskiy@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=isgsmirnov@gmail.com \
--cc=kuba@kernel.org \
--cc=regressions@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.