From: Ben Hutchings <ben@decadent.org.uk>
To: "François Romieu" <romieu@fr.zoreil.com>
Cc: Arnout Boelens <aboelens@engin.umass.edu>,
595265@bugs.debian.org, netdev <netdev@vger.kernel.org>
Subject: Re: Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
Date: Mon, 18 Oct 2010 01:23:51 +0100 [thread overview]
Message-ID: <1287361431.20865.133.camel@localhost> (raw)
In-Reply-To: <201010171116.00514.aboelens@engin.umass.edu>
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
Arnout Boelens reported that his RTL8111/8168B fails to link-up after
suspend and resume, both under Debian's kernel based on 2.6.32 and under
2.6.36-rc6. Full details are at <http://bugs.debian.org/595265>, though
the log isn't very informative:
[31837.396594] PM: Finishing wakeup.
[31837.396597] Restarting tasks ... done.
[31840.267267] r8169: eth0: link down
Can you suggest how to investigate this further?
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next parent reply other threads:[~2010-10-18 0:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100902154312.12515.10390.reportbug@bird.umass.edu>
[not found] ` <201009211624.12744.aboelens@engin.umass.edu>
[not found] ` <1286760421.2955.287.camel@localhost>
[not found] ` <201010171116.00514.aboelens@engin.umass.edu>
2010-10-18 0:23 ` Ben Hutchings [this message]
2010-10-18 21:45 ` Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend Francois Romieu
2010-10-18 22:48 ` Ben Hutchings
2010-10-18 22:50 ` Eric Dumazet
2010-10-19 23:06 ` Francois Romieu
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=1287361431.20865.133.camel@localhost \
--to=ben@decadent.org.uk \
--cc=595265@bugs.debian.org \
--cc=aboelens@engin.umass.edu \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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).