Re: [Intel-wired-lan] igc kernel module crashes on new hardware (Intel Ethernet I225-V)

From: "Neftin, Sasha" <sasha.neftin@intel.com>
To: Conor Dooley <conor@kernel.org>, Jakub Kicinski <kuba@kernel.org>
Cc: "Fuxbrumer, Devora" <devora.fuxbrumer@intel.com>,
	regressions@lists.linux.dev, "Meir,
	NaamaX" <naamax.meir@intel.com>,
	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: Sat, 19 Nov 2022 20:06:05 +0200	[thread overview]
Message-ID: <a15508df-eab4-ce00-7340-69323c462fdc@intel.com> (raw)
In-Reply-To: <Y3gTdsg4l71L0vz9@spud>

On 11/19/2022 01: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. I'm generally a little unsure as to when
> I should trigger regzbot in general:
> - immediately when I find something?
> - only if it goes a while with nothing constructive?
> - is it okay to use it outside of "this used to work and now doesnt"?
> 
> Either way, but I did some more googling and found this reddit thread:
> https://www.reddit.com/r/intel/comments/lqb4km/for_people_having_i225v_connection_issues/
> 
> That's being reported against windows & I dunno if the dude is using
> firmware and driver interchangeably etc. But the disabling power saving
> etc sounds oddly like the issue we have here, since that was a proposed
> workaround in Ivan's 2022 reddit thread.
> 
> Supposedly I am on firmware-version 1082:8770, but /I/ I have no idea
> how that corresponds to windows versioning. That may lend some credence
> to your assertion about firmware being the source of many issues.
> 
>> Finding a kernel release which does not suffer from the problem
>> would certainly strengthen your case.
> 
> Aye, likely to be a little difficult to do a meaningful bisection for
> me at least, since the motherboard I have with the problem is an AM5
> one for the new Zen4 stuff. I'm not an x86 person, so not entirely
> sure when that support landed. I may do some poking tomorrow..
> 
I do not think we can resolve this problem on this forum.
In early Ivan's report was reported error to netdev "PCIe link lost, 
device now detached"). Since the PCIe link unexpectedly drops it could 
lead to many problems (not only crashes).
Before you go to SW/FW bisection (change FW(NVM), go back with a kernel 
version) - please, contact your board vendor (ASUS). Why PCIe link drop?
Circuit problem on board, the system performs power management flows and 
does not stop the driver.

"failed to read reg 0xc030" (just symptom) happen after PCIe link lost.

_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan