netdev - RE: e1000 fails to initialize in current -git

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]

Date:	Mon, 19 Jan 2009 11:52:46 -0800
From:	"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
To:	Patrick McHardy <kaber@...sh.net>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: e1000 fails to initialize in current -git

Patrick McHardy wrote:
> I get this with 2.6.29-rc1
> 
> [    1.415322] Intel(R) PRO/1000 Network Driver - version
> 7.3.20-k3-NAPI [    1.415402] Copyright (c) 1999-2006 Intel
> Corporation. [    1.426013] e1000 0000:00:0c.0: enabling device (0000
> -> 0003) [    1.426101] e1000 0000:00:0c.0: PCI INT A -> GSI 17
> (level, low) -> 
> IRQ 17
> [    1.426187] e1000 0000:00:0c.0: PCI: Disallowing DAC for device
> [    1.426277] e1000 0000:00:0c.0: setting latency timer to 64
> [    1.495882] e1000: EEPROM initialization failed
> [    1.516170] e1000 0000:00:0c.0: PCI INT A disabled
> [    1.516252] e1000: probe of 0000:00:0c.0 failed with error -5
> 
> and the device is not registered. If someone wants me to test patches
> or do something else, just let me know.


are you still having this issue?  My guess is that it may be because
the pci_enable_device logic for devices in D3 got broken, but I think 
that is now fixed.

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