Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751771AbdISPkV (ORCPT ); Tue, 19 Sep 2017 11:40:21 -0400 Received: from mail.bix.bg ([193.105.196.21]:53039 "HELO mail.bix.bg" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751377AbdISPkS (ORCPT ); Tue, 19 Sep 2017 11:40:18 -0400 Message-ID: <1505835616.2634.14.camel@declera.com> Subject: Re: [regression 4.14rc] 74def747bcd0 (genirq: Restrict effective affinity to interrupts actually using it) From: Yanko Kaneti To: Marc Zyngier Cc: LKML , Thomas Gleixner Date: Tue, 19 Sep 2017 18:40:16 +0300 In-Reply-To: <4374f6c0-dd67-3bd3-91a0-685eb9a0d711@arm.com> References: <1505833936.2634.11.camel@declera.com> <4374f6c0-dd67-3bd3-91a0-685eb9a0d711@arm.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.0 (3.26.0-1.fc28) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1765 Lines: 36 On Tue, 2017-09-19 at 16:33 +0100, Marc Zyngier wrote: > 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? Sorry, I might need some basic help here (i.e where do I count them...) After the watchdog switches the clocksource to hpet the system is still somewhat alive, so I'll guess some clock is still ticking.... -Yanko