[HP TouchSmart tm2-2010eg] Linux hangs with: "[drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting"

[Simon K]

Symptom: Linux isn't displaying changes after switching to tty1 and back to Unity. Steps to reproduce:
1. Starting up to Unity
2. Switch to tty1 (Strg + Alt + F1)
3. Switching back to Unity

or resuming the system from suspend leads to the same isssue.This method isn't as reliable as the method stated above.

What happens: The screen freezes. Magic Keys [Alt + Print + S/U/B] are working thou (so linux-kernel is responding?!) I can't switch to tty1 either. The system becomes responding again after ~2min. Switching VTs is possible afterwards but leads to the same bug again.

What is expected: Showing up a responding Unity.

WORKAROUND: My radeon is switched off using:
echo"OFF">/sys/kernel/debug/vgaswitcheroo/switch
By turning "ON" the graphics card the above stated problem doesn't appear.

A kern.log:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1062077/+attachment/3374796/+files/kern.log

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-17-generic 3.5.0-17.26
ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: octavian 2405 F.... pulseaudio
Date: Fri Oct 5 09:07:44 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
ProcFB:
 0 inteldrmfb
 1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=2e9be59f-1f91-4313-bfac-3babbffc5c00 ro quiet splash pcie_aspm=force i915.i915_enable_rc6=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-17-generic N/A
 linux-backports-modules-3.5.0-17-generic N/A
 linux-firmware 1.94
SourcePackage: linux
UpgradeStatus: Upgraded to quantal on 2012-09-14 (20 days ago)
dmi.bios.date: 07/30/2010
dmi.bios.vendor: Insyde
dmi.bios.version: F.12
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1486
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 83.1A
dmi.chassis.asset.tag: CNU0250216
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.12:bd07/30/2010:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr0489200000252A20001220000:rvnHewlett-Packard:rn1486:rvr83.1A:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP TouchSmart tm2 Notebook PC
dmi.product.version: 0489200000252A20001220000
dmi.sys.vendor: Hewlett-Packard
---
.tmp.unity.support.test.0:

ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
DistUpgraded: 2013-02-07 06:43:51,807 DEBUG enabling apt cron job
DistroCodename: raring
DistroRelease: Ubuntu 13.04
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.1.22, 3.5.0-23-generic, x86_64: installed
 virtualbox, 4.1.22, 3.8.0-4-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:1486]
 Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 Series] [1002:68e0] (rev ff) (prog-if ff)
