From: Andrew Morton <akpm@linux-foundation.org>
To: Thomas Gleixner <tglx@linutronix.de>, john stultz <johnstul@us.ibm.com>
Cc: linux-kernel@vger.kernel.org,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>,
dang@gentoo.org
Subject: Re: [Bugme-new] [Bug 8479] New: gettimeofday returning 1000000 in tv_usec on core2duo
Date: Mon, 14 May 2007 22:09:01 -0700 [thread overview]
Message-ID: <20070514220901.90aab9e0.akpm@linux-foundation.org> (raw)
In-Reply-To: <200705150417.l4F4HlvS013354@fire-2.osdl.org>
On Mon, 14 May 2007 21:17:47 -0700 bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8479
>
> Summary: gettimeofday returning 1000000 in tv_usec on core2duo
> Kernel Version: 2.6.21
> Status: NEW
> Severity: normal
> Owner: ak@suse.de
> Submitter: dang@gentoo.org
>
>
> Most recent kernel where this bug did *NOT* occur: 2.6.20
> Distribution: Gentoo
> Hardware Environment: core2duo T7200 (all reporters had this same CPU)
> Software Environment: Linux 2.6.21, glibc 2.5
> Problem Description:
>
> gettimeofday returns 1 - 1000000 in tv_usec, not 0 - 999999
> This does not happen on any of my AMD-based 32 or 64 bit boxes, only on my
> core2duo; I have 2 other reports of this problem, all on T7200's
>
> Steps to reproduce:
>
> call gettimeofday a lot. Eventually, you'll get 1000000 returned in tv_usec. My
> average is ~1 in 1000000 calls. I've attached my test program, with output from
> various boxes. One of the other reporters tried the test program too, and got
> similar output. .config will be attached too.
err, whoops.
next parent reply other threads:[~2007-05-15 5:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705150417.l4F4HlvS013354@fire-2.osdl.org>
2007-05-15 5:09 ` Andrew Morton [this message]
2007-05-15 6:06 ` [Bugme-new] [Bug 8479] New: gettimeofday returning 1000000 in tv_usec on core2duo Eric Dumazet
2007-05-15 6:23 ` Andrew Morton
2007-05-15 7:22 ` Andi Kleen
2007-05-15 8:17 ` Eric Dumazet
2007-05-15 14:55 ` Daniel Gryniewicz
2007-05-19 14:30 ` Bill Davidsen
2007-05-19 17:59 ` Eric Dumazet
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=20070514220901.90aab9e0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=dang@gentoo.org \
--cc=johnstul@us.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.