From: "Jarek Kamiński" <jarek@vilo.eu.org>
To: Ben Hutchings <ben@decadent.org.uk>,
609538@bugs.debian.org,
Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
netdev <netdev@vger.kernel.org>,
Hayes Wang <hayeswang@realtek.com>
Subject: Re: Bug#609538: r8169: long delay during resume
Date: Thu, 20 Jan 2011 14:55:34 +0100 [thread overview]
Message-ID: <20110120135534.GA24545@rocket.almost.secure.la> (raw)
In-Reply-To: <1295493603.2906.107.camel@localhost>
On Thu, Jan 20, 2011 at 03:20:03AM +0000, Ben Hutchings wrote:
> On Thu, 2011-01-20 at 10:04 +0700, Daniel J Blueman wrote:
>> I see that Francois' patch is present in 2.6.38-rc1; is there a way to
>> avoid this delay, or is this likely in request_firmware?
> It's a known problem with calls to request_firmware() when userland is
> not running (early initialisation or resume from sleep). It may be
> fixable.
It was partially fixed in commit
f1e02ed109df5f99abf942b8ccc99960cb09dd38 in linux-2.6.git (r8169: keep
firmware in memory.). Sorry for not reporting it here, I clicked "reply"
instead of "group reply" late in the night.
If this commit could be included in Debian kernel, the bug could be
closed.
J.
next prev parent reply other threads:[~2011-01-20 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 3:04 Bug#609538: r8169: long delay during resume Daniel J Blueman
2011-01-20 3:20 ` Ben Hutchings
2011-01-20 13:55 ` Jarek Kamiński [this message]
[not found] <20110110131439.GA663@rocket.almost.secure.la>
2011-01-11 5:49 ` 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
2011-01-11 20:28 ` 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=20110120135534.GA24545@rocket.almost.secure.la \
--to=jarek@vilo.eu.org \
--cc=609538@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=daniel.blueman@gmail.com \
--cc=hayeswang@realtek.com \
--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 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.