From: "Jarek Kamiński" <jarek@vilo•eu.org>
To: Francois Romieu <romieu@fr•zoreil.com>
Cc: Ben Hutchings <ben@decadent•org.uk>,
609538@bugs•debian.org, Hayes Wang <hayeswang@realtek•com>,
netdev <netdev@vger•kernel.org>
Subject: Re: Bug#609538: r8169: long delay during resume
Date: Tue, 11 Jan 2011 19:21:28 +0100 [thread overview]
Message-ID: <4D2C9FA8.7010401@vilo.eu.org> (raw)
In-Reply-To: <20110111132524.GA2479@electric-eye.fr.zoreil.com>
W dniu 11.01.2011 14:25, Francois Romieu pisze:
> Jarek Kamiński <jarek@vilo•eu.org> :
> [...]
>> The last 2.6.36 I've tried was 2.6.36-1~experimental.1, I've then
>> passsed and returned to 2.6.32 for unrelated problems. I think it wasn't
>> affected, but I can re-check it and/or test later 2.6.36 versions if it
>> may help.
>
> The patch below against 2.6.37-git + davem's pending fixes (see
> http://marc.info/?l=linux-netdev&m=129448910825754) should help.
>
> Can you give it a try ?
>
> r8169: keep firmware in memory.
This patch applied against current git tree fixes problem (with firmware
installed). However, cherry-picking
eee3a96c6368f47df8df5bd4ed1843600652b337 (r8169: delay phy init until
device opens.) from net-2.6.git and applying "r8169: keep firmware in
memory." still results with
#v+
Jan 11 19:05:18 rocket kernel: [ 673.176439] ata1.00: configured for
UDMA/100
Jan 11 19:05:18 rocket kernel: [ 731.639054] r8169 0000:13:00.0: eth0:
unable to apply firmware patch
Jan 11 19:05:18 rocket kernel: [ 731.640486] PM: resume of devices
complete after 60228.033 msecs
#v-
(I don't fully understand why)
"r8169: delay phy init until device opens." alone also doesn't do the trick.
--
pozdr(); // Jarek
next prev parent reply other threads:[~2011-01-11 18:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110110131439.GA663@rocket.almost.secure.la>
2011-01-11 5:49 ` Bug#609538: r8169: long delay during resume Ben Hutchings
2011-01-11 7:29 ` Jarek Kamiński
2011-01-11 13:25 ` Francois Romieu
2011-01-11 18:21 ` Jarek Kamiński [this message]
2011-01-11 20:28 ` Francois Romieu
2011-01-20 3:04 Daniel J Blueman
2011-01-20 3:20 ` Ben Hutchings
2011-01-20 13:55 ` Jarek Kamiński
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=4D2C9FA8.7010401@vilo.eu.org \
--to=jarek@vilo$(echo .)eu.org \
--cc=609538@bugs$(echo .)debian.org \
--cc=ben@decadent$(echo .)org.uk \
--cc=hayeswang@realtek$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=romieu@fr$(echo .)zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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