On Sat, May 9, 2009 at 2:06 PM, Robert Noland wrote:
> Which update, what? I haven't touched the kernel tree in a while, just
> trying to sort it all out with patches here and there. Are you saying
> the the 2.7.0 intel driver helped? Or maybe the Xserver or mesa
> updates?
updating intel driv
On Sat, 2009-05-09 at 15:10 +0200, Dominic Fandrey wrote:
> Robert Noland wrote:
> > On Sat, 2009-05-09 at 10:26 +0200, Dominic Fandrey wrote:
> >> Robert Noland wrote:
> >>> On Fri, 2009-04-10 at 16:53 +0200, Dominic Fandrey wrote:
> Robert Noland wrote:
> > I've been working on the Intel
Robert Noland wrote:
> On Sat, 2009-05-09 at 10:26 +0200, Dominic Fandrey wrote:
>> Robert Noland wrote:
>>> On Fri, 2009-04-10 at 16:53 +0200, Dominic Fandrey wrote:
Robert Noland wrote:
> I've been working on the Intel vblank / irq issues. Every time I commit
> something thinking th
On Sat, 2009-05-09 at 10:26 +0200, Dominic Fandrey wrote:
> Robert Noland wrote:
> > On Fri, 2009-04-10 at 16:53 +0200, Dominic Fandrey wrote:
> >> Robert Noland wrote:
> >>> I've been working on the Intel vblank / irq issues. Every time I commit
> >>> something thinking that I have it resolved, i
Robert Noland wrote:
> On Fri, 2009-04-10 at 16:53 +0200, Dominic Fandrey wrote:
>> Robert Noland wrote:
>>> I've been working on the Intel vblank / irq issues. Every time I commit
>>> something thinking that I have it resolved, it isn't. So I'm waiting on
>>> hardware to arrive that will let me
Robert Noland wrote:
> On Fri, 2009-04-10 at 16:53 +0200, Dominic Fandrey wrote:
>> Robert Noland wrote:
>>> I've been working on the Intel vblank / irq issues. Every time I commit
>>> something thinking that I have it resolved, it isn't. So I'm waiting on
>>> hardware to arrive that will let me
On Fri, 2009-04-10 at 16:53 +0200, Dominic Fandrey wrote:
> Robert Noland wrote:
> > I've been working on the Intel vblank / irq issues. Every time I commit
> > something thinking that I have it resolved, it isn't. So I'm waiting on
> > hardware to arrive that will let me test this all more thoro
Robert Noland wrote:
> I've been working on the Intel vblank / irq issues. Every time I commit
> something thinking that I have it resolved, it isn't. So I'm waiting on
> hardware to arrive that will let me test this all more thoroughly. I do
> have a patch that I think fixes most of the issues
Robert Noland wrote:
> On Sat, 2009-04-04 at 12:31 +0200, Dominic Fandrey wrote:
>> Robert Noland wrote:
>>> On Fri, 2009-04-03 at 11:43 +0200, Dominic Fandrey wrote:
Alexander Motin wrote:
> Dominic Fandrey wrote:
>> I can rule out drm0 as the cause, because uhci0 is the only common
>
On Sat, 2009-04-04 at 12:24 -0700, Norbert Papke wrote:
> On April 4, 2009, Robert Noland wrote:
> > On Sat, 2009-04-04 at 10:01 -0700, Norbert Papke wrote:
> > > Hi Robert,
> > >
> > > On April 3, 2009, Robert Noland wrote:
> > > > Use a radeon? ;(
> > >
> > > Is there any particular model of Rade
On April 4, 2009, Robert Noland wrote:
> On Sat, 2009-04-04 at 10:01 -0700, Norbert Papke wrote:
> > Hi Robert,
> >
> > On April 3, 2009, Robert Noland wrote:
> > > Use a radeon? ;(
> >
> > Is there any particular model of Radeon PCIe that you would recommend?
>
> Most all of them should work ok...
On Sat, 2009-04-04 at 10:01 -0700, Norbert Papke wrote:
> Hi Robert,
>
> On April 3, 2009, Robert Noland wrote:
> > Use a radeon? ;(
>
> Is there any particular model of Radeon PCIe that you would recommend?
Most all of them should work ok... You won't have 3d on r600+ just yet,
but... I'm runn
Hi Robert,
On April 3, 2009, Robert Noland wrote:
> Use a radeon? ;(
Is there any particular model of Radeon PCIe that you would recommend?
Cheers,
-- Norbert Papke.
npa...@acm.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.or
On Sat, 2009-04-04 at 12:31 +0200, Dominic Fandrey wrote:
> Robert Noland wrote:
> > On Fri, 2009-04-03 at 11:43 +0200, Dominic Fandrey wrote:
> >> Alexander Motin wrote:
> >>> Dominic Fandrey wrote:
> I can rule out drm0 as the cause, because uhci0 is the only common
> presence in all oc
Robert Noland wrote:
> On Fri, 2009-04-03 at 11:43 +0200, Dominic Fandrey wrote:
>> Alexander Motin wrote:
>>> Dominic Fandrey wrote:
I can rule out drm0 as the cause, because uhci0 is the only common
presence in all occurrences of this problem.
>>> You have other examples? If you mean "
On Fri, 2009-04-03 at 11:43 +0200, Dominic Fandrey wrote:
> Alexander Motin wrote:
> > Dominic Fandrey wrote:
> >> I can rule out drm0 as the cause, because uhci0 is the only common
> >> presence in all occurrences of this problem.
> >
> > You have other examples? If you mean "irq16: hdac0 uhci+"
Dominic Fandrey wrote:
> Alexander Motin wrote:
>> Dominic Fandrey wrote:
>>> I can rule out drm0 as the cause, because uhci0 is the only common
>>> presence in all occurrences of this problem.
>> You have other examples? If you mean "irq16: hdac0 uhci+" string, then
>> "+" there means "and some o
Alexander Motin wrote:
> Dominic Fandrey wrote:
>> I can rule out drm0 as the cause, because uhci0 is the only common
>> presence in all occurrences of this problem.
>
> You have other examples? If you mean "irq16: hdac0 uhci+" string, then
> "+" there means "and some other devices", which in thi
Alexander Motin wrote:
> Dominic Fandrey wrote:
>> I can rule out drm0 as the cause, because uhci0 is the only common
>> presence in all occurrences of this problem.
>
> You have other examples? If you mean "irq16: hdac0 uhci+" string, then
> "+" there means "and some other devices", which in thi
Alexander Motin wrote:
> Dominic Fandrey wrote:
>> I can rule out drm0 as the cause, because uhci0 is the only common
>> presence in all occurrences of this problem.
>
> You have other examples? If you mean "irq16: hdac0 uhci+" string, then
> "+" there means "and some other devices", which in thi
Dominic Fandrey wrote:
I can rule out drm0 as the cause, because uhci0 is the only common
presence in all occurrences of this problem.
You have other examples? If you mean "irq16: hdac0 uhci+" string, then
"+" there means "and some other devices", which in this case is probably
drm0.
There
Dominic Fandrey wrote:
> Dominic Fandrey wrote:
>> Alexander Motin wrote:
>>> Dominic Fandrey wrote:
Alexander Motin wrote:
> It means that one of your CPUs spent most of it's time in interrupt
> processing and so far from idle. What does `top -P` shows you? Where
> have you seen t
Dominic Fandrey wrote:
> Alexander Motin wrote:
>> Dominic Fandrey wrote:
>>> Alexander Motin wrote:
It means that one of your CPUs spent most of it's time in interrupt
processing and so far from idle. What does `top -P` shows you? Where
have you seen that ~6% CPU load?
>>> That is t
Alexander Motin wrote:
> Dominic Fandrey wrote:
>> Alexander Motin wrote:
>>> It means that one of your CPUs spent most of it's time in interrupt
>>> processing and so far from idle. What does `top -P` shows you? Where
>>> have you seen that ~6% CPU load?
>>
>> That is the load shown by the e17 CPU
Dominic Fandrey wrote:
Alexander Motin wrote:
It means that one of your CPUs spent most of it's time in interrupt
processing and so far from idle. What does `top -P` shows you? Where
have you seen that ~6% CPU load?
That is the load shown by the e17 CPU module. It's display has always
been in
Alexander Motin wrote:
> Dominic Fandrey wrote:
>> Alexander Motin wrote:
>>> Dominic Fandrey wrote:
Alexander Motin wrote:
> Dominic Fandrey wrote:
>> Since I updated to the 7.2 prerelease, powerd is broken.
>>
>>> uname -a
>> FreeBSD mobileKamikaze.norad 7.2-PRERELEASE Fr
Dominic Fandrey wrote:
Alexander Motin wrote:
Dominic Fandrey wrote:
Alexander Motin wrote:
Dominic Fandrey wrote:
Since I updated to the 7.2 prerelease, powerd is broken.
uname -a
FreeBSD mobileKamikaze.norad 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #0:
Tue Mar 24 07:57:30 CET 2009
r...@m
Alexander Motin wrote:
> Dominic Fandrey wrote:
>> Alexander Motin wrote:
>>> Dominic Fandrey wrote:
Since I updated to the 7.2 prerelease, powerd is broken.
> uname -a
FreeBSD mobileKamikaze.norad 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #0:
Tue Mar 24 07:57:30 CET 2009
>>>
Dominic Fandrey wrote:
Alexander Motin wrote:
Dominic Fandrey wrote:
Since I updated to the 7.2 prerelease, powerd is broken.
uname -a
FreeBSD mobileKamikaze.norad 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #0:
Tue Mar 24 07:57:30 CET 2009
r...@mobilekamikaze.norad:/usr/obj/HP6510b/amd64/usr/
Alexander Motin wrote:
> Dominic Fandrey wrote:
>> Since I updated to the 7.2 prerelease, powerd is broken.
>>
>>> uname -a
>> FreeBSD mobileKamikaze.norad 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #0:
>> Tue Mar 24 07:57:30 CET 2009
>> r...@mobilekamikaze.norad:/usr/obj/HP6510b/amd64/usr/src/sys/H
Dominic Fandrey wrote:
Since I updated to the 7.2 prerelease, powerd is broken.
uname -a
FreeBSD mobileKamikaze.norad 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #0: Tue Mar
24 07:57:30 CET 2009
r...@mobilekamikaze.norad:/usr/obj/HP6510b/amd64/usr/src/sys/HP6510b amd64
It increases the CPU f
Since I updated to the 7.2 prerelease, powerd is broken.
> uname -a
FreeBSD mobileKamikaze.norad 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #0: Tue Mar
24 07:57:30 CET 2009
r...@mobilekamikaze.norad:/usr/obj/HP6510b/amd64/usr/src/sys/HP6510b amd64
It increases the CPU frequency very aggressivel
32 matches
Mail list logo
