From: Frans Pop <elendil@planet.nl>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [regression] __tick_program_event of hpet is stuck
Date: Tue, 9 Sep 2008 21:20:44 +0200 [thread overview]
Message-ID: <200809092120.45295.elendil@planet.nl> (raw)
In-Reply-To: <alpine.LFD.1.10.0809091503460.3271@apollo.tec.linutronix.de>
On Tuesday 09 September 2008, Thomas Gleixner wrote:
> It's nothing to worry about. I out the WARN_ON() there to get some
> information about the validation of min_delta_ns and to see in which
> range this happens.
Ah, OK. A WARN_ON is perhaps a bit heavy for that, unless you actually
want to be flooded with reports :-)
In my case it prevented me from running the kernel on other boxes than the
laptop because I feared some possibly important issue.
Also, a single line can easily be filtered out from logcheck reports while
doing the same for WARN_ONs is much harder and even not advisable.
> I'm going to remove the WARN_ON() and just keep the information that
> we need to increase the min_delta_ns value for safe operation.
Sounds like a plan; have already done so locally.
Here are some results I've got so far. You can see reboots and supend
to RAMs. Maximum observed value on the HP 2510p is now 80000 with the
system mostly idle or in light use.
Sep 8 00:58:29 aragorn kernel: Linux version 2.6.27-rc5 (root@faramir) ...
Sep 8 00:59:17 aragorn kernel: CE: increasing min_delta_ns 5000 to 10000 nsec
Sep 8 01:56:38 aragorn kernel: CE: increasing min_delta_ns 10000 to 20000 nsec
Sep 8 02:51:23 aragorn kernel: CE: increasing min_delta_ns 20000 to 40000 nsec
Sep 8 05:11:10 aragorn kernel: Back to C!
Sep 9 00:04:16 aragorn kernel: Linux version 2.6.27-rc5 (root@faramir) ...
Sep 9 00:09:04 aragorn kernel: CE: increasing min_delta_ns 5000 to 10000 nsec
Sep 9 14:31:49 aragorn kernel: Back to C!
Sep 9 14:39:41 aragorn kernel: CE: increasing min_delta_ns 10000 to 20000 nsec
Sep 9 14:39:51 aragorn kernel: CE: increasing min_delta_ns 20000 to 40000 nsec
Sep 9 16:59:22 aragorn kernel: Linux version 2.6.27-rc5 (root@faramir) ...
Sep 9 16:59:22 aragorn kernel: CE: increasing min_delta_ns 5000 to 10000 nsec
Sep 9 17:02:18 aragorn kernel: Linux version 2.6.27-rc5 (root@faramir) ...
Sep 9 17:15:10 aragorn kernel: CE: increasing min_delta_ns 5000 to 10000 nsec
Sep 9 17:38:34 aragorn kernel: CE: increasing min_delta_ns 10000 to 20000 nsec
Sep 9 17:57:21 aragorn kernel: CE: increasing min_delta_ns 20000 to 40000 nsec
Sep 9 18:57:26 aragorn kernel: Back to C!
Sep 9 19:06:25 aragorn kernel: Back to C!
Sep 9 19:20:19 aragorn kernel: CE: increasing min_delta_ns 40000 to 80000 nsec
I also tried getting these on my desktop by switching the clocksource from
tsc to hpet, but that did not result in any output (identical x86_64 kernel).
Cheers,
FJP
next prev parent reply other threads:[~2008-09-09 19:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-07 23:14 [regression] __tick_program_event of hpet is stuck Frans Pop
2008-09-08 1:13 ` Frans Pop
2008-09-08 18:34 ` Stefan Hellermann
2008-09-08 20:56 ` Thomas Gleixner
2008-09-08 22:11 ` Frans Pop
2008-09-08 22:12 ` Guillaume Chazarain
2008-09-09 10:49 ` Thomas Gleixner
2008-09-09 12:38 ` Frans Pop
2008-09-09 13:27 ` Thomas Gleixner
2008-09-09 19:20 ` Frans Pop [this message]
2008-09-09 19:36 ` 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=200809092120.45295.elendil@planet.nl \
--to=elendil@planet.nl \
--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