From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760296Ab1D0XwI (ORCPT ); Wed, 27 Apr 2011 19:52:08 -0400 Received: from mail-iy0-f174.google.com ([209.85.210.174]:47255 "EHLO mail-iy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752736Ab1D0XwF convert rfc822-to-8bit (ORCPT ); Wed, 27 Apr 2011 19:52:05 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=ginkel.com; s=google; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; b=fsJ9+t+w4SN6noImF6ua0/Z/RX0HvXJpYctex3P2OmXmSBFUok+34r7TxStkMdYUS2 35Dxju1Q1jWBaVK2bf9nRpv6hHd9nBqgMWK2+nKL68OMc85X/29gmWltOLvZhX1HERtm D0YfZH0osDgSi9337IeKPNIFn6aXR1XkX29fk= MIME-Version: 1.0 X-Originating-IP: [91.17.168.251] In-Reply-To: <20110426131132.GG878@htj.dyndns.org> References: <201104172135.40189.arnd@arndb.de> <20110426131132.GG878@htj.dyndns.org> From: Thilo-Alexander Ginkel Date: Thu, 28 Apr 2011 01:51:34 +0200 Message-ID: Subject: Re: Soft lockup during suspend since ~2.6.36 [bisected] To: Tejun Heo Cc: Arnd Bergmann , "Rafael J. Wysocki" , linux-kernel@vger.kernel.org, dm-devel@redhat.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 26, 2011 at 15:11, Tejun Heo wrote: > Hello, sorry about the delay.  Was on the road and then sick. No problem. Thanks for getting back to me. >> In the meantime I also figured out that 2.6.39-rc3 seems to fix the >> issue (there have been some work queue changes, so this is somewhat >> sensible) > > Hmmm... that's a big demotivator.  :-) Well, I get your point. ;-) Maybe this fact can help as a motivator: I ran some further tests and while -rc3 seems to be ok (and survived 100 suspend/resume cycles), the issue strangely seems to be back with -rc4 (the softlockup call stack that I can see is identical to the photos below; the lockup happened after only two cycles). > Before I go ahead and try that, do you happen to have softlockup dump? > ie. stack traces of the stuck tasks?  I can't find the original > posting. Sure: >>From : > Unfortunately, the output via a serial console becomes garbled after > "Entering mem sleep", so I went for patching dumpstack_64.c and a > couple of other source files to reduce the verbosity. I hope not to > have stripped any essential information. The result is available in > these pictures: > https://secure.tgbyte.de/dropbox/IeZalo4t-1.jpg > https://secure.tgbyte.de/dropbox/IeZalo4t-2.jpg > > For both traces, the printed error message reads: "BUG: soft lockup - > CPU#3 stuck for 67s! [kblockd:28]" Thanks, Thilo