On Thu, Jul 28, 2011 at 01:41, <[email protected]> wrote: > Hello, > > With a 82559EB card a customer often comes into the situation that no packet > can be received anymore until network restart. > The symptom is that the rx_missed_errors register counts each packet but no > more packets can be seen by the kernel. > > We are using a 2.6.32 kernel with version: 2.0.44-k2. > > I am aware that this is an old driver version, but please give me a chance to > explain why I'm asking for information anyway: > > - The driver is part of the 2.6.32 stable branch. > - It takes 2 - 10 days to reproduce it in the lab. So if we use a newer > version, we cannot be sure that the problem is fixed just because we don't > see it anymore. > - According to the customer the issue started with an update that adds the > memory boundary and disables packet split (errata #45). PSRTYPE register is > not initialized in this version. Everything in the previous version worked > (so with the even older driver). > - It is a critical customer. If we provide a new version and it fails again > this will become a problem. > - All reports about this issue end up without resolution or the advice to > update the driver. I really tried to extract an explanation or the exact > changeset that fixes the issue. But I failed. So for documentation purposes > it would be a good thing to make the solution googleble. > > Don Skidmore wrote in: > > http://sourceforge.net/mailarchive/forum.php?thread_name=29F4ED941D916B48B88B4D2A4F3D1B9C01D2E285AF%40orsmsx509.amr.corp.intel.com&forum_name=e1000-devel > > "Have you tried using the latest Source Forge driver (3.2.9). Including in > it was a fix that corrected an erratum that sounds very similar to your > issue." > > I'd greatly appreciate if someone can point me to the right direction. What > I'd like to understand is: >
Don seems to be have been working with you, so I will let him continue in assisting you (since he is the ixgbe Maintainer). There have been 15 more recent out-of-tree driver release's since the you are using, so it is very possible that the issue you are seeing was fixed later on in one of the more recent driver releases, and the fix was not back-ported to the older 2.6.32 kernel. If Don does not have the information already, any information that you can provide (i.e. kernel config, lspci -vvv output. dmesg log with the error's you are seeing). This information can help us greatly in determining what fixes that were implemented in later versions of the driver would have an effect on the issue you are seeing. Once we narrow down the fix(es) that resolve the issue, then we can provide the additional information on what the exact change is and why. With some (not all) fixes, we should have testing scenarios which would consistently reproduce the issue, so that we can accurately determine if the fix(es) resolved the issue. I know that I am speaking in generalities and nothing specific, this is mainly because I do not the exact issue you are having the the possible fixes that Don is aware of. I have added Don to this email thread, and will let him work with you to get the specifics on the issue(s) you are seeing. So that we can work on getting a resolution to you, whether it be an updated driver or a patchset against your kernel. Cheers, Jeff > - What change exactly is the fix for this issue? > - How can I verify that I am seeing the same issue (some special > register/memory dump/...)? > - How can I verify that the issue is fixed. > > I know - I'm asking for support for a driver that is part of the stable > kernel but very old in your development line. > So I would be even happier if someone takes the time to answer my questions. > > Cheers, > Martin > > Martin Zielinski > Dipl. Inform > Senior Engineer > > McAfee GmbH > > Firmensitz: Muenchen > Amtsgericht: AG Muenchen > Handelsregister: HRB 144340 > Geschaeftsfuehrer: Emmet Russell, Keith Krzeminski, Douglas Rice > Bankverbindung: ABN-Amro Bank N.V. Konto 671 211 9006 > UST-ID: DE168122444 > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > 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 > -- Cheers, Jeff ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ 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
