8086:27a2 [Dell MP061] i945: Random complete freeze using dual monitors

Bug #1079440 reported by mikesmithv
74
This bug affects 15 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Medium
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

I can run all day without problems if I boot up using just the laptop screen, but using an external monitor to extend the viewing area I get a crash after about an hour or two of use, 100% guaranteed. It seems completely random. I was getting similar crashes in 12.04 but using 2d "fixed" that. Now with 12.10 I have to use 3d. By complete freeze I mean no mouse click or key press does anything but I can still see the cursor move with the mouse.

When I first installed 12.10 and the system froze I could use ctrl-alt-F1 to restart the display manager, but since a recent system update ctrl-alt-F1 just switches to a black screen (no text). Typing any kind of command seems to have no effect, so it is more than the characters simply not displaying. So this recent system update seems to make the crash more severe when it happens.

Description: Ubuntu 12.10
Release: 12.10

compiz:
  Installed: 1:0.9.8.4+bzr3407-0ubuntu1
  Candidate: 1:0.9.8.4+bzr3407-0ubuntu1
  Version table:
 *** 1:0.9.8.4+bzr3407-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     1:0.9.8.4-0ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: compiz 1:0.9.8.4+bzr3407-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Thu Nov 15 14:13:02 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus: vboxhost, 4.2.4, 3.5.0-18-generic, x86_64: installed
EcryptfsInUse: Yes
GraphicsCard:
 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:01cd]
   Subsystem: Dell Device [1028:01cd]
InstallationDate: Installed on 2012-10-31 (15 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: Dell Inc. MP061
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=0650f48a-9821-4f03-aad9-130f0ff78d65 ro quiet splash vt.handoff=7
SourcePackage: compiz
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0FF049
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd12/18/2006:svnDellInc.:pnMP061:pvr:rvnDellInc.:rn0FF049:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MP061
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3

Revision history for this message
mikesmithv (mikesmithv) wrote :
Revision history for this message
Keith McClelland (zismylaptop) wrote :

I get the same problem with the same description except that it only takes a few minutes.

My Hardware is HP Mini 110. It appears that it only works properly using 800x600 for the external monitor, but I can use native 1024x600 for the internal screen.

After a few minutes it freezes up in such a way that mouse movement can be seen but nothing can be clicked or typed. Forced rebooting with the power switch is the only option.

Revision history for this message
Keith McClelland (zismylaptop) wrote :

I've looked into this further.

First, the bug is heavily related to screen, keyboard, and/or mouse activity. If I set up two monitors and don't have anything going on more interesting than the clock changing once a minute, all is fine for hours. If I set up activities on both screens and start playing with applications, the system freezes within a few minutes. (Perl printing out an infinite run of integers is very nice, so is system monitor's "resources" screen.)

Second, while this happens using either the installed 12.10 or the live 12.10 DVD, it does not happen using the 12.04 live CD. Perl had counted to 180 million, taking several hours, and I had played with various applications during that time. [There were some minutes of screen blanking due to inactivity as well.]

I could not find anything in /var/log that appeared to relate to this problem.

Revision history for this message
Keith McClelland (zismylaptop) wrote :

More information:

Although this is marked above as applying to compiz, I feel that it is really the i915 driver that powers both screens. Ubuntu 12.04 uses xserver-xorg-video-intel 2:2.17.0-1ubuntu4. 12.10 uses 2:2.20.9-0ubuntu2. It's more of a feeling than a certainty. The driver would probably be easier to replace since there has been a lot of work in compiz, gnome, etc. since 12.04.

Also, I was able to prove, despite what the original report says, that keystrokes DO come through after the freeze. I don't think mouse clicks do, but that is probably harder to be sure of.

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

OS: Ubuntu 12.10 (Quantal Quetzal).
Version of xserver-xorg-video-intel: 2:2.20.9-0ubuntu2
Computer: HP Mini 110
Video chips: VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03) and Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)

I can set up dual screens and everything works pretty nicely for a while (with the restriction that no resolution above 800x600 can be used on the VGA). However, before long everything freezes up. The mouse pointer can still wander freely across both screens, and I can prove by careful preparation that the keyboard is still sending keys to the selected window. I suspect that the actual event is triggered by a keystroke or mouse movement because it doesn't seem to happen if you just set it up and wait for failure.

Only two things can change the video display. (1) CTL-ALT-F1 blanks the VGA display but then the usual login message is not written to it. (2) the inevitable "press and hold the power button" causes blank screens when the power finally goes off.

Note that this happens with either the installed 12.10 or a live DVD of 12.10. It does not appear to be a problem with Ubuntu 12.04 (tested using a live CD). 12.04 uses xserver-xorg-video-intel version 2:2.17.0-1ubuntu4.

I'd like to try swapping drivers but am unwilling to go down that path without advice.

Thanks.

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

This is also reported in Launchpad bug 1079440.

Revision history for this message
In , Chris Wilson (ickle) wrote :

To be frank we fixed a lot of issues in the upstream kernel, so please do look for the current set of drivers in the xorg-edgers and either a mainline 3.7 kernel of drm-intel-experimental (which tracks our upstream branch).

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

Okay,

I've loaded up a nightly build of 3.7.0 (http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/ -- the one I got was "3.7.0-994.201212210409". That didn't change things. Then I set up the xorg-edgers PPA as described in "https://launchpad.net/~xorg-edgers/+archive/ppa/+index?batch=75". [That brings in yet another 3.7.0 kernel.]

With all the new xorg software, using the current kernel or either of the 3.7.0 kernels, nothing seems to be broken that didn't used to be broken, but the problem still occurs after a few minutes.

The effect of CTL-ALT-F1 (virtual terminal) is inconsistent, so I can't rely on that to upload more details. I could probably set something up on a regular terminal that could be sent by a few simple keystrokes after the freeze occurs. I don't know what that would be, perhaps some form of appport. If someone would like me to do this, please suggest a method.

