failed to set mtrr: invalid argument

[Paul B. Mahol]

On 5/20/09, Robert Noland <rnoland at freebsd.org> wrote:
> On Wed, 2009-05-20 at 16:16 +0200, Paul B. Mahol wrote:
>> On 5/20/09, Robert Noland <rnoland at freebsd.org> wrote:
>> > On Tue, 2009-05-19 at 16:10 -0700, Chris H wrote:
>> >> > So, zapping is off by default now in 1.6.x.  If you want it, add
>> >> Option
>> >> > "DontZap" "off".  The cross hatch is also gone, that is what the
>> >> -retro
>> >> > option is supposed to do.  The session leader in a failsafe twm
>> >> session
>> >> > is the left hand xterm.  Typing exit in that window should exit the
>> >> > session.
>> >>
>> >> DOH! Sorry. My bad. I have since determined that turning off hald &&
>> >> dbus
>> >> improve performance. I built the X server with the hald option picked.
>> >> But, when I bounced the box, and started an X session (with a WM),
>> >> performance was improved. BUT. Performance pretty much sucks. I have 4
>> >> of these boards running with the onbord (mach64) video, and the mere
>> >> 2Mb
>> >> built in RAM. They run with better performance than does this one with
>> >> (200Mhz less CPU) comparable RAM && this one has 64Mb onboard && a
>> >> faster
>> >> Gpu. But they also run 6.4-STABLE && xorg-6.9.
>> >> So, I'm going to experiment by rebuilding the X server w/o the HAL
>> >> driver - make option && untick HAL. Then portupgrade -fi xorg-server.
>> >>
>> >> I'll report back should there be any improvement.
>> >
>> > So, the use of hal or not shouldn't produce any performance difference.
>> > It is only used to detect input devices kbd/mouse.
>> >
>> > One thing that I have discovered and I'm hoping for someone to send me a
>> > patch, is that if you build xorg-server without hal support it doesn't
>> > get linked to pthread libraries.  This causes issues with libdrm on
>> > Intel at least.  Not sure what else may be impacted.
>>
>> I ignored this info first time, but I will ask now. Does this implies
>> that libthr is listed in Xorg ldd(1) output?
>>
>> I use server build without hal support on 945GM(irq not MSI) and I do
>> not experience problems with drm/dri/OpenGL/xv or whatever other
>> protocol you name it.
>
> Yes, if xserver is built with HAL support, I see it linked with libthr.
> If HAL is disabled, it doesn't appear to be.  I'm trying to remember
> exactly what the reported issue was, but I think it was X crashing on
> exit.

Looking at xorg-server source I did not see anything that points it
must link to libthr, perhaps HAL support makes libthr linking
mandatory.

X doesnt crash on exit for me, well it did before (maybe because drm
outputs ressurected *pipe disabled* message on console all the time).
Should this finnaly be replaced with DRM_DEBUG ?

-- 
Paul