Nouveau - Aug 2007 - [Bug 11918] New: drmMap of framebuffer failed

http://bugs.freedesktop.org/show_bug.cgi?id=11918

           Summary: drmMap of framebuffer failed
           Product: Mesa
           Version: CVS
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/nouveau
        AssignedTo: nouveau at lists.freedesktop.org
        ReportedBy: pmandin at caramail.com


With latest drm changes (0.0.10 revision), glxgears (and maybe other GL apps)
fails to initialize nouveau dri:

libGL error: drmMap of framebuffer failed (Invalid argument)
libGL error: reverting to (slow) indirect rendering


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.freedesktop.org/show_bug.cgi?id=11918





------- Comment #1 from carlos at cmartin.tk  2007-08-09 11:44 PST -------
This is due to the glxext trying to mmap part of the card's memory. With my
card it's trying to allocate half the card's memory (64KiB).

It is possible to map an amount of memory equal to that which the DRM has
allocated for itself in its own channel, so my guess is that it's affecting
it
somehow.

By eliminating the call for the DRM to get its own channel, this mapping
succeeds.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.freedesktop.org/show_bug.cgi?id=11918





------- Comment #2 from pq at iki.fi  2007-08-09 12:53 PST -------
I hit this too, all DRM, DDX and DRI from today.

There seems to be a collision of mappings (as noticed by cmn) in the DRM:

[ 3024.352588] [drm:drm_addmap_core] offset = 0xf0000000, size = 0x04000000,
type = 0
...
[ 3024.368286] [drm:nouveau_dma_channel_init] 
[ 3024.368291] [drm:drm_addmap_core] offset = 0xf0000000, size = 0x00008000,
type = 0
[ 3024.368295] [drm:drm_addmap_core] Matching maps of type 0 with mismatched
sizes, (32768 vs 67108864)
[ 3024.368299] [drm] allocated 0x0
[ 3024.368303] [drm] Allocating FIFO number 0
[ 3024.368306] [drm:nouveau_notifier_init_channel] Allocating notifier block in
262
[ 3024.368310] [drm:drm_addmap_core] offset = 0x00000000, size = 0x00001000,
type = 3
[ 3024.368314] [drm:drm_addmap_core] AGP offset = 0xe8000000, size = 0x00001000
[ 3024.368317] [drm] allocated 0x0

Notice how at the address 0xf0000000, which is the start of my VRAM, first is
allocated the FB block of 64MB, and then a block of 32kB, which overwrites the
previous 64MB mapping. I.e., creating the FIFO for the DRM messes things up,
but perhaps just triggers a bug elsewhere, in DRI parameter communication.

Later in the log:
[ 3024.370650] [drm:drm_addmap_core] offset = 0xf0008000, size = 0x04000000,
type = 0

Now, the DDX seems to be ok with this, because /proc/<Xserver>/maps
contains
the line:
2b95ab8ed000-2b95af8ed000 rw-s f0008000 00:0b 41226                     
/dev/dri/card0

But however, glxinfo tries to do the following syscall:
mmap(NULL, 67108864, PROT_READ|PROT_WRITE, MAP_SHARED, 4, 0xf0000000) = -1
EINVAL (Invalid argument)
which leads to the "drmMap of framebuffer failed" error message.

cmn therefore inferred that libGL does not get the correct information for
mapping the framebuffer, but tries it with a wrong address. A quote:
< cmn> glxext knows the offset at which it should request the FB memory
from
XF86DRIGetDeviceInfo(), but I haven't been able to see where we tell it the
address


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.freedesktop.org/show_bug.cgi?id=11918





------- Comment #3 from carlos at cmartin.tk  2007-08-09 13:27 PST -------
xf86-video-nouveau/src/nv_dri.c has a comment showing that we expect (and need)
the FB to be at the beginning of the physical VRAM space.

This has broken now because FIFOs are created in VRAM, so when DRM allocates a
FIFO for itself, it allocates it at the beginning of VRAM, creating a mapping
which is much smaller (32KiB) than the one glxext expects to find at that
offset (namely, half the VRAM).

A second mapping is created, but currently neither the DDX nor glxext are aware
of this change and expect the FB address not to move.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.freedesktop.org/show_bug.cgi?id=11918





------- Comment #4 from carlos at cmartin.tk  2007-08-09 15:01 PST -------
Created an attachment (id=11070)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=11070&action=view)
Move the FB to the high half of VRAM

In the attached patch I move the FB to the higher half of the VRAM. We probably
won't run into this bug again, as it's unlikely that that much memory is
taken.
In the final solution I'd like for the DDX to know where the FB should be
located based on other allocations, but I don't know if that is possible.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.freedesktop.org/show_bug.cgi?id=11918


carlos at cmartin.tk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Comment #5 from carlos at cmartin.tk  2007-08-11 05:04 PST -------
Patch committed upstream as a work-around until this mapping disappears.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugs.freedesktop.org/show_bug.cgi?id=11918


okias <d.okias at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |d.okias at gmail.com
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




--- Comment #6 from okias <d.okias at gmail.com>  2008-07-05 10:26:11 PST
---
I have this with lastest Nouveau too.

All aplication with 3D showing this error (glx*,openarena)

PIII 1Ghz, 512MB RAM, nVidia 7600 GS 256MB RAM DDR3[NV4B]

Debian testing/unstable


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=11918


okias <d.okias at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WORKSFORME




--- Comment #7 from okias <d.okias at gmail.com>  2008-07-07 06:52:13 PST
---
After lastest update libdrm and xserver-xorg-video-nouveau from Debian
experimental repositary, working.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=11918


ajax at nwnk dot net <ajax at nwnk.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|CVS                         |git




--- Comment #8 from ajax at nwnk dot net <ajax at nwnk.net>  2009-08-24
12:27:42 PST ---
Mass version move, cvs -> git


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.