> On Thu, Mar 27, 2008 at 01:32:46PM +0200, Danny Braniss wrote: > > > On Thu, Mar 27, 2008 at 12:57:31PM +0200, Danny Braniss wrote: > > > > Hi, > > > > Under load, the msk has problems, with hw.msk.legacy_intr=1 > and 0. > > > > with = 1, i get > > > > TCP segementation error > > > > watchdog timeout > > > > with = 0, > > > > Tx MAC parity error > > > > watchdog timeout > > > > > > > > > > Would you show me verbosed boot messages related with msk(4)/e1000phy(4)? > > > > > mskc0: <Marvell Yukon 88E8056 Gigabit Ethernet> port 0xc800-0xc8ff mem > > 0xfeafc000-0xfeafffff irq 17 at device 0.0 on pci1 > > mskc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xfeafc000 > > mskc0: MSI count : 1 > > mskc0: attempting to allocate 1 MSI vectors (1 supported) > > msi: routing MSI IRQ 256 to vector 52 > > mskc0: using IRQ 256 for MSI > > mskc0: RAM buffer size : 128KB > > mskc0: Port 0 : Rx Queue 85KB(0x00000000:0x000153ff) > > mskc0: Port 0 : Tx Queue 43KB(0x00015400:0x0001ffff) > > msk0: <Marvell Technology Group Ltd. Yukon EC Ultra Id 0xb4 Rev 0x03> on > mskc0 > > msk0: bpf attached > > msk0: Ethernet address: 00:1e:8c:6d:5c:fe > > miibus0: <MII bus> on msk0 > > e1000phy0: <Marvell 88E1149 Gigabit PHY> PHY 0 on miibus0 > > e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > 1000baseTX-FDX, > > auto > > mskc0: [MPSAFE] > > mskc0: [FILTER] > > > > is this enough? > > Yes, it seems that 88E8056/88E1149 PHY has several issues. I recall > that there had been several reports for this issue. Since nfe(4) > with 88E1149 also have some stability issues, e1000phy(4) has lack > of required code for 88E1149 PHY. Up to date, I couldn't find a > clue, sorry. I'll let you know if I have a code to give it spin.
great and thanks, danny _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"