Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 2 Sep 2009 16:24:18 +0200
From:      Rene Ladan <rene@freebsd.org>
To:        Andriy Gapon <avg@icyb.net.ua>
Cc:        freebsd-current@freebsd.org, x11@freebsd.org
Subject:   Re: DRI initialiazation fails on 8.0-BETAx/M54
Message-ID:  <e890cae60909020724j17d970d7x2e0db533b0c1eef5@mail.gmail.com>
In-Reply-To: <4A9E7B42.9070608@icyb.net.ua>
References:  <4A9D7560.7060902@freebsd.org> <1251840705.1689.4440.camel@balrog.2hip.net> <4A9E7B42.9070608@icyb.net.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
2009/9/2 Andriy Gapon <avg@icyb.net.ua>:
> on 02/09/2009 00:31 Robert Noland said the following:
>> On Tue, 2009-09-01 at 21:26 +0200, Rene Ladan wrote:
>>> Hi,
>>>
>>> it looks like DRI initalization sometimes fails on my 8.0-BETA3/amd64
>>> (official freebsd-update) laptop which has a ATI M54 card (radeonhd
>>> driver), reverting to software rendering for everything. The ports are
>>> up-to-date.
>>>
>>> =A0From Xorg.0.log:
>>> (EE) RADEONHD(0): rhdAtomGetDDCIndex: GPIO_DDC Index 6 exceeds maximum =
5
>>> ..
>>> (EE) RADEONHD(0): [pci] Out of memory (-12)
>>> (EE) RADEONHD(0): [pci] PCI failed to initialize. Disabling the DRI.
>>> ..
>>> (II) RADEONHD(0): Using MMIO Command Submission for aceleration.
>>> ...
>>>
>>> Full xorg.conf and Xorg.0.log(.old) are at ftp://rene-ladan/pub/freebsd=
/
>>>
>>> Any clues? =A0Could it be related to hald giving timeouts on acd0 after=
 which
>>> I just kill that hald subprocess and starting X after that?
>>
>> Is this happening when you start X after the system has been up for a
>> bit? =A0I suspect that what is happening is that memory has become
>> fragmented and since bus_dma tries to allocate large chunks of
>> contiguous memory for drm, it has a tendency to fail after the system
>> has been running for a bit. =A0This ultimately needs to be fixed in
>> bus_dma, but that hasn't happened yet.
>
> BTW, I have a different but potentially related problem - after running a
> head/current system for a while I am losing an ability to start VirtualBo=
x. It
> complains about something "no memory" too.
> The system is amd64 with 4G of RAM with only a handful of processes start=
ed.
> Maybe we got some regression in memory area (e.g. pmap)?
>
FWIW, my main memory size is 2GB.  I haven't tried vbox (yet).
More information at ftp://rene-ladan.nl/pub/freebsd/dmesg-80b3.txt

Ren=E9



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e890cae60909020724j17d970d7x2e0db533b0c1eef5>