public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Voluspa <lista1@comhem.se>
Cc: tglx@linutronix.de, mingo@elte.hu, akpm@osdl.org, pavel@suse.cz,
	brugolsky@telemetry-investments.com,
	linux-kernel@vger.kernel.org
Subject: Re: hires timer patchset [was Re: 2.6.19 -mm merge plans]
Date: 23 Sep 2006 18:34:43 +0200
Date: Sat, 23 Sep 2006 18:34:43 +0200	[thread overview]
Message-ID: <20060923163443.GA51112@muc.de> (raw)
In-Reply-To: <20060923172517.01ec72b5@loke.fish.not>

On Sat, Sep 23, 2006 at 05:25:17PM +0200, Voluspa wrote:
> Andi,
> 
> See http://marc.theaimsgroup.com/?l=linux-kernel&m=115897798118500&w=2
> for my original report.
> 
> I've now built without NO_HZ (but still HIGH_RES_TIMERS) and that fixes
> the issue. You've got most of my machine specs since previous, even an
> output from dmidecode, but feel free to ask for more if this bug
> interests you.
> 
> I'm not particularly eager to get it solved... the nvidia driver still
> needs one more hack for the glue to build against -rt3.

-rt* bugs are handled by Ingo and Thomas.

-Andi

  reply	other threads:[~2006-09-23 16:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-23 15:25 hires timer patchset [was Re: 2.6.19 -mm merge plans] Voluspa
2006-09-23 16:34 ` Andi Kleen [this message]
2006-09-25 11:18 ` Arjan van de Ven
  -- strict thread matches above, loose matches on Subject: below --
2006-09-23  2:17 Voluspa
2006-09-23 18:09 ` Daniel Walker
2006-09-23 19:22   ` Voluspa
2006-09-23 19:58   ` Voluspa
2006-09-23 20:20     ` Ingo Molnar
2006-09-24  2:36       ` Voluspa
2006-09-20 20:54 2.6.19 -mm merge plans Andrew Morton
2006-09-21 13:14 ` Ingo Molnar
2006-09-22 13:06   ` Pavel Machek
2006-09-22 19:01     ` Ingo Molnar
2006-09-22 20:29       ` hires timer patchset [was Re: 2.6.19 -mm merge plans] Bill Rugolsky Jr.

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=20060923163443.GA51112@muc.de \
    --to=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=brugolsky@telemetry-investments.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lista1@comhem.se \
    --cc=mingo@elte.hu \
    --cc=pavel@suse.cz \
    --cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox