Date: Wed, 18 Nov 2020 00:42:58 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 251226] ixgbe: resume from real S3 suspend resets the whole system (Intel X520 NIC) Message-ID: <bug-251226-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251226 Bug ID: 251226 Summary: ixgbe: resume from real S3 suspend resets the whole system (Intel X520 NIC) Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: greg@unrelenting.technology The ix driver seems to have actual suspend-resume support, which is nice. However.. With this device ("X520"): ix0@pci0:44:0:0: class=3D0x020000 rev=3D0x01 hdr=3D0x00 vendor=3D0x8= 086 device=3D0x10fb subvendor=3D0x8086 subdevice=3D0x0006 vendor =3D 'Intel Corporation' device =3D '82599ES 10-Gigabit SFI/SFP+ Network Connection' everything works great under debug.acpi.suspend_bounce=3D1, but resuming fr= om *real* S3 sleep results in failure =E2=80=94 namely instant system reset, w= ithout a coredump :( How to even debug this? Mainboard LED blinks, GPU LEDs turn on, NIC LEDs turn on and boom reset, mainboard LED blinks again indicating reboot, system boots again freshly. If that matters: the platform is AMD X370 (1st gen Ryzen), the NIC is connecte= d to the bottom (chipset) PCIe slot. However a Mellanox (mlx4en) NIC in the same slot does survive suspend-resume cycles, apart from panicking sometimes bec= ause there's no actual support for suspend-resume in mlx4 (bug 251154). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-251226-227>