From: Ben Hutchings <ben@decadent.org.uk>
To: Daniel J Blueman <daniel.blueman@gmail.com>, 609538@bugs.debian.org
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 03:20:03 +0000 [thread overview]
Message-ID: <1295493603.2906.107.camel@localhost> (raw)
In-Reply-To: <AANLkTikxpOS2fJ1Sqv=Lg6cX1TE+1W-ZxFV+YMOH1+Yp@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
On Thu, 2011-01-20 at 10:04 +0700, Daniel J Blueman wrote:
> When resuming from suspended with 2.6.38-rc1 with my RTL8168d/8111d
> hardware, I see significant delays [1].
>
> The only firmware I see in /lib/firmware is RTL8192E, thus it looks
> like this is due to it being not present.
If you're using Debian, the necessary blob is in the firmware-realtek
package.
> 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.
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 prev parent reply other threads:[~2011-01-20 3:20 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 [this message]
2011-01-20 13:55 ` Jarek Kamiński
[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=1295493603.2906.107.camel@localhost \
--to=ben@decadent.org.uk \
--cc=609538@bugs.debian.org \
--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.