From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: ltp@lists.linux.it
Subject: [LTP] [patch V2 00/20] timer: Refactor the timer wheel
Date: Wed, 22 Jun 2016 11:06:07 +0200 [thread overview]
Message-ID: <1466586367.3188.45.camel@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1606221037310.5839@nanos>
On Wed, 2016-06-22 at 10:44 +0200, Thomas Gleixner wrote:
> B1;2802;0cOn Wed, 22 Jun 2016, Mike Galbraith wrote:
> > FWIW, testing with ltp, I noticed a new failure in logs. It turns
> out
> > to be intermittent, but the testcase mostly fails.
>
> You forgot to cc the LTP folks ...
This ain't the only one, it's just new. I'll mention it.
File under FYI/FWIW: I also plugged the set into RT, and nothing fell
out of local boxen. The below is falling out of my 8 socket box
though.. maybe a portage booboo.
[ 1503.988863] clocksource: timekeeping watchdog on CPU42: Marking clocksource 'tsc' as unstable because the skew is too large:
[ 1504.203800] clocksource: 'hpet' wd_now: 38b55bb wd_last: 8303f269 mask: ffffffff
[ 1504.296111] clocksource: 'tsc' cs_now: 3a3aa717794 cs_last: 354624eea7b mask: ffffffffffffffff
[ 1504.402329] clocksource: Switched to clocksource hpet
next prev parent reply other threads:[~2016-06-22 9:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160617121134.417319325@linutronix.de>
[not found] ` <1466581044.3188.34.camel@gmail.com>
2016-06-22 8:44 ` [LTP] [patch V2 00/20] timer: Refactor the timer wheel Thomas Gleixner
2016-06-22 9:06 ` Mike Galbraith [this message]
2016-06-22 13:37 ` Mike Galbraith
2016-06-22 10:28 ` Cyril Hrubis
2016-06-23 8:27 ` Thomas Gleixner
2016-06-23 11:47 ` Cyril Hrubis
[not found] ` <20160623135803.636.qmail@ns.sciencehorizons.net>
2016-06-23 14:10 ` Thomas Gleixner
2016-06-23 15:11 ` Cyril Hrubis
2016-06-23 15:21 ` Thomas Gleixner
2016-06-23 16:31 ` Cyril Hrubis
[not found] ` <20160626190025.GC11162@amd>
2016-06-26 19:21 ` Arjan van de Ven
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=1466586367.3188.45.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=ltp@lists.linux.it \
/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