http://bugs.freedesktop.org/show_bug.cgi?id=14575
Gordon Jin <[EMAIL PROTECTED]> changed:
What|Removed |Added
Priority|medium |high
--- Comment #1 f
http://bugs.freedesktop.org/show_bug.cgi?id=14344
--- Comment #8 from Shuang He <[EMAIL PROTECTED]> 2008-02-20 18:23:25 PST ---
backtrace:
Program received signal SIGABRT, Aborted.
[Switching to Thread 4158691552 (LWP 3189)]
0xe410 in __kernel_vsyscall ()
(gdb) bt
#0 0xe410 in __kern
http://bugs.freedesktop.org/show_bug.cgi?id=14344
--- Comment #7 from Shuang He <[EMAIL PROTECTED]> 2008-02-20 18:13:33 PST ---
(In reply to comment #6)
> Does it works on 32 bit system?
>
we only have 64-bit OS installed on Q35. and quake4-demo can run on G33 with
32-bit OS.
I just found,
http://bugs.freedesktop.org/show_bug.cgi?id=14344
--- Comment #6 from Zou Nan hai <[EMAIL PROTECTED]> 2008-02-20 17:16:04 PST ---
Does it works on 32 bit system?
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
Y
On Feb 20, 2008 5:20 AM, Michel Dänzer <[EMAIL PROTECTED]> wrote:
>
> On Fri, 2008-02-15 at 09:57 -0500, Kristian Høgsberg wrote:
> >
> > Anyway, the code is out there, shouldn't break anything unless you
> > enable it, [...]
>
> Actually, it looks like you broke at least direct rendering for every
http://bugs.freedesktop.org/show_bug.cgi?id=14518
--- Comment #14 from Joel Bosveld <[EMAIL PROTECTED]> 2008-02-20 04:32:23 PST
---
After loading drm module with debug=1 there is one extra entry in
/var/log/messages, which is the last thing before kernel panic:
" kernel: <7drm_unlocked_
http://bugs.freedesktop.org/show_bug.cgi?id=14518
--- Comment #13 from Joel Bosveld <[EMAIL PROTECTED]> 2008-02-20 04:06:52 PST
---
Is there any way I can get more log files (such as kernel panic output?) in
order to make finding the source of the problem easier?
--
Configure bugmail: htt
On Fri, 2008-02-15 at 09:57 -0500, Kristian Høgsberg wrote:
>
> Anyway, the code is out there, shouldn't break anything unless you
> enable it, [...]
Actually, it looks like you broke at least direct rendering for every
driver that doesn't provide __dri2DriverInitScreen because that symbol
is un
http://bugs.freedesktop.org/show_bug.cgi?id=13837
Colin.Joe <[EMAIL PROTECTED]> changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
--- Comment #