Pyun YongHyeon wrote: > On Thu, Aug 20, 2009 at 02:07:39PM -0400, Travis Mikalson wrote: >> Pyun YongHyeon wrote: >>> On Thu, Aug 13, 2009 at 07:56:05PM -0700, Ryan Rogers wrote: >>>> Pyun YongHyeon wrote: >>>>> On Wed, Jul 22, 2009 at 03:26:43PM -0700, Ryan Rogers wrote: >>>>>> Weongyo Jeong wrote: >>>>>>> On Wed, Jul 22, 2009 at 05:26:07AM -0500, Sam Fourman Jr. wrote: >>>>>>>>> svn co svn://svn.freebsd.org/base/head >>>>>>>>> svn merge -c -193289 >>>>>>>>> >>>>>>>>> Thereafter, in the root of the repo: >>>>>>>>> svn up >>>>>>>>> svn merge >>>>>>>> Confirmed, running the above set of commands fixed my 88E1116 nfe >>>>>>>> problem >>>>>>>> everything works as it should now. thanks guys for the help. >>>>>>>> >>>>>>>> Sam Fourman Jr. >>>>>>>> >>>>>>>> ps. svn was WAY faster than csup, I think I am going to use svn all >>>>>>>> the time now. >>>>>>> I know that yongari_at_ knows what the problem is and the solution but he >>>>>>> could not access the internet right now due to relocation to USA. >>>>>>> >>>>>>> It looks he is busy with looking for house and etc... >>>>>>> >>>>>>> regards, >>>>>>> Weongyo Jeong >>>>>>> >>>>>>> >>>>>>> >>>>>> Well, the good news is that r193289 was the only thing keeping my nics >>>>> >from working. I was able to update to current as of today and revert >>>>>> that patch, and everything is working nicely now. So I'll just keep my >>>>>> eye on the commit logs and patch that up by hand whenever I need to >>>>>> update until yongari is able to get situated. >>>>>> >>>>> Would you try attached patch and let me know how it goes on your >>>>> box? >>>> The patch works great, thanks! >>> Thanks for testing. >>> Unfortunately the change requires more testing on various >>> controllers. 88E1116 PHY is commonly found on Yukon Ultra or newer >>> Yukon controllers as well as NVIDIA controllers. Since we are in >>> 8.0-BETA stage changing common PHY code at this time looks >>> dangerous. >> Before I start a bug report, I'm curious, do you think it is possible >> for this issue to also affect the general stability in operation of the >> nfe driver? I mean if nfe comes up and works fine for many days and then >> suddenly stops passing traffic? >> >> In both 8.0 and 7.2-STABLE some time after the beginning of June, two >> separate systems with two different nfe NICs started showing exactly the >> same issue. The 7.2-STABLE system was built from June 16th source and >> has a Marvell 88E1116. The 8.0-BETA2 system has a Marvell 88E1111 and is >> built from Aug 13th source. Both systems did not ever have this issue >> with code from before June (7.2-RELEASE included). >> > > Sorry, I don't know. Both Marvell, vendor of PHY hardware and NIVIA > , vendor of ethernet controller didn't release documentation to > open source developers, so some part of code might be wrong on some > controllers. I think nfe(4) didn't have code changes during that > time window. e1000phy(4) received a couple changes to support LED > for Yukon FE+, Yukon Ultra and Yukon Extrme. But I don't think it > may cause problems on nfe(4) as the change only affects LED > blinking rate. You can verify it by backing out r193291. > >> Both will stop passing traffic across their nfe0 NIC randomly and >> require an ifconfig nfe0 down; ifconfig nfe0 up to continue. In the >> meantime before the interface is reset, ping says sendto no buffer space >> available and named starts spitting out a lot of "error sending >> response: not enough free resources" from the DNS queries it was in the >> middle of responding to. > > By chance are you using jumbo frame? Before digging into source > code it would be even better to know which controllers you have. > Just sending dmesg(1) output related with nfe(4)/e1000phy(4) would > be enough to know that. Not using jumbo frames, using regular 1500 MTU. On the 7.2-STABLE box: nfe0: <NVIDIA nForce MCP55 Networking Adapter> port 0xb400-0xb407 mem 0xfeaf8000-0xfeaf8fff,0xfeaf7c00-0xfeaf7cff,0xfeaf7800-0xfeaf780f irq 20 at device 8.0 on pci0 miibus0: <MII bus> on nfe0 e1000phy0: <Marvell 88E1116 Gigabit PHY> PHY 2 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto nfe1: <NVIDIA nForce MCP55 Networking Adapter> port 0xb080-0xb087 mem 0xfeaf6000-0xfeaf6fff,0xfeaf7400-0xfeaf74ff,0xfeaf7000-0xfeaf700f irq 21 at device 9.0 on pci0 miibus1: <MII bus> on nfe1 e1000phy1: <Marvell 88E1116 Gigabit PHY> PHY 3 on miibus1 e1000phy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto On the 8.0-BETA2 box: nfe0: <NVIDIA nForce4 CK804 MCP9 Networking Adapter> port 0x1460-0x1467 mem 0xb0003000-0xb0003fff irq 23 at device 10.0 on pci0 miibus0: <MII bus> on nfe0 e1000phy0: <Marvell 88E1111 Gigabit PHY> PHY 1 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nfe1: <NVIDIA nForce4 CK804 MCP9 Networking Adapter> port 0x3000-0x3007 mem 0xd0401000-0xd0401fff irq 52 at device 10.0 on pci128 miibus1: <MII bus> on nfe1 e1000phy1: <Marvell 88E1111 Gigabit PHY> PHY 1 on miibus1 e1000phy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, autoReceived on Thu Aug 20 2009 - 17:59:22 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:54 UTC