If developers would like to try to find this on their own systems, let me point out that both of the reports in launchpad bug 1079440 concern computers with the same combination of i954 chips.

My setup is simple: (1) use a terminal to run a perl-one-liner that squirts a running count to the screen, then position that on the boundary of the two displays; (2) set up a system monitor so that the activity graph is scrolling across both monitors; (3) set up an emacs editor and select its window; (4) wait a few minutes, typing into emacs as you please -- then save your scribblings after the freeze.

Let me know what more I can do to help you find this.

Revision history for this message
Keith McClelland (zismylaptop) wrote :

I have also entered a bug in the bugzilla at freedesktop.org. This bug is number 58594. I was advised in response to that bug that many changes have been made in related software recently and I should try a "drm-intel" daily build of kernel 3.7.0 plus the entire suite of "xorg-edgers" updates.

I was able to do this; more details are available at the freedesktop bug. But there was no change in behavior.

I think it is noteworthy that both my computer and mikesmithv's computer use the same i954 chips even though they are otherwise different.

Revision history for this message
mikesmithv (mikesmithv) wrote :

I believe your focus on the Intel driver is correct. I originally had problems with 12.04 and it just got worse with 12.10. I believe it is the same problem discussed here:

http://linux.slashdot.org/story/12/09/20/1245240/stubborn-intel-graphics-bug-haunts-ubuntu-1204

If I had it to do over again I would have not used the word "random" in the bug title, it is 100% guaranteed it will crash when the external monitor is used. With 12.04 it happened with a day, with 12.10 it more like an hour and even faster for Keith. What exactly triggered the crash may be random the there is no doubt that it is the external monitor makes it happen.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in compiz (Ubuntu):
status: New → Confirmed
Revision history for this message
Bambitroll (juan-btcorp) wrote :

I have the same problem but with a nVidia card:
sudo lshw -c video
  *-display
       description: VGA compatible controller
       product: GT218 [NVS 3100M]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a2
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
       configuration: driver=nouveau latency=0

Revision history for this message
Bambitroll (juan-btcorp) wrote :

I have now installed the nVidia proprietary driver and hopefully it will help...

Revision history for this message
In , Younes Manton (younes-m) wrote :

Created attachment 72479
Reg dump after dual monitor hang (w/ AccelMethod SNA)

Revision history for this message
In , Younes Manton (younes-m) wrote :

I see a very similar problem on a Thinkpad T400. Using the laptop panel everything is fine, but plugging in a monitor eventually leads to a very hard hang. The monitor's resolution is correctly detected in my case, and the GPU is indentified as "Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller])".

I can hit the problem within 5 minutes using AccelMethod SNA; using UXA can give me several hours on average, but eventually it too dies. In both cases:

cat /sys/kernel/debug/dri/0/i915_error_state
no error state collected

I did grab a register dump after it died using SNA, if that's of any help.

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

I've made a breakthrough in understanding this problem. It seems to give me a 100% workaround but of course I can't be sure.

The solution is to use "taskset" to force the "Xorg" and "compiz" processes to always be run on the same CPU. The simple terminal commands are:

taskset -pa 1 $(pgrep -x compiz)
sudo taskset -pa 1 $(pgrep -x Xorg)

You might need to do this before the second monitor is connected.

I have run for several hours both in a quiet state and with as much complexity and CPU bashing as the computer can reasonably handle. The high CPU loading makes the system sluggish, but it does not fail.

Good luck turning this workaround into a real fix!

Revision history for this message
Keith McClelland (zismylaptop) wrote :

I've made a breakthrough in understanding this problem. It seems to give me a 100% workaround but of course I can't be sure.

The solution is to use "taskset" to force the "Xorg" and "compiz" processes to always be run on the same CPU. The simple terminal commands are:

taskset -pa 1 $(pgrep -x compiz)
sudo taskset -pa 1 $(pgrep -x Xorg)

You might need to do this before the second monitor is connected.

I have run for several hours both in a quiet state and with as much complexity and CPU bashing as the computer can reasonably handle. The high CPU loading makes the system sluggish, but it does not fail.

Good luck turning this workaround into a real fix!

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: i945: Random complete freeze using dual monitors

Nice workaround.

The fact that the mouse pointer is implemented in hardware yet invisible, as well as Ctrl+Alt+F1 not working properly mean this is almost certainly a driver problem. In the kernel (i915 module) or mesa.

summary: - Random complete freeze using dual monitors
+ i945: Random complete freeze using dual monitors
affects: compiz (Ubuntu) → linux (Ubuntu)
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

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

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.8-rc2-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-da-key
Revision history for this message
mikesmithv (mikesmithv) wrote : Re: [Bug 1079440] Re: i945: Random complete freeze using dual monitors
Download full text (6.4 KiB)

I installed kernel v3.8-rc2 and rebooted. I noticed one difference right
away. I could suspend and resume without crashing. Before that was a
guaranteed crash (black screen on resume, keyboard dead). But then just
minutes after the successful resume I got the dialog box saying "an
internal error occurred, do you want to report it". I clicked "Yes" and
everything seem normal for a few minutes. It happened around 1:20PM PST if
that helps find that report. Anyway, a few minutes later the same freeze
occurred, cursor moves but clicking anywhere does nothing. The only thing
going on was I was typing into a browser window (typing this).

I restarted WITHOUT the second monitor plugged in. So far everything is
fine. No freezes, no "internal error" messages. I have suspended and
resumed 3 times while typing this without any problems.

In summary, something was fixed in that I could come back from a suspend
with the second monitor plugged in. Otherwise, it appears the
same instability exists with the second monitor and everything is OK using
just the laptop screen.

On Mon, Jan 7, 2013 at 9:42 AM, Joseph Salisbury <
<email address hidden>> wrote:

> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v3.8 kernel[0] (Not a kernel in the daily directory) and install both
> the linux-image and linux-image-extra .deb packages.
>
> 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.8-rc2-raring/
>
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Tags added: kernel-da-key
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1079440
>
> Title:
> i945: Random complete freeze using dual monitors
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> I can run all day without problems if I boot up using just the laptop
> screen, but using an external monitor to extend the viewing area I get
> a crash after about an hour or two of use, 100% guaranteed. It seems
> completely random. I was getting similar crashes in 12.04 but using
> 2d "fixed" that. Now with 12.10 I have to use 3d. By complete freeze
> I mean no mouse click or key press does anything but I can still see
> the cursor move with the mouse.
>
> When I first installed 12.10 and the system froze I could use ctrl-
> alt-F1 to restart the display manager, but since a recent system
> update ctrl-alt-F1 just switches to a black screen (no text). Typing
> any kind of command seems to have no effect, so it is more th...

Read more...

Revision history for this message
mikesmithv (mikesmithv) wrote : Re: i945: Random complete freeze using dual monitors

I should add that I cannot mark this as Confirmed since I am the original poster. It is up to someone else (Keith?) to confirm this using v3.8-rc2.

Revision history for this message
Keith McClelland (zismylaptop) wrote :

Sorry, I wasn't subscribed to notifications so I thought there was nothing going on.

I loaded 3.8-rc5 but the system still freezes after a few minutes.

I don't know how to add the tag 'kernel-bug-exists-upstream' but need to.

tags: added: kernel-bug-exists-upstream
Revision history for this message
mikesmithv (mikesmithv) wrote :

Keith McClelland (zismylaptop) confirms this bug still persists in 3.8-rc5

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Keith McClelland (zismylaptop) wrote :

I have a refinement for my workaround. I supposed that the important thing was to keep Xorg and compiz on the same CPU. But that is not the case. The most important thing seems to be to run Xorg on CPU 1. Note that my computer is an Intel Atom N280 whose two cores are is not advertised to be identical. I'd be suspicious of hairy signal timing based on this table. (Xorg 1 means "taskset" Xorg to CPU 1 etc.):

|| || Xorg 1 || Xorg 2 || Xorg unpinned||
|| Compiz 1 || WORKS || FAILS || WORKS ||
|| Compiz 2 || WORKS || FAILS || FAILS ||
|| Compiz unpinned || WORKS || FAILS || FAILS ||

All the cases that "WORK" have run with dual monitors and heavy use for more than an hour; many hours for the Xorg 1 cases. The ones that "FAIL" have never run more than a half hour or so under the same conditions.

Hope this helps.

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

Note that the related launchpad bug is beginning to get some attention based on finding that even kernel 3.8-rc5 doesn't help.

I have a refinement for my workaround. I supposed that the important thing was to keep Xorg and compiz on the same CPU. But that is not the case. The most important thing seems to be to run Xorg on CPU 1. Note that my computer is an Intel Atom N280 whose two cores are is not advertised to be identical. I'd be suspicious of hairy signal timing based on this table. (Xorg 1 means "taskset" Xorg to CPU 1 etc.):

|| || Xorg 1 || Xorg 2 || Xorg unpinned||
|| Compiz 1 || WORKS || FAILS || WORKS ||
|| Compiz 2 || WORKS || FAILS || FAILS ||
|| Compiz unpinned || WORKS || FAILS || FAILS ||

All the cases that "WORK" have run with dual monitors and heavy use for more than an hour; many hours for the Xorg 1 cases. The ones that "FAIL" have never run more than a half hour or so under the same conditions.

Hope this helps.

Revision history for this message
In , Daniel-ffwll (daniel-ffwll) wrote :

Younes Manton, can you please file a separate bug for your issue? You have a completely different platform, so rather likely you hit a different bug.

Revision history for this message
In , Daniel-ffwll (daniel-ffwll) wrote :

LP link for reference: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1079440

Keith, can you try to log in via ssh and grab logfiles once the system freezes up like you describe? Since mouse still works, it's likely just a gfx render issue and everything else works.

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

Created attachment 73851
auth.log

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

Okay, here are all the logs I can find that cover the time period of this failure.

Background. After I hooked up the monitor, I started the following perl one-liner:

perl -e'my $x = 0; int $x;while(1){++$x;print"$x\n" unless $x % 1000000}'

This spits out a new million about twice a second. I then started the gnome-system-monitor and positioned the terminal window and the monitor window so that both of them were regularly updating both monitors. The video hung at 8:26 with a count of 2.2 billion. I was doing other things and didn't get back to issue this report until after 11:00. By that time the perl process had run at almost 100% CPU usage for more than 200 minutes and thus many billions more counts. Xorg was moving, but slowly, only 12 minutes total. Compiz was stopped dead at 5 minutes.

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

Created attachment 73852
syslog

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

Created attachment 73854
wtmp

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

Created attachment 73855
lastlog

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

Created attachment 73856
Xorg.0.log

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

Created attachment 73857
pm-powersave.log

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

Created attachment 73858
syslog.1

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

Created attachment 73859
udev

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

Created attachment 73860
kern.log

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

Created attachment 73861
boot.log

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

Created attachment 73862
dmesg

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

One more thing I should add about this sequence.

I have added 'taskset -pa 1 $(pgrep -x Xorg)' to the rcX.d set of things. So initially the computer came up with my workaround in place. I reversed that with 'sudo taskset -pa 3 $(pgrep -x Xorg)' before connecting the external monitor.

All of this was about an hour after the computer was booted up at 6:57.

Revision history for this message
Keith McClelland (zismylaptop) wrote :

I've added as many log files and additional information as I could to freedesktop-bugs #58594.

Changed in linux:
importance: Unknown → Medium
status: Unknown → Incomplete
Revision history for this message
Davide Depau (depau) wrote : Re: i945: Random complete freeze using dual monitors

This problem affects me too. Sometimes, when I use two monitors in extended mode, the PC suddenly freezes. When I hover something, the cursor changes (e.g. if I hover an entry the cursor becomes a "I"), but if I click, this doesn't happen any more. Also, if I disconnect the secondary monitor, the primary becomes black. When the screen is not black, I can however switch to a TTY and try to restart the desktop manager, but it doesn't show up and I need to restart.

