From: john stultz <johnstul@us.ibm.com>
To: Adrian Yee <brewt-linux-kernel@brewt.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tsc clock issues with dual core and question about irq balancing
Date: Wed, 14 Dec 2005 12:14:32 -0800 [thread overview]
Message-ID: <1134591272.16294.3.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <GMail.1134551267.12292355.45625751005@brewt.org>
On Wed, 2005-12-14 at 01:07 -0800, Adrian Yee wrote:
> Hi John,
>
> >> I'm currently testing the system with "nosmp noapic acpi=off
> >> clock=tsc" (it was losing interrupts and wouldn't boot properly
> >> with apic/acpi on) and so far everything seems to work (this
> >> includes ssh and desktop usage is better).
> >
> > So keeping the above settings, does removing just the "clock=tsc"
> > cause the sluggishness to appear?
>
> I just tried booting with the pmtmr enabled and incoming ssh is bad
> (I had an ls pause for over 20 seconds, while another connection was
> somewhat fine). I wish I had more concrete tests since the problems
> I'm seeing are so subjective. I guess I'll have to ignore this
> problem until I get a better test.
>From your dmesg, you're still running w/ smp, apic, acpi as well. I was
curious if you could run just as you had before without issue using
"nosmp noapic acpi=off clock=tsc", only drop the clock=tsc bit.
I just want to be sure we're only changing one variable at a time. :)
> > Also would you open a bugzilla bug on this and attach your .config
> > and dmesg?
>
> Done: http://bugzilla.kernel.org/show_bug.cgi?id=5740
Thanks for filling that out! I'll see if I cannot reproduce anything
similar using your config.
thanks again,
-john
next prev parent reply other threads:[~2005-12-14 20:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-13 7:26 Adrian Yee
2005-12-14 1:04 ` john stultz
2005-12-14 9:07 ` Adrian Yee
2005-12-14 9:54 ` Jonas Oreland
2005-12-14 20:14 ` john stultz [this message]
2005-12-14 20:27 ` Adrian Yee
2005-12-14 20:57 ` john stultz
2005-12-14 23:47 ` Jeff Carr
2005-12-15 4:35 ` Adrian Yee
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=1134591272.16294.3.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=brewt-linux-kernel@brewt.org \
--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
all inboxes | Powered by JetHome®