Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753058AbeAKAVL (ORCPT + 1 other); Wed, 10 Jan 2018 19:21:11 -0500 Received: from mga11.intel.com ([192.55.52.93]:20956 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752473AbeAKAVK (ORCPT ); Wed, 10 Jan 2018 19:21:10 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,342,1511856000"; d="scan'208";a="20633779" Message-ID: <1515630068.17761.16.camel@linux.intel.com> Subject: Re: [BUG] function_graph trace causes hang when using sleepgraph (4.15.0-rc1 and newer) From: Todd Brandt Reply-To: todd.e.brandt@linux.intel.com To: Steven Rostedt Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, len.brown@intel.com, todd.e.brandt@intel.com Date: Wed, 10 Jan 2018 16:21:08 -0800 In-Reply-To: <20180109111334.2628dcc5@vmware.local.home> References: <1515455714.17761.7.camel@linux.intel.com> <1515459749.17761.10.camel@linux.intel.com> <20180108200756.08712bb4@vmware.local.home> <1515461115.17761.12.camel@linux.intel.com> <20180109111334.2628dcc5@vmware.local.home> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Tue, 2018-01-09 at 11:13 -0500, Steven Rostedt wrote: > On Mon, 08 Jan 2018 17:25:15 -0800 > Todd Brandt wrote: > > > Can you reproduce the issue there? I just want to be sure it's not > > something local to our machines here, as long as you have CONFIG_PM > > enabled it should work the same hopefully.  > > Just to let you know, I'm currently traveling, so my testing ability > is > limited at the time being. ok, it's not an emergency, we're using a patched version of the kernel with those two commits removed in the interim. I tried running kgdb over serial console, but unfortunately it doesn't work over a USB-to- Serial dongle (even Greg K-H says it won't work, :P). This is the best output I could get, considering: # run the test script here [  545.733458] PM: suspend entry (deep) [  545.734535] PM: Syncing filesystems ... done. [  546.580551] Freezing user space processes ... (elapsed 0.013 seconds) done. [  546.594846] OOM killer disabled. [  546.595002] Freezing remaining freezable tasks ... (elapsed 0.005 seconds) done. [  557.808719] NMI watchdog: Watchdog detected hard LOCKUP on cpu 0 So it's definitely a hard lockup, I just can't get the stack trace without a system with a built in serial console. > > -- Steve