From: Conor Dooley <conor@kernel.org>
To: "Neftin, Sasha" <sasha.neftin@intel.com>
Cc: "Fuxbrumer, Devora" <devora.fuxbrumer@intel.com>,
helgaas@kernel.org, regressions@lists.linux.dev, "Meir,
NaamaX" <naamax.meir@intel.com>,
Ivan Smirnov <isgsmirnov@gmail.com>,
intel-wired-lan@lists.osuosl.org,
Jakub Kicinski <kuba@kernel.org>,
"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: Mon, 2 Jan 2023 11:09:10 +0000 [thread overview]
Message-ID: <Y7K7VgArVFijJMY4@spud> (raw)
In-Reply-To: <Y7BPIYsBXN0ivoLE@spud>
[-- Attachment #1.1: Type: text/plain, Size: 545 bytes --]
On Sat, Dec 31, 2022 at 03:02:57PM +0000, Conor Dooley wrote:
> I didn't actually give the bios stuff a go in the end. I figured that
> changing everything at once would likely not be a good idea - but what I
> did do was try v6.1.1 & have now been running for 50-something hours
> without any issues while using the igc iface.
Bah, it died last night about about the 90 hour mark. Still an order of
magnitude longer than I had got it to work sequentially for before, but
not fixed :(
I'll give the bios a go I suppose, sorry for the noise!
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 162 bytes --]
_______________________________________________
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: Conor Dooley <conor@kernel.org>
To: "Neftin, Sasha" <sasha.neftin@intel.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
Ivan Smirnov <isgsmirnov@gmail.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, "Lifshits,
Vitaly" <vitaly.lifshits@intel.com>,
"naamax.meir" <naamax.meir@linux.intel.com>,
"Meir, NaamaX" <naamax.meir@intel.com>,
helgaas@kernel.org
Subject: Re: [Intel-wired-lan] igc kernel module crashes on new hardware (Intel Ethernet I225-V)
Date: Mon, 2 Jan 2023 11:09:10 +0000 [thread overview]
Message-ID: <Y7K7VgArVFijJMY4@spud> (raw)
In-Reply-To: <Y7BPIYsBXN0ivoLE@spud>
[-- Attachment #1: Type: text/plain, Size: 545 bytes --]
On Sat, Dec 31, 2022 at 03:02:57PM +0000, Conor Dooley wrote:
> I didn't actually give the bios stuff a go in the end. I figured that
> changing everything at once would likely not be a good idea - but what I
> did do was try v6.1.1 & have now been running for 50-something hours
> without any issues while using the igc iface.
Bah, it died last night about about the 90 hour mark. Still an order of
magnitude longer than I had got it to work sequentially for before, but
not fixed :(
I'll give the bios a go I suppose, sorry for the noise!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-01-03 16:48 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 [this message]
2023-01-02 11:09 ` Conor Dooley
2022-11-20 10:32 ` Thorsten Leemhuis
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=Y7K7VgArVFijJMY4@spud \
--to=conor@kernel.org \
--cc=amir.avivi@intel.com \
--cc=devora.fuxbrumer@intel.com \
--cc=dima.ruinskiy@intel.com \
--cc=helgaas@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=isgsmirnov@gmail.com \
--cc=kuba@kernel.org \
--cc=naamax.meir@intel.com \
--cc=regressions@lists.linux.dev \
--cc=sasha.neftin@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 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.