From: "Lifshits, Vitaly" <vitaly.lifshits@intel.com>
To: Jesper Juhl <jesperjuhl76@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
"Tony Nguyen" <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
<intel-wired-lan@lists.osuosl.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] igc: Network failure, reboot required: igc: Failed to read reg 0xc030!
Date: Sun, 15 Sep 2024 10:03:45 +0300 [thread overview]
Message-ID: <534406c8-80d3-4978-702a-afa2f33573f7@intel.com> (raw)
In-Reply-To: <CAHaCkmfkD0GkT6OczjMVZ9x-Ucr9tS0Eo8t_edDgrrPk-ZNc-A@mail.gmail.com>
On 9/14/2024 12:52 AM, Jesper Juhl wrote:
> On Fri, 13 Sept 2024 at 09:02, Lifshits, Vitaly
> <vitaly.lifshits@intel.com> wrote:
>> On 9/12/2024 10:45 PM, Jesper Juhl wrote:
>>>> Would you be able to decode the stack trace? It may be helpful
>>>> to figure out which line of code this is:
>>>>
>>>> igc_update_stats+0x8a/0x6d0 [igc
>>>> 22e0a697bfd5a86bd5c20d279bfffd
>>>> 131de6bb32]
>>> Of course. Just tell me what to do.
>>>
>>> - Jesper
>>>
>>> On Thu, 12 Sept 2024 at 17:37, Jakub Kicinski <kuba@kernel.org> wrote:
>>>> On Thu, 12 Sep 2024 15:03:14 +0200 Jesper Juhl wrote:
>>>>> It just happened again.
>>>>> Same error message, but different stacktrace:
>>>> Hm, I wonder if it's power management related or the device just goes
>>>> sideways for other reasons. The crashes are in accessing statistics
>>>> and the relevant function doesn't resume the device. But then again,
>>>> it could just be that stats reading is the most common control path
>>>> operation.
>>>>
> I doubt it's related to power management since the machine is not idle
> when this happens.
>
>>>> Hopefully the Intel team can help.
>>>>
>>>> Would you be able to decode the stack trace? It may be helpful
>>>> to figure out which line of code this is:
>>>>
>>>> igc_update_stats+0x8a/0x6d0 [igc
>>>> 22e0a697bfd5a86bd5c20d279bfffd131de6bb32]
> I didn't manage to decode it with the distro kernel. I'll build a
> custom kernel straight from the git repo and wait for the problem to
> happen again, then I'll report back with a decoded trace.
>
>> Hi Jasper,
>>
>> I agree with Kuba that it might be related to power management, and I
>> wonder if it can be related to PTM.
>> Anyway, can you please share the following information?
>>
>> 1. Is runtime D3 enabled? (you can check the value in
>> /sys/devices/pci:(pci SBDF)/power/control)
> $ cat /sys/devices/pci0000\:00/power/control
> auto
>
>> 2. What is the NVM version that your NIC has? (ethtool -i eno1)
> $ sudo ethtool -i eno1
> driver: igc
> version: 6.10.9-arch1-2
> firmware-version: 1082:8770
> expansion-rom-version:
> bus-info: 0000:0c:00.0
> supports-statistics: yes
> supports-test: yes
> supports-eeprom-access: yes
> supports-register-dump: yes
> supports-priv-flags: yes
I see that you have an old NVM version, 1.82.
In the recent versions, some power and stability bug fixes were
introduced to the NVM.
These fixes in the NVM might resolve completely your issue.
Therefore, I'd like to ask you to contact your board vendor, Asus, to
update the NVM to the latest version.
>> 3. Can you please elaborate on you bug?
>> Does it happen while the system is in idle state?
> I don't know. It might, but I've only ever observed it while actively
> using the machine. I usually notice the problem when watching a
> youtube video or playing an online game and suddenly the network
> connection dies.
>
>> Does it run any
>> traffic?
> Yes, there's usually always network traffic when the problem occurs.
>
>> What is the system's link partner (switch? other NIC?)
> It's a "tp-link" switch: TL-SG105-M2 5-Port 2.5G Multi-Gigabit Desktop Switch
>
> Kind regards
> Jesper Juhl
next prev parent reply other threads:[~2024-09-15 7:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 15:10 igc: Network failure, reboot required: igc: Failed to read reg 0xc030! Jesper Juhl
2024-09-12 13:03 ` Jesper Juhl
2024-09-12 15:37 ` Jakub Kicinski
2024-09-12 19:45 ` Jesper Juhl
2024-09-13 0:46 ` Jakub Kicinski
2024-09-13 7:02 ` [Intel-wired-lan] " Lifshits, Vitaly
2024-09-13 21:52 ` Jesper Juhl
2024-09-15 7:03 ` Lifshits, Vitaly [this message]
2024-09-17 11:39 ` Jesper Juhl
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=534406c8-80d3-4978-702a-afa2f33573f7@intel.com \
--to=vitaly.lifshits@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesperjuhl76@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@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