From: James Bottomley <James.Bottomley@SteelEye.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] Work around for periodic do_gettimeofday hang
Date: 24 Nov 2004 10:49:42 -0600 [thread overview]
Message-ID: <1101314988.1714.194.camel@mulgrave> (raw)
On the voyager systems particularly (but also on some of my slower
parisc boxes) I periodically get hangs where the system just seems to
stop (although it does remain able to execute alt-sysrq). The traces
always seem to implicate do_gettimeofday in the xtime seqlock.
I've not been able to trace an exact cause for this, but it does seem to
be pretty much eliminated by lowering the clock speed to 100HZ. I
propose the following patch to do this for the slower intel processors
(basically pentiums and below)
James
--
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
===== include/asm-i386/param.h 1.6 vs edited =====
--- 1.6/include/asm-i386/param.h 2004-06-24 03:55:46 -05:00
+++ edited/include/asm-i386/param.h 2004-11-22 18:36:42 -06:00
@@ -1,8 +1,15 @@
#ifndef _ASMi386_PARAM_H
#define _ASMi386_PARAM_H
+#include <linux/config.h>
+
#ifdef __KERNEL__
-# define HZ 1000 /* Internal kernel timer frequency */
+# if defined(CONFIG_M386) || defined(CONFIG_M486) || defined(CONFIG_M586) \
+ || defined(CONFIG_M586TSC) || defined(CONFIG_M586MMX)
+# define HZ 100
+# else
+# define HZ 1000 /* Internal kernel timer frequency */
+# endif
# define USER_HZ 100 /* .. some user interfaces are in "ticks" */
# define CLOCKS_PER_SEC (USER_HZ) /* like times() */
#endif
next reply other threads:[~2004-11-24 16:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 16:49 James Bottomley [this message]
2004-11-24 19:13 ` Arjan van de Ven
2004-11-25 4:27 ` James Bottomley
2004-11-25 4:33 ` Andrew Morton
2004-11-25 4:40 ` James Bottomley
2004-11-25 8:20 ` Arjan van de Ven
2004-11-27 22:38 ` Lee Revell
2004-11-25 11:18 ` Roman Zippel
2004-11-25 13:42 ` Jan Engelhardt
2004-11-25 15:47 ` Alan Cox
2004-11-25 17:33 ` James Bottomley
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=1101314988.1714.194.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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®