From: Jakub Kicinski <kuba@kernel.org>
To: Conor Dooley <conor@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: Fri, 18 Nov 2022 14:54:43 -0800 [thread overview]
Message-ID: <20221118145443.427ecf10@kernel.org> (raw)
In-Reply-To: <Y3gKkYeijrAIhxjc@spud>
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/
Finding a kernel release which does not suffer from the problem
would certainly strengthen your case.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2022-11-18 22:54 UTC|newest]
Thread overview: 19+ 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:54 ` Jakub Kicinski [this message]
2022-11-18 23:21 ` Conor Dooley
2022-11-19 18:06 ` Neftin, Sasha
2022-11-20 19:55 ` Conor Dooley
2022-12-21 17:30 ` Conor Dooley
2022-12-31 15:02 ` Conor Dooley
2023-01-02 11:09 ` Conor Dooley
2022-11-20 10:32 ` Thorsten Leemhuis
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=20221118145443.427ecf10@kernel.org \
--to=kuba@kernel.org \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox