Ubuntu
xserver-xorg-video-intel package

Screen lockup in Jaunty, running an intel video card

Bug #359817 reported by crashsystems
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

The screen on my Inspiron 1420 laptop (Intel GPU) froze, though I could still move the mouse around. I'm running Jaunty with the latest updates, compiz enabled with an ext4 file system. At the time I had Firefox, Pidgin, Gwibber and the Gimp open. This is the forth time this has happened in a 72 hour period. One other time I was ripping a DVD with Handbrake, though the other times the system was idle, with the only open programs were Firefox, Pidgin and Gwibber. I was able to SSH into the machine, during which I had full CLI access, and was able to read and write files. While logged in via SSH, I gathered a bunch of log files, the xorg.conf file, and the Intel GPU register state both during and after the lockup. I'll be posting those files to this report via email just as soon as I hit submit.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: xserver-xorg-video-intel 2:2.6.3-0ubuntu9
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-11-generic (buildd@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009
SourcePackage: xserver-xorg-video-intel
Uname: Linux 2.6.28-11-generic x86_64

Revision history for this message
crashsystems (crashsystems) wrote :
Revision history for this message
crashsystems (crashsystems) wrote : Log files
  • reg_bad.txt Edit (7.8 KiB, text/plain; charset=US-ASCII; name="reg_bad.txt")
  • dmesg Edit (49.1 KiB, application/octet-stream; name=dmesg)
  • dmesg.log Edit (49.4 KiB, text/x-log; charset=US-ASCII; name="dmesg.log")
  • gdm.0.log Edit (748 bytes, text/x-log; charset=US-ASCII; name="gdm.0.log")
  • gdm.0.log.1 Edit (748 bytes, application/octet-stream; name="gdm.0.log.1")
  • gdm.0.log.2 Edit (865 bytes, application/octet-stream; name="gdm.0.log.2")
  • kern.log Edit (792.8 KiB, text/x-log; charset=US-ASCII; name="kern.log")
  • kern.log.0 Edit (472.3 KiB, application/octet-stream; name="kern.log.0")
  • reg_good.txt Edit (7.8 KiB, text/plain; charset=US-ASCII; name="reg_good.txt")
  • syslog Edit (1013.6 KiB, application/octet-stream; name=syslog)
  • syslog.0 Edit (305.6 KiB, application/octet-stream; name="syslog.0")
  • Xorg.0.log Edit (25.2 KiB, text/x-log; charset=UTF-8; name="Xorg.0.log")
  • Xorg.0.log.old Edit (25.7 KiB, application/x-trash; name="Xorg.0.log.old")
  • xsession-errors Edit (8.2 KiB, application/octet-stream; name=xsession-errors)

Here are all the info I collected while SSHed into the machine, including a
bunch of logs, and my intel register state both during and after the
lockup.

Revision history for this message
Andres Mujica (andres.mujica) wrote :

Hi crash, i'm marking this as dupe from bug #359392

thanks for report the issue and the logs

Revision history for this message
Andres Mujica (andres.mujica) wrote :

please attach your dpkg.log to the metabug

thanks

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

Other bug subscribers

Remote bug watches

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