[drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting

Bug #683398 reported by Angel Guzman Maeso
60
This bug affects 12 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xorg

When I try to suspend the laptop it fails showing this messages on screen:

$ cat /var/log/syslog | grep "drm:"
Nov 29 17:35:14 steros kernel: [429829.826906] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting
Nov 29 17:35:14 steros kernel: [429829.826914] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CAB4 (len 67, WS 0, PS 0) @ 0xCAE3
Nov 29 18:48:24 steros kernel: [432995.727849] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting
Nov 29 18:48:24 steros kernel: [432995.727857] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CAB4 (len 67, WS 0, PS 0) @ 0xCAE3
Nov 29 23:49:00 steros kernel: [ 18.144258] drm: registered panic notifier

The suspend request fails.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-23.40-generic-pae 2.6.35.7
Uname: Linux 2.6.35-23-generic-pae i686
Architecture: i386
DRM.card0.HDMI_Type_A.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1366x768 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480
 edid-base64:
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
Date: Tue Nov 30 22:56:23 2010
DkmsStatus:
 blcr, 0.8.2: added
 virtualbox-ose, 3.2.8, 2.6.35-21-generic-pae, i686: built
 virtualbox-ose, 3.2.8, 2.6.35-22-generic-pae, i686: built
 virtualbox-ose, 3.2.8, 2.6.35-23-generic-pae, i686: installed
 nvidia-current, 260.19.06, 2.6.35-23-generic-pae, i686: installed
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100713)
MachineType: Acer Aspire 5943G
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic-pae root=UUID=46948cee-dbfc-439f-b97b-e75af50c2f62 ro quiet splash
ProcEnviron:
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
dmi.bios.date: 05/07/2010
dmi.bios.vendor: Acer
dmi.bios.version: V1.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire 5943G
dmi.board.vendor: Acer
dmi.board.version: V1.06
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.06
dmi.modalias: dmi:bvnAcer:bvrV1.06:bd05/07/2010:svnAcer:pnAspire5943G:pvrV1.06:rvnAcer:rnAspire5943G:rvrV1.06:cvnAcer:ct10:cvrV1.06:
dmi.product.name: Aspire 5943G
dmi.product.version: V1.06
dmi.sys.vendor: Acer
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-23-generic-pae

Revision history for this message
Angel Guzman Maeso (shakaran) wrote :
bugbot (bugbot)
affects: xorg (Ubuntu) → xorg-server (Ubuntu)
Revision history for this message
Upayavira (uv) wrote :

This appears to have been solved at source:

https://bugs.freedesktop.org/show_bug.cgi?id=32066

Seeing as this is an error that occurred *after* 10.10 was released (it broke some weeks after), what are the chances of having the mentioned patch applied to 10.10?

The patch that apparently fixes it:

  https://bugs.freedesktop.org/attachment.cgi?id=41218

Unfortunately, my I haven't compiled a kernel since 1995, so I'm not really in a position to test this (without guidance).

Upayavira

Revision history for this message
Upayavira (uv) wrote :

Note, this is a kernel bug, not an xorg one.

It is still present, preventing resume every time.

Upayavira

Revision history for this message
Angel Guzman Maeso (shakaran) wrote :

Using Natty with new kernel, the issue seems to be fixed:

 $ uname -a
Linux steros 2.6.38-3-generic-pae #30-Ubuntu SMP Thu Feb 10 00:54:59 UTC 2011 i686 i686 i386 GNU/Linux

Thanks!

Revision history for this message
Upayavira (uv) wrote :

Is it possible to get a later kernel for Maverick, to try?

Upayavira

Revision history for this message
Upayavira (uv) wrote :

Seems the kernel update that came in a few days ago may have fixed this. Fingers crossed (I've seen it come and go before, but not seen it work this consistently).

Revision history for this message
Johannes Daprà (johannes-dapra) wrote :

Sorry to dissapoint you Upayavira, but it happend to me just now with kernel 2.6.35-27-generic (i assume it is the one you're speaking about)

Is it normal, that this bug doesn't occur every time on tries to suspend the computer? Because it worked today, and 1 h later the bug came again. Could it have something to do with the wireless? because the first time it was off and the second time it was on (with the mechanic switch)

Revision history for this message
Upayavira (uv) wrote :

Johannes,

You are, unfortunately, correct - it was a blip. I installed the latest 2.6.36 and 2.6.37 kernels from the Ubuntu Kernel PPA, and neither of them seemed to resolve it :-(

Revision history for this message
roy.nico (roy-nico) wrote :

I confirm the same issue, with Maverick 64bit on my Laptop Hp Touchsmart Tm2.
It happens not every time, but randomly. For me, not only while trying tu suspend, but also when trying to shutdown. It shuts down eventually, but need near 3 or 4 minutes.
:(

madbiologist (me-again)
affects: xorg-server (Ubuntu) → linux (Ubuntu)
Revision history for this message
madbiologist (me-again) wrote :

The abovementioned fix is included upstream in kernel 2.6.37 - see the changelog at http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.37

As the original reporter has confirmed the fix on Natty, I'm marking this bug as Fix Released.

Upayavira - if you are still having problems with the 2.6.37 kernel then you have a different bug and should file a new bug report.

Changed in linux (Ubuntu):
status: New → Fix Released
Revision history for this message
Marcin Janowski (janowski-m) wrote :

I have this in 12.10 on Acer Aspire 4820TG

Revision history for this message
madbiologist (me-again) wrote :

@Marcin - Please file a new bug so that we can get copies of your log files and hardware information.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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