From: Fionn Behrens <fionn@unix-ag.org>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: System time warping around real time problem - please help
Date: 26 Mar 2003 11:48:19 +0100 [thread overview]
Message-ID: <1048675698.4951.17.camel@rtfm> (raw)
In-Reply-To: <1048637613.29944.17.camel@irongate.swansea.linux.org.uk>
On Mit, 2003-03-26 at 01:13, Alan Cox wrote:
> On Tue, 2003-03-25 at 22:55, Fionn Behrens wrote:
> > > This all sounds very much like the TSCs are drifting WRT each other.
> > > Is it possible that you have some power management code (or hardware)
> > > that is slowing one cpu and not the other?
> >
> > The only suspect in that case would be the amd76x_pm.o kernel module
> > which I am admittedly using. It saves about 90Watts of power when the
> > machine is idle...
>
> If you are using amd76x_pm boot with "notsc", ditto for that matter
> on dual athlons with APM or ACPI in some cases.
I booted without amd76x_pm today and the problems are gone. I tried
notsc yesterday and dmesg said TSC had been deactivated on both CPUs. No
libc6 problems - debian is using the i386 version by default.
Oddly enough the system still crashed on those two for (;;) time(); test
loops posted earlier in this thread. So the only (unsatisfying) solution
I see for now is to keep the CPUs glowing hot for the sake of stability.
Any idea what else could cause the crashes in the absence of TSC usage?
As a yet unresolved side note I am still unable to execute the first
test program with my default user (immediately exits with retval 1).
Being run as root or as the system test user, the program runs as
expected (including crash with amd76x_pm). ldd shows no difference. Same
shell being used.
With kind regards,
F. Behrens
next prev parent reply other threads:[~2003-03-26 10:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 16:32 System time warping around real time problem - please help Fionn Behrens
2003-03-25 17:07 ` Richard B. Johnson
2003-03-25 17:17 ` Tim Schmielau
2003-03-25 18:12 ` Fionn Behrens
2003-03-25 18:29 ` Richard B. Johnson
2003-03-25 21:16 ` Fionn Behrens
2003-03-25 22:14 ` george anzinger
2003-03-25 22:55 ` Fionn Behrens
2003-03-26 0:13 ` Alan Cox
2003-03-26 2:28 ` george anzinger
2003-03-26 14:38 ` Alan Cox
2003-03-26 16:12 ` george anzinger
2003-03-26 17:06 ` Richard B. Johnson
2003-03-26 18:12 ` george anzinger
2003-03-26 3:11 ` Chris Friesen
2003-03-26 14:35 ` Alan Cox
2003-03-26 10:48 ` Fionn Behrens [this message]
[not found] <20030325164014$031c@gated-at.bofh.it>
2003-03-26 9:31 ` Kay Diederichs
-- strict thread matches above, loose matches on Subject: below --
2003-04-03 13:22 Fionn Behrens
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=1048675698.4951.17.camel@rtfm \
--to=fionn@unix-ag.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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