Time Issue on OpenBSD 4.2 with rc.69 (Was: Re: Sparc64 OpenBSD4.1 Compile issue)
Carter Bullard
carter at qosient.com
Mon Feb 11 12:56:09 EST 2008
Gentle people,
Hmmmm, well I'm just wondering why we're getting problems with
i386 argus() -> i386 ra() ? That's just not right at all. I'm pretty
confident
this stuff works somewhere, as I don't have any machines anywhere
with this problem, and we have this running on MIPS, Intel, PPC, Sparc,
all with 32 and 64 bit architectures, so I am a bit puzzled.
For the Tilera board (64 core MIPS like chip) we had to change the
pack()
pragma in ./include/argus_out.h, which went from "pack(4)" to "pack(2)".
That didn't break anything anywhere else, and you tested reverting these
values back to 4, on all your software, ......, yes?
And there is no radium() anywhere?
Did argus ever run on these machines?
Carter
On Feb 11, 2008, at 12:11 PM, Eric Pancer wrote:
> On Feb 11, 2008 9:58 AM, Carter Bullard <carter at qosient.com> wrote:
>> OK, so I think we have a fundamental testing issue. You should
>> not be in ArgusNtoH if we're testing on the sparc64 machine. I
>> think testing anywhere else is not going to be fruitful. So lets
>> move to the sparc64 and see what its doing!!!
>
> Well, the clients aren't giving good time no matter where they're run.
>
> i386 clients to sparc64 server
> sparc64 clients to i386 server
> i386 clients to i386 server
> sparc64 clients to sparc64 server
>
>> OK, assuming that you only get the problem when it is a sparc64
>> argus(), you should be doing all of these tests on the sparc64
>> machine. Can you rerun the last test on the sparc64?
>
> Yes I can; give me a few hours.
>
> - Eric
>
> p.s. I think Peter just replied and his reply looks just about correct
> on the issue.
>
More information about the argus
mailing list