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

[Xiong Huang <Xiong.Huang@Atheros.com>]

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@fifthhorseman.net] 
Sent: Wednesday, February 23, 2011 9:35
To: Xiong Huang
Cc: Ben Hutchings; Jay Cliburn; Chris Snook; Jie Yang; 614622@bugs.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