2018-06-12 9:49 GMT+02:00 John Halfpenny <[email protected]>: > The device seems to have detected, however when I attempt to connect over > DHCP it locks up the machine, > and I have to do a cold reboot to get it going again. > > [ 1.045467] mskc0 at pci1 dev 0 function 0, Yukon-2 Extreme rev. B0 (0x2): > ioapic0 pin 16 > [ 1.045467] msk0 at mskc0 port A: Ethernet address 00:1d:72:eb:86:41 > [ 1.045467] makphy0 at msk0 phy 0: Marvell 88E1149 Gigabit PHY, rev. 1 > [ 1.002124] mskc0 at pci1 dev 0 function 0, Yukon-2 Extreme rev. B0 (0x2): > ioapic0 pin 16 > [ 1.002124] msk0 at mskc0 port A: Ethernet address 00:1d:72:eb:86:41 > [ 1.002124] makphy0 at msk0 phy 0: Marvell 88E1149 Gigabit PHY, rev. 1 > > ^ The output from dmesg shows the device but the model number is incorrect. > It is an 88E8071.
That 88E1149 is just the PHY model, that's why it's different. Can you please try if the following patch would fix the lock up? It contains port of changes in OpenBSD driver rev 1.66-1.79, including 1.74 which supposed to fix hard lock up on 8072, so maybe it would fix your 8071 too. http://www.netbsd.org/~jdolecek/if_msk_fix_hard_lock.diff There are also some MII fixes in their eephy.c but nothing of that looks relevant to your 88E1149. Jaromir
