FS#39065 - Screen ficker with linux 3.13 kernel and radeon card

Attached to Project: Arch Linux
Opened by Ivan (galadog) - Thursday, 27 February 2014, 19:05 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Wednesday, 05 March 2014, 19:19 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Screen goes black for a couple of seconds at random moments. Than returns to normal.

Additional info:
core/linux 3.13.5-1
kde 4.12.2
ATI card: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Redwood XT [Radeon HD 5670/5690/5730]

There is absoulutly no issue on the same machine with kernels 3.12 and older.

.xsession-errors file:

X Error: BadWindow (invalid Window parameter) 3
Major opcode: 2 (X_ChangeWindowAttributes)
Resource id: 0x1a0086b
kwin(616) KWin::Workspace::updateClientArea: screens: 2 desktops: 5
kwin(616) KWin::Workspace::updateClientArea: Done.
kwin(616) KWin::Client::readUserTimeMapTimestamp: User timestamp, ASN: 1851449
kwin(616) KWin::Client::readUserTimeMapTimestamp: User timestamp, final: 'ID: 27263525 ;WMCLASS: "plasma" : "plasma" ;Caption: "plasma-desktop" ' : 1851449
kwin(616) KWin::Workspace::allowClientActivation: Activation, compared: 'ID: 27263525 ;WMCLASS: "plasma" : "plasma" ;Caption: "plasma-desktop" ' : 1851449 : 1882168 : false
kwin(616) KWin::Workspace::updateClientArea: screens: 2 desktops: 5
kwin(616) KWin::Workspace::updateClientArea: Done.
kwin(616) KWin::Client::configureRequest: KWin::Client(0x1dbc830) true false false
kwin(616) KWin::Client::configureRequest: PERMITTED 'ID: 27263525 ;WMCLASS: "plasma" : "plasma" ;Caption: "plasma-desktop" ' true
kwin(616) KWin::Workspace::updateClientArea: screens: 2 desktops: 5
kwin(616) KWin::Workspace::updateClientArea: Done.
kwin(616) KWin::Client::readUserTimeMapTimestamp: User timestamp, ASN: 1851449
kwin(616) KWin::Client::readUserTimeMapTimestamp: User timestamp, final: 'ID: 27265168 ;WMCLASS: "plasma-desktop" : "plasma-desktop" ;Caption: "plasma-desktop" ' : 1851449
kwin(616) KWin::Workspace::allowClientActivation: Activation, compared: 'ID: 27265168 ;WMCLASS: "plasma-desktop" : "plasma-desktop" ;Caption: "plasma-desktop" ' : 1851449 : 1894600 : false
kwin(616) KWin::Workspace::updateClientArea: screens: 2 desktops: 5
kwin(616) KWin::Workspace::updateClientArea: Done.
kwin(616) KWin::Workspace::updateClientArea: screens: 2 desktops: 5
kwin(616) KWin::Workspace::updateClientArea: Done.
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 2 (X_ChangeWindowAttributes)
Resource id: 0x1a00890
kwin(616) KWin::Client::readUserTimeMapTimestamp: User timestamp, ASN: 1851449
kwin(616) KWin::Client::readUserTimeMapTimestamp: User timestamp, final: 'ID: 27263525 ;WMCLASS: "plasma" : "plasma" ;Caption: "plasma-desktop" ' : 1851449
kwin(616) KWin::Workspace::allowClientActivation: Activation, compared: 'ID: 27263525 ;WMCLASS: "plasma" : "plasma" ;Caption: "plasma-desktop" ' : 1851449 : 1894600 : false
kwin(616) KWin::Workspace::updateClientArea: screens: 2 desktops: 5
kwin(616) KWin::Workspace::updateClientArea: Done.
kwin(616) KWin::Client::configureRequest: KWin::Client(0x1dbc830) true false false
kwin(616) KWin::Client::configureRequest: PERMITTED 'ID: 27263525 ;WMCLASS: "plasma" : "plasma" ;Caption: "plasma-desktop" ' true
kwin(616) KWin::Workspace::updateClientArea: screens: 2 desktops: 5
kwin(616) KWin::Workspace::updateClientArea: Done.

dmesg and Xorg.0.log seem to be clean


Steps to reproduce:
start X-server, work for about 5-10 minutes.
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Wednesday, 05 March 2014, 19:19 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Thursday, 27 February 2014, 19:54 GMT
Open source or proprietary drivers? Does it happen in other DEs/WMs? If proprietary drivers, what version of xorg?
Comment by Ivan (galadog) - Thursday, 27 February 2014, 23:26 GMT
Open source drivers. I will try to test with mate tomorrow.
Comment by Ivan (galadog) - Wednesday, 05 March 2014, 17:40 GMT
From that time I never observed any problems X-server. Maybe it was a hardware bug... Anyway I cannot reproduce it now.

Loading...