Bug 70219 - [radeon] Cannot restore video mode after vt switch or GPU lockup
Summary: [radeon] Cannot restore video mode after vt switch or GPU lockup
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2013-10-07 09:17 UTC by Sergej Pupykin
Modified: 2019-11-19 08:38 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

dmesg (58.89 KB, text/plain)
2013-10-08 11:23 UTC, Sergej Pupykin
no flags Details
Xorg.log (42.46 KB, text/plain)
2013-10-08 11:24 UTC, Sergej Pupykin
no flags Details

Description Sergej Pupykin 2013-10-07 09:17:29 UTC
Steps to reproduce:
- boot using "radeon.modeset=1 video=DIN-1:1024x768-24@60e"
- switch off S-Video: "xrandr --output DIN --off"
- Ctrl+Alt+F1 - vt1 console appears
- Ctrl+Alt+F7 - monitor shows no video input

- Ctrl+Alt+F1 again
- login and export proper DISPLAY
- xrandr --output DIN --auto
- Ctrl+Alt+F7 - Xorg works

Booting with forced S-Video and switching it off from Xorg makes problem. Also video mode cannot be restored in this case after GPU lockup. Restarting Xorg from vt1 helps too.

Arch Linux x86_64
linux 3.11.3-1
xorg-server 1.14.3-1
libdrm 2.4.46-2
xf86-video-ati 1:7.2.0-1
Comment 1 Alex Deucher 2013-10-07 16:24:47 UTC
Please attach your xorg log and dmesg output.
Comment 2 Sergej Pupykin 2013-10-08 11:23:48 UTC
Created attachment 87272 [details]
Comment 3 Sergej Pupykin 2013-10-08 11:24:18 UTC
Created attachment 87273 [details]
Comment 4 Martin Peres 2019-11-19 08:38:55 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/393.

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.