From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org, Jay Cliburn <jcliburn@gmail.com>,
Chris Snook <chris.snook@gmail.com>,
Jie Yang <jie.yang@atheros.com>
Cc: bugme-daemon@bugzilla.kernel.org, dkg@fifthhorseman.net
Subject: Re: [Bugme-new] [Bug 40732] New: atl2 NIC claims NO CARRIER after suspend/resume; rmmod + insmod fixes problem
Date: Tue, 23 Aug 2011 13:43:06 -0700 [thread overview]
Message-ID: <20110823134306.827091ce.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-40732-10286@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Mon, 8 Aug 2011 18:10:08 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=40732
>
> URL: http://bugs.debian.org/614622
> Summary: atl2 NIC claims NO CARRIER after suspend/resume; rmmod
> + insmod fixes problem
> Product: Drivers
> Version: 2.5
> Kernel Version: 3.0
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Network
> AssignedTo: drivers_network@kernel-bugs.osdl.org
> ReportedBy: dkg@fifthhorseman.net
> Regression: No
>
>
> As reported in more detail at http://bugs.debian.org/614622, i have an atl2 NIC
> (03:00.0 Ethernet controller: Atheros Communications L2 Fast Ethernet (rev a0))
> which sometimes reports NO CARRIER after i suspend/resume.
>
> This has been the case since 2.6.37 and it persists with 3.0 as well. I'm
> using debian's 686 kernels.
>
parent reply other threads:[~2011-08-23 20:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-40732-10286@https.bugzilla.kernel.org/>]
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=20110823134306.827091ce.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=chris.snook@gmail.com \
--cc=dkg@fifthhorseman.net \
--cc=jcliburn@gmail.com \
--cc=jie.yang@atheros.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).