Revision history for this message
In , Chris Wilson (ickle) wrote :

Can you please try drm-intel-next with

commit 21ad833075801a7cd81b5ef1604ffc6c600e5ff9
Author: Ville Syrjälä <email address hidden>
Date: Tue Feb 19 15:16:39 2013 +0200

    drm/i915: Fix races in gen4 page flip interrupt handling

Revision history for this message
In , Chris Wilson (ickle) wrote :

We have good indication from other bugs that the race fix is indeed good. Preemptively closing...

Revision history for this message
In , mikesmithv (mikesmithv) wrote : Re: [Bug 1079440]
Download full text (4.8 KiB)

Could someone post the complete url to drm-intel-next? I found something
but it did not contain commit 21ad833075801a7cd81b5ef1604ffc6c600e5ff9 and
I want to be sure I am testing the right kernel.

On Wed, Feb 20, 2013 at 6:35 AM, Chris Wilson <email address hidden>wrote:

> Can you please try drm-intel-next with
>
> commit 21ad833075801a7cd81b5ef1604ffc6c600e5ff9
> Author: Ville Syrjälä <email address hidden>
> Date: Tue Feb 19 15:16:39 2013 +0200
>
> drm/i915: Fix races in gen4 page flip interrupt handling
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1079440
>
> Title:
> i945: Random complete freeze using dual monitors
>
> Status in The Linux Kernel:
> Incomplete
> Status in “linux” package in Ubuntu:
> Triaged
>
> Bug description:
> I can run all day without problems if I boot up using just the laptop
> screen, but using an external monitor to extend the viewing area I get
> a crash after about an hour or two of use, 100% guaranteed. It seems
> completely random. I was getting similar crashes in 12.04 but using
> 2d "fixed" that. Now with 12.10 I have to use 3d. By complete freeze
> I mean no mouse click or key press does anything but I can still see
> the cursor move with the mouse.
>
> When I first installed 12.10 and the system froze I could use ctrl-
> alt-F1 to restart the display manager, but since a recent system
> update ctrl-alt-F1 just switches to a black screen (no text). Typing
> any kind of command seems to have no effect, so it is more than the
> characters simply not displaying. So this recent system update seems
> to make the crash more severe when it happens.
>
> Description: Ubuntu 12.10
> Release: 12.10
>
> compiz:
> Installed: 1:0.9.8.4+bzr3407-0ubuntu1
> Candidate: 1:0.9.8.4+bzr3407-0ubuntu1
> Version table:
> *** 1:0.9.8.4+bzr3407-0ubuntu1 0
> 500 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main
> amd64 Packages
> 100 /var/lib/dpkg/status
> 1:0.9.8.4-0ubuntu2 0
> 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64
> Packages
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.10
> Package: compiz 1:0.9.8.4+bzr3407-0ubuntu1
> ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
> Uname: Linux 3.5.0-18-generic x86_64
> .tmp.unity.support.test.0:
>
> ApportVersion: 2.6.1-0ubuntu6
> Architecture: amd64
> CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
> CompositorRunning: compiz
> Date: Thu Nov 15 14:13:02 2012
> DistUpgraded: Fresh install
> DistroCodename: quantal
> DistroVariant: ubuntu
> DkmsStatus: vboxhost, 4.2.4, 3.5.0-18-generic, x86_64: installed
> EcryptfsInUse: Yes
> GraphicsCard:
> Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated
> Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
> Subsystem: Dell Device [1028:01cd]
> Subsystem: Dell Device [1028:01cd]
> InstallationDate: Installed on 2012-10-31 (15 days ago)
> InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Rel...

Read more...

Changed in linux:
status: Incomplete → Fix Released
Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

I couldn't find a "commit" with the number Chris gave. But I loaded up the "3.8.0-997_3.8.0-997.201302180432" kernel from "drm-intel-next". However, despite the fact that it seems to have built and installed okay, it dies with an almost-all-black screen a few seconds after it starts initializing the ramfs. I repeated it all and got the same results. Both downloads of the parts gave the same md5sums as follows:

8b88e669a4117f72e58d57481247e936 linux-headers-3.8.0-997_3.8.0-997.201302180432_all.deb
86c4099dfb41e40d7e976493681a2af9 linux-headers-3.8.0-997-generic_3.8.0-997.201302180432_i386.deb
ec53ae004b3c74f097d31dfc61ffeb6c linux-image-3.8.0-997-generic_3.8.0-997.201302180432_i386.deb
057040a505e5c463cc99b42f8c814d4b linux-image-extra-3.8.0-997-generic_3.8.0-997.201302180432_i386.deb

???

Revision history for this message
In , Chris Wilson (ickle) wrote :

(In reply to comment #25)
> I couldn't find a "commit" with the number Chris gave. But I loaded up the
> "3.8.0-997_3.8.0-997.201302180432" kernel from "drm-intel-next". However,
> despite the fact that it seems to have built and installed okay, it dies
> with an almost-all-black screen a few seconds after it starts initializing
> the ramfs. I repeated it all and got the same results. Both downloads of the
> parts gave the same md5sums as follows:

That's a complete different problem. And a critical one to boot. Normally if it breaks that early it is because the initramfs is broken and needs to be rebuilt. Try passing nomodeset to your kernel as it boots and see if that makes diagnosing the problem easier.

Besides the date on kernel is earlier than the patch I referenced to fix the original issue.

Revision history for this message
In , Keith McClelland (zismylaptop) wrote : Re: [Bug 1079440]
Download full text (5.5 KiB)

Chris,

That's the latest kernel in drm-intel-next. There is a newer one (23rd of
Feb) in drm-intel-nightly that has the same Ville S. fixes at the top but
COMMIT is another different number. I'll try that; I don't see any point in
pursuing a different bug at this moment.

Keith

On Mon, Feb 25, 2013 at 5:30 AM, Chris Wilson <email address hidden>wrote:

