Date: Mon, 16 Jul 2018 04:13:47 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 229727] bge watchdog timeout with MacBook Pro Message-ID: <bug-229727-7501-tAYf4I6tvt@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229727-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-229727-7501@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=3D229727 Eugene Grosbein <eugen@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|On install, Broadcom |bge watchdog timeout with |chipset doesn't receive |MacBook Pro |DHCPOFFER | --- Comment #17 from Eugene Grosbein <eugen@freebsd.org> --- SIMPLEX flag is pretty normal and should be. It just says the NIC does not = get incoming copies of frames it have just sent and system does not need to fil= ter them out. Almost all modern ethernet interfaces have this flag. So, your real problem are "bge watchdog timeouts" and not DHCP. These point= to some kind of driver problem or hardware problem (cables, ethernet switch an= d/or ports etc.) Are you having no problems with Debian and EXACTLY same set of hardware including cables? If no, try replacing hardware with known working set. If yes, this rules out hardware problem and points to driver problem. There is Korean blog article http://hyogeollee.blogspot.com/2011/11/ of year 2011 describing similar problem with FreeBSD on MacBook Pro (2010). It says: "In case of bge which is Ethernet driver, watchdog timeout occurs and it is= not operated. However, if you add the polling option to the kernel configuratio= n, it will work normally. Maybe there is a problem on the driver side. If you build by adding options DEVICE_POLLING to the kernel configuration, and then boot to the new kernel, it works fine." The kernel option DEVICE_POLLING prevents usage of MSI within bge(4) driver that may be source of this problem due to wrong interrupt handling. There a= re other ways to disable usage of MSI. You should try to escape to bootloader prompt at early stage while booting installation media and do: set hw.pci.enable_msi=3D0 set hw.pci.enable_msix=3D0 boot Then check if this works to run using static IP address. If so, re-check wi= th DHCP. --=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-229727-7501-tAYf4I6tvt>