http://bugs.freedesktop.org/show_bug.cgi?id=23670
--- Comment #6 from Shuang He 2009-09-08 23:01:02 PST ---
(In reply to comment #5)
> (In reply to comment #4)
> > Could you provide more details about the failing cases (maybe run conform
> > with
> > -v 2)? It looks like the failures are r
http://bugs.freedesktop.org/show_bug.cgi?id=23670
--- Comment #5 from Shuang He 2009-09-08 22:40:03 PST ---
(In reply to comment #4)
> Could you provide more details about the failing cases (maybe run conform with
> -v 2)? It looks like the failures are related to glCopyPixels(GL_DEPTH) and
2009/9/9 Mike Lothian :
> I'm reporting a regression from the r6xx-r7xx-3d tree, the new code
> causes X to restart
Probably EXA (already confirmed on some machines) bug. What is your
X's backtrace?
--
Rafał
--
Let Crys
On Tue, Sep 8, 2009 at 8:20 PM, Mike Lothian wrote:
> 2009/9/9 Alex Deucher :
>> On Tue, Sep 8, 2009 at 7:17 PM, Mike Lothian wrote:
>>> 2009/9/8 Mike Lothian :
2009/9/8 Alex Deucher :
> On Tue, Sep 8, 2009 at 6:34 PM, Mike Lothian wrote:
>> Hi
>>
>> When using the new drm-next
2009/9/9 Alex Deucher :
> On Tue, Sep 8, 2009 at 7:17 PM, Mike Lothian wrote:
>> 2009/9/8 Mike Lothian :
>>> 2009/9/8 Alex Deucher :
On Tue, Sep 8, 2009 at 6:34 PM, Mike Lothian wrote:
> Hi
>
> When using the new drm-next branch KMS fails (see attached logs) with
> radeon.modes
On Tue, Sep 8, 2009 at 7:17 PM, Mike Lothian wrote:
> 2009/9/8 Mike Lothian :
>> 2009/9/8 Alex Deucher :
>>> On Tue, Sep 8, 2009 at 6:34 PM, Mike Lothian wrote:
Hi
When using the new drm-next branch KMS fails (see attached logs) with
radeon.modeset=0 passed the computer will har
Hi
When using the new drm-next branch KMS fails (see attached logs) with
radeon.modeset=0 passed the computer will hard lockup when KDM is
starting (I think this is when the compositing is started)
Unfortunately I don't have any logs of the hard crash even a remote
ssh with tail -f /var/log/messa
2009/9/8 Mike Lothian :
> 2009/9/8 Alex Deucher :
>> On Tue, Sep 8, 2009 at 6:34 PM, Mike Lothian wrote:
>>> Hi
>>>
>>> When using the new drm-next branch KMS fails (see attached logs) with
>>> radeon.modeset=0 passed the computer will hard lockup when KDM is
>>> starting (I think this is when the
2009/9/8 Alex Deucher :
> On Tue, Sep 8, 2009 at 6:34 PM, Mike Lothian wrote:
>> Hi
>>
>> When using the new drm-next branch KMS fails (see attached logs) with
>> radeon.modeset=0 passed the computer will hard lockup when KDM is
>> starting (I think this is when the compositing is started)
>
> [drm
On Tue, Sep 8, 2009 at 6:34 PM, Mike Lothian wrote:
> Hi
>
> When using the new drm-next branch KMS fails (see attached logs) with
> radeon.modeset=0 passed the computer will hard lockup when KDM is
> starting (I think this is when the compositing is started)
[drm:r600_ib_test] *ERROR* radeon: fen
http://bugs.freedesktop.org/show_bug.cgi?id=23670
--- Comment #4 from Brian Paul 2009-09-08 15:32:57
PST ---
Could you provide more details about the failing cases (maybe run conform with
-v 2)? It looks like the failures are related to glCopyPixels(GL_DEPTH) and
glDrawPixels(GL_DEPTH_COMP
http://bugs.freedesktop.org/show_bug.cgi?id=23793
Alex Deucher changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On Tue, 08 Sep 2009 10:37:38 +0200
Michel Dänzer wrote:
> On Sun, 2009-09-06 at 09:46 -0700, Jesse Barnes wrote:
> > On Sun, 06 Sep 2009 12:23:12 +0200
> > Michel Dänzer wrote:
> >
> > > On Fri, 2009-09-04 at 12:17 -0700, Jesse Barnes wrote:
> > > > I've been working on coding up the server a
http://bugs.freedesktop.org/show_bug.cgi?id=23793
--- Comment #2 from 414N 2009-09-08 09:40:35 PST ---
(In reply to comment #1)
> Looks like bug 13176. Does the patch there in comment 18 help?
Yes, it helps. I forgot to mention my kernel version before: it is 2.6.29.6.
OpenOffice doesn't h
http://bugs.freedesktop.org/show_bug.cgi?id=23793
--- Comment #1 from Alex Deucher 2009-09-08 08:44:27 PST ---
Looks like bug 13176. Does the patch there in comment 18 help?
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail beca
http://bugs.freedesktop.org/show_bug.cgi?id=23793
Alex Deucher changed:
What|Removed |Added
Attachment #29339|application/octet-stream|text/plain
mime type|
http://bugs.freedesktop.org/show_bug.cgi?id=20647
--- Comment #18 from 414N 2009-09-08 08:33:37 PST ---
(In reply to comment #17)
> I'm gonna open a new bug report.
Done. It's bug #23793
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving
http://bugs.freedesktop.org/show_bug.cgi?id=23793
Summary: OpenOffice and wine cause X hang-ups on radeon X800 XT
PE
Product: DRI
Version: XOrg 6.7.0
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
http://bugs.freedesktop.org/show_bug.cgi?id=20647
--- Comment #17 from 414N 2009-09-08 08:09:45 PST ---
> Sounds like bug 13176. Please try the patch there in comment 18.
Don't know why I didn't see this before.
After the hang up occurs, the X log gets filled with these messages:
[mi] EQ
On Tue, Sep 8, 2009 at 8:26 AM, Pauli Nieminen wrote:
> Bliting data while some of engines is still running or 2D engine as dirty
> cache may cause pixmap or font glyph corruption.
>
> Fix is to wait for 3D engine to be idle. Then we have to also flush 2D engine
> in case if cache has outdated data
http://bugs.freedesktop.org/show_bug.cgi?id=20647
--- Comment #16 from Alex Deucher 2009-09-08 07:17:20 PST ---
(In reply to comment #14)
> I stumbled upon this "resolved bug" report searching a solution for my issue
> "not resolved", seeing symptoms so close to mines.
> I've got an ATI Rade
http://bugs.freedesktop.org/show_bug.cgi?id=23745
Michel Dänzer changed:
What|Removed |Added
Component|libdrm |DRM/other
--- Comment #1 from Michel
Bliting data while some of engines is still running or 2D engine as dirty
cache may cause pixmap or font glyph corruption.
Fix is to wait for 3D engine to be idle. Then we have to also flush 2D engine
in case if cache has outdated data for system memory where we are going to blit.
While it would
http://bugs.freedesktop.org/show_bug.cgi?id=20647
Michel Dänzer changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|
http://bugs.freedesktop.org/show_bug.cgi?id=20647
414N changed:
What|Removed |Added
CC||[email protected]
Status|RESOLVED
http://bugs.freedesktop.org/show_bug.cgi?id=23710
--- Comment #6 from Michel Dänzer 2009-09-08 01:53:22 PST
---
The hang is probably related to the DRI1 lock, and may not happen with DRI2.
Not sure anything can be done for DRI1, though this may have been made worse by
a recent signal relate
On Sun, 2009-09-06 at 09:46 -0700, Jesse Barnes wrote:
> On Sun, 06 Sep 2009 12:23:12 +0200
> Michel Dänzer wrote:
>
> > On Fri, 2009-09-04 at 12:17 -0700, Jesse Barnes wrote:
> > > I've been working on coding up the server and client side of
> > > SGI_video_sync, OML_sync_control and SGI_swap_
http://bugs.freedesktop.org/show_bug.cgi?id=23710
--- Comment #5 from Fabio 2009-09-08 01:07:13 PST ---
Just want to add that after killing the game without the patch I get this
assert:
doom.x86: radeon_mipmap_tree.c:117: compute_tex_image_offset: Assertion
`lvl->size > 0' failed.
while whe
http://bugs.freedesktop.org/show_bug.cgi?id=23710
--- Comment #4 from Fabio 2009-09-08 01:02:39 PST ---
OK, the game can indeed be killed from another box after sshing from it. I also
tried the patch attached to bug #22372 comment #8, but it doesn't change
anything.
Other bugs that may be r
29 matches
Mail list logo