> (In reply to comment #25)
> > I couldn't find a "commit" with the number Chris gave. But I loaded up
> the
> > "3.8.0-997_3.8.0-997.201302180432" kernel from "drm-intel-next". However,
> > despite the fact that it seems to have built and installed okay, it dies
> > with an almost-all-black screen a few seconds after it starts
> initializing
> > the ramfs. I repeated it all and got the same results. Both downloads of
> the
> > parts gave the same md5sums as follows:
>
> That's a complete different problem. And a critical one to boot.
> Normally if it breaks that early it is because the initramfs is broken
> and needs to be rebuilt. Try passing nomodeset to your kernel as it
> boots and see if that makes diagnosing the problem easier.
>
> Besides the date on kernel is earlier than the patch I referenced to fix
> the original issue.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1079440
>
> Title:
> i945: Random complete freeze using dual monitors
>
> Status in The Linux Kernel:
> Fix Released
> Status in “linux” package in Ubuntu:
> Triaged
>
> Bug description:
> I can run all day without problems if I boot up using just the laptop
> screen, but using an external monitor to extend the viewing area I get
> a crash after about an hour or two of use, 100% guaranteed. It seems
> completely random. I was getting similar crashes in 12.04 but using
> 2d "fixed" that. Now with 12.10 I have to use 3d. By complete freeze
> I mean no mouse click or key press does anything but I can still see
> the cursor move with the mouse.
>
> When I first installed 12.10 and the system froze I could use ctrl-
> alt-F1 to restart the display manager, but since a recent system
> update ctrl-alt-F1 just switches to a black screen (no text). Typing
> any kind of command seems to have no effect, so it is more than the
> characters simply not displaying. So this recent system update seems
> to make the crash more severe when it happens.
>
> Description: Ubuntu 12.10
> Release: 12.10
>
> compiz:
> Installed: 1:0.9.8.4+bzr3407-0ubuntu1
> Candidate: 1:0.9.8.4+bzr3407-0ubuntu1
> Version table:
> *** 1:0.9.8.4+bzr3407-0ubuntu1 0
> 500 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main
> amd64 Packages
> 100 /var/lib/dpkg/status
> 1:0.9.8.4-0ubuntu2 0
> 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64
> Packages
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.10
> Package: compiz 1:0.9.8.4+bzr3407-0ubuntu1
> ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
> Uname: Linux 3.5.0-18-generic x86_64
> .tmp.unity.support.test.0:
>
> ApportVersion: 2.6.1-0ubuntu6
> Architecture: amd64
> CompizPlugins: No value se...

Read more...

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

Since Chris pointed out that the drm-intel-next build (Feb 18) is too old for this fix (never mind that it also seems to exhibit a critical bug on my computer), I tried the latest build from drm-intel-nightly (Feb 23). No critical bug there.

However, it wastes very little time -- a few seconds -- before freezing up. This may be a slightly different freeze as well because the cursor was not responsive. It also didn't do CTL-ALT-F1 though that was never a reliable thing in the past during this freeze.

Revision history for this message
In , Chris Wilson (ickle) wrote :

Yikes. You're not having much fun are you? :(

Do you happen to be able to set up a netconsole and grab the dmesg leading to the hard hang?

Revision history for this message
In , Keith McClelland (zismylaptop) wrote :

Fun has returned. I don't know why the Feb 18 drm-intel-next insists on crashing and I have no idea why the first attempt at the Feb 23 drm-intel-nightly was a failure, but I returned to using it (3.8.0-994-generic) with complete success later on. A 5-hour run, an 8-hour run, and it is currently running and working fine with 2 monitors.

So I agree that the problem is both resolved and fixed. Thanks!

Revision history for this message
In , Keith McClelland (zismylaptop) wrote : Re: [Bug 1079440]
Download full text (5.9 KiB)

Chris,

I don't know how to report this as a bug so I'll just tell you and see if
you know.

A friend of mine has been having a horrible time with 12.10 and really
various other releases as well: the system freezes up in a manner very
reminiscent of the dual monitor problem I have--though he's not using a
second monitor. He's had to run with a rather old kernel in order to get
going at all.

He's been very disgruntled about this, feeling that the people who deal
with Ubuntu bugs were trying to find an excuse to ignore them. He also says
that this "syndrome" seems to have been reported many times by many people
and always goes nowhere.

Anyway, when I saw that the Feb 23 intel-drm-nightly solved the dual
monitor problem, I suggested that he try it. He had a Linux-booting problem
very similar to the "you're not having much fun" problem I had but then it
worked for him.

Here are his words:

Hah! I'm up with 994. Running for about 90 min with two sessions of
Chromium. First Rachmaninof/Paganini and now Brahms piano. Tough time
coming up - took three tries. Died black the first, recovery mode on second
got badly tangled, third graphic seems ok.

If this really fixes this seemingly widespread problem, some folks should
see that the word gets out and quiets the waters. If there's something I
can do to help with this, please let me know.

Thanks,
Keith

On Mon, Feb 25, 2013 at 5:15 PM, Chris Wilson <email address hidden>wrote:

> Yikes. You're not having much fun are you? :(
>
> Do you happen to be able to set up a netconsole and grab the dmesg
> leading to the hard hang?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1079440
>
> Title:
> i945: Random complete freeze using dual monitors
>
> Status in The Linux Kernel:
> Fix Released
> Status in “linux” package in Ubuntu:
> Triaged
>
> Bug description:
> I can run all day without problems if I boot up using just the laptop
> screen, but using an external monitor to extend the viewing area I get
> a crash after about an hour or two of use, 100% guaranteed. It seems
> completely random. I was getting similar crashes in 12.04 but using
> 2d "fixed" that. Now with 12.10 I have to use 3d. By complete freeze
> I mean no mouse click or key press does anything but I can still see
> the cursor move with the mouse.
>
> When I first installed 12.10 and the system froze I could use ctrl-
> alt-F1 to restart the display manager, but since a recent system
> update ctrl-alt-F1 just switches to a black screen (no text). Typing
> any kind of command seems to have no effect, so it is more than the
> characters simply not displaying. So this recent system update seems
> to make the crash more severe when it happens.
>
> Description: Ubuntu 12.10
> Release: 12.10
>
> compiz:
> Installed: 1:0.9.8.4+bzr3407-0ubuntu1
> Candidate: 1:0.9.8.4+bzr3407-0ubuntu1
> Version table:
> *** 1:0.9.8.4+bzr3407-0ubuntu1 0
> 500 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main
> amd64 Packages
> 100 /var/lib/dpkg/status
> 1:0.9.8.4-0ubuntu2 0
> 500...

Read more...

Revision history for this message
Hubert Hesse (hubx) wrote : Re: i945: Random complete freeze using dual monitors

With 12.10 I can confirm the multi monitor setup problem.
With 13.04 (3.8.0-12 generic) this problem also occurs also without using a second monitor. Ctrl+Alt+F1 doesn't work. Via SSH I can see that Xorg uses up 99% of one CPU core. I don't see any relevant output in X.org.0.log or dmesg.

Keith's workaround `sudo taskset -pa 1 $(pgrep -x Xorg` fixes the issue temporarily.

I'm able to help with further logs or debugging.

lspci -vv: http://pastebin.com/jmz7mAcE

Revision history for this message
thomas janssen (janssenth) wrote :

Hi,

I've got the same problem with asus eee x101h (intel N570 gma 3150) and I'am relative shure that the problem affected to composite.
I installed on another partition bodhi linux with e17. The error ocurred there too, if I enable the composite window effects.
I can run the second monitor with every other window manager without composite, but only unity is only working with composite. Why I can't disable composite and run unity2d in 12.10 anymore?
And why is the importance just "medium"? For my small display it is very useful to work with unity. It is very unfortunate that. I love to work with multiple monitor. And so unity ist unusable for me.

Greetings
Thomas

Revision history for this message
thomas janssen (janssenth) wrote :

For me nothing worked. I tried many kernel, even the newest and made unity and compiz update per ppa and a dist-upgrade to 13.04. Always the same effect. Freezen System after a few minute or some mouse-Clicks. There is absolutly no indication in dmesg, kernel.log, syslog or Xorg.log. There is no Input between the time of beginning freeze system and the reboot . Now I'm back to 12.04, because it is working fine with multiple monitor. It' a pity!

Revision history for this message
Markcortbass (markcortbass) wrote :

I confirm this critical bug. It still happens in the latest Ubuntu 13.04.

Hardware:
Dell Inspiron mini 1018

OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) IGD x86/MMX/SSE2
OpenGL version string: 1.4 Mesa 9.0.3

