From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Simon Kirby <sim@hostway.ca>
Cc: linux-kernel@vger.kernel.org, john stultz <johnstul@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [2.6.37-rc5] Timer or ICE1724 issues, HZ=250, NO_HZ=y
Date: Mon, 13 Dec 2010 12:19:00 +0100 [thread overview]
Message-ID: <20101213111900.GA2310@gentoo.trippels.de> (raw)
In-Reply-To: <20101213105440.GA12768@hostway.ca>
On 2010.12.13 at 02:54 -0800, Simon Kirby wrote:
> With Linus git HEAD just compiled earlier today, I noticed a weird issue
> just now while in the middle of some coding. I think this may have
> happened before (maybe in 2.6.36), but not as obvious as this time.
>
> The music that was playing stopped, and the key I had just pressed did
> not show up in rxvt. I figured the machine had hung, but I hit another
> key and the music played again for another second and my _previous_
> keystroke output appeared.
>
> Looking at /proc/interrupts, "timer" had completely stopped. "perf top"
> showed "snd_pcm_hwsync" was at the top of the profile with about 80%
> usage. Spinning in "snd_pcm_stream_lock_irq" from other CPUs, probably..
>
> dmesg showed:
>
> [13995.498393] Clocksource tsc unstable (delta = -8589909196 ns)
> [13995.511452] Switching to clocksource hpet
> [14039.525074] NOHZ: local_softirq_pending 100
> [14039.882183] hrtimer: interrupt took 30800 ns
> [14134.540724] NOHZ: local_softirq_pending 100
Welcome to the club. This is a known problem on newer AMD systems see:
http://thread.gmane.org/gmane.linux.kernel/1054283
and the following patch:
http://thread.gmane.org/gmane.linux.kernel/1069458
But the real problem is that no patch found its way to Linus yet and
2.6.37 will be released in a few days.
I think Thomas' solution (with a hardcoded hpet_min_tick):
return res < 128 ? -ETIME : 0;
is the only sane option left this late in the series.
--
Markus
next prev parent reply other threads:[~2010-12-13 11:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 10:54 Simon Kirby
2010-12-13 11:19 ` Markus Trippelsdorf [this message]
2010-12-13 11:24 ` Thomas Gleixner
2010-12-13 12:46 ` [tip:x86/urgent] x86: HPET: Chose a paranoid safe value for the ETIME check tip-bot for Thomas Gleixner
2011-07-28 15:31 ` [stable-longterm] " Konstantin Khlebnikov
2011-07-28 15:52 ` Greg KH
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=20101213111900.GA2310@gentoo.trippels.de \
--to=markus@trippelsdorf.de \
--cc=bp@alien8.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sim@hostway.ca \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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®