From: Jesse Pollard <jesse@cats-chateau.net>
To: Daniel Egger <degger@fhm.edu>,
Linux Mailing List Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8 and 2.6.9 Dual Opteron glitches
Date: Tue, 2 Nov 2004 15:56:28 -0600 [thread overview]
Message-ID: <04110215562800.15809@tabby> (raw)
In-Reply-To: <5AC1EEB8-2CD7-11D9-BF00-000A958E35DC@fhm.edu>
On Tuesday 02 November 2004 07:59, Daniel Egger wrote:
>
>
> 2) 64 bit kernel vgettimeofday panic: The kernel panics in
> arch/x64_64/vsyscall.c:169 on boot.
>
> static int __init vsyscall_init(void)
> {
> if ((unsigned long) &vgettimeofday !=
> VSYSCALL_ADDR(__NR_vgettimeofday))
> panic("vgettimeofday link addr broken");
>
> Replacing those panic(s) by printk make the machine boot just fine
> and also work (seemingly) without any problems under load.
>
This may be all wet but....
> if ((unsigned long) &vgettimeofday !=
^^^^ this is a 32 bit value
> VSYSCALL_ADDR(__NR_vgettimeofday))
^^^^^^^^^^^^ and I think this is a 64 bit value.
> panic("vgettimeofday link addr broken");
And elevating an unsigned 32 bit to 64 will not match under any circumstances.
Bet it would work if "(unsigned long)" were "(void *)"
next prev parent reply other threads:[~2004-11-02 22:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 13:59 2.6.8 and 2.6.9 Dual Opteron glitches Daniel Egger
2004-11-02 16:58 ` Thomas Zehetbauer
2004-11-02 17:55 ` Tomas Carnecky
2004-11-02 21:52 ` Thomas Zehetbauer
2004-11-02 22:37 ` Daniel Egger
2004-11-02 21:53 ` Rafael J. Wysocki
2004-11-06 23:06 ` Christopher E. Brown
2004-11-02 21:56 ` Jesse Pollard [this message]
[not found] <5AC1EEB8-2CD7-11D9-BF00-000A958E35DC@fhm.edu.suse.lists.linux.kernel>
2004-11-03 5:06 ` Andi Kleen
2004-11-03 10:53 ` Daniel Egger
2004-11-03 11:05 ` Andi Kleen
2004-11-03 15:06 ` Jesse Pollard
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=04110215562800.15809@tabby \
--to=jesse@cats-chateau.net \
--cc=degger@fhm.edu \
--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