From: Jiri Slaby <jslaby@suse.cz>
To: "Mihai Donțu" <mihai.dontu@gmail.com>, linux-kernel@vger.kernel.org
Cc: e1000-devel@lists.sourceforge.net
Subject: Re: e1000e: nic does not work properly after cold power on
Date: Mon, 04 Mar 2013 16:21:32 +0100 [thread overview]
Message-ID: <5134BBFC.2050907@suse.cz> (raw)
In-Reply-To: <20130304124631.2ac730f3@mdontu-l.dsd.ro>
On 03/04/2013 11:46 AM, Mihai Donțu wrote:
> Hi,
>
> I apologize in advance for posting on two lists at once and for not
> even being subscribed to e1000-devel.
>
> Ever since upgrading to 3.8.x, I'm unable to use my wired connection
> (e1000e - Intel Corporation 82579LM Gigabit) immediately after power
> on. I have to boot into an older kernel (3.2.0 I happen to have around)
> and _then_ boot into 3.8.1. There are no errors in dmesg that I can
> see. The only one behaving strangely is NetworkManager who simply says
> the device is managed and skips it. Also, there's no 'link becomes
> ready' in dmesg either (and I swear the cable is plugged in).
>
> Has anyone else encountered this?
Hi, I think so:
http://lists.opensuse.org/opensuse-factory/2013-03/msg00099.html
(I have no idea what the issue is, just adding another report.)
--
js
suse labs
next prev parent reply other threads:[~2013-03-04 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 10:46 e1000e: nic does not work properly after cold power on Mihai Donțu
2013-03-04 15:21 ` Jiri Slaby [this message]
2013-03-04 18:15 ` Morten Stevens
2013-03-04 21:48 ` e1000e 3.9-rc1 suspend failure (was: Re: e1000e: nic does not work properly after cold power on) Borislav Petkov
2013-03-04 22:58 ` Mihai Donțu
2013-03-05 2:11 ` [E1000-devel] " Allan, Bruce W
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5134BBFC.2050907@suse.cz \
--to=jslaby@suse.cz \
--cc=e1000-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mihai.dontu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox