All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pedro Ribeiro <pedrib@gmail.com>
To: Nigel Cunningham <nigel@tuxonice.net>
Cc: Kernel development list <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	TuxOnIce-devel <tuxonice-devel@tuxonice.net>
Subject: Re: [TuxOnIce-devel] Thinkpad hotkeys and USB audio not working after resume in 3.0.x
Date: Thu, 1 Sep 2011 13:28:48 +0100	[thread overview]
Message-ID: <CAEDdjHcucDs7uyNzD1293bJNihQRS1UtOxxBYfSq9qHMLv3A0w@mail.gmail.com> (raw)
In-Reply-To: <CAEDdjHeDYFqq7gLMEnhwP8jfA-xqTpTGVOSN017avC1JmXrEpg@mail.gmail.com>

On 1 September 2011 13:26, Pedro Ribeiro <pedrib@gmail.com> wrote:
> On 1 September 2011 13:16, Nigel Cunningham <nigel@tuxonice.net> wrote:
>> Hi Pedro.
>>
>> On 01/09/11 20:36, Pedro Ribeiro wrote:
>>> Hi,
>>>
>>> I'm hitting a bug with my thinkpad T400. After resuming from Hibernate,
>>> the thinkpad hotkeys and my USB audio card do not work at all.
>>> Suspending to RAM and resuming seem to solve the problem, but after
>>> another hibernation it comes back again.
>>>
>>> This only happens with TuxOnIce but not with the vanilla kernel.
>>>
>>> Rafael, can you please point out from the top of your head if there was
>>> any change that could have caused this?
>>
>> Sorry for my slowness in getting back to you Pedro.
>>
>> When you invoke swsusp, is it in exactly the same way that TuxOnIce is
>> invoked? I'm wondering whether modules are unloaded and services stopped
>> in one scenario that are handled differently in the other.
>>
>> Regards,
>>
>> Nigel
>> --
>> Evolution (n): A hypothetical process whereby improbable
>> events occur with alarming frequency, order arises from chaos, and
>> no one is given credit.
>>
>
> Hi Nigel,
>
> Thanks for your response.
>
> I just tried using echo disk > /sys/power/state using both methods
> (swsusp and ToI) and the result is the same.
>
> With swsusp the keys and the USB interface work fine, but with ToI
> they stop working until I suspend to RAM.
>
> Regards,
> Pedro
>

Forgot to say, I tried reverting "PM / Runtime: Rework runtime PM
handling during driver
 removal" but it didn't help.

Regards,
Pedro

  reply	other threads:[~2011-09-01 12:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEDdjHfu71X04JR2Yx8N495bDoJRudch3xbzNAEmUpVxYS+Oww@mail.gmail.com>
2011-09-01 10:37 ` Fwd: Thinkpad hotkeys and USB audio not working after resume in 3.0.x Pedro Ribeiro
2011-09-01 12:16 ` [TuxOnIce-devel] " Nigel Cunningham
2011-09-01 12:26   ` Pedro Ribeiro
2011-09-01 12:28     ` Pedro Ribeiro [this message]
2011-09-01 21:44     ` Nigel Cunningham

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=CAEDdjHcucDs7uyNzD1293bJNihQRS1UtOxxBYfSq9qHMLv3A0w@mail.gmail.com \
    --to=pedrib@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigel@tuxonice.net \
    --cc=rjw@sisk.pl \
    --cc=tuxonice-devel@tuxonice.net \
    /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.