InstallationDate: Installed on 2012-12-04 (64 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
MarkForUpload: True
Package: xorg 1:7.7+1ubuntu4
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-4-generic root=UUID=b78f0013-4cb2-4ad2-9c13-9d884b091f3a ro
ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6
Tags: raring running-unity ubuntu regression reproducible compiz-0.9
Uname: Linux 3.8.0-4-generic x86_64
UpgradeStatus: Upgraded to raring on 2013-02-07 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 07/30/2010
dmi.bios.vendor: Insyde
dmi.bios.version: F.12
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1486
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 83.1A
dmi.chassis.asset.tag: CNU0250216
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.12:bd07/30/2010:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr0489200000252A20001220000:rvnHewlett-Packard:rn1486:rvr83.1A:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP TouchSmart tm2 Notebook PC
dmi.product.version: 0489200000252A20001220000
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.9~daily13.02.04-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.42-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.0-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2
xserver.bootTime: Thu Feb 7 22:37:06 2013
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.13.2-0ubuntu1
xserver.video_driver: intel

[Russ Dill (russ-dill)]

Created attachment 40753
ATOM BIOS

During resume, I get:

[18832.030013] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[18832.030016] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing E8B8 (len 86, WS 4, PS 0) @ 0xE8EB
[18837.060015] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[18837.060019] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing E8B8 (len 86, WS 4, PS 0) @ 0xE8EB
[18842.380012] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[18842.380016] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing E8B8 (len 86, WS 4, PS 0) @ 0xE8EB
[18842.430097] PM: resume of drv:radeon dev:0000:01:00.0 complete after 15575.937 msecs

I have a:

(--) RADEON(0): Chipset: "ATI Mobility Radeon X1600" (ChipID = 0x71c5)

[Russ Dill (russ-dill)]

Created attachment 40754
Kernel log

[Russ Dill (russ-dill)]

Created attachment 40755
Xorg log

[Glisse (glisse)]

We need a dump of your video bios see bottom of http://dri.freedesktop.org/wiki/TestingAndDebugging

[Airlied-freedesktop (airlied-freedesktop)]

Jerome the bios is attached already,

This is the UpdateCRTC_DoubleBufferRegisters table, I've got the same issue here on my rv530 I just noticed.

decoding the table shows it waiting for both crtcs, I wonder if they made this table saner in r6xx.

[agd5f (agd5f)]

*** Bug 32307 has been marked as a duplicate of this bug. ***

[agd5f (agd5f)]

(In reply to comment #4)
> Jerome the bios is attached already,
>
> This is the UpdateCRTC_DoubleBufferRegisters table, I've got the same issue
> here on my rv530 I just noticed.
>
> decoding the table shows it waiting for both crtcs, I wonder if they made this
> table saner in r6xx.

We don't get this issue during normal modeset, so I suspect the regs are in a wonky state after resume. Perhaps a hard reset before asic_init would help.

[Russ Dill (russ-dill)]

I'm currently running ubuntu nartty with xorg-edgers, so its pretty easy for me to test something. Let me know if there is something you'd like me to try.

[agd5f (agd5f)]

Created attachment 41218
possible fix

This patch should fix the issues. We were attempting to unblank the displays before the timing was set up in the resume path.

[agd5f (agd5f)]

*** Bug 27744 has been marked as a duplicate of this bug. ***

[Peter (peter-weber-q)]

I'am sorry, but the patch doesn't fix the issue.

[Peter (peter-weber-q)]

Created attachment 41343
dmesg output after patch

[agd5f (agd5f)]

(In reply to comment #10)
> I'am sorry, but the patch doesn't fix the issue.

Can you attach a copy of your vbios?
(as root)
(use lspci to get the bus id)
cd /sys/bus/pci/devices/<pci bus id>
echo 1 > rom
cat rom > /tmp/vbios.rom
echo 0 > rom

[Peter (peter-weber-q)]

Shame on me!
I'm so sorry! I was my failure: I booted up the old kernel.

I tested the patch with vanilla-kernel 2.6.37-rc6 and everything works perfect!
It is a really nice christmans present for me, to see this bug fixed :-)

Thank you Alex

[Peter (peter-weber-q)]

General Question, maybe I should open an other bug:
Did your terminal scroll sometimes slow "from top to bottom" (exampe dmesg), after the second or third suspend-cycle? This is fixed by "ctrl+l" or the next suspend-cycle.

What I forgot:
Will we see this patch in the next rc7 ord rc8, if all results are well as mine?
Happy Christmas!

Thanks

[agd5f (agd5f)]

(In reply to comment #14)
> General Question, maybe I should open an other bug:
> Did your terminal scroll sometimes slow "from top to bottom" (exampe dmesg),
> after the second or third suspend-cycle? This is fixed by "ctrl+l" or the next
> suspend-cycle.
>

Not familiar with that.

> What I forgot:
> Will we see this patch in the next rc7 ord rc8, if all results are well as
> mine?

I've sent the patch to Dave. Hopefully it will hit 2.6.37.

[Gmalazdrewicz (gmalazdrewicz)]

In my case, error is not shown now in dmesg (after applying patch), but there still is a significant delay waking up.

ATI HD5850, BIOS in the bug 32307.

[Peter (peter-weber-q)]

What need time for wakeup dmesg prints?
Mine is around 500msec

[Peter (peter-weber-q)]

Tested 2.6.37-rc8 (patch is included already).
Works perfect. No glitches here.

[Russ Dill (russ-dill)]

I haven't had a chance to test yet, but I did notice an additional debug message:

[drm:atom_execute_table_locked] *ERROR* atombios stuck executing E8B8 (len 86, WS 4, PS 0) @ 0xE8EB

[Russ Dill (russ-dill)]

Just testing with 2.6.37 and this is fixed.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-quantal/

[Jonas Schwabe (jonas-schwabe)]

It takes about 2 minutes for unity to respond again. This also happens afert suspend which is very annoying.
Bug exists upstream (3.6.0-030600-generic) as well.

[Riccardo Schirone (firexy)]

I have the same issue.

Steps to reproduce:
1. Starting up to Unity
2. Switch to tty1 (Strg + Alt + F1)
3. Switching back to Unity

or

1. Starting up to Unity
2. Suspend computer
3. Resume computer

In both cases i have to wait about 2 minutes, because video is freeze.

But I have noticed that if i do in that way :
1. Starting up to Unity
2. Login to my account
3. Logout

Then the problem no longer exists. I can switch to tty1-2-3-etc, suspend and resume and do anything without have to wait 2 min.

[Felix Eckhofer (eckhofer)]

Seeing the same problem in raring (3.7.0-7-generic). Is there anything that can be done to help debug this?

[Maurus Cuelenaere (mcuelenaere)]

Just tested 3.8.0-rc2 and the problem is still present (switched to tty1 and switched back to X).

mcuelenaere@hp4530s:~$ uname -a
Linux hp4530s 3.8.0-rc2+ #55 SMP Thu Jan 3 17:48:58 CET 2013 x86_64 x86_64 x86_64 GNU/Linux
mcuelenaere@hp4530s:~$ dmesg|tail -n 32
[ 187.558865] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 187.558877] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE1C (len 62, WS 0, PS 0) @ 0xCE38
[ 192.552774] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 192.552784] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE1C (len 62, WS 0, PS 0) @ 0xCE38
[ 197.546689] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 197.546700] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE1C (len 62, WS 0, PS 0) @ 0xCE38
[ 202.540605] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 202.540624] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE1C (len 62, WS 0, PS 0) @ 0xCE38
[ 207.534515] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 207.534532] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE1C (len 62, WS 0, PS 0) @ 0xCE38
[ 212.528425] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 212.528438] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE1C (len 62, WS 0, PS 0) @ 0xCE38
[ 217.522339] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 217.522354] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE1C (len 62, WS 0, PS 0) @ 0xCE38
[ 222.516250] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 222.516267] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE1C (len 62, WS 0, PS 0) @ 0xCE38
[ 227.511742] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 227.511758] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE1C (len 62, WS 0, PS 0) @ 0xCE38
[ 232.508152] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 232.508166] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE1C (len 62, WS 0, PS 0) @ 0xCE38
[ 237.504561] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 237.504574] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE1C (len 62, WS 0, PS 0) @ 0xCE38
[ 242.500967] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 242.500978] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE1C (len 62, WS 0, PS 0) @ 0xCE38
[ 247.497380] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 247.497396] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE1C (len 62, WS 0, PS 0) @ 0xCE38
[ 252.493790] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 252.493806] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CE1C (len 62, WS 0, PS 0) @ 0xCE38
[ 257.4901...

[Maurus Cuelenaere (mcuelenaere)]

Note: when re-enabling the radeon card using vgaswitcheroo (echo ON > /sys/kernel/debug/vgaswitcheroo/switch) the bug doesn't appear, so this is probably related to vgaswitcheroo disabling the card and the radeon driver not being aware of that fact (this worked in Ubuntu 12.04 though).

[Simon K (octav14n)]

I tried running Weston today, in this process i became aware of the fact that the "Atombios stuck" thing only happens if I switch *TO* an X.org screen (eg from one tty-terminal or from my weston-display [:1])
So this bug has to have to be in X.org.

I even tried to stop lightdm (sudo service lightdm stop). After that [no X-Server was running] I could continusly switch between Weston/Wayland and all my tty-displays. Not even one "stuck" in the whole testing-time.

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Simon K (octav14n)]

