Freeze after login with KMS enabled on Radeon HD6310
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-driver-ati |
Fix Released
|
Medium
|
|||
linux (Ubuntu) |
Fix Released
|
High
|
Andy Whitcroft | ||
xserver-xorg-video-ati (Ubuntu) |
Invalid
|
High
|
Robert Hooker |
Bug Description
Binary package hint: xserver-
I'm using Natty on an HP dm1z-3000 series, which has an AMD Radeon HD 6310 on-board graphics. The system boots as expected, but once I log in the system becomes completely unresponsive. This seems due to hardware acceleration, because if I choose either 'safe mode' option, I get a useable desktop without hardware acceleration. The same is true if I disable KMS with radeon.modeset=0 at boot time; I get a useable desktop, albeit without hardware acceleration.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: xserver-
ProcVersionSign
Uname: Linux 2.6.38-2-generic x86_64
Architecture: amd64
Date: Tue Feb 8 13:25:55 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: ubuntu
GdmLog2:
GraphicsCard: Subsystem: Hewlett-Packard Company Device [103c:1611]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110207)
MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC
ProcEnviron:
LANGUAGE=en_CA:en
LANG=en_CA.UTF-8
LC_MESSAGES=
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xserver-
dmi.bios.date: 12/20/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.03
dmi.board.
dmi.board.name: 1611
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 96.19
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Pavilion dm1 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.2.
version.libdrm2: libdrm2 2.4.23-1ubuntu3
version.
version.
version.
version.
version.
Changed in xserver-xorg-video-ati (Ubuntu): | |
status: | Incomplete → New |
tags: | added: freeze |
Changed in xserver-xorg-video-ati (Ubuntu): | |
importance: | Undecided → High |
status: | Incomplete → Confirmed |
Changed in xserver-xorg-driver-ati: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
tags: | added: hwe-blocker |
Changed in xserver-xorg-video-ati (Ubuntu): | |
assignee: | nobody → Robert Hooker (sarvatt) |
Changed in xserver-xorg-video-ati (Ubuntu): | |
status: | Invalid → In Progress |
status: | In Progress → Invalid |
Changed in linux (Ubuntu): | |
assignee: | Jeremy Foshee (jeremyfoshee) → Andy Whitcroft (apw) |
status: | Triaged → In Progress |
Changed in xserver-xorg-driver-ati: | |
status: | Confirmed → Fix Released |
Reproduce the issue, log in, and with the system frozen collect the output of dmesg, your /var/log/ Xorg.0. log, and your /var/log/kern.log.
Also, avivotool can be used to assist in debugging this issue. avivotool is provided with the radeontool package, so to install it run:
sudo apt-get install radeontool
After installing it, you run it like this:
avivotool regs all > regdump_good.txt
avivotool regs all > regdump_broke.txt
Run it two times. Once when you have a working screen, and once in the broken case (either from the tty console or logged into the sick box remotely). Attach both of those to this bug report.