linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maarten Lankhorst <m.b.lankhorst@gmail.com>
To: Stefan Seyfried <stefan.seyfried@googlemail.com>
Cc: linux-kernel@vger.kernel.org, Oren Weil <oren.jer.weil@intel.com>
Subject: Re: 3.0-rc2: mei breaks suspend
Date: Thu, 16 Jun 2011 11:38:41 +0200	[thread overview]
Message-ID: <BANLkTimBrsSoYi-Cqr3DhbTQO0iCBEEuJg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinfNKKeyC9RB-uvFSVq5OeNXiw95Q@mail.gmail.com>

2011/6/16 Maarten Lankhorst <m.b.lankhorst@gmail.com>:
> Hi Stefan,
>
> 2011/6/16 Stefan Seyfried <stefan.seyfried@googlemail.com>:
>> Hi,
>>
>> having the "mei" driver loaded, which happened automatically on my
>> ThinkPad X200s, successfully prevents any suspend efforts:
>>
>> [39736.728116] pci_pm_suspend(): mei_pci_suspend+0x0/0xc0 [mei] returns 9999
>>
>> The code has not changed since 3.0-rc2, so I did not try compiling latest
>> git.
>>
>> Jiri Slaby hinted that this code in drivers/staging/mei/wd.c is to blame:
>>
>> 169         ret = wait_event_interruptible_timeout(dev->wait_stop_wd,
>> 170                                         dev->wd_stopped, 10 * HZ);
>>
>> I am, however, not familiar enough with timers and stuff to immediately
>> spot the problem.
>>
>> Removing the module before suspend is a workaround.
>>
>> This could be considered a regression, as suspend worked very well before
>> this driver was introduced :-)
Nm, stupid suggestion.

Adding the author to cc, maybe he knows.

  reply	other threads:[~2011-06-16  9:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16  9:02 3.0-rc2: mei breaks suspend Stefan Seyfried
2011-06-16  9:19 ` Maarten Lankhorst
2011-06-16  9:38   ` Maarten Lankhorst [this message]
2011-06-16 10:24 ` Arkadiusz Miskiewicz
2011-06-16 14:27   ` Stefan Seyfried

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=BANLkTimBrsSoYi-Cqr3DhbTQO0iCBEEuJg@mail.gmail.com \
    --to=m.b.lankhorst@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oren.jer.weil@intel.com \
    --cc=stefan.seyfried@googlemail.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;
as well as URLs for NNTP newsgroup(s).