From: Richard <tuxbox.guru@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: trenn@suse.de, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>,
"andreas.herrmann3" <andreas.herrmann3@amd.com>,
eumaster@gmail.com, uli.geins@geins-web.de
Subject: Re: AMD Mobile Semprons (3500+, 3600+,...) break with nohz and highres enabled
Date: Mon, 16 Jun 2008 20:06:48 +0000 [thread overview]
Message-ID: <4856C7D8.4040508@gmail.com> (raw)
In-Reply-To: <4856A8E0.4060408@zytor.com>
H. Peter Anvin wrote:
> Thomas Renninger wrote:
>> - This affects AMD Mobile Semprons (at least 3500+ and 3600+)
>>
>> This seem to be a mainline kernel regression since the nohz/highres
>> patches have been added.
>> I do not own such a machine myself (Richard, Evgeny, Uli (and Anvin?)
>> have such a machine and already helped to come that far).
>
> 'Fraid I don't. :(
>
> -hpa
>
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 :-)
Richard
next prev parent reply other threads:[~2008-06-16 19:07 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 [this message]
2008-07-16 16:27 ` [PATCH] " Thomas Renninger
2008-07-16 19:03 ` Thomas Gleixner
2008-07-16 19:56 ` Thomas Renninger
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=4856C7D8.4040508@gmail.com \
--to=tuxbox.guru@gmail.com \
--cc=andreas.herrmann3@amd.com \
--cc=eumaster@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=trenn@suse.de \
--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.