linux-kernel - [PATCH RFC 0/2] e1000e: 82574 also needs ASPM L1 completely disabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1335216578-21542-1-git-send-email-bootc@bootc.net>
Date:	Mon, 23 Apr 2012 22:29:36 +0100
From:	Chris Boot <bootc@...tc.net>
To:	e1000-devel@...ts.sourceforge.net, netdev@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org, nix@...eri.org.uk,
	carolyn.wyborny@...el.com, Chris Boot <bootc@...tc.net>
Subject: [PATCH RFC 0/2] e1000e: 82574 also needs ASPM L1 completely disabled

After much toing and froing on LKML, netdev and the e1000 mailing lists
over the past few months we've determined that the 82574L needs to have
both ASPM L0s and L1 disabled or else it's likely to lock up. This
little series does just that, also cleaning up some now-unnecessary code
that disables L1 on the 82573 and 82574 if the MTU is greater than 1500
bytes.

Please note I haven't as-yet tested this code at all, but I do know that
disabling ASPM L1 on these NICs (using setpci) fixes the hangs that I
have been seeing on my Supermicro servers with X9SCL-F boards. I hope to
get the chance to install an updated kernel on my two afftected servers
later this week.

Chris Boot (2):
  e1000e: Disable ASPM L1 on 82574
  e1000e: Remove special case for 82573/82574 ASPM L1 disablement

 drivers/net/ethernet/intel/e1000e/82571.c  |    3 ++-
 drivers/net/ethernet/intel/e1000e/netdev.c |    8 --------
 2 files changed, 2 insertions(+), 9 deletions(-)

-- 
1.7.10

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/