Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751851AbdISPdH (ORCPT ); Tue, 19 Sep 2017 11:33:07 -0400 Received: from foss.arm.com ([217.140.101.70]:52066 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751377AbdISPdG (ORCPT ); Tue, 19 Sep 2017 11:33:06 -0400 Subject: Re: [regression 4.14rc] 74def747bcd0 (genirq: Restrict effective affinity to interrupts actually using it) To: Yanko Kaneti Cc: LKML , Thomas Gleixner References: <1505833936.2634.11.camel@declera.com> From: Marc Zyngier Organization: ARM Ltd Message-ID: <4374f6c0-dd67-3bd3-91a0-685eb9a0d711@arm.com> Date: Tue, 19 Sep 2017 16:33:03 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <1505833936.2634.11.camel@declera.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1496 Lines: 33 On 19/09/17 16:12, Yanko Kaneti wrote: > Hello, > > Fedora rawhide config here. > AMD FX-8370E > > Bisected a problem to: > 74def747bcd0 (genirq: Restrict effective affinity to interrupts actually using it) > > It seems to be causing stalls, short lived or long lived lockups very shortly after boot. > Everything becomes jerky. > > The only visible in the log indication is something like : > .... > [ 59.802129] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: > [ 59.802134] clocksource: 'hpet' wd_now: 3326e7aa wd_last: 329956f8 mask: ffffffff > [ 59.802137] clocksource: 'tsc' cs_now: 423662bc6f cs_last: 41dfc91650 mask: ffffffffffffffff > [ 59.802140] tsc: Marking TSC unstable due to clocksource watchdog > [ 59.802158] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. > [ 59.802161] sched_clock: Marking unstable (59802142067, 15510)<-(59920871789, -118714277) > [ 60.015604] clocksource: Switched to clocksource hpet > [ 89.015994] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 209.660 msecs > [ 89.016003] perf: interrupt took too long (1638003 > 2500), lowering kernel.perf_event_max_sample_rate to 1000 > .... > > Just reverting that commit on top of linus mainline cures all the symptoms Interesting. Do you still get HPET interrupts? Thanks, M. -- Jazz is not dead. It just smells funny...