Ubuntu
xserver-xorg-video-ati package

Multiple graphics problems, regression

Bug #1242478 reported by Christoffer Cronström on 2013-10-21

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xserver-xorg-video-ati (Ubuntu)	Expired	Low	Unassigned

Bug Description

Graphics driver will regularly freeze for ~30 seconds, emitting this type of messages over and over:

[ 1652.976556] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CC98 (len 62, WS 0, PS 0) @ 0xCCB4
[ 1652.976562] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C372 (len 861, WS 0, PS 0) @ 0xC3CF
[ 1657.984602] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 1657.984611] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D024 (len 72, WS 0, PS 0) @ 0xD053
[ 1662.992448] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 1662.992456] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CC98 (len 62, WS 0, PS 0) @ 0xCCB4

I can reproduce this failure at any time by changing the screen brightness on the laptop. It sometimes happens spontaneously as well, and sometimes when I start the "Screen Display" settings app.

When it finally unfreezes, I get incorrect screen resolutions, incorrect number of monitors, a frozen mouse pointer on screen (on top of everything else, even on top of the real mouse pointer), and sometimes rendering glitches. It will continue emitting this type of message:

[ 2747.265512] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[ 2747.310454] radeon 0000:01:00.0: couldn't schedule ib
[ 2747.310460] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[ 2747.339220] radeon 0000:01:00.0: couldn't schedule ib
[ 2747.339226] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[ 2747.371411] radeon 0000:01:00.0: couldn't schedule ib

These messages will not cease unless I reboot, adding 50 lines/second to my logs.

This is a clean install of Ubuntu 13.10, running Gnome shell (I installed gnome-core). Previously this laptop ran 12.10 and while I did see the occasional glitch it was never this severe.

I should also add that I have a script which switches off the discrete graphics chip on startup (through echo OFF > /sys/kernel/debug/vgaswitcheroo/switch). I will deactivate this to see if it make any difference.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:

ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Oct 21 01:50:04 2013
DistUpgraded: Fresh install
DistroCodename: saucy
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Device [1025:0359]
Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] [1002:68e0] (rev ff) (prog-if ff)
InstallationDate: Installed on 2013-10-20 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Acer Aspire 4820TG
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/16/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JM41_CP
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvrV1.25:bd03/16/2011:svnAcer:pnAspire4820TG:pvrV1.25:rvnAcer:rnJM41_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire 4820TG
dmi.product.version: V1.25
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.46-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Mon Oct 21 01:12:38 2013
xserver.configfile: default
xserver.errors:
RADEON(G0): [XvMC] Failed to initialize extension.
RADEON(G0): failed to set mode: No space left on devicehave a master to look out for
RADEON(G0): failed to set mode: No space left on devicereporting 7 6 20 149
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 12348
vendor AUO
xserver.version: 2:1.14.3-3ubuntu2

Tags:

Revision history for this message

Christoffer Cronström (hymyly) wrote on 2013-10-21:

