Bug 8191 - a running org crahses when swithing back from a fb console with dri enabled on an amd64 with a mga g550
a running org crahses when swithing back from a fb console with dri enabled o...
Status: NEW
Product: DRI
Classification: Unclassified
Component: DRM/other
unspecified
Other Linux (All)
: high normal
Assigned To: Default DRI bug account
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-09-08 07:08 UTC by markus gapp
Modified: 2013-03-26 11:00 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description markus gapp 2006-09-08 07:08:07 UTC
Hi, 

on an amd64 based system with 64 bit (gentoo) linux and xorg 

X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: Linux 2.6.17.11_hope3 x86_64
Current Operating System: Linux hope 2.6.17.11_hope3 #2 SMP Sun Sep 3 22:32:32 
CEST 2006 x86_64
Build Date: 05 September 2006
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present

the X server locks with a corrupted screen when switching back from a kernel 
framebuffer console to an already running instance, if dri on a matrox mga g550
 card is enbaled, complaining about:

Sep  7 11:19:22 hope [drm:mga_dma_reset] *ERROR* mga_dma_reset called without 
lock held
Sep  7 11:19:22 hope [drm:mga_dma_flush] *ERROR* mga_dma_flush called without 
lock held
Sep  7 11:19:22 hope [drm:mga_dma_reset] *ERROR* mga_dma_reset called without 
lock held
Sep  7 11:19:22 hope [drm:mga_dma_flush] *ERROR* mga_dma_flush called without 
lock held

[...]

in /var/log messages, and 

(EE) MGA(0): [dri] Idle timed out, resetting engine...
(EE) MGA(0): [dri] Idle timed out, resetting engine...
[..]

in Xorg.log

will attach a sample xorg.log.

thank you 

markus
Comment 1 Michal Suchanek 2006-11-30 14:26:29 UTC
I am getting lockups on x86 when switching to a dri enabled xorg from fb console
or another X server. Reproduced on Ubuntu with drm/mesa/mga head, xorg server
7.1.1ubuntu6, also Gentoo mga 1.4.1-r1, xserver 1.1.1-r1.
I tried several times on Ubuntu - it is the switch to the X server what crashes
it. It is possible to switch to console, terminate the X server, and start a new
one, all OK.
I am not sure how much the system locks up. I do not see anything special in the
Xorg log, and I cannot turn off the system using the acpi button. The screen
displays copy of the console content in somewhat garbled way, and a piece of the
X screen (probably leftover in the vram).
Comment 2 Michal Suchanek 2007-04-07 02:18:33 UTC
This does not happen for me with X server 1.2.0, mga 1.4.6.1, mesa 6.5.2, x86.
Comment 3 chemtech 2013-03-25 09:15:06 UTC
markus gapp,
Do you still experience this issue with newer soft ?
Please check the status of your issue.
Or close this bug.
Comment 4 markus gapp 2013-03-25 17:59:25 UTC
Hi, thanks for your interest. The affected machine died a year ago. I Don't have a matrox card right now. So, sorry, I can't test. Can't close either. markus
Comment 5 chemtech 2013-03-26 03:30:15 UTC
How can`t you close this bug?
Comment 6 markus gapp 2013-03-26 11:00:25 UTC
I only can change the status to: assigned, resolved oder needinfo -- none of them seems appropriate, but please feel free to change...

markus