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]
Message-ID: <EA929A9653AAE14F841771FB1DE5A1365FF4B057A0@rrsmsx501.amr.corp.intel.com>
Date:	Wed, 14 Jul 2010 13:22:25 -0600
From:	"Tantilov, Emil S" <emil.s.tantilov@...el.com>
To:	Nico Schottelius <nico-linux-20100702@...ottelius.org>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
CC:	LKML <linux-kernel@...r.kernel.org>,
	netdev <netdev@...r.kernel.org>,
	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>,
	"Allan, Bruce W" <bruce.w.allan@...el.com>
Subject: RE: e1000e: receives no packets after resume
 (2.6.35-rc3-00262-g984bc96)

Nico Schottelius wrote:
> Hey Jeff,
> 
> Jeff Kirsher [Fri, Jul 02, 2010 at 02:47:26PM -0700]:
>> On Fri, Jul 2, 2010 at 00:28, Nico Schottelius
>> <nico-linux-20100702@...ottelius.org> wrote:
>> [...]
>> Adding the Networking Kernel mailing list (netdev) and Intel Linux
>> LAN Driver mailing list (e1000-patches)...
>> 
>> Would it be possible to get more information about the system/setup?
>> 
>> For example, can you provide the following information:
>>      - full lspci output (lspci -vvv)
>>      - ethtool -i ethX
>>      - dmesg  - after loading the driver and configuring the
>> interfaces 
>>      - kernel config
> 
> Attached!
> 
> Cheers,
> 
> Nico

<snip>

>[   12.228826] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X
>[   12.279610] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X
>[   12.280200] ADDRCONF(NETDEV_UP): eth0: link is not ready
>[   18.282340] e1000e 0000:00:19.0: eth0: Error reading PHY register

Note the error from your dmesg log. This is a known issue and we are working on it.
In meantime you should be able to w/a it by reloading the driver.

Thanks,
Emil
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