Date: Thu, 25 Feb 2016 00:19:15 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 196944] [bge] [ipmi] regression IPMI access disabled when bge driver is loaded Message-ID: <bug-196944-2472-QhiXfeicjm@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-196944-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-196944-2472@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D196944 --- Comment #6 from Andrew Daugherity <andrew.daugherity@gmail.com> --- No, it doesn't. The only difference is the interface speed is 100BaseTX at boot and then 1000BaseT after running ifconfig or dhclient, but IPMI ceases= to work once the kernel loads, before any interface configuration is done. However, I have found a workaround: enabling PXE in the BIOS. I'm still booting via local disk, not over PXE, but with PXE enabled, it prints a mes= sage during BIOS load and apparently resets/initializes the NIC in such a way th= at IPMI still works after FreeBSD loads its bge driver. To clarify: with FreeBSD 9.1 (and my test kernels with if_bge.c rolled back) and Linux, IPMI works regardless of PXE setting. With FreeBSD >=3D 9.2, IPMI only works when PXE is enabled. This is true f= or both the PowerEdge 850 and PowerEdge SC1435, and I would expect the 860 as well. For completeness, I also tested OpenBSD (snapshot) and NetBSD 7.0, and IPMI also breaks with both of those, even with PXE enabled. The default Dell BIOS setting is "enabled with PXE" for bge0 and "enabled without PXE" for bge1, but I had disabled PXE on some systems to speed up booting and avoid accidentally booting the wrong device. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-196944-2472-QhiXfeicjm>