GUI fail while on battery with Asus X51R

[SpinningAround]

With Ubuntu 9.10 Karmic Koala Alpha 6 (i386) and with most recent updates for today wont my laptop Asus X51R run on battery if it uses GUI, non GUI mode seem to work fine as far as I can tell. What happens if I unplug the AC connection in gnome while not using the computer is that the computer will lock and become unusable it's almost like it's lagging. To get around this problem is a hard reset needed and that the AC is plugged in again, neither ctrl+alt+f2, ctrl+alt+backspace, ctrl+alt+del work.

I'm unsure where to look for information but in the syslog did I find this, unsure if it's related to the problem
gdm-simple-greeter[2444]: WARNING: Could not ask power manager if user can suspend: The name org.freedesktop.PowerManagement was not provided by any .service files
---
Architecture: i386
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] Filen eller katalogen finns inte
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. X51R
Package: xserver-xorg-video-ati 1:6.13.0-1ubuntu5
PackageArchitecture: i386
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=fb7d0781-dc8b-4f91-ade6-8e7935e9264a ro quiet splash
ProcEnviron:
 LANG=sv_SE.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Tags: lucid lucid
Uname: Linux 2.6.32-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/02/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 207
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X51R
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr207:bd05/02/2007:svnASUSTeKComputerInc.:pnX51R:pvr1.0:rvnASUSTeKComputerInc.:rnX51R:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: X51R
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
glxinfo: Error: [Errno 2] Filen eller katalogen finns inte
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-22-generic

[David Heidelberg (okias)]

Problem confirmed.

This problem appear with Kubuntu 9.10 beta on i386.

Without KMS - freeze in stage loading KDE.
With KMS - freeze when moving to kdm from accelerated console. Looks like some problem related to graphics.

Problem show up less, when X running in shadowfb mode.

When is unplugged cable when system running, sometimes remain OKey (for while), somethime do screen corruption and then freeze (no logs, nothing)

In this moment I can't provide any logs, because I'm not direct user of this laptop...

[SpinningAround (spinningaround-deactivatedaccount)]

Laptop still wont work, if there is any logs that you need please say so :) Unsure but I attach lshw maybe it is useful for solving this bug.

[Philip Muškovac (yofel)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the final Ubuntu release? Thanks in advance.

[SpinningAround (spinningaround-deactivatedaccount)]

It's present so far given the latest updates for today (including new kernel update), I guess it has something to do with the xserver as you have pointed out. I tried to boot in recovery mode and jump to promt/shell/bash and it work fine as does normal boot if I press ctrl + alt + f2 during loading, I can't get xserver to start properly since it stop with black screen when I run xstart. On battery mode ofc since AC is working fine, a little notice is that Windows 7 seem to work fine, the problem started with 9.10. Thanks for take time to look into it.

[Michael Dundee (dundee-michael)]

This bug is still present in 10.04. I haven't tried text mode yet but the system freezes as soon as it loads GDM.

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi SpinningAround,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 434871

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 434871 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/434871

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[SpinningAround (spinningaround-deactivatedaccount)]

apport information

[Bryce Harrington (bryce)]

Looks like you mis-filed this against X. It's probably the kernel that you're having troubles with. GUI failure is just a side effect of whatever the bug is.

Also, you ought to re-test this against the development release (currently maverick), since that is the version that developers are focusing their time on.

[SpinningAround (spinningaround-deactivatedaccount)]

Problem seem to still exist in Xubuntu 10.10, was looking though syslog and found theses lines.
Dec 25 06:58:59 linux-X51R kernel: [ 1251.459560] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
Dec 25 06:58:59 linux-X51R kernel: [ 1251.469364] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(0).
Dec 25 06:58:59 linux-X51R kernel: [ 1251.472504] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
Dec 25 06:58:59 linux-X51R kernel: [ 1251.479292] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(1).
Dec 25 06:58:59 linux-X51R kernel: [ 1251.482411] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
Dec 25 06:59:00 linux-X51R kernel: [ 1252.767781] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(2).
Dec 25 06:59:00 linux-X51R kernel: [ 1252.770880] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
Dec 25 06:59:00 linux-X51R kernel: [ 1252.784173] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(3).
Dec 25 06:59:00 linux-X51R kernel: [ 1252.787236] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
Dec 25 06:59:00 linux-X51R kernel: [ 1252.798292] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(4).
Dec 25 06:59:00 linux-X51R kernel: [ 1252.801365] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
Dec 25 06:59:00 linux-X51R kernel: [ 1252.810317] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(5).
Dec 25 06:59:00 linux-X51R kernel: [ 1252.813397] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !
Dec 25 06:59:00 linux-X51R kernel: [ 1252.818401] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(6).
Dec 25 06:59:00 linux-X51R kernel: [ 1252.821497] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !

[SpinningAround (spinningaround-deactivatedaccount)]

I can confirm that the bug is still present in Ubuntu 11.04 (32 bit). I tried to do some debugging myself and noticed a few thing, everything works find while on AC-power. Adding 'acpi=off' to boot line make it possible to use the computer while on battery power but battery indicator is lost and the wireless card are unable to find local WLANs even if the module is loaded. Booting with 'acpi=ht' on battery power will freeze the system completely.

There seem to be some problems related to WLAN card, if ath5k is blacklisted will it still freeze if booting but if unplugging the AC-power while laptop is running will instead cause X to crash with output mention in last post, console/terminal commands still work.

[penalvch (penalvch)]

SpinningAround, thank you for reporting this and helping make Ubuntu better. 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 capture the oops following https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Capturing_OOPs ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Launchpad Janitor (janitor)]

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