From: Yanko Kaneti <yaneti@declera.com>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [regression 4.14rc] 74def747bcd0 (genirq: Restrict effective affinity to interrupts actually using it)
Date: Tue, 19 Sep 2017 18:12:16 +0300 [thread overview]
Message-ID: <1505833936.2634.11.camel@declera.com> (raw)
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
Regards
- Yanko
next reply other threads:[~2017-09-19 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 15:12 Yanko Kaneti [this message]
2017-09-19 15:33 ` [regression 4.14rc] 74def747bcd0 (genirq: Restrict effective affinity to interrupts actually using it) Marc Zyngier
2017-09-19 15:40 ` Yanko Kaneti
2017-09-19 15:51 ` Marc Zyngier
2017-09-20 0:30 ` Chuck Ebbert
2017-10-01 12:46 ` Thorsten Leemhuis
2017-10-01 13:06 ` Yanko Kaneti
2017-10-01 13:17 ` Thorsten Leemhuis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1505833936.2634.11.camel@declera.com \
--to=yaneti@declera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.