Revision history for this message
yemu (yemu) wrote :

I also confirm this bug. It affects me on Dell Latitude E6410 - Intel 965 video card and ubuntu 13.04

Revision history for this message
Ohad Eytan (ohadey) wrote :

I confirm this critical bug. It still happens in the latest Ubuntu 13.04 on Thinkpad X220 with Intel® Sandybridge Mobile x86/MMX/SSE2

Revision history for this message
Keith McClelland (kmmlkm) wrote :

This must be a very difficult situation for developers. There's no question in my mind that the problem that I could detect when I created this bug was resolved in February (as well as the related freedesktop-bugs #58594 which is where it was ultimately resolved). The difference may be that I was using software from Xorg-edgers at that time (12.10) and have dropped that since loading 13.04.

Anyway, I agree with the three previous comments that the situation is less perfect than it was in February. I cannot create the problem easily like I could before, but I have seen it happen on my HP mini 110. I also borrowed a friend's Dell Inspiron to convert it to Ubuntu. It has seemingly the same video controller as my mini (945) and exhibits similar problems. There seem to be other video problems with that unit but I can't characterize them well.

For reference, I have once again set up the "taskset -pa 1 $(pgrep -x compiz)" fix in my HP mini and haven't seen the problem since but I wouldn't call it definitive.

Thanks for your attention; please let us know if we can perform experiments to help you fix this for real.

Revision history for this message
mikesmithv (mikesmithv) wrote :

I have a new laptop now but just to verify this bug I fired up my old laptop, upgraded to 13.04 and the bug still exists for me as well. This is on the same machine I used when I originally reported this bug. One aspect of this that is 100% reproducible now is that when the external monitor is plugged in and I suspend (either by shutting the lid or from the main menu) then it hangs. The screen just goes black and the computer is on but no longer responsive to anything but a hard shut-down. If the external monitor is NOT plugged it then it suspends normally, 100%. I don't recall this being the case before. FYI, the new laptop (Dell 17R SE) works great with dual monitors on 13.04 and in a way I'm glad I had this excuse to upgrade, the new gen machines are amazing!

Revision history for this message
Nigel Spowage (nigel-launchpad) wrote :

I believe I'm also experiencing this bug on my Asus Eee PC 1015PEM which appears to be using an Intel i915 graphics chip (at least that is the driver thats dmesg says is loaded). As described above this works fine when using the laptops build in screen and no external monitor. Attaching an external monitor will provide a usable display for an unpredictable amount of time before a freeze will happen.

Most of the time the freeze will still allow the mouse pointer to move and also allow CTRL + ALT + F1 to bring up the console. Sometimes neither the mouse moves or the console can be brought up.

I've tried using the taskset workaround but this has not worked for me. This is still a bug using 13.04 with the latest updates installed (kernel 3.8.0-27-generic).

Revision history for this message
Chris (cmavr8) wrote :

I'm also experiencing the problem, but I CAN go back to different ttys and login/restart from there. Also, while "frozen", ctrl+alt+backspace works to log me off (I have enabled it in the settings).

So, I am asking, shouldn't we open a new bug?

Chris

Revision history for this message
penalvch (penalvch) wrote :

mikesmithv, as per http://www.dell.com/support/drivers/us/en/19/DriverDetails?driverId=R243190&fileId=2731117184 an update is available for your BIOS (A10). If you update to this following https://help.ubuntu.com/community/BiosUpdate , 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

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

