public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: "Weil, Oren jer" <oren.jer.weil@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: mei driver breaks suspend on 3.0git
Date: Sun, 12 Jun 2011 20:40:21 +0200	[thread overview]
Message-ID: <201106122040.21950.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <201106122038.36623.a.miskiewicz@gmail.com>

On Sunday 12 of June 2011, Arkadiusz Miskiewicz wrote:
> On Sunday 12 of June 2011, Arkadiusz Miskiewicz wrote:
> > On Sunday 12 of June 2011, Winkler, Tomas wrote:
> > > > -----Original Message-----
> > > > From: Weil, Oren jer
> > > > Sent: Sunday, June 12, 2011 8:36 PM
> > > > To: Arkadiusz Miskiewicz
> > > > Cc: Winkler, Tomas; linux-kernel@vger.kernel.org
> > > > Subject: RE: mei driver breaks suspend on 3.0git
> > > > 
> > > > >It's thinkpad t400 with
> > > > >00:03.0 Communication controller [0780]: Intel Corporation Mobile 4
> > > > >Series Chipset MEI Controller [8086:2a44] (rev 07)
> > > > 
> > > > Can you send us more details? Does it happened in stress? How do I
> > > > reproduce
> > > > it?
> > 
> > No stress. This is my daily use notebook and I simply suspend to ram when
> > sitting under X in kde4.
> > 
> > > > Can you send us the debug prints?
> > 
> > Attached. suspend starts, tries to resume devices, MEI suspend fails
> > causing whole suspend to be aborted.
> 
> Shouldn't ret > 0 in mei_wd_stop to be "success"?

I meant this one:

        ret = wait_event_interruptible_timeout(dev->wait_stop_wd,
                                        dev->wd_stopped, 10 * HZ);


And that was possible untested solution that relies on wd being stopped and 
not anything else.

> 
> diff --git a/drivers/staging/mei/wd.c b/drivers/staging/mei/wd.c
> index 2564b03..608245a 100644
> --- a/drivers/staging/mei/wd.c
> +++ b/drivers/staging/mei/wd.c
> @@ -171,8 +171,10 @@ int mei_wd_stop(struct mei_device *dev, bool preserve)
>         mutex_lock(&dev->device_lock);
>         if (!dev->wd_stopped)
>                 dev_dbg(&dev->pdev->dev, "stop wd failed to complete.\n");
> -       else
> +       else {
> +               ret = 0;
>                 dev_dbg(&dev->pdev->dev, "stop wd complete.\n");
> +       }
> 
>         if (preserve)
>                 dev->wd_timeout = wd_timeout;


-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/

  reply	other threads:[~2011-06-12 18:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-12 11:14 mei driver breaks suspend on 3.0git Arkadiusz Miskiewicz
2011-06-12 17:35 ` Weil, Oren jer
2011-06-12 17:49   ` Winkler, Tomas
2011-06-12 18:16     ` Arkadiusz Miskiewicz
2011-06-12 18:38       ` Arkadiusz Miskiewicz
2011-06-12 18:40         ` Arkadiusz Miskiewicz [this message]
2011-06-12 19:41           ` Winkler, Tomas
2011-06-21 18:39             ` Marc Koschewski
2011-06-21 19:07               ` Winkler, Tomas
2011-06-21 19:23                 ` Marc Koschewski
2011-06-21 19:36                   ` Winkler, Tomas
2011-06-22  0:11                 ` Greg KH

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=201106122040.21950.a.miskiewicz@gmail.com \
    --to=a.miskiewicz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oren.jer.weil@intel.com \
    --cc=tomas.winkler@intel.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