From: Eric Dumazet <eric.dumazet@gmail.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
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: Tue, 19 Oct 2010 00:50:57 +0200 [thread overview]
Message-ID: <1287442257.2361.11.camel@edumazet-laptop> (raw)
In-Reply-To: <20101018214536.GA14344@electric-eye.fr.zoreil.com>
Le lundi 18 octobre 2010 à 23:45 +0200, Francois Romieu a écrit :
> Ben Hutchings <ben@decadent.org.uk> :
> [...]
> > 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?
>
> Something like the patch made by Stanislaw at :
> https://bugzilla.redhat.com/show_bug.cgi?id=502974
>
Seems to be down at this moment, patch is also here (and included in
2.6.36-rc8 ) :
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=aeb19f6052b5e5c8a24aa444fbff73b84341beac
next prev parent reply other threads:[~2010-10-18 22:51 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 ` Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend Ben Hutchings
2010-10-18 21:45 ` Francois Romieu
2010-10-18 22:48 ` Ben Hutchings
2010-10-18 22:50 ` Eric Dumazet [this message]
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=1287442257.2361.11.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=595265@bugs.debian.org \
--cc=aboelens@engin.umass.edu \
--cc=ben@decadent.org.uk \
--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