[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1161305999.6961.142.camel@localhost>
Date: Thu, 19 Oct 2006 17:59:58 -0700
From: john stultz <johnstul@...ibm.com>
To: sergio@...giomb.no-ip.org
Cc: Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
"Paul E. McKenney" <paulmck@...ibm.com>,
Dipankar Sarma <dipankar@...ibm.com>,
Arjan van de Ven <arjan@...radead.org>,
Mike Galbraith <efault@....de>,
Daniel Walker <dwalker@...sta.com>,
Manish Lachwani <mlachwani@...sta.com>, bastien.dugue@...l.net,
Lee Revell <rlrevell@...-job.com>
Subject: Re: 2.6.18-rt6
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists