Machine hung, display frozen

[Jorma Seppänen]

Description: Ubuntu 11.04
Release: 11.04

I unplugged my laptop HP4525s to move it to another location, what happened then was that the display froze and the machine did not respond to any keyboard sequence. I had to use the power button to force boot.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-8-generic 2.6.38-8.42
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jorma 1673 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xd4300000 irq 16'
   Mixer name : 'IDT 92HD81B1X5'
   Components : 'HDA:111d7605,103c142d,00100402 HDA:11c11040,103c3066,00100200'
   Controls : 14
   Simple ctrls : 9
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xd4220000 irq 45'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Fri Jun 3 13:26:49 2011
HibernationDevice: RESUME=UUID=a3aafa42-830b-4c6f-a7d2-8d3cc0206f7f
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
MachineType: Hewlett-Packard HP ProBook 4525s
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=676e573c-9584-4814-bae8-f6a9e22bbca9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-8-generic N/A
 linux-backports-modules-2.6.38-8-generic N/A
 linux-firmware 1.52
SourcePackage: linux
StagingDrivers: brcm80211
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CPK Ver. F.08
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 142D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 51.16
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPKVer.F.08:bd12/06/2010:svnHewlett-Packard:pnHPProBook4525s:pvr:rvnHewlett-Packard:rn142D:rvrKBCVersion51.16:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 4525s
dmi.sys.vendor: Hewlett-Packard

[Jussi Schultink (jussi01)]

Happened again, and resetting via ctrl+alt+sysrq-reisub worked.

The relevant part of the syslog: (as per requested by apw on irc)
Jun 7 10:07:33 monster kernel: [79555.673906] usb 4-3: USB disconnect, address 3
Jun 7 10:07:35 monster kernel: [79557.460073] usb 4-3: new low speed USB device using ohci_hcd and address 4
Jun 7 10:07:35 monster kernel: [79557.661429] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:12.0/usb4/4-3/4-3:1.0/input/input13
Jun 7 10:07:35 monster kernel: [79557.661594] generic-usb 0003:046D:C050.0003: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:12.0-3/input0
Jun 7 10:17:01 monster CRON[13591]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jun 7 10:32:05 monster kernel: [81028.414275] SysRq : Keyboard mode set to system default
Jun 7 10:32:07 monster kernel: [81029.756536] SysRq : Terminate All Tasks

[Andy Whitcroft (apw)]

This tells us the machine is not completly dead as the syslog recording deamons were alive and could write to the disk. This tends to imply its either X or the output drivers which are dead. Please add W and T to your REISUB sequence, specifically RWTEISUB, but do allow W and T some time to output their output and for syslog to record it to disk before continuing (you will likely see the disk activity for T as it produces a complete task list).

[penalvch (penalvch)]

Jorma Seppänen, thank you for reporting this bug and helping make Ubuntu better. Please execute the following at the Terminal:
apport-collect 792291

As well, what you have described seems to be a generic X freeze. It could be caused by any number of things, and you need to take some additional steps to provide a complete report.

When did you upgrade to this version of Ubuntu? When did you first notice the freezes occurring?

How frequently do the freezes occur? How many per day would you say you experience?

List the applications you typically have open at the time of the freeze.

Think back to the last few times it froze. What activities were you doing in each of those times?

Do you have compiz enabled? Does the issue go away if you disable it?

If your system is a laptop, do you suspend/resume it? Had you resumed at some point prior to the freezes?

Finally, and most importantly, please collect a GPU dump after reproducing the bug. Packages to install and directions for doing this are available at:
https://wiki.ubuntu.com/X/Troubleshooting/Freeze#How%20to%20Get%20a%20Batchbuffer%20Dump%20(-intel%20only)

With the GPU dump in hand, we will be able to upstream this bug.

For more tips on troubleshooting freeze bugs, please refer to this link:
https://wiki.ubuntu.com/X/Troubleshooting/Freeze

[bugbot (bugbot)]

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.