tech-x11 archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Further DRM report on Intel chipset



Hi folks,

Well, the DRM with Intel is making progress, but I am still unable to get it work, even with the latest 2.2.1 driver and the latest drm code. But it is much better than before: I get a neat error code.

(II) intel(0): [drm] installed DRM signal handler
(II) intel(0): [DRI] installation complete
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x01000000 (pgoffset 4096)
(II) intel(0): xf86BindGARTMemory: bind key 1 at 0x02000000 (pgoffset 8192)
(II) intel(0): xf86BindGARTMemory: bind key 2 at 0x05000000 (pgoffset 20480)
(II) intel(0): xf86BindGARTMemory: bind key 3 at 0x06000000 (pgoffset 24576)
(II) intel(0): xf86BindGARTMemory: bind key 4 at 0x07000000 (pgoffset 28672)
(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB)
(II) intel(0): 0x00020000-0x00029fff: HW cursors (40 kB)
(II) intel(0): 0x0002a000-0x00031fff: logical 3D context (32 kB)
(II) intel(0): 0x00032000-0x00032fff: overlay registers (4 kB)
(II) intel(0): 0x00033000-0x00033fff: HW status (4 kB)
(II) intel(0): 0x006ff000:            end of stolen memory
(II) intel(0): 0x01000000-0x01ffffff: front buffer (11520 kB) X tiled
(II) intel(0): 0x02000000-0x041bffff: exa offscreen (34560 kB)
(II) intel(0): 0x05000000-0x05ffffff: back buffer (11520 kB) X tiled
(II) intel(0): 0x06000000-0x06ffffff: depth buffer (11520 kB) X tiled
(II) intel(0): 0x07000000-0x08ffffff: classic textures (32768 kB)
(II) intel(0): 0x10000000:            end of aperture
(II) intel(0): Output configuration:
(II) intel(0):   Pipe A is on
(II) intel(0):   Display plane A is now enabled and connected to pipe A.
(II) intel(0):   Pipe B is off
(II) intel(0):   Display plane B is now disabled and connected to pipe B.
(II) intel(0):   Output VGA is connected to pipe A
(EE) intel(0): hw status page initialization Failed
(EE) intel(0): Fail to setup hardware status page.
(II) intel(0): [drm] removed 1 reserved context for kernel
(II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xc1c46000 at 0xbb901000

Fatal server error:
AddScreen/ScreenInit failed for driver 0

(II) intel(0): xf86UnbindGARTMemory: unbind key 0
(II) intel(0): xf86UnbindGARTMemory: unbind key 1
(II) intel(0): xf86UnbindGARTMemory: unbind key 2
(II) intel(0): xf86UnbindGARTMemory: unbind key 3
(II) intel(0): xf86UnbindGARTMemory: unbind key 4

Now DRM_DEBUG shows this:

[drm:pid453:i915_initialize] hw status page @ 0xcc640000
[drm:pid453:i915_initialize] Enabled hardware status page
[drm:pid453:drm_ioctl] pid=453, cmd=0xc0186415, nr=0x15, dev 0xc19d5c00, auth=1
[drm:pid453:drm_addmap] offset = 0xd1000000, size = 0x00b40000, type = 3
[drm:pid453:drm_addmap] Added map 3 0xd1000000/0xb40000
[drm:pid453:drm_ioctl] pid=453, cmd=0xc0186415, nr=0x15, dev 0xc19d5c00, auth=1
[drm:pid453:drm_addmap] offset = 0xd5000000, size = 0x00b40000, type = 3
[drm:pid453:drm_addmap] Added map 3 0xd5000000/0xb40000
[drm:pid453:drm_ioctl] pid=453, cmd=0xc0186415, nr=0x15, dev 0xc19d5c00, auth=1
[drm:pid453:drm_addmap] offset = 0xd6000000, size = 0x00b40000, type = 3
[drm:pid453:drm_addmap] Added map 3 0xd6000000/0xb40000
[drm:pid453:drm_ioctl] pid=453, cmd=0xc0186415, nr=0x15, dev 0xc19d5c00, auth=1
[drm:pid453:drm_addmap] offset = 0xd7000000, size = 0x02000000, type = 3
[drm:pid453:drm_addmap] Added map 3 0xd7000000/0x2000000
[drm:pid453:drm_ioctl] pid=453, cmd=0x800c644a, nr=0x4a, dev 0xc19d5c00, auth=1 [drm:pid453:drm_ioctl] pid=453, cmd=0x80086447, nr=0x47, dev 0xc19d5c00, auth=1 [drm:pid453:drm_ioctl] pid=453, cmd=0x80086447, nr=0x47, dev 0xc19d5c00, auth=1 [drm:pid453:drm_ioctl] pid=453, cmd=0xc0086420, nr=0x20, dev 0xc19d5c00, auth=1
[drm:pid453:drm_ctxbitmap_next] drm_ctxbitmap_next bit : 1
[drm:pid453:drm_addctx] 1
[drm:pid453:drm_ioctl] pid=453, cmd=0x80086422, nr=0x22, dev 0xc19d5c00, auth=1 [drm:pid453:drm_ioctl] pid=453, cmd=0x8008642a, nr=0x2a, dev 0xc19d5c00, auth=1 [drm:pid453:drm_lock] 1 (pid 453) requests lock (0x00000000), flags = 0x00000000
[drm:pid453:drm_lock] 1 has lock
[drm:pid453:drm_ioctl] pid=453, cmd=0x8004667d, nr=0x7d, dev 0xc19d5c00, auth=1 [drm:pid453:drm_ioctl] pid=453, cmd=0x8004667c, nr=0x7c, dev 0xc19d5c00, auth=1 [drm:pid453:drm_ioctl] pid=453, cmd=0x8004644d, nr=0x4d, dev 0xc19d5c00, auth=1 [drm:pid453:drm_ioctl] pid=453, cmd=0x8004644d, nr=0x4d, dev 0xc19d5c00, auth=1 [drm:pid453:drm_ioctl] pid=453, cmd=0x8004644d, nr=0x4d, dev 0xc19d5c00, auth=1 [drm:pid453:drm_ioctl] pid=453, cmd=0x8004644d, nr=0x4d, dev 0xc19d5c00, auth=1 [drm:pid453:drm_ioctl] pid=453, cmd=0x80086451, nr=0x51, dev 0xc19d5c00, auth=1
[drm:pid453:drm_ioctl] Bad driver ioctl number, 0x11 (of 0xf)
[drm:pid453:drm_ioctl] pid=453, cmd=0x80446440, nr=0x40, dev 0xc19d5c00, auth=1 [drm:pid453:drm_ioctl] pid=453, cmd=0x8004667d, nr=0x7d, dev 0xc19d5c00, auth=1 [drm:pid453:drm_ioctl] pid=453, cmd=0xc0086421, nr=0x21, dev 0xc19d5c00, auth=1
[drm:pid453:drm_rmctx] 1
[drm:pid453:drm_ioctl] pid=453, cmd=0xc0086426, nr=0x26, dev 0xc19d5c00, auth=1 [drm:pid453:drm_ioctl] pid=453, cmd=0xc0086426, nr=0x26, dev 0xc19d5c00, auth=1 [drm:pid453:drm_ioctl] pid=453, cmd=0x8008642b, nr=0x2b, dev 0xc19d5c00, auth=1
[drm:pid453:drm_close] open_count = 1
[drm:pid453:drm_close] setting priv->refs 1 to 1
[drm:pid453:drm_close] setting open_count 1 to 1
[drm:pid453:drm_close_pid] pid = 453, device = 0xc19d5c00, open_count = 1
[drm:pid453:drm_lastclose]
[drm:pid453:drm_mtrr_del] offset=d0000000 size=4096
[drm:pid453:drm_rmmap] mtrr_del = 0
[drm:pid453:drm_lastclose]

So there seems to be a bad ioctl call. Any clue? I am going to dig farther in the code.


Vincent


Home | Main Index | Thread Index | Old Index