ux-
> > ker...@vger.kernel.org
> > Subject: Kernel regression introduced by "e1000e: Do not write lsc to ics in
> > msi-x mode" and/or "e1000e: Do not read ICR in Other interrupt"
> >
> > Hi there,
> >
> > I have some servers with
> > Reverting these two commits resolves the Link is Down/Link is Up
> > messages. This has been tested on about six servers so far and all have
> > stopped reporting these link flaps.
>
> Are you able to revert either of the patches independently, I don't
> recall if they were stand alone or not.
-kernel@vger.kernel.org
Subject: Re: [Intel-wired-lan] Kernel regression introduced by "e1000e: Do not
write lsc to ics in msi-x mode" and/or "e1000e: Do not read ICR in Other
interrupt"
> From: Jack Suter [mailto:j...@suter.io]
> Sent: Tuesday, November 1, 2016 4:57 PM
>
oduced by "e1000e: Do not write lsc to ics in
> msi-x mode" and/or "e1000e: Do not read ICR in Other interrupt"
>
> Hi there,
>
> I have some servers with an 82574L based NIC and recently upgraded from
> a 4.4 series kernel to 4.7. Upon doing so, servers with t
On 2016/11/01 19:56, Jack Suter wrote:
> Hi there,
>
> I have some servers with an 82574L based NIC and recently upgraded from
> a 4.4 series kernel to 4.7. Upon doing so, servers with this chipset
> have begun frequently reporting "Link is Down" and "Link is Up"
> messages. No other related netwo
Hi there,
I have some servers with an 82574L based NIC and recently upgraded from
a 4.4 series kernel to 4.7. Upon doing so, servers with this chipset
have begun frequently reporting "Link is Down" and "Link is Up"
messages. No other related network errors are reported by the kernel or
e1000e driv
6 matches
Mail list logo