netdev - RE: Bug#614622: linux-image-2.6.37-1-686: atl2 NIC claims NO CARRIER after suspend/resume; rmmod+insmod fixes the problem

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]

Message-ID: <0FBC7C9C2640634A8B837C2EFFCFF32F01837E4A63@SHEXMB-01.global.atheros.com>
Date:	Wed, 23 Feb 2011 09:38:52 +0800
From:	Xiong Huang <Xiong.Huang@...eros.com>
To:	Daniel Kahn Gillmor <dkg@...thhorseman.net>
CC:	Ben Hutchings <ben@...adent.org.uk>,
	Jay Cliburn <jcliburn@...il.com>,
	Chris Snook <chris.snook@...il.com>,
	"614622@...s.debian.org" <614622@...s.debian.org>,
	Cloud Ren <Cloud.Ren@...eros.com>,
	netdev <netdev@...r.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

Hi Daniel

   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 :)

Thanks
Xiong
-----Original Message-----
From: Daniel Kahn Gillmor [mailto:dkg@...thhorseman.net] 
Sent: Wednesday, February 23, 2011 9:35
To: Xiong Huang
Cc: Ben Hutchings; Jay Cliburn; Chris Snook; Jie Yang; 614622@...s.debian.org; netdev
Subject: Re: Bug#614622: linux-image-2.6.37-1-686: atl2 NIC claims NO CARRIER after suspend/resume; rmmod+insmod fixes the problem

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