From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Jay Cliburn <jcliburn@gmail.com>,
Chris Snook <chris.snook@gmail.com>,
Jie Yang <jie.yang@atheros.com>,
614622@bugs.debian.org, 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 21:06:44 -0500 [thread overview]
Message-ID: <4D646BB4.3020302@fifthhorseman.net> (raw)
In-Reply-To: <1298423651.2211.496.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 947 bytes --]
On 02/22/2011 08:14 PM, Ben Hutchings wrote:
> This bug report was made against Debian's package of Linux 2.6.37:
[...]
> I don't see any changes to this driver between 2.6.37-rc4 (the first
> version we built as '2.6.37-trunk-686') and 2.6.37, so I think Daniel
> just had good luck with the earlier versions.
I was running 2.6.37-1~experimental.1, fwiw, since 2011-01-09. I don't
think that was based off of rc4, because i was running
2.6.37~rc5-1~experimental.3 before that since 2010-12-16.
so the dates are:
2010-12-16: start running 2.6.37~rc5-1~experimental.3
2011-01-09: start running 2.6.37-1~experimental.1
2011-02-17: start running 2.6.37-1
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.
--dkg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 1030 bytes --]
prev parent reply other threads:[~2011-02-23 2:06 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
2011-02-23 2:06 ` Daniel Kahn Gillmor [this message]
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=4D646BB4.3020302@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=614622@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=chris.snook@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.