From: Thomas Renninger <trenn@suse.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"andreas.herrmann3" <andreas.herrmann3@amd.com>,
Richard <tuxbox.guru@gmail.com>,
eumaster@gmail.com, uli.geins@geins-web.de
Subject: Re: [PATCH] Re: AMD Mobile Semprons (3500+, 3600+,...) break with nohz and highres enabled
Date: Wed, 16 Jul 2008 21:56:00 +0200 [thread overview]
Message-ID: <200807162156.00983.trenn@suse.de> (raw)
In-Reply-To: <alpine.LFD.1.10.0807162100380.4316@apollo.tec.linutronix.de>
On Wednesday 16 July 2008 09:03:12 pm you wrote:
> On Wed, 16 Jul 2008, Thomas Renninger wrote:
> > This is against Andi's (ak) release branch,
> > hope that is ok...
>
> No idea what that is.
The branch Andi will merge his ACPI stuff into 2.6.27.
>
> > Can this one be reviewed/added, pls.
>
> Reviewed yes. Added no.
>
> > kernel/time/tick-sched.c | 31 +++++++++++++++++++++++++++++++
> > 1 files changed, 31 insertions(+), 0 deletions(-)
> >
> > diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
> > index b854a89..bda0164 100644
> > --- a/kernel/time/tick-sched.c
> > +++ b/kernel/time/tick-sched.c
> > @@ -589,6 +589,32 @@ static enum hrtimer_restart tick_sched_timer(struct
> > hrtimer *timer)
> > return HRTIMER_RESTART;
> > }
> >
> > +#if defined(CONFIG_X86) && defined(CONFIG_NO_HZ)
> > +static __init int is_nohz_broken(void)
> > +{
>
> We definitely do not add x86 quirks into the generic code.
So the right solution (if nobody cares about this one) is to set
tick_no_hz_enabled global and disable it through:
arch/x86/kernel/quirks.c
is that correct?
>
> Is there really no other way to fix this problem ?
I have no idea.
Richard's last message:
"I can help out as needed, just a work deadline I have to meet so I
haven't been able to dig further. Just point me in the direction and
I'll gladly be someones hands on the beastly machine"
has silently be ignored.
> Which chipset is
> involved here ? SB400/600 perhaps ?
No, it is probably much older and I am pretty sure that it is not chipset
related, but related to the "Mobile" in the Mobile Sempron as this exactly
seem to hit 3500 and 3600 Mobile Sempron CPUs.
I can't help much further because:
- I have not such a machine
- I don't know these parts. I hoped to get some hints to help these guys
Thomas
next prev parent reply other threads:[~2008-07-16 19:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 17:47 AMD Mobile Semprons (3500+, 3600+,...) break with nohz and highres enabled Thomas Renninger
2008-06-16 17:54 ` H. Peter Anvin
2008-06-16 20:06 ` Richard
2008-07-16 16:27 ` [PATCH] " Thomas Renninger
2008-07-16 19:03 ` Thomas Gleixner
2008-07-16 19:56 ` Thomas Renninger [this message]
2008-07-17 6:55 ` Richard
2008-07-17 10:51 ` Thomas Gleixner
2008-07-17 11:58 ` Richard
2008-07-17 11:11 ` Thomas Gleixner
2008-07-17 12:23 ` Richard
2008-07-17 12:03 ` Thomas Gleixner
2008-07-17 17:47 ` Richard
2008-07-17 16:59 ` Thomas Gleixner
2008-07-18 11:03 ` Richard
2008-07-18 17:12 ` Richard
2008-07-18 17:14 ` Richard
2008-07-18 17:15 ` Richard
2008-07-17 10:32 ` Thomas Renninger
2008-07-17 11:44 ` Richard
2008-07-17 11:05 ` Thomas Gleixner
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=200807162156.00983.trenn@suse.de \
--to=trenn@suse.de \
--cc=andreas.herrmann3@amd.com \
--cc=eumaster@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tuxbox.guru@gmail.com \
--cc=uli.geins@geins-web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.