From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758213AbYA1Le0 (ORCPT ); Mon, 28 Jan 2008 06:34:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750802AbYA1LeT (ORCPT ); Mon, 28 Jan 2008 06:34:19 -0500 Received: from ogre.sisk.pl ([217.79.144.158]:33329 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750798AbYA1LeS (ORCPT ); Mon, 28 Jan 2008 06:34:18 -0500 From: "Rafael J. Wysocki" To: Steven Rostedt Subject: Re: [Regression] 2.6.24-git3: Major annoyance during suspend/hibernation on x86-64 (bisected) Date: Mon, 28 Jan 2008 12:31:50 +0100 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) Cc: Ingo Molnar , Andrew Morton , Linus Torvalds , LKML , Dmitry Adamushko , Peter Zijlstra References: <200801272229.48955.rjw@sisk.pl> <200801280226.22013.rjw@sisk.pl> <479D3287.1050604@redhat.com> In-Reply-To: <479D3287.1050604@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801281231.51545.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday, 28 of January 2008, Steven Rostedt wrote: > Rafael J. Wysocki wrote: > > > No, this isn't the WARN_ON(). > > > >> this does have the feel of being scheduling related, but are you > >> absolutely sure about the precise identity of the patch? > > > > Actually, not quite. That's why I have verified it and found that another > > patch is really responsible for the issue, namely: > > > > commit 82a1fcb90287052aabfa235e7ffc693ea003fe69 > > Author: Ingo Molnar > > Date: Fri Jan 25 21:08:02 2008 +0100 > > > > softlockup: automatically detect hung TASK_UNINTERRUPTIBLE tasks > > Are you getting a bunch of prints from the softlockup detector in dmesg? No, I don't. In fact, I don't get _any_ messages from it whatsoever. > I wonder if the detector can detect a long timeout caused by suspend and > resume and if not is triggering false positives? I'm not sure, but the code is supposed to be suspend-aware, IIRC. However, I'm seeing a similar symptom on poweroff on an SMP x86-64 box, so it may be more directly related to the CPU hotplug. I'll try to verify that. Thanks, Rafael