From: devzero@web.de
To: tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [clocksource] jiffies as clocksource kills box
Date: Sat, 02 Feb 2008 14:01:27 +0100 [thread overview]
Message-ID: <141139231@web.de> (raw)
>I have a patch pending for the PIT issue. Will add jiffies to this as
>well.
yes, please.
while trying to analyze a timer issue and learning about that timer stuff, i "killed" my box twice because i didn`t know that "echo jiffies|pit > current_clocksource" is a no-no with dynticks.
this happened with vendor kernel and thought i hit a bug, so i tried vanilla but.....same issue.
not a big one, but that patch would be a time-saver for those who don`t know...
roland
>> Per $subject, echo jiffies > current_clocksource pretty thoroughly kills
>> my P4 box, and does so with every kernel I have (2.6.22->present). I
>> can drive the box via mouse clicks and poke around, but trying to select
>> another clocksource thereafter is nogo.. cat current_clocksource emits
>> jiffies, and box remains comatose unless prodded.
>
>I guess your box has high resolution timers and/or dynamic ticks
>enabled. In that case we really can not switch to jiffies. We also
>have to prevent PIT from being selected.
>
>I have a patch pending for the PIT issue. Will add jiffies to this as
>well.
>
>We'll fix that in .25 as it requires root user interaction and does
>not show up magically.
>
>Thanks,
> tglx
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066
next reply other threads:[~2008-02-02 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 13:01 devzero [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-15 5:49 [clocksource] jiffies as clocksource kills box Mike Galbraith
2008-01-16 13:54 ` Thomas Gleixner
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=141139231@web.de \
--to=devzero@web.de \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox