Bug 27536 - Bus error 7 with todays DRT bisected.
Summary: Bus error 7 with todays DRT bisected.
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/R600 (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-08 06:25 UTC by Andy Furniss
Modified: 2010-04-20 04:28 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Andy Furniss 2010-04-08 06:25:58 UTC

    
Comment 1 Andy Furniss 2010-04-08 06:34:51 UTC
Card id rv670 AGP, running git xorg, ddx, mesa, libdrm and drt kernel.

Yesterdays DRT was fine for me, but after todays commits I am getting kicked out of X with a backtrace that looks like below. The trace varies from 3 down depending on what I was doing when triggering it, the one included was running x11perf -putimage500.

I can't restart X after this a it just gets another signal 7.

Happens with both agp gart and pcie gart.

Git bisect came up with -

b562614485ca2247384f540c859e00357fe7adcb is first bad commit
commit b562614485ca2247384f540c859e00357fe7adcb
Author: Jerome Glisse <jglisse@redhat.com>
Date:   Wed Apr 7 10:21:24 2010 +0000

    drm/radeon/kms: add support for new fault callback V6
    
    This add the support for the new fault callback and also the
    infrastructure for supporting unmappable VRAM.
    
    V2 validate BO with no_wait = true
    V3 don't derefence bo->mem.mm_node as it's not NULL only for
       VRAM or GTT
    V4 update to splitted no_wait ttm change
    V5 update to new balanced io_mem_reserve/free change
    V6 callback is responsible for iomapping memory



[    68.793] 0: /home/andy/Src/Xorg-git/modular/bin/Xorg (xorg_backtrace+0x3b) [0x80e05cb]
[    68.793] 1: /home/andy/Src/Xorg-git/modular/bin/Xorg (0x8048000+0x5a325) [0x80a2325]
[    68.793] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]
[    68.793] 3: /home/andy/Src/Xorg-git/modular/lib/xorg/modules/libexa.so (0xb71bc000+0x728e) [0xb71c328e]
[    68.793] 4: /home/andy/Src/Xorg-git/modular/bin/Xorg (0x8048000+0xce6da) [0x81166da]
[    68.793] 5: /home/andy/Src/Xorg-git/modular/bin/Xorg (0x8048000+0x26274) [0x806e274]
[    68.793] 6: /home/andy/Src/Xorg-git/modular/bin/Xorg (0x8048000+0x25110) [0x806d110]
[    68.793] 7: /home/andy/Src/Xorg-git/modular/bin/Xorg (0x8048000+0x1a92c) [0x806292c]
[    68.793] 8: /lib/libc.so.6 (__libc_start_main+0xd0) [0xb73b9380]
[    68.793] 9: /home/andy/Src/Xorg-git/modular/bin/Xorg (0x8048000+0x1a531) [0x8062531]
[    68.793] Bus error at address 0xb6a80000
[    68.793] 
Fatal server error:
[    68.793] Caught signal 7 (Bus error). Server aborting
Comment 2 Andy Furniss 2010-04-08 13:13:24 UTC
(In reply to comment #0)
> 

More info - I am not enabling dynpm for these tests.

In dmesg after the signal 7 X shutdown I am seeing - 

vmap allocation for size 8192 failed: use vmalloc=<size> to increase size.
vmap allocation for size 49152 failed: use vmalloc=<size> to increase size.

This one was triggered by running glxgears for about 10 seconds.
Comment 3 Andy Furniss 2010-04-20 04:28:38 UTC
Fixed with todays drt.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.