Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751458AbcC3KW4 (ORCPT ); Wed, 30 Mar 2016 06:22:56 -0400 Received: from www.linutronix.de ([62.245.132.108]:39931 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751203AbcC3KWy (ORCPT ); Wed, 30 Mar 2016 06:22:54 -0400 Date: Wed, 30 Mar 2016 12:22:51 +0200 From: Sebastian Andrzej Siewior To: Thomas Gleixner Cc: Clark Williams , Daniel Wagner , RT , LKML Subject: Re: [RT] Warning from swake_up_all_locked in rt-4.4.4-rt11 Message-ID: <20160330102251.GB21849@linutronix.de> References: <20160313225358.4eb9316a@sluggy.hsv.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Key-Id: 2A8CF5D1 X-Key-Fingerprint: 6425 4695 FFF0 AA44 66CC 19E6 7B96 E816 2A8C F5D1 User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 797 Lines: 23 * Thomas Gleixner | 2016-03-14 09:49:52 [+0100]: >On Sun, 13 Mar 2016, Clark Williams wrote: > >> I'm hitting the WARN_ON(wakes > 2) in $SUBJECT when resuming from suspend on my laptop (quad-core i7 with HT on). Looks like the warning gets hit 36 times on resume. E.g.: >> This trace (and a similar one with device_resume) happens on all cpus so the >> trace info is kinda jumbled up. I'll try it with WARN_ON_ONCE instead >> tomorrow. > >If resume is the only case, then we can filter that out and not worry about it >at all :) I see here 3 to 7 loops on each warning in the resume case and I see approx 7 warnings. It wakes always a kworker/u*/* task. system_state is always set to SYSTEM_RUNNING so I am not sure what can be used for filtering. Any suggestions? >Thanks, > > tglx Sebastian