BootDmesg.txt Edit (59.7 KiB, text/plain; charset="utf-8")
BootLog.txt Edit (3.0 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (156.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (6.2 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (1.3 MiB, text/plain; charset="utf-8")
GconfCompiz.txt Edit (45.5 KiB, text/plain; charset="utf-8")
LightdmDisplayLog.txt Edit (6.2 KiB, text/plain; charset="utf-8")
LightdmGreeterLog.txt Edit (6.0 KiB, text/plain; charset="utf-8")
LightdmLog.txt Edit (5.1 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (23.2 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (438 bytes, text/plain; charset="utf-8")
MonitorsUser.xml.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.3 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (297 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.6 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (142.7 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (322.7 KiB, text/plain; charset="utf-8")
UnitySupportTest.txt Edit (610 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (79.4 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (84.9 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (7.5 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (4.8 KiB, text/plain; charset="utf-8")
xserver.devices.txt Edit (559 bytes, text/plain; charset="utf-8")

Timo Aaltonen (tjaalton) on 2013-10-21

affects:

xorg (Ubuntu) → xserver-xorg-video-ati (Ubuntu)

Revision history for this message

penalvch (penalvch) wrote on 2014-01-09:

Christoffer Cronström, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xserver-xorg-video-ati REPLACE-WITH-BUG-NUMBER

Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in xserver-xorg-video-ati (Ubuntu):
importance:	Undecided → Low
status:	New → Incomplete

Revision history for this message

josejuan05 (josejuan05) wrote on 2014-01-17:

Download full text (4.3 KiB)

I'm commenting here because I have a very similar problem (and have had said problem for some time), but which manifests in something of the opposite way:

After boot my script, as yours, does `echo OFF > /sys/kernel/debug/vgaswitcheroo/switch`. Several seconds later, I begin receiving
[ 50.069942] radeon 0000:01:00.0: couldn't schedule ib
[ 50.069951] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
in the kernel log/dmesg 50-100 lines/sec

At this point xrandr reports outputs for both the discrete and the integrated video cards. So, for example, if I have no external devices plugged in I'll receive:

Screen 0: minimum 320 x 200, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm
   1366x768 60.1*+ 40.1
   1360x768 59.8 60.0
   1024x768 60.0
   800x600 60.3 56.2
   640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
LVDS-1-1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1366x768 60.1*+
   1280x720 59.9
   1152x768 59.8
   1024x768 59.9
   800x600 59.9
   848x480 59.7
   720x480 59.7
   640x480 59.4
HDMI-1-0 disconnected (normal left inverted right x axis y axis)
VGA-1-1 connected (normal left inverted right x axis y axis)
   1024x768 60.0
   800x600 60.3 56.2
   848x480 60.0
   640x480 59.9
  1366x768 (0x47) 69.3MHz
        h: width 1366 start 1404 end 1426 total 1436 skew 0 clock 48.3KHz
        v: height 768 start 771 end 777 total 803 clock 60.1Hz
  1024x768 (0xc2) 65.0MHz
        h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.4KHz
        v: height 768 start 771 end 777 total 806 clock 60.0Hz
  800x600 (0xc3) 40.0MHz
        h: width 800 start 840 end 968 total 1056 skew 0 clock 37.9KHz
        v: height 600 start 601 end 605 total 628 clock 60.3Hz
  800x600 (0xc4) 36.0MHz
        h: width 800 start 824 end 896 total 1024 skew 0 clock 35.2KHz
        v: height 600 start 601 end 603 total 625 clock 56.2Hz

I'm commenting here because I have a very similar problem (and have had said problem for some time), but which manifests in something of the opposite way:

After boot my script, as yours, does `echo OFF > /sys/kernel/debug/vgaswitcheroo/switch`. Several seconds later, I begin receiving 
[   50.069942] radeon 0000:01:00.0: couldn't schedule ib
[   50.069951] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
in the kernel log/dmesg 50-100 lines/sec

At this point xrandr reports outputs for both the discrete and the integrated video cards. So, for example, if I have no external devices plugged in I'll receive:

Screen 0: minimum 320 x 200, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm
   1366x768       60.1*+   40.1  
   1360x768       59.8     60.0  
   1024x768       60.0  
   800x600        60.3     56.2  
   640x480        59.9  
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
LVDS-1-1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1366x768       60.1*+
   1280x720       59.9  
   1152x768       59.8  
   1024x768       59.9  
   800x600        59.9  
   848x480        59.7  
   720x480        59.7  
   640x480        59.4  
HDMI-1-0 disconnected (normal left inverted right x axis y axis)
VGA-1-1 connected (normal left inverted right x axis y axis)
   1024x768       60.0  
   800x600        60.3     56.2  
   848x480        60.0  
   640x480        59.9  
  1366x768 (0x47)   69.3MHz
        h: width  1366 start 1404 end 1426 total 1436 skew    0 clock   48.3KHz
        v: height  768 start  771 end  777 total  803           clock   60.1Hz
  1024x768 (0xc2)   65.0MHz
        h: width  1024 start 1048 end 1184 total 1344 skew    0 clock   48.4KHz
        v: height  768 start  771 end  777 total  806           clock   60.0Hz
  800x600 (0xc3)   40.0MHz
        h: width   800 start  840 end  968 total 1056 skew    0 clock   37.9KHz
        v: height  600 start  601 end  605 total  628           clock   60.3Hz
  800x600 (0xc4)   36.0MHz
        h: width   800 start  824 end  896 total 1024 skew    0 clock   35.2KHz
        v: height  600 start  601 end  603 total  625           clock   56.2Hz

Upon connecting or disconnecting an external monitor, putting the computer into standby gdm crashes and I get the following lines onscreen and in the kernel log:
[  922.267146] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[  922.267188] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEA6 (len 62, WS 0, PS 0) @ 0xCEC2
[  927.268332] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[  927.268372] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEA6 (len 62, WS 0, PS 0) @ 0xCEC2
[  927.268410] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C558 (len 861, WS 0, PS 0) @ 0xC5B5
[  932.269534] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[  932.269617] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEA6 (len 62, WS 0, PS 0) @ 0xCEC2
[  937.270719] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[  937.270768] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEA6 (len 62, WS 0, PS 0) @ 0xCEC2
[  942.271910] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[  942.271994] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEA6 (len 62, WS 0, PS 0) @ 0xCEC2

Then gdm starts. At this point the IB scheduling errors stop and the xrandr outputs associated with the disabled video card no longer appear. The above also occurs if I log out of a gdm session.

After this point, subsequent device changes and session logouts occur normally until the computer is restarted.

I haven't been keeping track (I haven't had time to mess with this) of this rigorously, but while the IB scheduling errors only showed up in 13.10, the atom_execute_table_locked/op_jump errors have occurred since at least 12.04, I believe. I believe the extra displays part of the bug has occurred since at least 12.10, but possibly before. These are all reported together because they all occur in a very predictable sequence.

Revision history for this message

penalvch (penalvch) wrote on 2014-01-17:

josejuan05, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal:
ubuntu-bug xorg

For more on this, please see the official Ubuntu documentation:
Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report will delay your problem being addressed as quickly as possible.

Thank you for your understanding.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-03-19:

[Expired for xserver-xorg-video-ati (Ubuntu) because there has been no activity for 60 days.]

Changed in xserver-xorg-video-ati (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntuxserver-xorg-video-ati package

Multiple graphics problems, regression

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
xserver-xorg-video-ati package