From: Andreas Baer <lnx1@gmx.net>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with Asus P4C800-DX and P4 -Northwood-
Date: Tue, 26 Jul 2005 18:13:24 +0200 [thread overview]
Message-ID: <42E66124.7020709@gmx.net> (raw)
In-Reply-To: <42E64B11.6030908@tmr.com>
Bill Davidsen wrote:
> Andreas Baer wrote:
>
>>
>>
>> Bill Davidsen wrote:
>>
>>>
>>> One other oddment about this motherboard, Forgive if I have
>>> over-snipped this trying to make it relevant...
>>>
>>> Andreas Baer wrote:
>>>
>>>>
>>>> Willy Tarreau wrote:
>>>>
>>>>> On Mon, Jul 25, 2005 at 03:10:08PM +0200, Andreas Baer wrote:
>>>>
>>>>
>>>
>>>
>>>>> There clearly is a problem on the system installed on this machine.
>>>>> You should
>>>>> use strace to see what this machine does all the time, it is
>>>>> absolutely not
>>>>> expected that the user/system ratios change so much between two nearly
>>>>> identical systems. So there are system calls which eat all CPU. You
>>>>> may want
>>>>> to try strace -Tttt on the running process during a few tens of
>>>>> seconds. I
>>>>> guess you'll immediately find the culprit amongst the syscalls, and
>>>>> it might
>>>>> give you a clue.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> I hope you are talking about a hardware/kernel problem and not a
>>>> software
>>>> problem, because I tried it also with LiveCD's and they showed the
>>>> same results
>>>> on this machine.
>>>> I'm not a linux expert, that means I've never done anything like
>>>> that before,
>>>> so it would be nice if you give me a hint what you see in this
>>>> results. :)
>>>>
>>>
>>> Am I misreading this, or is your program doing a bunch of seeks not
>>> followed by an i/o operation? I would doubt that's important, but
>>> your vmstat showed a lot of system time, and I just wonder if
>>> llseek() is more expensive in Linux than Windows. Or if your code is
>>> such that these calls are not optimized away by gcc.
>>
>>
>>
>> I don't know what exactly produces this _llseek calls, but I ran the
>> compiled binaries on both machines (desktop + notebook) without any
>> recompilation and so I think they should do the same (even if this is
>> bad or not optimized), but I see a time difference of more than 2:30
>> :) This _llseek calls also don't seem to be faster or slower if you
>> compare the times on the notebook and the desktop.
>
>
>
> If the program and test data is not proprietary, would it help to have
> me run the test on my P4P800, P4-2.8, HT on, and see if that's an issue
> with your particular board or BIOS? I have the 1086 BIOS from my notes
> on that machine, I think you were running a later BIOS? 1091 or so, from
> memory?
>
> Anyway, I would run a test that takes 3 minutes if it helps as a data
> point.
Properly a good idea, but you have a completely different chipset related to
the Asus Website. I think it's a i865 and I have i875. I'm also running BIOS
1019(!).
That's the driver page for my Board:
http://support.asus.com/download/download.aspx?Type=All&model=P4C800%20Deluxe
It would be better if someone has at least the same board.
Does anyone have a Asus P4C800-Deluxe with a P4 around 2.4 GHz running on this
mailing list and would sacrifice himself/herself to run a little test with my
software for a maximum of 4 minutes? Would be approx. 10 MB for data transmission.
prev parent reply other threads:[~2005-07-26 16:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 0:50 Problem with Asus P4C800-DX and P4 -Northwood- Andreas Baer
2005-07-25 5:12 ` Willy Tarreau
2005-07-25 13:10 ` Andreas Baer
2005-07-25 14:00 ` Paulo Marques
2005-07-25 15:24 ` Willy Tarreau
2005-07-25 19:51 ` Andreas Baer
2005-07-25 20:03 ` Erik Mouw
2005-07-25 20:12 ` Andreas Baer
2005-07-25 20:26 ` Erik Mouw
2005-07-25 20:38 ` Jesper Juhl
2005-07-25 21:01 ` Erik Mouw
2005-07-25 20:03 ` Valdis.Kletnieks
2005-07-25 20:03 ` Dmitry Torokhov
2005-07-25 20:48 ` Bill Davidsen
2005-07-25 21:51 ` Andreas Baer
2005-07-26 14:39 ` Bill Davidsen
2005-07-26 16:13 ` Andreas Baer [this message]
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=42E66124.7020709@gmx.net \
--to=lnx1@gmx.net \
--cc=davidsen@tmr.com \
--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