On Mon, Sep 27, 2010 at 5:18 PM, Vasily Khoruzhick wrote:
> On 26 of September 2010 13:53:35 Stefan Biereigel wrote:
>
> > Hello Everyone,
> > just to add on to reports of this problem, there was a Thread here in
> > LKML some months ago targeting the same problem (but not really
> > attacking it
On 26 of September 2010 13:53:35 Stefan Biereigel wrote:
> Hello Everyone,
> just to add on to reports of this problem, there was a Thread here in
> LKML some months ago targeting the same problem (but not really
> attacking it at the Chipset driver). As I have one of those Laptops with
> a 945GM-
On 27 of September 2010 03:46:23 Shaohua Li wrote:
> does disable msi help with 'pci=nomsi'?
Doesn't help on my system :(
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
2010/9/26 Shaohua Li
> 2010/9/26 Stefan Biereigel :
> > Am 24.09.2010 21:51, schrieb Jesse Barnes:
> >>
> >> On Fri, 24 Sep 2010 22:48:36 +0300
> >> Vasily Khoruzhick wrote:
> >>
> >>> On 24 of September 2010 22:39:01 Jesse Barnes wrote:
>
> On Thu, 16 Sep 2010 23:06:46 +0300
>
>
2010/9/26 Stefan Biereigel :
> Am 24.09.2010 21:51, schrieb Jesse Barnes:
>>
>> On Fri, 24 Sep 2010 22:48:36 +0300
>> Vasily Khoruzhick wrote:
>>
>>> On 24 of September 2010 22:39:01 Jesse Barnes wrote:
On Thu, 16 Sep 2010 23:06:46 +0300
Vasily Khoruzhick wrote:
>
> В
On Fri, 24 Sep 2010 22:48:36 +0300
Vasily Khoruzhick wrote:
> On 24 of September 2010 22:39:01 Jesse Barnes wrote:
> > On Thu, 16 Sep 2010 23:06:46 +0300
> >
> > Vasily Khoruzhick wrote:
> > > В сообщении от 16 of September 2010 21:50:50 автор Thomas Gleixner
> написал:
> > > > Ok. The problem
On 24 of September 2010 22:39:01 Jesse Barnes wrote:
> On Thu, 16 Sep 2010 23:06:46 +0300
>
> Vasily Khoruzhick wrote:
> > В сообщении от 16 of September 2010 21:50:50 автор Thomas Gleixner
написал:
> > > Ok. The problematic part of HPET was not the clocksource, it was the
> > > clock event devi
On Thu, 16 Sep 2010 23:06:46 +0300
Vasily Khoruzhick wrote:
> В сообщении от 16 of September 2010 21:50:50 автор Thomas Gleixner написал:
> > Ok. The problematic part of HPET was not the clocksource, it was the
> > clock event device which failed to deliver interrupts occasionally. It
> > was wor
On Thu, 16 Sep 2010 18:03:04 +0300
Vasily Khoruzhick wrote:
> В сообщении от 15 of September 2010 01:41:11 автор Sitsofe Wheeler написал:
> > > > processor.max_cstate=2
> > >
> > > Nope, it doesn't work with max_cstate=2
> >
> > Perhaps intel_idle is being used? Any mention of it in dmesg?
On 22 of September 2010 01:56:53 Jesse Barnes wrote:
> Can you guys try something like this? My theory is that 945GM has some
> power management behavior we're failing to configure correctly. If
> disabling it works, then it's likely related.
Nope, it doesn't help, sorry
> diff --git a/driver
On Tue, 21 Sep 2010 20:26:07 +0200
Paolo Ornati wrote:
> On Fri, 17 Sep 2010 15:50:43 +0300
> Vasily Khoruzhick wrote:
>
> > > Vasily, can you try the qos workaround on your machine and see if it works
> > > too?
> > >
> > > Thanks,
> >
> > Just give me a patch :)
>
> Me too...
>
> I've a
В сообщении от 17 of September 2010 19:30:26 автор Jesse Barnes написал:
> Yeah if that works we could definitely add some qos calls to the driver.
> When vblanks are alive we'd need a latency less tha the refresh rate, and
> when commands are oustanding we'd probably want it even lower.
>
> Vasi
Yeah if that works we could definitely add some qos calls to the driver. When
vblanks are alive we'd need a latency less tha the refresh rate, and when
commands are oustanding we'd probably want it even lower.
Vasily, can you try the qos workaround on your machine and see if it works too?
Than
On Thursday 16 September 2010, Vasily Khoruzhick wrote:
> В сообщении от 15 of September 2010 01:41:11 автор Sitsofe Wheeler написал:
> > > > processor.max_cstate=2
> > >
> > > Nope, it doesn't work with max_cstate=2
> >
> > Perhaps intel_idle is being used? Any mention of it in dmesg?
>
>
В сообщении от 16 of September 2010 21:50:50 автор Thomas Gleixner написал:
> Ok. The problematic part of HPET was not the clocksource, it was the
> clock event device which failed to deliver interrupts occasionally. It
> was worth a try at least.
Hm, it seems that jerky glxgears is not related to
В сообщении от 16 of September 2010 21:30:58 автор Vasily Khoruzhick написал:
> В сообщении от 16 of September 2010 21:07:39 автор Thomas Gleixner написал:
> > > Btw, Jesse, any comments/solutions/workarounds except one with
> > > processor.max_cstate=1 in kernel commandline? Should I file a bug on
В сообщении от 16 of September 2010 21:07:39 автор Thomas Gleixner написал:
> > Btw, Jesse, any comments/solutions/workarounds except one with
> > processor.max_cstate=1 in kernel commandline? Should I file a bug on fdo
> > bugzilla?
>
> we fixed a HPET related bug a few days ago, which might be
В сообщении от 15 of September 2010 01:41:11 автор Sitsofe Wheeler написал:
> > > processor.max_cstate=2
> >
> > Nope, it doesn't work with max_cstate=2
>
> Perhaps intel_idle is being used? Any mention of it in dmesg?
Sitsofe, maybe you misunderstood me, I mean with max_cstate=1 graphics is
В сообщении от 15 of September 2010 01:41:11 автор Sitsofe Wheeler написал:
> On Tue, Sep 14, 2010 at 03:29:48PM +0300, Vasily Khoruzhick wrote:
> > В сообщении от 14 of September 2010 12:52:57 автор Thomas Gleixner
написал:
> > > Can you try with NOHZ enabled and the following on the kernel comma
В сообщении от 14 of September 2010 12:52:57 автор Thomas Gleixner написал:
> Can you try with NOHZ enabled and the following on the kernel command line:
>
> processor.max_cstate=1
It works in this case (gears in glxgears move smoothly)
> If that works, then try
>
> processor.max_cstat
В сообщении от 14 of September 2010 03:55:32 автор Venkatesh Pallipadi
написал:
> Whats the clockevent in this case ("Tick Device" section of
> /proc/timer_list). clocksource= option only changes the clocksource used
> to maintain
> timeofday. But, timer interrupt (clockevent) source will not cha
В сообщении от 14 of September 2010 00:59:52 автор Jesse Barnes написал:
> On Tue, 14 Sep 2010 00:52:31 +0300
>
> Vasily Khoruzhick wrote:
> > В сообщении от 14 of September 2010 00:46:32 автор Jesse Barnes написал:
> > > Yes, you can set vblank_mode=0 in your environment or drirc. At least
> >
On Tue, 14 Sep 2010 00:52:31 +0300
Vasily Khoruzhick wrote:
> В сообщении от 14 of September 2010 00:46:32 автор Jesse Barnes написал:
>
> > Yes, you can set vblank_mode=0 in your environment or drirc. At least
> > I think 0 is no vsync. :)
>
> That doesn't help, glxgears shows ~1000fps, but i
В сообщении от 14 of September 2010 00:46:32 автор Jesse Barnes написал:
> Yes, you can set vblank_mode=0 in your environment or drirc. At least
> I think 0 is no vsync. :)
That doesn't help, glxgears shows ~1000fps, but it's output is jerky.
signature.asc
Description: This is a digitally sign
On Tue, 14 Sep 2010 00:41:18 +0300
Vasily Khoruzhick wrote:
> В сообщении от 14 of September 2010 00:19:55 автор Jesse Barnes написал:
> > On Tue, 14 Sep 2010 00:10:08 +0300
> >
> > Vasily Khoruzhick wrote:
> > > В сообщении от 13 of September 2010 23:44:41 автор Jesse Barnes написал:
> > > > I
В сообщении от 14 of September 2010 00:19:55 автор Jesse Barnes написал:
> On Tue, 14 Sep 2010 00:10:08 +0300
>
> Vasily Khoruzhick wrote:
> > В сообщении от 13 of September 2010 23:44:41 автор Jesse Barnes написал:
> > > I remember seeing a similar problem on an Eee PC I had; it seemed to be
> >
On Tue, 14 Sep 2010 00:10:08 +0300
Vasily Khoruzhick wrote:
> В сообщении от 13 of September 2010 23:44:41 автор Jesse Barnes написал:
> > I remember seeing a similar problem on an Eee PC I had; it seemed to be
> > timer/interrupt related somehow. If I booted with clocksource=tsc
> > (or maybe i
27 matches
Mail list logo
