Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#39959 - [linux] Shutdown problem with ASUS X5DAB (Mobility Radeon HD4570)

Attached to Project: Arch Linux
Opened by Stephan Munsch (waldbaer59) - Saturday, 19 April 2014, 10:34 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 13 August 2014, 07:46 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Shutdown problem with ASUS X5DAB (Mobility Radeon HD4570).

Additional info:
* package version(s): xorg-server: 1.15.1-1, xf86-video-ati: 1:7.3.0-1
Starting the system and using the notebook gives no problems. It only appears when shutting down.
For some of the messages associated with the error pls. look at the included file.

Steps to reproduce:
Shutting down the system yields the given messages. The Xorg.0.log gives no further useable information.
When not shutting down, changing to a root-terminal and inputting the command "killall -9 X" gives the same error messages.
Deinstalling xf86-video-ati and using VESA makes the error disappear.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Wednesday, 13 August 2014, 07:46 GMT
Reason for closing:  No response
Comment by Stephan Munsch (waldbaer59) - Saturday, 19 April 2014, 10:34 GMT
Screenshot of call-stack.
   IMG_20140415_192736.jpg (204.8 KiB)
Comment by Daniel Micay (thestinger) - Tuesday, 22 April 2014, 18:25 GMT
Please report this upstream. It's a genuine bug in the radeon support in the kernel, as userspace can never be blamed for an issue like this.
Comment by Laurent Carlier (lordheavy) - Friday, 11 July 2014, 16:52 GMT
Is it still a problem with kernel 3.15.5 ?

Loading...