> -----Original Message----- > From: Matt Edwards [mailto:[email protected]] > Sent: Friday, May 16, 2014 7:18 AM > To: Ertman, DavidX M; [email protected] > Subject: RE: 82579 Transmit hang with C200 and ME > > Hi Dave, > > Thanks for the reply. > > I meant to say the E1000e. I started with version 2.5.4 and merged in > anything new I found in version 3.04. > > Matt Edwards > > > -----Original Message----- > From: Ertman, DavidX M [mailto:[email protected]] > Sent: Thursday, May 15, 2014 5:45 PM > To: Matt Edwards; [email protected] > Subject: RE: 82579 Transmit hang with C200 and ME > > > -----Original Message----- > > From: Matt Edwards [mailto:[email protected]] > > Sent: Wednesday, May 07, 2014 10:04 AM > > To: [email protected] > > Subject: [E1000-devel] 82579 Transmit hang with C200 and ME > > > > Hello, > > > > I have modified the current E1000 for a small embedded system. The > > driver works well on systems that do not have Intel ME. On systems > > that have Intel ME the transmit hangs. BTW the only systems I have > > tested with ME are > > C200 PCH boards. The problem could also be the result of differences > > between the C200 and C202. > > > > On transmit I have verified that transmit descriptor head and tail > > pointer registers are correct after the driver loads up the DMA > > buffers but the MAC never sends the frames and never updates the head, > > and never sets the DD bit. This code works with other NIC's and on > > other 82579 NIC's. Receive DMA works fine. > > > > I've had transmit hangs when the PHY throws data away, but when that > > happens the MAC updates the descriptors as thought the packets were > > transmitted. > > > > Is there something at the system level that must be running with Intel ME. > > I've gone the E1000 driver to find all ME specific code and I think I > > have included it. > > > > Any help is very much appreciated, > > Best Regards, > > Matt > > > > Good afternoon Matt, > > You started with the e1000 driver? Why not the e1000e driver? There are > quite a few workarounds for 82579 in the e1000e driver that do not exist in > e1000. > > Dave Ertman
Matt, That clears up a few things. You mentioned that this was for an embedded system - what OS / kernel are you using? Does this problem reproduce with the in-kernel or SourceForge stock drivers? Dave Ertman ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
