netdev - Re: IGB driver upgrade

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: <4C293792.6070508@intel.com>
Date:	Mon, 28 Jun 2010 17:00:18 -0700
From:	Alexander Duyck <alexander.h.duyck@...el.com>
To:	sbs <gexlie@...il.com>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>
Subject: Re: IGB driver upgrade

sbs wrote:
> Hello guys.
> 
> Is it possible to upgrade intel gigabit adapter's e1000 driver to
> 2.2.9? This is the latest version according to Intel website.
> 
I assume you are referring to the igb driver since that is what is in 
the subject and not the e1000 driver correct?

> I've got a problem with 2.1.0-k2 drivers statically compiled into kernel.
> 
> Surely I can download drivers from intel and compile it as module, but
> I need to compile it statically
> Intel drivers do not provide sources for static compilation :(
> 
> Is it possible to upgrade drivers to igb-2.2.9 in the source tree and
> allow the static compilation of them?
> 
Normally the upstream driver should be up to date with any fixes that 
are in the standalone module.  What version of the kernel are you 
currently running?  Also have your tried testing the older standalone 
igb modules to see if the same issues exist there in either igb 2.1.9 or 
  igb 2.0.6?  This would help us to determine what changes in the 
standalone module might be missing from the in-kernel version of the driver.

> Because having 2.1.0-k2 we experience some strange random freezes with
> network interface which can be fixed only by restarting network.
> 
> 2.2.9 module has no such problems but we need to use static kernels
> according to our policy.

I have CCed our e1000-devel list.  In the future you may want to CC this 
list as it will provide better visibility to the Intel wired networking 
maintainers.

Thanks,

Alex
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html