DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=date:from:to:subject:message-id:x-mailer:mime-version:content-type
         :content-transfer-encoding;
        b=IMhGmg1FQZce5t4JtbMhwse3NCnoVXN9YZpUDcq7GPaMlZaVN9Ovbsu3gfkKk67Srz
         PJ1uBGRhtO/OkimORzsWZhxZlNguOrW1k/NFG1C0pAQVlaEd/xGeYQjImsrcjJEckqBj
         4QaE0h6s71xpzKmQ7a50pH6JtPY6DKbxGP0Ec=
Date: Thu, 16 Jun 2011 11:02:56 +0200
From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: linux-kernel@vger.kernel.org
Subject: 3.0-rc2: mei breaks suspend
Message-ID: <20110616110256.0890dd37@susi.home.s3e.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1223
Lines: 38

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 :-)

Best regards,

	Stefan
-- 
Stefan Seyfried

Linux Consultant & Developer
B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/