tags: added: bios-outdated-a10
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Keith McClelland (zismylaptop) wrote : Re: [Bug 1079440] Re: i945: Random complete freeze using dual monitors
Download full text (5.4 KiB)

Christopher,

My problem is (was?) with an HP Mini 110 not a Dell computer. I haven't
tried it recently so I can't say if it was fixed or not.

Thanks,
Keith

On Tue, Nov 19, 2013 at 7:09 AM, Christopher M. Penalver <
<email address hidden>> wrote:

> mikesmithv, as per
>
> http://www.dell.com/support/drivers/us/en/19/DriverDetails?driverId=R243190&fileId=2731117184
> an update is available for your BIOS (A10). If you update to this
> following https://help.ubuntu.com/community/BiosUpdate , 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
>
> Please note your current BIOS is already in the Bug Description, so
> posting this on the old BIOS would not be helpful.
>
> For more on BIOS updates and linux, please see
> https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
> .
>
> Thank you for your understanding.
>
> ** Tags added: bios-outdated-a10
>
> ** Changed in: linux (Ubuntu)
> Status: Triaged => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1079440
>
> Title:
> i945: Random complete freeze using dual monitors
>
> Status in The Linux Kernel:
> Fix Released
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> I can run all day without problems if I boot up using just the laptop
> screen, but using an external monitor to extend the viewing area I get
> a crash after about an hour or two of use, 100% guaranteed. It seems
> completely random. I was getting similar crashes in 12.04 but using
> 2d "fixed" that. Now with 12.10 I have to use 3d. By complete freeze
> I mean no mouse click or key press does anything but I can still see
> the cursor move with the mouse.
>
> When I first installed 12.10 and the system froze I could use ctrl-
> alt-F1 to restart the display manager, but since a recent system
> update ctrl-alt-F1 just switches to a black screen (no text). Typing
> any kind of command seems to have no effect, so it is more than the
> characters simply not displaying. So this recent system update seems
> to make the crash more severe when it happens.
>
> Description: Ubuntu 12.10
> Release: 12.10
>
> compiz:
> Installed: 1:0.9.8.4+bzr3407-0ubuntu1
> Candidate: 1:0.9.8.4+bzr3407-0ubuntu1
> Version table:
> *** 1:0.9.8.4+bzr3407-0ubuntu1 0
> 500 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main
> amd64 Packages
> 100 /var/lib/dpkg/status
> 1:0.9.8.4-0ubuntu2 0
> 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64
> Packages
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.10
> Package: compiz 1:0.9.8.4+bzr3407-0ubuntu1
> ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
> Uname: Linux 3.5.0-18-generic x86_64
> .tmp.unity.support.test.0:
>
> ApportVersion: 2.6.1-0ubuntu6
> Architecture: amd64
> CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
> Composito...

Read more...

Revision history for this message
penalvch (penalvch) wrote : Re: [Dell MP061] i945: Random complete freeze using dual monitors

Keith McClelland, 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 or comments, 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.

summary: - i945: Random complete freeze using dual monitors
+ [Dell MP061] i945: Random complete freeze using dual monitors
Revision history for this message
Keith McClelland (zismylaptop) wrote : Re: [Bug 1079440] Re: [Dell MP061] i945: Random complete freeze using dual monitors
Download full text (5.8 KiB)

I don't think I have a new bug.

Keith
On Nov 19, 2013 7:15 PM, "Christopher M. Penalver" <
<email address hidden>> wrote:
>
> Keith McClelland, 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 or
> comments, 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.
>
> ** Summary changed:
>
> - i945: Random complete freeze using dual monitors
> + [Dell MP061] i945: Random complete freeze using dual monitors
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1079440
>
> Title:
> [Dell MP061] i945: Random complete freeze using dual monitors
>
> Status in The Linux Kernel:
> Fix Released
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> I can run all day without problems if I boot up using just the laptop
> screen, but using an external monitor to extend the viewing area I get
> a crash after about an hour or two of use, 100% guaranteed. It seems
> completely random. I was getting similar crashes in 12.04 but using
> 2d "fixed" that. Now with 12.10 I have to use 3d. By complete freeze
> I mean no mouse click or key press does anything but I can still see
> the cursor move with the mouse.
>
> When I first installed 12.10 and the system froze I could use ctrl-
> alt-F1 to restart the display manager, but since a recent system
> update ctrl-alt-F1 just switches to a black screen (no text). Typing
> any kind of command seems to have no effect, so it is more than the
> characters simply not displaying. So this recent system update seems
> to make the crash more severe when it happens.
>
> Description: Ubuntu 12.10
> Release: 12.10
>
> compiz:
> Installed: 1:0.9.8.4+bzr3407-0ubuntu1
> Candidate: 1:0.9.8.4+bzr3407-0ubuntu1
> Version table:
> *** 1:0.9.8.4+bzr3407-0ubuntu1 0
> 500 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main
amd64 Packages
> 100 /var/lib/dpkg/status
> 1:0.9.8.4-0ubuntu2 0
> 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64
Packages
>
> Probl...

Read more...

Revision history for this message
Chris (cmavr8) wrote : Re: [Dell MP061] i945: Random complete freeze using dual monitors

I experience the same, in a 13.04 Lenovo Thinkpad X201s with i915 graphics. Updated but not upgraded to 13.10. Latest BIOS flashed yesterday. Problem existed before and after flashing.

The following phrase (copied from another comment) describes my experience exactly:
"After a few minutes it freezes up in such a way that mouse movement can be seen but nothing can be clicked or typed. Forced rebooting with the power switch is the only option."

Most logs in /var/log show nothing interesting. The event happened a bit before time 39909 so here's Xorg.0.log's relevant part (attached).

It only happens when I try to wake the screens up after they have turned off. If I disable screen auto off function I am fine. Ctrl+Alt+Backspace works so I just relogin. Very annoying when I have virtual machines running though... they get shut off improperly.

