From: john stultz <johnstul@us.ibm.com>
To: timothy parkinson <t@timothyparkinson.com>
Cc: hauan@cmu.edu, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.1 "clock preempt"?
Date: Fri, 23 Jan 2004 12:06:45 -0800 [thread overview]
Message-ID: <1074888405.12447.41.camel@localhost> (raw)
In-Reply-To: <20040123193635.GA492@h00a0cca1a6cf.ne.client2.attbi.com>
On Fri, 2004-01-23 at 11:36, timothy parkinson wrote:
> On Fri, Jan 23, 2004 at 11:17:29AM -0800, john stultz wrote:
> > Well, lost ticks can be caused by many things, but your point is valid,
> > the message could be a bit more elightening.
>
> googling for this issue turns up quite a few questions about it - there's
> already one possible answer in the source, couldn't hurt to stick in a few
> more:
>
>
> if (lost_count++ > 100) {
> printk(KERN_WARNING "Losing too many ticks!\n");
> printk(KERN_WARNING "TSC cannot be used as a timesource.\n"
> "Are you running with SpeedStep?\n"
> + "Perhaps you should enable DMA using \"hdparm\"?\n"
> + "etc..........)\n");
> printk(KERN_WARNING "Falling back to a sane timesource.\n");
> clock_fallback();
> }
>
> not that you have to actually listen to me or anything... :-)
Looks good by me. Would you mind sending such a patch to Andrew?
thanks
-john
next prev parent reply other threads:[~2004-01-23 20:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 20:36 2.6.1 "clock preempt"? Steinar Hauan
2004-01-20 21:26 ` john stultz
2004-01-21 15:06 ` Steinar Hauan
2004-01-21 18:19 ` john stultz
2004-01-22 19:37 ` timothy parkinson
2004-01-22 19:42 ` john stultz
2004-01-22 19:50 ` timothy parkinson
2004-01-22 19:54 ` john stultz
2004-01-22 20:00 ` timothy parkinson
2004-01-22 21:21 ` john stultz
2004-01-23 19:02 ` timothy parkinson
2004-01-23 19:17 ` john stultz
2004-01-23 19:36 ` timothy parkinson
2004-01-23 20:06 ` john stultz [this message]
2004-01-23 20:38 ` timothy parkinson
2004-01-23 21:04 ` john stultz
2004-01-27 21:30 ` markus reichelt
2004-01-30 23:32 ` Bartlomiej Zolnierkiewicz
2004-01-31 0:24 ` timothy parkinson
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=1074888405.12447.41.camel@localhost \
--to=johnstul@us.ibm.com \
--cc=hauan@cmu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=t@timothyparkinson.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