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>,
"614622@bugs.debian.org" <614622@bugs.debian.org>,
Cloud Ren <Cloud.Ren@Atheros.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: 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:57:55 -0500 [thread overview]
Message-ID: <4D6469A3.50401@fifthhorseman.net> (raw)
In-Reply-To: <0FBC7C9C2640634A8B837C2EFFCFF32F01837E4A63@SHEXMB-01.global.atheros.com>
[-- Attachment #1: Type: text/plain, Size: 590 bytes --]
Hi Xiong--
On 02/22/2011 08:38 PM, Xiong Huang wrote:
> What I mean is to check if the cable link (you can check the peer link LED if your onboard NIC haven't) is ON.
> If the cable link is ON, we may focus on software layer :)
the peer (mini-switch) link LED stays off, regardless of unplug/replug
of the cable, power-cycling the mini-switch, or of tweaking the
interface via:
ip link set eth0 down
ip link set eth0 up
However, the peer link LED turns on immediately when i do:
modprobe -v -r atl2
modprobe -v atl2
hope this is useful info,
--dkg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 1030 bytes --]
next prev parent reply other threads:[~2011-02-23 1:58 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
2011-02-23 1:38 ` Xiong Huang
2011-02-23 1:57 ` Daniel Kahn Gillmor [this message]
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=4D6469A3.50401@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=614622@bugs.debian.org \
--cc=Cloud.Ren@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).