netdev - Re: [Bugme-new] [Bug 10600] New: e1000 updates rx

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4827D947.8090804@acm.org>
Date:	Mon, 12 May 2008 00:44:39 -0500
From:	Ben Liblit <liblit@....org>
To:	"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
CC:	Michael Chan <mchan@...adcom.com>,
	David Miller <davem@...emloft.net>, akpm@...ux-foundation.org,
	netdev <netdev@...r.kernel.org>,
	bugme-daemon@...zilla.kernel.org,
	"Ronciak, John" <john.ronciak@...el.com>
Subject: Re: [Bugme-new] [Bug 10600] New: e1000 updates rx_bytes infrequently

Jesse Brandeburg wrote:
> and for e1000e (which you should be using for 82566)

That seems unlikely.  When I replace "alias eth0 e1000" with "alias eth0 
e100e" in my module configuration I lose the network interface entirely. 
  "ip link" does not mention it and it does not appear in 
"/sys/class/net".  Switching back to "alias eth0 e1000" restores the 
ability to use the network interface.

It seems pretty clear from my end that the e1000e driver is *not* 
recognizing and driving my Intel 82566DC ethernet device.
--
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