Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753456AbbLISYv (ORCPT ); Wed, 9 Dec 2015 13:24:51 -0500 Received: from mail-pa0-f48.google.com ([209.85.220.48]:36531 "EHLO mail-pa0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753147AbbLISYu (ORCPT ); Wed, 9 Dec 2015 13:24:50 -0500 Date: Wed, 9 Dec 2015 10:24:47 -0800 From: Jeremiah Mahler To: linux-kernel@vger.kernel.org Subject: Re: [BUG, linux-next] slow resume, hard LOCKUP on cpu 1 Message-ID: <20151209182447.GA19415@localhost.localdomain> Mail-Followup-To: Jeremiah Mahler , linux-kernel@vger.kernel.org References: <20151205212001.GA3622@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151205212001.GA3622@localhost.localdomain> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 778 Lines: 21 On Sat, Dec 05, 2015 at 01:20:01PM -0800, Jeremiah Mahler wrote: > all, > > Running the latest linux-next (20151202+) on an Acer C720, it will > sporadically be very slow to resume from a suspend. Sometimes it > resumes normally, other times it can take over a minute. During the > worst cases the NMI watchdog will detect a hard lockup on cpu 1 as > shown in the log snippet below (full log is attached). > ... Apparently something got fixed because it seems to be working fine with linux-next 20151207. -- - Jeremiah Mahler -- 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/