linux-kernel - Re: [E1000-devel] 3.11-rc4 ixgbevf: endless "Last Request of type 00 to PF Nacked" messages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAErSpo4LKRHyq=o5PC70heoiDiHOTvqzcML9F_OVwg+EtvUw6A@mail.gmail.com>
Date:	Thu, 12 Sep 2013 16:26:34 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	"Skidmore, Donald C" <donald.c.skidmore@...el.com>
Cc:	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Don Dutile <ddutile@...hat.com>
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 <bhelgaas@...gle.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/