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] [day] [month] [year] [list]
Date:	Mon, 16 Apr 2007 13:12:47 -0700
From:	"Jesse Brandeburg" <jesse.brandeburg@...il.com>
To:	"Dave Jones" <davej@...hat.com>
Cc:	netdev@...r.kernel.org
Subject: Re: 2.6.21rc7 e1000 media-detect oddness.

On 4/15/07, Dave Jones <davej@...hat.com> wrote:
> I booted up 2.6.21rc7 without an ethernet cable plugged in,
> and noticed this..
>
> e1000: 0000:02:00.0: e1000_probe: The EEPROM Checksum Is Not Valid
> e1000: probe of 0000:02:00.0 failed with error -5
>
> I plugged a cable in, did rmmod e1000;modprobe e1000, and got this..
>
> e1000: 0000:02:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) 00:16:d3:3a:62:d3
> e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
> e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX
> e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO
>
> and it works fine..
> Why would no cable make it think the EEPROM is invalid ?
>
> I repeated this a few times, just to be sure it wasn't a fluke, and it
> seems to happen 100% reproducably.

This is a known issue, having to do with a power saving mode on the
PCIe side of the adapter, that is enabled when link is down.

There are several fixes, an eeprom fix, or changing the code to call
e1000_validate_eeprom_checksum twice in a row if the first fails.

this bug has some text about this and an attachment with the fix script
http://sourceforge.net/tracker/index.php?func=detail&aid=1474679&group_id=42302&atid=447449

Jesse
-
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