From owner-freebsd-bugs@freebsd.org Mon Sep 30 16:50:46 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id ABE7F12C53A for ; Mon, 30 Sep 2019 16:50:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 46hpLZ48Qnz48tm for ; Mon, 30 Sep 2019 16:50:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 8E67A12C538; Mon, 30 Sep 2019 16:50:46 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8E2C612C537 for ; Mon, 30 Sep 2019 16:50:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46hpLZ3FSwz48tl for ; Mon, 30 Sep 2019 16:50:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 52DC1597D for ; Mon, 30 Sep 2019 16:50:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x8UGokYZ060448 for ; Mon, 30 Sep 2019 16:50:46 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x8UGokDj060432 for bugs@FreeBSD.org; Mon, 30 Sep 2019 16:50:46 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 240944] System Crash with Intel 82571EB NIC with AMD Piledriver and Steamroller APUs Date: Mon, 30 Sep 2019 16:50:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: tinfever6@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Sep 2019 16:50:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240944 Bug ID: 240944 Summary: System Crash with Intel 82571EB NIC with AMD Piledriver and Steamroller APUs Product: Base System Version: 12.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: tinfever6@gmail.com When using an Intel 82571EB quad-port gigabit NIC (HP NC364T) in a system w= ith an AMD Piledriver or Steamroller APU, any taxing Ethernet workload will cau= se the entire system to either permanently lock up (requiring a hard reboot by holding down the power button to reset), or crash and reboot. Initial discussion of this issue can be found in the pfSense subreddit: https://www.reddit.com/r/PFSENSE/comments/da6nh7/multiport_intel_82571ebbas= ed_network_cards_not/ I have confirmed this issue is present even on the FreeBSD 12.0 release so = it is not an issue introduced by pfSense or OPNsense. Hardware used for testing and reproduction: HP T730 thin client AMD RX-427BB APU (4 core) 4GB RAM 16GB SSD HP NC364T Network Controller (Uses Intel 82571EB chipset) Steps to reproduce: 1. Download "FreeBSD-12.0-RELEASE-amd64-mini-memstick.img" 2. Used Etcher to load to flash drive. 3. Boot up in UEFI or Legacy to flash drive 4. Run as live CD instead of installer 5. Run "dhclient em3" to get network access. 6. Run command "fetch http://speedtest.tele2.net/1GB.zip -o /dev/null" 7. Crash happens within the first 60 seconds. When it crashes, the system goes 100% unresponsive. No amount of Ctl-Alt-Del will do anything. I have to hold power button to do a hard reboot. System h= as been left in unresponsive state for 12+ hours with no change. There are no = log entries or bug checks present (that I have seen) Troubleshooting done: 1. Issue reoccurs using both UEFI and Legacy boot methods 2. Issue reoccurs with onboard NIC disabled 3. Issue reoccurs using included 7.6.1 and latest 7.7.5 Intel drivers 4. Issue reoccurs when using either USB or SSD boot media 5. Hardware works perfectly fine when booting to Ubuntu live USB for testing 6. Hardware passed memtest64+ @ 4 passes Other user reports (see Reddit discussion link) indicate that: 1. Issue reoccurs with on every NC364T card when testing several of them 2. Issue occurs on NC360T (dual-port Intel 82571EB NIC) 3. Issue does not occur with NC112T (Intel 82574L-based single port NIC) 4. Issue occurs with other versions of pfSense including 2.1.5, 2.2.4, 2.3.= 3, and 2.5.0 (20190928). I have not looked up the correlation between pfSense = and FreeBSD versions. I'm no Linux/Unix guru, nor do I have very much time I can allocate to seei= ng this through to a resolution, but I will try to assist in any testing or da= ta collection needed to hopefully address this issue. Thanks. --=20 You are receiving this mail because: You are the assignee for the bug.=