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

[Moritz Mühlenhoff <jmm@inutil.org>]

On Wed, Aug 03, 2011 at 07:15:02PM -0400, Daniel Kahn Gillmor wrote:
> On 07/29/2011 11:20 AM, Moritz Mühlenhoff wrote:
> > On Tue, Feb 22, 2011 at 09:06:44PM -0500, Daniel Kahn Gillmor wrote:
> >> I run this machine every day, connect it to multiple wired networks, and
> >> have a usage pattern of suspend-to-ram at least twice a day.  I never
> >> saw this problem until i was running 2.6.37-1.
> >>
> >> I don't think i was simply lucky with the previous versions.
> > 
> > Does this still occur with more recent kernels, e.g. 3.0?
> 
> I'm now running 3.0 (3.0.0-1-686-pae), and i see the same misbehavior.
> 
> Plugging/unplugging the network cable does not resolve the no-carrier
> state; power cycling the peer switch does not resolve it.
> 
> Removing and re-loading atl2.ko does resolve it.
> 
> Sorry to be the bearer of bad news :(

Please report this upstream at http://bugzilla.kernel.org, product "Drivers"
and component "Networking".

The reason why we ask you to file this bug report yourself is because
the kernel maintainers for that component will have questions specific
to your setup/hardware.

Once you've filed the bug, please send us the bugnumber or mark the bug
as forwarded yourself.

Cheers,
        Moritz