apport information

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Simon K (octav14n)]

I only get this Bug if i start a 3D (X11 based) Desktop-Environment.
Tested:
Bug appears:
Gnome-Shell
Unity

Bug doesn't appear:
Gnome Classic
Gnome (without effects)
XFCE
Weston

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Felix Eckhofer (eckhofer)]

My vgaswitcheroo-enabled system is currently unusable with raring's xserver-xorg-video-radeon 1:7.1.0-0ubuntu1 (after typing the password, the screen turns on and off multiple times with lots of "atombios stuck" messages in the syslog and sometimes will start the unity session in low resolution with wrong aspect ratio, most of the time it just hangs however).
With version 1:6.99.99~git20120913.8637f772-0ubuntu1 everything is fine.

[Miguelángel León (migueleonm)]

Same problem with default configuration and kernel in raring ringtail and in quantal quetzal with the xorg-edgers packages (kernel 3.7).

Dual AMD gpus, radeon HD4200/HD5650 (mobility). It happens with the main configuration, discrete gpu ON, and Ubuntu never start, it always stops with the drm messages and with the X windows saying that is in low graphic mode but the desktop never starts, not even in low graphic mode. Lightdm doesn't start manually either.

With the discrete GPU OFF (with switcheroo) it launches the drm erros and lightdm doesn't start either but I can Start lightdm manually.

