Hi Dave, Sorry for your troubles. I have to agree that that does not really look like a NIC device issue but a bridge issue with the system. This is why I'm trying to figure out a way to change the configuration to see if the problem moves to other ports or always says with this port/interface. Can you try to move things around in the system to look for that? Are there things in the BIOS that can be changed wrt PCI slot parameters? If so maybe something there would have an effect as well.
Please let us know. I'm travelling on business so emails may be delayed. Thanks. Cheers, John > -----Original Message----- > From: Dr. David Alan Gilbert [mailto:[email protected]] > Sent: Saturday, February 15, 2014 12:13 PM > To: Ronciak, John > Cc: [email protected] > Subject: Re: [E1000-devel] dual e100 'exec cuc_dump_reset' vs PCI > latency (possibly vs Tulip) > > * Ronciak, John ([email protected]) wrote: > > Hi Dave, > > Hi John, > > > Sorry for the delay. So it ran for about 19 minutes before it > stopped > receiving correct? > > Probably a bit under that, but yes a few minutes, but that's with the > 128 PCI latency; with the 32 it would do it in seconds. > > > The e100 NIC port that fails is just receiving data from the camera > > correct? > > Well it's a PC just sitting there with a browser looking at the camera > > > From that stats something is doing an awful lot of transmitting. An > > order of magnitude more if I read this correctly. > > What is it transmitting? Am I understanding of this correct? if so > > can you please tell me what's going on with all the transmits? > > It doesn't seem a lot; this was extracted by grepping for tx_bytes in > that log; each line is one minute > > rx_bytes bytes/min bytes/sec > 243797360 0 0 > 243797360 0 0 > 243799556 2196 36.6 > 243799736 180 3 > 243802072 2336 38.9333 > 243802072 0 0 > 244921827 1119755 18662.6 > 251741140 6819313 113655 < A > 258691588 6950448 115841 > 265594929 6903341 115056 > 276003297 10408368 173473 > 302321897 26318600 438643 < B > 328971818 26649921 444165 > 355240830 26269012 437817 > 381531716 26290886 438181 > 407800668 26268952 437816 > 434062530 26261862 437698 > 460339412 26276882 437948 > 486653710 26314298 438572 > 507377956 20724246 345404 > 507377956 0 0 > 507382596 4640 77.3333 > > So I suspect at A I started it going, at B probably increased the frame > rate; the camera is doing JPEG images, at about 15 fps max, so 430KB/15 > ~ 30KByte/image which is reasonable for a 640x480 image. > > > Also, have you tried a different e100 NIC? This problem is very > strange so maybe it's a real HW failure? > > I was running a plain e100 single NIC I think without trouble (although > I'd have to check what was plugged into it), this is the only dual card > I've > got. Personally I was guessing it was related to the bridge > arrangement > which is why I guessed at PCI latency in the 1st place - but that's a > straight guess. > > Dave > > -- > -----Open up your eyes, open up your mind, open up your code ------- > / Dr. David Alan Gilbert | Running GNU/Linux | Happy \ > \ gro.gilbert @ treblig.org | | In Hex / > \ _________________________|_____ http://www.treblig.org |_______/ ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ 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
