From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Xiong Huang <Xiong.Huang@Atheros.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
Jay Cliburn <jcliburn@gmail.com>,
Chris Snook <chris.snook@gmail.com>,
Jie Yang <Jie.Yang@Atheros.com>,
"614622@bugs.debian.org" <614622@bugs.debian.org>,
netdev <netdev@vger.kernel.org>
Subject: Bug#614622: linux-image-2.6.37-1-686: atl2 NIC claims NO CARRIER after suspend/resume; rmmod+insmod fixes the problem
Date: Tue, 22 Feb 2011 20:34:52 -0500 [thread overview]
Message-ID: <4D64643C.1020001@fifthhorseman.net> (raw)
In-Reply-To: <0FBC7C9C2640634A8B837C2EFFCFF32F01837E4A48@SHEXMB-01.global.atheros.com>
[-- Attachment #1: Type: text/plain, Size: 605 bytes --]
Hi Xiong,
On 02/22/2011 08:22 PM, Xiong Huang wrote:
> after the onboard NIC claims NO Carrier after resuming from suspend-to-RAM, how about it if unplug then re-plug the cable ?
i've tried that, and it is not sufficient to remove the NO CARRIER flag
from the output of "ip link". I've also tried power-cycling the 10/100
miniswitch on the other end of the ethernet cable, but no luck there either.
So far, the only thing i've found that clears the NO CARRIER state is to
remove and re-insert atl2.ko.
I remain open to other suggestions. And thanks for the speedy followup!
--dkg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 1030 bytes --]
next prev parent reply other threads:[~2011-02-23 1:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110222180821.5217.2375.reportbug@localhost.localdomain>
2011-02-23 1:14 ` Bug#614622: linux-image-2.6.37-1-686: atl2 NIC claims NO CARRIER after suspend/resume; rmmod+insmod fixes the problem Ben Hutchings
2011-02-23 1:22 ` Xiong Huang
2011-02-23 1:34 ` Daniel Kahn Gillmor [this message]
2011-02-23 1:38 ` Xiong Huang
2011-02-23 1:57 ` Daniel Kahn Gillmor
2011-02-23 2:06 ` Daniel Kahn Gillmor
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=4D64643C.1020001@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=614622@bugs.debian.org \
--cc=Jie.Yang@Atheros.com \
--cc=Xiong.Huang@Atheros.com \
--cc=ben@decadent.org.uk \
--cc=chris.snook@gmail.com \
--cc=jcliburn@gmail.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).