| Summary: | Turning off a monitor leaves a black screen which can only be recovered by a reboot. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Herbert Poetzl <herbert> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | herbert, marja11, tmb, yvesbrungard |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | radeon-firmware-20150722-1.mga5.nonfree (?) | CVE: | |
| Status comment: | |||
|
Description
Herbert Poetzl
2015-08-20 19:36:27 CEST
(In reply to Herbert Poetzl from comment #0) > Description of problem: > When turning off a monitor on a dual display port setup (radeon) and turning > it on again, the monitor stays black. A service restart (dm) doesn't change > that and starting a new Xorg instance doesn't change anything either. For > now, the only way I found to get the displays working again is to reboot the > system. > > Version-Release number of selected component (if applicable): > x11-server-xorg-1.16.4-2.1.mga5 > radeon-firmware-20150722-1.mga5.nonfree > kernel-desktop-latest-4.1.6-1.mga5 All of them from updates_testing ;-) Did you have the same issue before updating? > > How reproducible: > Always > > Steps to Reproduce: > 1. Boot into graphical desktop > 2. Turn off one monitor > 3. Turn back on the monitor > I don't have the slightest idea which package to assign this to, nor how to debug this. Is it the same when you use a different DM + DE ? Do you see anything in ~/.xsession-errors or journalctl output? CC:
(none) =>
marja11, qa-bugs, tmb Yes, same issue before updating. Nothing unusual in ~/.xsession-errors or journalctl output. I suspect an issue with the radeon driver, because it wasn't the case when I used HDMI on a slightly different graphics card. The current card is a: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device 7250 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 53 Region 0: Memory at 383fe0000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at fbd00000 (64-bit, non-prefetchable) [size=256K] Region 4: I/O ports at d000 [size=256] Expansion ROM at fbd40000 [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 256 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 8GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+, EqualizationPhase1+ EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest- Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee00658 Data: 0000 Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [200 v1] #15 Capabilities: [270 v1] #19 Kernel driver in use: radeon Kernel modules: radeon Best, Herbert CC:
(none) =>
herbert Thx for the feedback Removing QA team from the CC, because the issue wasn't introduced by a package that's now in updates_testing CC:
qa-bugs =>
(none) Hello, Which DE do you use? I have similar problems using KDE, and the problem is kscreen. https://bugs.kde.org/show_bug.cgi?id=359602 CC:
(none) =>
yves.brungard_mageia I'm using Gnome, and I just checked and it seems to have been fixed somewhere along the road (no idea where and when). So I can now turn off my displays and on again without reboot - yay! Best, Herbert Status:
NEW =>
RESOLVED |