On Tue, Oct 30, 2007 at 10:42:33AM +0200, Oleg Lomaka wrote: > Pyun YongHyeon wrote: > >On Thu, Oct 25, 2007 at 05:30:32PM +0900, To Oleg Lomaka wrote: > > > >[...] > > > > > > tdevil% grep -iE "msk|phy" /var/run/dmesg.boot > > > > pci0: domain=0, physical bus=0 > > > > pci2: domain=0, physical bus=2 > > > > mskc0: <Marvell Yukon 88E8038 Gigabit Ethernet> port 0x2000-0x20ff > > mem > > 0xd0100000-0xd0103fff irq 16 at device 0.0 on pci2 > > > > mskc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xd0100000 > > > > mskc0: MSI count : 2 > > > > mskc0: RAM buffer size : 16KB > > > > mskc0: Port 0 : Rx Queue 10KB(0x00000000:0x000027ff) > > > > mskc0: Port 0 : Tx Queue 10KB(0x00002800:0x00004fff) > > > > msk0: <Marvell Technology Group Ltd. Yukon FE Id 0xb7 Rev 0x01> on > > mskc0 > > > > msk0: bpf attached > > > > msk0: Ethernet address: 00:1b:24:0e:bc:26 > > > > miibus0: <MII bus> on msk0 > > > > e1000phy0: <Marvell 88E3082 10/100 Fast Ethernet PHY> PHY 0 on > > miibus0 > > > > e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > > > ukphy0: <Generic IEEE 802.3u media interface> PHY 3 on miibus0 > > > > ukphy0: OUI 0x001000, model 0x0004, rev. 0 > > > > ukphy0: no media present > > > > ukphy1: <Generic IEEE 802.3u media interface> PHY 6 on miibus0 > > > > ukphy1: OUI 0x004400, model 0x0011, rev. 0 > > > > ukphy1: no media present > > > > mskc0: [MPSAFE] > > > > mskc0: [FILTER] > > > > pci3: domain=0, physical bus=3 > > > > pci4: domain=0, physical bus=4 > > > > pci5: domain=0, physical bus=5 > > > > pci10: domain=0, physical bus=10 > > > > > > > > > > Thanks for the info. Would please try attached patch? > > > > > > >Any progress here? > >I guess it's very important to fix the bug as it would affect all > >Yukon FE based NIC. > > > > > I've applied your patch again yesterday. There was no halts for few > hours already (after ports cvs up and other network/cpu loads). I'll > give you a note in a day or two if there will no be any troubles. > Thanks for your help. >
Glad to hear that. Would you show me the verbosed boot messages related with msk(4)? According to your dmesg output I guess you have phantom PHYs attached to msk(4) too. So I'd also like to know the output of "devinfo -rv". -- Regards, Pyun YongHyeon _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
