-
go_jesse changed the public information on the Intel Wired Ethernet project.
2010-01-04 19:25:31 UTC in Intel Wired Ethernet
-
Also, looking in your logs, in lspci I see ASPM enabled L0s L1 for the upstream port (device 00:1c.5) which means it was probably enabled on the downstream port. I'm wondering if this could be related to your issue.
Does the BIOS have options to disable ASPM (or L1 or L0s) or PCIe power management, possible in the per-slot menus? Is your kernel enabled for CONFIG_PCIEASPM ?.
2010-01-04 18:40:32 UTC in Intel Wired Ethernet
-
I'm afraid you likely have bad hardware. is it still within warranty?.
2010-01-04 17:36:54 UTC in Intel Wired Ethernet
-
please comment if you have updated your bios, I think you had but would like confirmation in this bug.
I'll try to look to tomorrow at your MANC2H values and eeprom against what we believe to be the correct setup.
2009-12-22 08:12:41 UTC in Intel Wired Ethernet
-
thanks for the follow up and I'm glad you were able to work out your issue. Please let us know if you have any other issues and we will do our best to help. I realize we didn't get back to you very fast this time, we had a death on the team, and its not an excuse, but it has made our time spread a little thin. Again, thanks for the report and the follow up.
2009-12-22 08:09:07 UTC in Intel Wired Ethernet
-
Thanks for the feedback and the kind comments. I'll close the bug please let us know of other issues should they pop up.
2009-12-21 17:15:13 UTC in Intel Wired Ethernet
-
Hi, are you still having autoneg problems with the e100 adapter? I also have a suspicion that maybe the MDI-X code in e100 could be causing an issue for you, however the 0x1229 devices I think don't support MDI-X. We can disable MDI-X, as if you have proper cabling and/or your remote supports MDI-X then the e100 doesn't need to be doing it.
after having the issue does an ethtool -r ethX fix...
2009-12-09 18:52:18 UTC in Intel Wired Ethernet
-
sorry to hear about your issue. We believed the 1.1.2 driver to have a fix, but multiple users have still reported issues, we are investigating.
2009-12-09 18:48:28 UTC in Intel Wired Ethernet
-
sorry to hear of your problem. Our driver handles allocation failures just fine, but the kernel developers wanted us to leave in the WARN message from the memory allocator. We can make the warning go away with a small code change to add a GFP_NOWARN to the allocation flags. The driver will still work and count memory allocation failures in the ethtool statistics. Otherwise as long as your...
2009-12-09 17:36:12 UTC in Intel Wired Ethernet
-
Due to a death on the team, ownership of this work has been transferred to me. Please be patient while we adjust accordingly. If you have any questions, please let me know.
Please let us know if you can complete the experiment with tcpdump, as that woudl be extremely useful.
2009-12-09 17:28:47 UTC in Intel Wired Ethernet