With the main kernel (3.5) in quantal quetzal, all runs normal.

[Xavier Bugaud (xavier-bugaud)]

Same problem here running kubuntu 13.04 (stock kernel) on a HP Envy 17 (3070nr) with the radeon HD7690 switched off and the Intel GPU switched on.
Everything was ok with kubuntu 12.10.

Please ask if more information is needed.

[Anton (tosha-korneev)]

Same problem with Acer Aspire 4820TG laptop (dual intel + radeon graphics) on Ubuntu 13.04 with ppa:gnome3-team/gnome3 and gdm/gnome-shell as desktop manager/shell. I am using

  $ echo OFF | sudo tee /sys/kernel/debug/vgaswitcheroo/switch

to reduce power usage.

Suspend command works fine, but resume takes a few minutes (and system is not responsive to any keyboard or mouse activity). Looking at dmesg after I can see a bunch of lines with:

...
[ 8265.630421] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 8265.630431] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CF24 (len 62, WS 0, PS 0) @ 0xCF40
[ 8270.621677] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 8270.621681] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CF24 (len 62, WS 0, PS 0) @ 0xCF40
[ 8275.613016] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[ 8275.613021] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CF24 (len 62, WS 0, PS 0) @ 0xCF40
...

[josvanr (josvanr)]

same problem on hp envy 17 2100 ed. Let me know if I can do something..

[Tomas Drbota (argoneuscze)]

I have got the same problem on my HP ProBook 4340s. In addition, my system seems to hang in random intervals.

[penalvch (penalvch)]

Simon K, could you please provide the full computer model as noted on the sticker?

[Simon K (octav14n)]

The Sticker reads as following::

Product: WN867EA#ABD
Model: tm2-1110eg

[penalvch (penalvch)]

Simon K, I'm struggling to find the support page for this model via HP's website. Could you please provide the URL?

[Simon K (octav14n)]

I can't find a page either.

It seems like my model is a rebranded tm2-2010eg (the model-number in front of the "#" is the same), only sold by amazon.de as a "tm2-1110eg". The hardware details, as far as I can see, are the same for both models.

tm2-2010eg details:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c02262928&cc=us&destPage=document&lang=de&lc=en&product=4213107&tmp_docname=c02266791

amazon.de product page for tm2-1110eg:
http://www.amazon.de/dp/B003NWQ2MM

[penalvch (penalvch)]

Simon K, as per http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=4063&lc=en&cc=us&dlc=en&sw_lang=&product=4213107#N1356 an update is available for your BIOS (F.25). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

[Simon K (octav14n)]

So after finding an Windows image and flashing my Bios to F.25 the problem is still the there.

What happened:
I installed WinVista, flashed my BIOS (The Insyde-Setup sayed: old ID: 1486, old Version: F.12 - new ID: 1486, new Version: F.25)
After finishing the setup my PC shutdown. The power seemed to be "disconnected" abruptly (like when I disconnect my power-cable and there is no battery while the notebook is running)

After that I started my notebook, the BIOS seems to sometimes not register my keys (i.e. I can't open some pages from others, where I could before).
Ubuntu didn't show anything on the build in screen. I plugged in an external screen, started Ubuntu and switched, via tty1, the graphicscard to "Intel only" (IGD).
At this point I started Ubuntu in the "Recovery Mode" (via Grub) and activated Xorg failsafe. It did however hang a huge time without starting any X. So I rebooted.
After a new restart I could change my brightness with my FN-keys again (my Notebook starts with a blank screen every time, I have to higher the brightness then).

octavian-tm2:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for octavian:
F.25
02/18/2011

I hope the important informations where mentioned by me.

PS: I've tested a few times, subjectively I would say that it got better (it hangs for a shorter time period), this however needs more testing to be sure.

[penalvch (penalvch)]

Simon K, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Simon K (octav14n)]

