From: hotdog day <hotdogday@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc2 and Hyperthreading. (SMT)
Date: Tue, 14 Sep 2004 00:44:07 -0500 [thread overview]
Message-ID: <7798951e040913224462ea2243@mail.gmail.com> (raw)
In-Reply-To: <7798951e04091322402fe830ff@mail.gmail.com>
Does anyone have any other suggestions on this issue? I know others
who are experincing the same thing.
On Tue, 14 Sep 2004 00:40:57 -0500, hotdog day <hotdogday@gmail.com> wrote:
> Actually, it just hardlocked again. Is there anything else that could
> be done, or am I stuck without SMP?
>
>
>
>
> On Mon, 13 Sep 2004 23:21:05 -0500, hotdog day <hotdogday@gmail.com> wrote:
> > Turning off CONFIG_SCHED_SMT has apparently fixed the issue.
> >
> > Three Q's:
> >
> > 1) Am I taking some kind of performance hit by doing this?
> >
> > 2) Is this something we can look forward to seeing fixed?
> >
> > 3) Do you need any info from me to help you?
> >
> > Thanks,
> >
> > Troy McFerron
> >
> >
> >
> >
> > On Tue, 14 Sep 2004 12:07:00 +1000, Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> > >
> > >
> > > hotdog day wrote:
> > > > I have been testing the 2.6.9-rc1, and 2.6.9-rc2 kernel patches over
> > > > the past couple days and have been having some issues with
> > > > hyperthreading (SMT) turned on.
> > > >
> > > > This problem first exhibited itself when I was testing
> > > > 2.6.9-rc2-mm2-love2. I noticed the following quirks that ONLY show
> > > > themselves with hyperthreading enabled on my 3.0C Pentium 4.
> > > >
> > > > Random HARD LOCKS. No messages from the kernel. Just a good swift hard lock.
> > > >
> > > > Hard locks when mounting two cdrom drives in quick succession.
> > > >
> > > > Turning off hyperthreading solves these issues. Going back to 2.6.8.1
> > > > solves these issues.
> > > >
> > > > I then tried 2.6.9-rc1 with no mm or love patches. I had the exact same issues.
> > > >
> > > > Today I downloaded the prepatch to 2.6.9-rc2 and applied it to clean
> > > > 2.6.8 source. The issues are still there.
> > > >
> > > > I hope someone is paying attention to the way scheduler tweaks and
> > > > changes are affecting SMT enabled kernels. I don't think anyone wants
> > > > to disable features of their hardware in order to run an optimized
> > > > scheduler.
> > >
> > > Try turning off CONFIG_SCHED_SMT and see how you go. Thanks.
> > >
> >
>
next prev parent reply other threads:[~2004-09-14 5:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 0:27 2.6.9-rc2 and Hyperthreading. (SMT) hotdog day
2004-09-14 2:07 ` Nick Piggin
2004-09-14 4:21 ` hotdog day
[not found] ` <7798951e04091322402fe830ff@mail.gmail.com>
2004-09-14 5:44 ` hotdog day [this message]
2004-09-15 1:11 ` Darren Williams
2004-09-15 6:09 ` Troy McFerrron
2004-09-15 10:10 ` Darren Williams
2004-09-15 22:59 ` Darren Williams
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=7798951e040913224462ea2243@mail.gmail.com \
--to=hotdogday@gmail.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