public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: sergio@sergiomb.no-ip.org
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	"Paul E. McKenney" <paulmck@us.ibm.com>,
	Dipankar Sarma <dipankar@in.ibm.com>,
	Arjan van de Ven <arjan@infradead.org>,
	Mike Galbraith <efault@gmx.de>,
	Daniel Walker <dwalker@mvista.com>,
	Manish Lachwani <mlachwani@mvista.com>,
	bastien.dugue@bull.net, Lee Revell <rlrevell@joe-job.com>
Subject: Re: 2.6.18-rt6
Date: Thu, 19 Oct 2006 17:59:58 -0700	[thread overview]
Message-ID: <1161305999.6961.142.camel@localhost> (raw)
In-Reply-To: <1161303812.3020.15.camel@localhost.portugal>

On Fri, 2006-10-20 at 01:23 +0100, Sergio Monteiro Basto wrote:
> I just test rt6 it in my problematic VIA Board with one PENTIUM D (DUAL)
> 
> 1. don't apply cleaning to 2.16.18.1 (on sparc arch )
> 2. I usual boot with notsc (because without it give me many lost time
> tickets)
>     I try 2.16.18.1-rt6 without notsc and freeze on boot. 
>     I try with notsc and says 
>         Time: acpi_pm clocksource has been installed.
>         Looks stable and don't show any lost timer ticket on dmesg.

Out of curiosity, does 2.6.18.1 require notsc (or booting w/
clocksource=acpi_pm) to be stable? Or is it just -rt6 that has this
problem?

> But I want also work with Nvidia dri which is a close drive from NVIDIA.
> I install that drive and I enable DRI, After a few minutes I got a
> spontaneous reboot.
> I will keep testing without nvidia close source.
> 
> And I like to know if this rt6 patch make this new clocksource (acpi_pm)
> or just found it and use it ? 

-rt6 includes a patch from Thomas Gleixner that disables the TSC if
dynticks are enabled in your config.

thanks
-john



  reply	other threads:[~2006-10-20  1:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18  8:39 2.6.18-rt6 Ingo Molnar
2006-10-18  9:14 ` 2.6.18-rt6 Sébastien Dugué
2006-10-18 10:05   ` 2.6.18-rt6 Ingo Molnar
2006-10-18 14:53 ` 2.6.18-rt6 Paul E. McKenney
2006-10-18 21:07 ` 2.6.18-rt6 Esben Nielsen
2006-10-20  0:23 ` 2.6.18-rt6 Sergio Monteiro Basto
2006-10-20  0:59   ` john stultz [this message]
2006-10-23 20:33     ` 2.6.18-rt6 and compile fail with rt7 on x86_64 Sergio Monteiro Basto
2006-10-20 15:00 ` 2.6.18-rt6 Lee Revell
2006-10-20 15:53   ` 2.6.18-rt6 Mark Knecht
2006-10-23 16:34   ` -rt7 announcement? (was Re: 2.6.18-rt6) Lee Revell
2006-10-23 18:29     ` Mark Knecht
2006-10-23 18:35     ` Thomas Gleixner
2006-10-23 18:44       ` Mark Knecht
2006-10-23 18:59         ` Thomas Gleixner
2006-10-23 20:09           ` Mark Knecht
2006-10-23 18:49       ` Lee Revell
2006-10-23 18:58         ` Thomas Gleixner
2006-10-23 20:26       ` Sergio Monteiro Basto
2006-10-23 20:40         ` Lee Revell
2006-10-24  1:26           ` -rt7 announcement? (was Re: 2.6.18-rt6) and more info about a compile error Sergio Monteiro Basto
2006-10-24  4:38             ` Thomas Gleixner
2006-10-24 16:48               ` Daniel Walker

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=1161305999.6961.142.camel@localhost \
    --to=johnstul@us.ibm.com \
    --cc=arjan@infradead.org \
    --cc=bastien.dugue@bull.net \
    --cc=dipankar@in.ibm.com \
    --cc=dwalker@mvista.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mlachwani@mvista.com \
    --cc=paulmck@us.ibm.com \
    --cc=rlrevell@joe-job.com \
    --cc=sergio@sergiomb.no-ip.org \
    --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