The problem is still the same (as described in post #1 ) with the latest upstream release-candidate of kernel 3.11 (r5).

octavian@octavian-tm2:~$ uname -r
3.11.0-031100rc5-generic

however there was no package "linux-image-extra*" or "pae" (like listed in the wiki).

PS: I've tested some more, seems like the periode, my PC hangs is a bit random but on average it's still the same amount of time as before doing BIOS and kernel-mainline upgrades.

[penalvch (penalvch)]

Simon K, did this problem not occur in a release prior to Quantal?

[Simon K (octav14n)]

Just a quick report:

I downloaded Ubuntu 12.04.2. I couldn't reproduce my bug on this system, everything looks fine.
(However I installed it on an USB-Stick, not my actual hard drive but this shouldn't make any difference, I hope)

However I used Kernel "3.5.0-23".
But this bug was reported under Ubuntu 12.10, Kernel "Linux 3.5.0-17-generic x86_64"

It seems like something else is causing this bug? Since the bug isn't there on a higher Version.
I'll now try Ubuntu 12.10 and look if the bug is reproduce able at the bare installation (without updates).

[kapad (rohankapadia)]

> We don't get this issue during normal modeset, so I suspect the regs are in a wonky state after resume. Perhaps a hard reset before asic_init would help.

What is a hard reset before asic_init

[Macros (Roger Rösch) (macros.)]

I am suffering from the same bug using a P502 also named Sager NP9150 (P150EM Barebone)
with an AMD 7970m and an Intel igpu.

As I workaround i use a small script I have attached. Placed in /etc/pm/sleep.d it seems to work for the moment.
Dont forget to make it executable.

I have no problems with random freezes, only with suspend and resume.

[penalvch (penalvch)]

Macros (Roger Rösch), if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
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 would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[Simon K (octav14n)]

So I found out, why those "hangs" occur (or better: how to "heal" them):
till now I've had a script in my "autostart"-section which essentially just disabled the dgpu (the power-gpu).
It seems like X.org or something isn't happy with getting "robbed" a card while it is running.

So my solution/fix is:
Deaktivating the card before X.org is even started, by setting up an Upstart-Job:
$ sudo nano /etc/init/disable-gpu.conf # content at: http://paste.ubuntu.com/6131570/

Now everything (including Audio, which had a "separate" bug) works fine, no hangs at shutdown, no problems at suspend/resume, no problems at VT-switching.

[penalvch (penalvch)]

Simon K, would disabling the discrete graphics card in BIOS be an additional available method?

As well, given the issue appears to be identified with vgaswitcheroo not quite being free of causing collatoral damage, and you have what appears to be an acceptable alternative to disabling your graphics card, would you like to pursue a fix for this, or would disabling the garphics card via upstart-job be considered a solution?

[Simon K (octav14n)]

There is no switch in my BIOS to disable the discrete graphics card, so no, this is no option.

And with seeing the changes that are coming up in Kernel 1.12 and 1.13, where VGAswitcheroo is to be ignored I don't know if it's worth the trouble.

But disabling the graphics-card with an upstart-job is good enough till above mentioned kernels are available.

[Alberto Salvia Novella (es20490446e)]

Importance changed to 'critical' because the bug renders the system temporarily or permanently unusable.

[Alberto Salvia Novella (es20490446e)]

Please, can anyone please report this bug upstream? (https://wiki.ubuntu.com/Bugs/HowToTriage#Forwarding_upstream)

[Alberto Salvia Novella (es20490446e)]

Chris; since the reason of why the bug status has been marked as "fix released" is unknown, I'm reverting it to its previous state. But you can change this at any time by explaining you choice.

[penalvch (penalvch)]

Not Critical due to WORKAROUND..

[penalvch (penalvch)]

Simon K, 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, please just make a comment to this.

If reproducible, could you also please test the latest upstream kernel available via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc6-trusty/ and advise to the results?

[solax (solax76)]

I'm still having the same issue with Ubuntu 13.10.

[penalvch (penalvch)]

solax, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
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.

Thank you for your understanding.

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

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[penalvch (penalvch)]

Samarjit Adhikari, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.