integrated radeon + ssd creates boot problems

Bug #1091828 reported by Urob
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I'm using an asus motherboard F1A75-Vpro with integrated graphic chipset.
No trouble whith 12.04 or 12.10 installation as long as i use a normal harddisk.
I recently bought a ssd drive, installation was successfull, but 50% of time when booting,
computer freezes.

On a frozen boot the file kern.log ends with:

Dec 16 11:51:23 witje kernel: [ 3.683005] input: HD-Audio Generic Line Out CLFE as /devices/pci0000:00/0000:00:14.2/sound/card1/input11
Dec 16 11:51:23 witje kernel: [ 3.683147] input: HD-Audio Generic Line Out Surround as /devices/pci0000:00/0000:00:14.2/sound/card1/input12
Dec 16 11:51:23 witje kernel: [ 3.683290] input: HD-Audio Generic Line Out Front as /devices/pci0000:00/0000:00:14.2/sound/card1/input13
Dec 16 11:51:24 witje kernel: [ 4.885715] r8169 0000:03:00.0: eth0: link up
Dec 16 11:51:24 witje kernel: [ 4.886605] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Dec 16 11:51:35 witje kernel: [ 15.372235] radeon 0000:00:01.0: GPU lockup CP stall for more than 10000msec
Dec 16 11:51:35 witje kernel: [ 15.372249] radeon 0000:00:01.0: GPU lockup (waiting for 0x0000000000000003 last fence id 0x0000000000000001)
Dec 16 11:51:35 witje kernel: [ 15.373317] radeon 0000:00:01.0: GPU softreset
Dec 16 11:51:35 witje kernel: [ 15.373319] radeon 0000:00:01.0: GRBM_STATUS=0xA0003828
Dec 16 11:51:35 witje kernel: [ 15.373321] radeon 0000:00:01.0: GRBM_STATUS_SE0=0x00000007
Dec 16 11:51:35 witje kernel: [ 15.373323] radeon 0000:00:01.0: GRBM_STATUS_SE1=0x00000007
Dec 16 11:51:35 witje kernel: [ 15.373325] radeon 0000:00:01.0: SRBM_STATUS=0x20020940
Dec 16 11:51:35 witje kernel: [ 15.524752] radeon 0000:00:01.0: Wait for MC idle timedout !
Dec 16 11:51:35 witje kernel: [ 15.524754] radeon 0000:00:01.0: GRBM_SOFT_RESET=0x00007F6B
Dec 16 11:51:35 witje kernel: [ 15.524856] radeon 0000:00:01.0: GRBM_STATUS=0x00003828
Dec 16 11:51:35 witje kernel: [ 15.524858] radeon 0000:00:01.0: GRBM_STATUS_SE0=0x00000007
Dec 16 11:51:35 witje kernel: [ 15.524860] radeon 0000:00:01.0: GRBM_STATUS_SE1=0x00000007
Dec 16 11:51:35 witje kernel: [ 15.524861] radeon 0000:00:01.0: SRBM_STATUS=0x20020940
Dec 16 11:51:35 witje kernel: [ 15.525854] radeon 0000:00:01.0: GPU reset succeed
Dec 16 11:51:35 witje kernel: [ 15.677414] radeon 0000:00:01.0: Wait for MC idle timedout !
Dec 16 11:51:35 witje kernel: [ 15.828827] radeon 0000:00:01.0: Wait for MC idle timedout !
Dec 16 11:51:35 witje kernel: [ 15.830690] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
Dec 16 11:51:35 witje kernel: [ 15.830772] radeon 0000:00:01.0: WB enabled
Dec 16 11:51:35 witje kernel: [ 15.830775] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff88021322ac00
Dec 16 11:51:36 witje kernel: [ 15.995526] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x8500)=0xCAFEDEAD)
Dec 16 11:51:36 witje kernel: [ 15.995529] [drm:evergreen_resume] *ERROR* evergreen startup failed on resume

Apparently, the fact that i boot from SSD has an influence on the integrated radeon chipset.
Is it because SSD boots much faster and radeon chipset not responding fast enough?

To reproduce bug you need to use
1. the F1A75-Vpro motherboard
2. the integrated AMD Radeon graphics
3. installation done on SSD

By integrating an extra video card the problem is solved.

Installing swap, /tmp, /var, /boot on a standard platter drive does not solve the problem

Installing / on a standard platter drive does solve the problem

Revision history for this message
Jackson Doak (noskcaj) wrote :

just to check, does getting a graphics card fix it?

Revision history for this message
Jackson Doak (noskcaj) wrote :

also, what ssd is it?

Jackson Doak (noskcaj)
Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Christopher Foster (chris-james-foster) wrote :

This bug occurs for me as well, but I am using a machine with no SSD.
I see *identical* output in my dmesg, however. This happens about 80% of the time I try to boot, resulting in a purely purple screen. The system is still responsive, and I can ctrl+alt+F[x] in order to log in as root and restart the machine. When doing this though, the screen still remains purple (so I basically restart blindly).

Revision history for this message
Christopher Foster (chris-james-foster) wrote :

This doesn't appear to exist in kernel 3.7 for me, as per https://bugs.archlinux.org/task/31668?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.