From: Marc Zyngier <marc.zyngier@arm.com>
To: Yanko Kaneti <yaneti@declera.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [regression 4.14rc] 74def747bcd0 (genirq: Restrict effective affinity to interrupts actually using it)
Date: Tue, 19 Sep 2017 16:51:06 +0100 [thread overview]
Message-ID: <225dd0d8-2c27-57a6-c17d-c552c011d8da@arm.com> (raw)
In-Reply-To: <1505835616.2634.14.camel@declera.com>
On 19/09/17 16:40, Yanko Kaneti wrote:
> 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...)
/proc/interrupts should display them.
> After the watchdog switches the clocksource to hpet the system is still
> somewhat alive, so I'll guess some clock is still ticking....
Probably, but I suspect they're not hitting the right CPU, hence the
lockups.
Unfortunately, my x86-foo is pretty minimal, and I'm about to drop off
the net for a few days.
Thomas, any insight?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2017-09-19 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 15:12 Yanko Kaneti
2017-09-19 15:33 ` Marc Zyngier
2017-09-19 15:40 ` Yanko Kaneti
2017-09-19 15:51 ` Marc Zyngier [this message]
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=225dd0d8-2c27-57a6-c17d-c552c011d8da@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yaneti@declera.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®