Bug 19394 - Crash on suspend/resume and return to console with 1 monitor turned off
Summary: Crash on suspend/resume and return to console with 1 monitor turned off
Status: RESOLVED NOTOURBUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/radeonhd (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Luc Verhaegen
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-04 18:15 UTC by Pyotr Berezhkov
Modified: 2009-01-08 02:16 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (88.20 KB, text/plain)
2009-01-06 10:36 UTC, Pyotr Berezhkov
no flags Details
gdb backtrace (2.66 KB, text/plain)
2009-01-06 10:37 UTC, Pyotr Berezhkov
no flags Details

Description Pyotr Berezhkov 2009-01-04 18:15:26 UTC
Suspending and mode switching (to console) crash with two monitors
physically connected and one monitor turned OFF.  No problem with both
monitors ON (xrandr --output VGA_1 --auto).

XRandR resizing works, but window placement is messed up when returning
from low resolution to normal resolution.

Hardware:
ASUS M3A78 Pro Motherboard
Athlon X2 5200+ 2700 MHz (Brisbane)
Host bridge: Advanced Micro Devices [AMD] RS780
VGA controller: Radeon HD 3200

Driver:
xf86-video-radeonhd git branch of Wed Dec 31 16:29:32 2008 +0100
(commit 421edfd7)
Comment 1 Matthias Hopf 2009-01-05 06:52:41 UTC
Can you try to create a stack dump from X? Depending on you distribution you have to install debug packages, and start X with xf86debug (or run it manually via a remote connection using gdb).

Also, always add Xorg.0.log
Comment 2 Pyotr Berezhkov 2009-01-06 10:36:27 UTC
Created attachment 21729 [details]
Xorg.0.log
Comment 3 Pyotr Berezhkov 2009-01-06 10:37:11 UTC
Created attachment 21730 [details]
gdb backtrace
Comment 4 Pyotr Berezhkov 2009-01-07 08:49:53 UTC
(Reply to Matthias Hopf)

Thanks much for your helpful advice.  Actually, after some more playing
around with the driver by running X over ssh, I discovered that the X
server isn't crashing at all, but simply blanking the screen.  Here's
the situation:

  X starts, both monitors display, except the VGA monitor is being
  driven at an incorrect resolution:

    # xrandr
    Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 1680 x 1680
    VGA_1 connected 1152x768+0+0 304mm x 228mm
       1024x768       60.0 +   75.1     71.9     70.1     60.0  
       1152x768       54.8* 
	. . .

  Note that the VGA monitor is 1024x768 pixel and doesn't even support
  the mode 1152x768.  (This happens with the radeon driver as well - see
  Bug 19393.)  The resolution can be fixed by issuing:

    # xrandr --output VGA_1 --auto
    Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 1680 x 1680
    VGA_1 connected 1024x768+0+0 304mm x 228mm
       1024x768       60.0*+   75.1     71.9     70.1     60.0* 
       1152x768       54.8  
	. . .

  Now, when I turn off the VGA monitor...

    # xrandr --output VGA_1 --off

  ...BOTH monitors go blank.  To get the DVI/HDMI monitor to display, I
  have to first turn it off, then on again:

    # xrandr --output DVI-D_1 --off
    # xrandr --output DVI-D_1 --auto
  
  After this, everything is OK.  I can turn the VGA monitor off and
  DVI/HDMI continues displaying.  Suspend/resume also works, with VGA on
  or off.  So obviously the problem here is with initialization.  And
  the incorrect mode for VGA mon. on startup is curious as well.

  -PGB
Comment 5 Matthias Hopf 2009-01-07 10:00:13 UTC
>   Now, when I turn off the VGA monitor...
>     # xrandr --output VGA_1 --off
>
>   ...BOTH monitors go blank.  To get the DVI/HDMI monitor to display, I
>   have to first turn it off, then on again:

*click*
I think I remember. Check the output of 'xrandr -v -q'. Check the used
CRTC for both outputs, check whether they are different. If they are
not, try using a different one (1 or 2) for one of the two outputs with
'xrandr --output xyz --crtc 2'. Then switching of the one output
shouldn't switch off the other one as well.

If that is the case, a newer xrandr will probably help you. I think I
fixed it for this case as well, for setting a different mode I fixed it
for sure.
Comment 6 Pyotr Berezhkov 2009-01-08 02:16:31 UTC
Bug closed, as it's not driver-related.


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.