Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752620AbbBKMGA (ORCPT ); Wed, 11 Feb 2015 07:06:00 -0500 Received: from tschil.ethgen.ch ([5.9.7.51]:47274 "EHLO tschil.ethgen.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751829AbbBKMF6 (ORCPT ); Wed, 11 Feb 2015 07:05:58 -0500 X-Greylist: delayed 1594 seconds by postgrey-1.27 at vger.kernel.org; Wed, 11 Feb 2015 07:05:58 EST Date: Wed, 11 Feb 2015 12:39:23 +0100 From: Klaus Ethgen To: linux-kernel@vger.kernel.org Subject: Problems with suspend on recent kernel (not necessary a bug) Message-ID: <20150211113919.GA5672@ikki.ethgen.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; x-action=pgp-signed OpenPGP: id=79D0B06F4E20AF1C; url=http://www.ethgen.ch/~klaus/79D0B06F4E20AF1C.txt; preference=signencrypt User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2446 Lines: 61 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi list, first, just punish me if I post on the wrong place for that but I think it it. :-) I moved recently my laptop (levovon X61s) from kernel version v3.13.11 to v3.18.6. Everything was fine except that suspend to RAM is not working anymore. Right after blanking the console the suspend stuck with still running fans and not reacting to any interrupt except hard switching of the box. I tried to debug that but with a blanked console it is pretty difficult to do so. At least I was able to set pm_trace and it gave me "tty ptyxc: hash matches". So there seems to be something with that subsystem I believe. Is there any further way to debug suspend that could give me more informations? As told in the subject, it might be a bug or not, I cannot say as there are several differences in config between that two versions without doing changes manually. This even makes it difficult to bisec the problem. Moreover that compiling need some time on that box. However, if there is no easier way, I plan to test at least with major versions... A small side note: I using the bfq patch. Currently I have no pointer of that being the source of the problem but could try to eliminate that too. So if anybody has an easy way to catch down that suspend beast, I would appreciate the help. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQGcBAEBCgAGBQJU2z9dAAoJEKZ8CrGAGfase8kL/3NEj1cHA/bsbOc6Xo8T+9AY St43xkTX/Ex0zHYfCNfm4/s2gAi7yHgmeni/GXCYLBCEpcN4jBbrwYFHfsd02USm KglqkFqjklXw7lHaE6sclinSn5txe8tZbRqjWtRgrxgLU+7EoUQqF0Ozvvpc2teK d0VXdO+RpsGg7ZIcwyCr5b8dRKhLshjGgGIpk12kkdZZmRipu8V5u9Ls6j3tZj7h xCQ97GLsYd3bDhNWok/YVXNRPAmdLYtmnqkAYTSMDTUqtJZoNahVCZs0Z6qFfdPS ycPK1NtksNQSnlAYa7n7RlvbnWcytNklKBn1jIcdDKMH61+YnrQ9wYwpNkKu0VP7 idL84OlY85t5nJUhNpseJ3o6iwUu6826AKSzt76tlXNKY+ZhoqdMAC+3Ku58nsTP CFS63zjxmFMBTXjFak3bKnk7ZHKzJ7G24j257Qed/wnVE82kQ+17F0xHPjhbMj8I lc9goaDgiPRxCOA6NqM6RmlgC604/xPOrAKMH3AkMg== =OYh9 -----END PGP SIGNATURE----- -- 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/