Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Neftin, Sasha" <sasha.neftin@intel.com>
To: Jakub Kicinski <kuba@kernel.org>,
	Ivan Smirnov <isgsmirnov@gmail.com>,
	"Avivi, Amir" <amir.avivi@intel.com>,
	naamax.meir <naamax.meir@linux.intel.com>,
	"Fuxbrumer, Devora" <devora.fuxbrumer@intel.com>
Cc: "Ruinskiy, Dima" <dima.ruinskiy@intel.com>,
	intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] igc kernel module crashes on new hardware (Intel Ethernet I225-V)
Date: Tue, 1 Nov 2022 18:20:56 +0200	[thread overview]
Message-ID: <03f7dc73-3e7c-1e6d-275f-85539493cd7f@intel.com> (raw)
In-Reply-To: <20221031170535.77be0eb5@kernel.org>

On 11/1/2022 02:05, Jakub Kicinski wrote:
> CC: intel-wired
> 
> On Sun, 30 Oct 2022 14:44:57 -0600 Ivan Smirnov wrote:
>> Hi folks,
>>
>> I found your commits on the linux kernel igc
>> <https://github.com/torvalds/linux/commits/master/drivers/net/ethernet/intel/igc>
>> folder. There appears to be a bug with the igc kernel module on Intel
>> I225-V chips.
>>
>> Specifically, the probe fails at startup with error: "igc: probe of
>> 0000:06:00.0 failed with error -13". When it does load, it crashes after a
>> few hours with error "igc failed to read reg 0xc030".
>>
Could you provide dmesg -w -T | grep -i igc on the boot stage? ethtool -i?
I've cc'd our PAE expert Amir who also could try to look at this problem.

>> There are several affected users posting on
>> https://www.reddit.com/r/buildapc/comments/xypn1m/network_card_intel_ethernet_controller_i225v_igc/
>> with more details.
>>
>> Could I help you debug this? This problem has been reproduced on the
>> following setups:
>>
>> 1. Asus TUF-GAMING-Z690-PLUS-WIFI-D4
>> <https://www.asus.com/motherboards-components/motherboards/tuf-gaming/tuf-gaming-z690-plus-wifi-d4/>
>> on
>> Arch Linux, kernel 6.0.2-arch1-1
>> 2. rog strix x670e-e gaming wifi
>> <https://rog.asus.com/us/motherboards/rog-strix/rog-strix-x670e-e-gaming-wifi-model/>
>> on
>> Proxmox 7, as well as Ubuntu Linux (kernel 5.19, I believe)
>>
>> I'm happy to load any debug modules or provide additional logs as per
>> your request.
>>
>> Thank you
>>
>>
>>
>>
>> --
>> Ivan Smirnov
>> https://ivans.io/ | https://blog.ivansmirnov.name/
>> https://www.linkedin.com/in/ismirnov |
>> *https://ivansmirnov.name/ <https://ivansmirnov.name/>*
>> *https://github.com/issmirnov <https://ivansmirnov.name/>*
> 

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

  reply	other threads:[~2022-11-01 16:21 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 [this message]
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
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=03f7dc73-3e7c-1e6d-275f-85539493cd7f@intel.com \
    --to=sasha.neftin@intel.com \
    --cc=amir.avivi@intel.com \
    --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=naamax.meir@linux.intel.com \
    /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