From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 27536] Bus error 7 with todays DRT bisected.
Date: Thu, 8 Apr 2010 06:34:51 -0700 (PDT) [thread overview]
Message-ID: <20100408133451.486C313005D@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-27536-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=27536
--- Comment #1 from Andy Furniss <lists@andyfurniss.entadsl.com> 2010-04-08 06:34:51 PDT ---
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
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next prev parent reply other threads:[~2010-04-08 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 13:25 [Bug 27536] New: Bus error 7 with todays DRT bisected bugzilla-daemon
2010-04-08 13:34 ` bugzilla-daemon [this message]
2010-04-08 20:13 ` [Bug 27536] " bugzilla-daemon
2010-04-20 11:28 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100408133451.486C313005D@annarchy.freedesktop.org \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox