From: "H. Peter Anvin" <hpa@zytor.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Avoid overflows in kernel/time.c
Date: Mon, 10 Dec 2007 10:59:20 -0800 [thread overview]
Message-ID: <475D8C88.5080706@zytor.com> (raw)
In-Reply-To: <20071204032949.c677c021.akpm@linux-foundation.org>
Andrew Morton wrote:
>
> My ia64 allmodconfig build has taken
>
> akpm 15700 89.6 0.0 8256 700 pts/4 RN+ 03:09 10:41 bc -q kernel/timeconst.bc
>
> 11 minutes so far. fc6/x86_64.
>
I just tried this on my system, using your cross-compiler chain. I got
a different error:
/opt/crosstool/gcc-3.4.5-glibc-2.3.6/ia64-unknown-linux-gnu/lib/gcc/ia64-unknown-linux-gnu/3.4.5/../../../../ia64-unknown-linux-gnu/bin/ld:
section .data.patch [a000000000000500 -> a000000000000507] overlaps
section .dynamic [a0000000000003c8 -> a000000000000507]
collect2: ld returned 1 exit status
make[2]: *** [arch/ia64/kernel/gate.so] Error 1
... but the timeconst stuff worked fine. I tried it both from the
command line and using your xb script.
This is on a fc7/x86-64 box. I also ran through all the values from 48
to 1024 on both an fc5 and an fc7 box (no fc6 box readily available,
although bc has been at 1.06 since 2000...)
In short, this is highly weird. Could you possibly do me a favour and
just run, at the command line:
echo 250 | bc -q kernel/timeconst.bc
... and see if it reproduces the lockup (I'm assuming HZ == 250 in your
config, since that's what I get when I do "make allmodconfig" on IA64.)
(No need to wait 11 minutes. It should run in a small fraction of a
second.)
-hpa
next prev parent reply other threads:[~2007-12-10 18:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 0:19 [PATCH] Avoid overflows in kernel/time.c H. Peter Anvin
2007-11-30 1:54 ` Andrew Morton
2007-11-30 3:01 ` H. Peter Anvin
2007-11-30 3:27 ` [PATCH] Documentation/Changes -> Documentation/Requirements H. Peter Anvin
2007-11-30 3:32 ` [PATCH] Documentation/Changes -> Documentation/Requirements (resend without truncated comment text) H. Peter Anvin
2007-11-30 7:16 ` Jarek Poplawski
2007-11-30 17:40 ` H. Peter Anvin
2007-11-30 17:47 ` [PATCH] Documentation/Changes -> Documentation/Requirements H. Peter Anvin
2007-11-30 18:09 ` Robert P. J. Day
2007-11-30 18:20 ` H. Peter Anvin
2007-11-30 1:59 ` [PATCH] Avoid overflows in kernel/time.c Chris Snook
2007-11-30 3:04 ` H. Peter Anvin
2007-11-30 3:40 ` Arjan van de Ven
2007-11-30 3:54 ` H. Peter Anvin
2007-12-02 18:37 ` Pavel Machek
2007-12-03 14:53 ` Jan Engelhardt
2007-12-10 16:37 ` H. Peter Anvin
2007-12-01 0:33 ` Adrian Bunk
2007-12-01 4:19 ` H. Peter Anvin
2007-12-01 13:20 ` Alan Cox
2007-12-01 13:33 ` Alan Cox
2007-12-02 1:53 ` H. Peter Anvin
2007-12-07 0:22 ` Jeremy Fitzhardinge
2007-12-04 11:29 ` Andrew Morton
2007-12-10 16:46 ` H. Peter Anvin
2007-12-10 18:59 ` H. Peter Anvin [this message]
2007-12-10 22:04 ` Andrew Morton
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=475D8C88.5080706@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.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