Revision history for this message
Chris (cmavr8) wrote :

Sorry, regarding my last comment, the last sentence of the quoted text is not accurate for me, as I explained later in the comment.

Also, should I gather more info? Using "apport-bug --save /tmp/foo.apport" from a new tty while the X system is frozen? Or restart it and then invoke apport-bug?

Thanks

Revision history for this message
penalvch (penalvch) wrote :

cmavr8, 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 or comments, 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.

summary: - [Dell MP061] i945: Random complete freeze using dual monitors
+ 8086:27a2 [Dell MP061] i945: Random complete freeze using dual monitors
Revision history for this message
Keith McClelland (zismylaptop) wrote : Re: [Bug 1079440] Re: 8086:27a2 [Dell MP061] i945: Random complete freeze using dual monitors
Download full text (6.0 KiB)

I don't know why you are sending this. So far as I know the problem has
been fixed--but I'm not doing dual monitor stuff now and not inclined to
make a new test.

Keith

On Nov 20, 2013 7:41 PM, "Christopher M. Penalver" <
<email address hidden>> wrote:
>
> cmavr8, 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 or
> comments, 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.
>
> ** Summary changed:
>
> - [Dell MP061] i945: Random complete freeze using dual monitors
> + 8086:27a2 [Dell MP061] i945: Random complete freeze using dual monitors
>
> ** Attachment removed: "Xorg.0.log"
>
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1079440/+attachment/3913504/+files/Xorg.0.log
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1079440
>
> Title:
> 8086:27a2 [Dell MP061] i945: Random complete freeze using dual
> monitors
>
> Status in The Linux Kernel:
> Fix Released
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> I can run all day without problems if I boot up using just the laptop
> screen, but using an external monitor to extend the viewing area I get
> a crash after about an hour or two of use, 100% guaranteed. It seems
> completely random. I was getting similar crashes in 12.04 but using
> 2d "fixed" that. Now with 12.10 I have to use 3d. By complete freeze
> I mean no mouse click or key press does anything but I can still see
> the cursor move with the mouse.
>
> When I first installed 12.10 and the system froze I could use ctrl-
> alt-F1 to restart the display manager, but since a recent system
> update ctrl-alt-F1 just switches to a black screen (no text). Typing
> any kind of command seems to have no effect, so it is more than the
> characters simply not displaying. So this recent system update seems
> to make the crash more severe when it happens.
>
> Description: Ubuntu 12.10
> Release: 12.10
>
> compiz:
> Installed: 1:0.9.8.4+bzr3407-0ubuntu1
> Candidate: 1:0.9.8.4+bzr3407-0ubuntu1
> Ve...

Read more...

Revision history for this message
Chris (cmavr8) wrote :

Christopher, I guess this is an automated response but I'll ask you anyway: How would I know if this is against the kernel or the graphics driver? Does anyone else have a clue?

Keith, why are you suggesting that it's been fixed?
Comments 56, 57, 58 and mine suggest otherwise...

Thanks :)
Chris

Revision history for this message
Keith McClelland (zismylaptop) wrote :
Download full text (5.0 KiB)

Good question, Chris,

Again my hardware is HP mini 110, not Dell. The xorg people fixed my
problem seemingly quite completely around 8 months ago (before 13.04). I
don't use dual monitors on a regular basis, so I don't know any more than
that.

Keith

On Thu, Nov 21, 2013 at 3:21 AM, cmavr8 <email address hidden> wrote:

> Christopher, I guess this is an automated response but I'll ask you
> anyway: How would I know if this is against the kernel or the graphics
> driver? Does anyone else have a clue?
>
>
> Keith, why are you suggesting that it's been fixed?
> Comments 56, 57, 58 and mine suggest otherwise...
>
> Thanks :)
> Chris
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1079440
>
> Title:
> 8086:27a2 [Dell MP061] i945: Random complete freeze using dual
> monitors
>
> Status in The Linux Kernel:
> Fix Released
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> I can run all day without problems if I boot up using just the laptop
> screen, but using an external monitor to extend the viewing area I get
> a crash after about an hour or two of use, 100% guaranteed. It seems
> completely random. I was getting similar crashes in 12.04 but using
> 2d "fixed" that. Now with 12.10 I have to use 3d. By complete freeze
> I mean no mouse click or key press does anything but I can still see
> the cursor move with the mouse.
>
> When I first installed 12.10 and the system froze I could use ctrl-
> alt-F1 to restart the display manager, but since a recent system
> update ctrl-alt-F1 just switches to a black screen (no text). Typing
> any kind of command seems to have no effect, so it is more than the
> characters simply not displaying. So this recent system update seems
> to make the crash more severe when it happens.
>
> Description: Ubuntu 12.10
> Release: 12.10
>
> compiz:
> Installed: 1:0.9.8.4+bzr3407-0ubuntu1
> Candidate: 1:0.9.8.4+bzr3407-0ubuntu1
> Version table:
> *** 1:0.9.8.4+bzr3407-0ubuntu1 0
> 500 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main
> amd64 Packages
> 100 /var/lib/dpkg/status
> 1:0.9.8.4-0ubuntu2 0
> 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64
> Packages
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.10
> Package: compiz 1:0.9.8.4+bzr3407-0ubuntu1
> ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
> Uname: Linux 3.5.0-18-generic x86_64
> .tmp.unity.support.test.0:
>
> ApportVersion: 2.6.1-0ubuntu6
> Architecture: amd64
> CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
> CompositorRunning: compiz
> Date: Thu Nov 15 14:13:02 2012
> DistUpgraded: Fresh install
> DistroCodename: quantal
> DistroVariant: ubuntu
> DkmsStatus: vboxhost, 4.2.4, 3.5.0-18-generic, x86_64: installed
> EcryptfsInUse: Yes
> GraphicsCard:
> Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated
> Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
> Subsystem: Dell Device [1028:01cd]
> Subsystem: ...

Read more...

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.