Re: 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"

On 2016/11/02 21:19, Brown, Aaron F wrote: > > From: Jack Suter [mailto:j...@suter.io] > > Sent: Tuesday, November 1, 2016 4:57 PM > > To: Kirsher, Jeffrey T > > Cc: intel-wired-...@lists.osuosl.org; bpoir...@suse.com; Brown, Aaron F > > ;

Re: 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"

On 2016/11/02 21:19, Brown, Aaron F wrote: > > From: Jack Suter [mailto:j...@suter.io] > > Sent: Tuesday, November 1, 2016 4:57 PM > > To: Kirsher, Jeffrey T > > Cc: intel-wired-...@lists.osuosl.org; bpoir...@suse.com; Brown, Aaron F > > ; jhod...@ucdavis.edu; linux- > > ker...@vger.kernel.org >

Re: 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"

> > 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

Re: 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"

> > 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

RE: 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"

-Original Message- From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On Behalf Of Brown, Aaron F Sent: Wednesday, November 02, 2016 11:20 PM To: Jack Suter ; Kirsher, Jeffrey T Cc: bpoir...@suse.com; jhod...@ucdavis.edu;

RE: 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"

-Original Message- From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On Behalf Of Brown, Aaron F Sent: Wednesday, November 02, 2016 11:20 PM To: Jack Suter ; Kirsher, Jeffrey T Cc: bpoir...@suse.com; jhod...@ucdavis.edu; intel-wired-...@lists.osuosl.org;

RE: 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 > To: Kirsher, Jeffrey T > Cc: intel-wired-...@lists.osuosl.org; bpoir...@suse.com; Brown, Aaron F > ; jhod...@ucdavis.edu; linux- > ker...@vger.kernel.org >

RE: 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 > To: Kirsher, Jeffrey T > Cc: intel-wired-...@lists.osuosl.org; bpoir...@suse.com; Brown, Aaron F > ; jhod...@ucdavis.edu; linux- > ker...@vger.kernel.org > Subject: Kernel regression introduced by "e1000e: Do

Re: 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"

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

Re: 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"

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

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 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

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 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