> -----Original Message----- > From: Bjorn Helgaas [mailto:bhelg...@google.com] > Sent: Thursday, September 12, 2013 3:27 PM > To: Skidmore, Donald C > Cc: e1000-de...@lists.sourceforge.net; linux-...@vger.kernel.org; linux- > ker...@vger.kernel.org; Don Dutile > Subject: Re: [E1000-devel] 3.11-rc4 ixgbevf: endless "Last Request of type 00 > to PF Nacked" messages > > On Tue, Aug 27, 2013 at 5:01 PM, Bjorn Helgaas <bhelg...@google.com> > wrote: > > > I haven't been able to reproduce the problem with the 2.10.3 ixgbevf > > driver from > > http://sourceforge.net/projects/e1000/files/ixgbevf%20stable/ > > ... > > Sorry for wasting so much time on something that appears to be already > fixed. > > I just tried the brand-new v3.11, and the usual, trivial: > > # echo -n 8 > /sys/bus/pci/devices/0000:04:00.0/sriov_numvfs > > was enough to blow up my box the same old boring way (infinite string of > "ixgbevf 0000:04:11.0: Last Request of type 03 to PF Nacked" > messages. > > I guess this is because v3.11 still includes the 2.7.12-k ixgbevf driver, not > the > apparently-fixed 2.10.3 version from your sourceforge page. > > According to sourceforge, 2.7.12 was released almost a YEAR ago, on 2012-10- > 18, and 2.10.3 was released 2013-07-26. Why isn't 2.10.3 in v3.11? > > Don't you guys care that it is so easy to blow up your driver with the > mainline > kernel? I'm quite frustrated by how much time I've wasted on this issue. > > I do not think that defending yourself with "please try the latest driver from > sourceforge" is a reasonable or friendly way to work in the Linux community. > > Bjorn
Your right I haven't been keeping the version strings up-to-date with our latest upstream pushes. I was hoping to reach a sync point were both drivers (upstream and out of tree) were closer before I bumped the upstream version. The relationship between the version number in the ixgbevf version number in the upstream kernel and our out of tree driver are not quite that straight forward as the version strings would suggest. We have pushed quite a few patches since the last version bump a year ago and in fact attempt to push patches upstream in parallel with any changes we make in the out of tree driver. But depending on quite a list of events (testing, release schedule, when net-next is open) one driver can receive patches earlier and or later than another. Also ixgbevf is currently going through a fair amount of refactoring to bring in more up to date with ixgbe so there are a fair amount of patches currently in play. The reason I suggested you try the out of tree driver (source forge) as I knew it was currently a bit more up to date. The good news is if the latest out of tree driver is correcting your problem the fix most likely is reroute to upstream. Likewise I can send you some of the upstream patches that are in the out of tree driver but are waiting to be sent upstream, if you would like to try them. Some of them touch code around the mbx messages, which like I mentioned in an early email the error message your seeing seems to imply something has gone wrong there. But since we can't seem to recreate your failure local I can't know for sure. Thanks, -Don Skidmore <donald.c.skidm...@intel.com> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
