That device is expected to have a VGA header on the motherboard, so it
would seem a manufacturing detect. (VGA link detection is all in
hardware.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242881
Yes, more often than not it is a short across a couple of pins.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242881
Title:
Greeter shows in secondary monitor mode when only one monitor
To manage
*** Bug 72048 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1140716
Title:
[regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on
*** Bug 72048 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround
This is almost certainly a bios bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254131
Title:
Lubuntu 13.10 lid close freeze
To manage notifications about this bug go to:
The tests are intentionally overkill - they are also intended to try and
test handling of large batches, as well as generally stress the system.
I hadn't noticed the basic-copyarea fail. That does look to be
different. So far, the failure pattern had seemed to be a subspan
doesn't get written
** Package changed: xserver-xorg-video-intel (Ubuntu) = xserver-xorg-
video-intel-lts-quantal (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252031
Title:
Xorg - high CPU load on playing
Your hw is falsely reporting a VGA connection. I see that you tried to
disable it with video=VGA1:d, but since that should read video=VGA-1:d.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242881
First step is to attach your Xorg.0.log. For mirroring with HDMI you
will be limited to the intersection of modes supported by both the
monitor and the LCD. If the HDMI monitor does not list 720p as being
supported, you will need to override it and add that mode yourself.
--
You received this
Bleh, Fix Committed, not released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1247785
Title:
Stipple pattern looks like uninitialized memory
To manage notifications about this bug go to:
commit 82b646a42f5a6271c8518ad454f1603714276caf
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Mon Nov 4 11:48:04 2013 +
sna: Only use the simple stipple upload path if wholly contained
If the stipple box is outside of the stipple pixmap, we need to
carefully upload
Your system is incompatible with nomodeset, we must debug the KMS issue
for anything to work.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: hundredpapercuts
Assignee: Chris Wilson (notgary) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/144334
Title:
Rythmbox should scan for new music on start
I'm happy with TearFree now. Please report any issues you find as
separate bugs, thanks everyone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/755841
Title:
[sandybridge] Graphics tearing when
No. (Though there maybe some hardware which may require TearFree by
default to function correctly, in which case it will be enabled
automatically.) The problem is that it increases memory allocation
considerably and reduces performance, giving you the same penalty as
using a compositor. If you
Requires the explicit Option TearFree, but is now possible as of
commit d788b69fdb5ea73b1d283a89e53b2b19eaa90e6e
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Mon Oct 21 23:44:29 2013 +0100
sna: Enable TearFree rendering for transformed scanouts
References: https
No, the original issue (still unresolved) here is in the hardware, which
makes it a kernel problem. However, there are lots of *different* bugs
that have been also reported here that are due to regressions in
mesa/i965.
--
You received this bug notification because you are a member of Ubuntu
It's a bug in mesa/i965.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1223332
Title:
[snb mesa blorp] False GPU lockup IPEHR: 0x7a02
To manage notifications about this bug go to:
TearFree should be much improved as of:
commit fa2687bdd5a4c8bc608dac8bb711035f0752a725
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Mon Oct 21 18:55:23 2013 +0100
sna: Eliminate the synchronous wait from inside TearFree
Defer the actual wait until the next use
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1207814
Title:
[Sandybridge GPU] Getting at least a GPU hang / day
To
Not enough information to diagnose the incomplete stacktrace, but the
logs have plenty of issues with xmir.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- Xorg crashed with SIGABRT in __GI_raise()
+ [prime] Xorg crashed in RRCrtcDetachScanoutPixmap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237943
Title:
[prime] Xorg
The hardware reports a hotplug disconnect for one of your DP monitors,
after which userspace responds by switching it off. We don't have much
control over the hotplug detection, so I don't think there is much we
can do to rectify it other than by manually polling the outputs.
--
You received
The first point is easily solved by attaching an Xorg.0.log, dmesg from
after the slow down. That will confirm whether or not is an application
or driver bug. Following that, profiling the system when the launcher
show abnormally high loads will tell us where to look for the bug and
probable fix -
Key question, which input driver is used? evdev?
** Package changed: xserver-xorg-video-intel (Ubuntu) = xserver-xorg-
input-evdev (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1238914
*** This bug is a duplicate of bug 1223332 ***
https://bugs.launchpad.net/bugs/1223332
** This bug has been marked a duplicate of bug 1223332
[snb mesa blorp] False GPU lockup IPEHR: 0x7a02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Summary changed:
- Intel DRM crashes with the attached dmesg errors, warnings appear whilst
booting and performance is degraded as a result
+ [915g] hotplug storm, display manager continuously performs a forced
detection cycle
--
You received this bug notification because you are a member
The original cause seems to be bad RAM - there is a single invalid byte
inside an uncached memory region, which is most likely due to a physical
error not software.
** Package changed: xserver-xorg-video-intel (Ubuntu) = xorg-server
(Ubuntu)
--
You received this bug notification because you are
No, that is not a cache coherency bug. It is very likely it is just the
lack of synchronisation on the dma-buf between the two drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1228506
Title:
In the crash dump, the instruction that blows up has a single byte
incorrect. That is a constant written by the kernel into uncached memory
to be read by the GPU, so the write should be fine. That leaves either
it gets overwritten by something else or there was a physical defect.
Since I could
Hmm, it is still being reported by xrandr, so all hope is not lost.
Can you try xrandr --output LVDS1 --preferred and see what happens?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237677
Title:
** Summary changed:
- [arrandale] GPU lockup IPEHR: 0xacfbf37f
+ [arrandale] incoherent CS reads after vgaswitcheroo wakeup
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I thought this was going to be related to
commit b16999da214803a026d7246ec4aa62031e82dfc8
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Wed Oct 9 23:54:57 2013 +0100
sna: Upon unwinding operations, also check for exec objects to clear
If we cancel an operation after
So I think this is just the display configuration tool getting confused,
the driver looks fine.
Does anyone know its package name so we can reassign this to the right
devs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please explain crashes. The ddx looks fine, but you appear to have a
hotplug interrupt storm triggering a full load detection cycle - which
is caused by userspace.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hmm, I thought this was fixed in 2.99.903.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1236968
Title:
GPU
Afaict those logs do not correspond with the stacktrace - there's no
sign a crash there. The stacktrace that has been captured is incomplete,
but looks to be coming from the core xserver. I wonder if the retracing
service will enlighten us?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Not much we can do if apport isn't able to grab enough information for
us to even identify the problem. :(
There is a memory corruption fix upstream though.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a
I've found a source of memory corruption:
commit 06a8ad9690590a605b1564012d062b98c60546a6
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Mon Oct 7 23:21:38 2013 +0100
sna/trapezoids: Recompute num_threads to match range
We need to be careful not to execute threads past
This is a UXA bug.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/871972
Title:
8086:0116 [i915] Screen
*** This bug is a duplicate of bug 1223332 ***
https://bugs.launchpad.net/bugs/1223332
** This bug has been marked a duplicate of bug 1223332
[snb mesa blorp] False GPU lockup IPEHR: 0x7a02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
A drm.debug=6 dmesg from across the switch and back is an essential
first step.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Remove nomodeset from the kernel commandline and we can begin to debug
the issue. (Your video bios is incompatible with the VESA driver - i.e.
a broken bios, but you shouldn't be using that driver in the first
place.)
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
You received
** Summary changed:
- Xmir crashes on plugging in external
+ [xmir] Who freed my ScreenPixmap? Crash after resize
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1236353
Title:
[xmir] Who freed my
*** This bug is a duplicate of bug 1152165 ***
https://bugs.launchpad.net/bugs/1152165
** This bug has been marked a duplicate of bug 1152165
[ivb] GPU lockup IPEHR: 0x upon context restore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1232546 ***
https://bugs.launchpad.net/bugs/1232546
** This bug has been marked a duplicate of bug 1232546
[i915g] GPU hang accessing tiled subsurface
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157458
Title:
visual glitch in Evolution's importance button,
I reordered the gen5 flushing to hopefully prevent this bug, that patch
should now be available in an updated -intel.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Can you please retest with the latest stack, as I am sure we have fixed
this one already?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(In reply to comment #107)
(In reply to comment #106)
(In reply to comment #104)
I'm not sure my problem is related to this bug.
Most likely it isn't - gpu hang is similar to an application crashing.
Please file a new bug report and don't forget to attach the error state
file.
This will fix the crash, but really it is just the last step in a long
journey of fail.
** Patch added: 0001-glx-glxdri2-Unwrap-EnterVT-LeaveVT-upon-CloseScreen.patch
** Summary changed:
- [i965gm] GPU lockup IPEHR: 0x78080003 while running glmark2
+ [i965gm mesa] garbage in batch while running glmark2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235280
Title:
** Summary changed:
- GPU lockup IPEHR: 0x0b160001 IPEHR: 0x1301
+ [hsw] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x1301
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235293
Title:
[hsw] GPU
From the description I would say this is eerily similar to
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1234120
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1234839
Bold move!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235133
Title:
Please enable GLAMOR Support
To manage notifications about this bug go to:
This just sounds like regular LVDS fail - nothing specific to
suspendresume, just that is the easiest way to provoke the bug. My
presumption would be failed sanitizing after the BIOS messes up state.
Can you please grab intel_reg_dumper (from intel-gpu-tools) and run it
before and after sr?
**
*** This bug is a duplicate of bug 1223332 ***
https://bugs.launchpad.net/bugs/1223332
** This bug has been marked a duplicate of bug 1223332
[snb mesa blorp] False GPU lockup IPEHR: 0x7a02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
(In reply to comment #107)
(In reply to comment #106)
(In reply to comment #104)
I'm not sure my problem is related to this bug.
Most likely it isn't - gpu hang is similar to an application crashing.
Please file a new bug report and don't forget to attach the error state
file.
From a stability point-of-view, I will never recommend glamor.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235133
Title:
Please enable GLAMOR Support
To manage notifications about this bug go
For example, I can not see where the default GTF modes are inferred from
the EDID...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235201
Title:
saucy beta 2 could not apply the stored
I suspect one of the key commits is:
commit dc498b433f36af5d2de3065e7c64cdb575385d81
Author: Adam Jackson a...@redhat.com
Date: Mon Feb 8 15:23:04 2010 -0500
xfree86: If the driver found modes on an output, don't add more
Inferring modes from sync ranges is only valid if the
The mode you picked is not present in the EDID, but it is a standard GTF
mode, and you have a GTF monitor... I suspect that they used to be
added...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can you check whether doing
cat /etc/X11/xorg.conf.g/vga.conf EOF
Section Monitor
Identifier Monitor0
Option DefaultModes true
EndSection
Section Device
Identfier Device0
Option monitor-VGA1 Monitor0
EndSection
EOF
restores the missing modes?
--
You received this bug notification
Yikes, mistyped. That should have been /etc/X11/xorg.conf.d/vga.conf
If you grep Monitor0 /var/log/Xorg.*.log that should confirm whether or
not the config is picked up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Afaict, it should be now doing the right thing - it only paints into the
destination box provided by mir which should correspond to an individual
monitor.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are
Finally!
commit a048f436a0210d076fc844404bf56b8b7fcb4b7b
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Wed Oct 2 14:59:11 2013 +0100
sna: Only delete unused io buffers
Before deleting the io buffer, we need to check that it is not active.
Currently we check
I've made quite a few minor fixes, none of which ostensibly look like it
should fix this issue, but double checking with the current rc kernel
(3.12-rc2) and latest xf86-video-intel.git is a must.
Afterwards, you can try enabling (independently, and/or in combination)
#define DBG_NO_UPLOAD_CACHE
** Summary changed:
- Reading WEB pages from Chromium. No crash, just this message : False GPU
lockup IPEHR: 0x780c
+ (needs 2.99.903) [hswReading WEB pages from Chromium.
** Summary changed:
- (needs 2.99.903) [hswReading WEB pages from Chromium.
+ (needs 2.99.903) [hsw] Reading WEB
Can you please grab a screenshot of the artifact? We have many different
possible components that may be at fault here, I would also try
LIBGL_ALWAYS_SOFTWARE to rule out mesa/i965 as a first step.
** Summary changed:
- In i915 hiding unity launcher leaves artefacts
+ [ilk] hiding unity launcher
Absolutely sure it was Xv and not GL? Because it sounds very similar to
a GL video bug...
Anyway can you please grab a screenshot or photograph of the corruption?
** Package changed: xserver-xorg-video-intel (Ubuntu) = xserver-xorg-
video-intel-lts-quantal (Ubuntu)
--
You received this bug
Sounds like:
commit 3fd116782bb1c05a140f4783e92a8ee6a57143cd
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Mon Sep 23 21:03:07 2013 +0100
sna/dri: Clear the clear hint upon applying DRI damage
Otherwise a later call to GetImage will not notice the DRI update
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1216252
Title:
scrolling in chrome leads to distorted images
To
Hmm, could this also be:
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Wed Oct 2 14:59:11 2013 +0100
sna: Only delete unused io buffers
Before deleting the io buffer, we need to check that it is not active.
Currently we check that it is not pending use in the current
*** This bug is a duplicate of bug 1216252 ***
https://bugs.launchpad.net/bugs/1216252
** This bug has been marked a duplicate of bug 1216252
scrolling in chrome leads to distorted images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Summary changed:
- [i965gm] GPU lockup IPEHR: 0x79050003
+ [i965gm mesa] GPU lockup IPEHR: 0x79050003
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1234212
Title:
[i965gm mesa] GPU lockup
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1211027
Title:
Xorg crashed with SIGABRT in __GI_raise()
To manage
Blergh. Random memory corruption, all I can suggest here is to reproduce
with xorg-edgers, something a lot closer to the current upstream.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Judging by the indirect GLX, I suspect this is
https://bugs.freedesktop.org/show_bug.cgi?id=65030
** Bug watch added: freedesktop.org Bugzilla #65030
https://bugs.freedesktop.org/show_bug.cgi?id=65030
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Whether or not it is screenshottable would be of interest.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233734
Title:
[snb] exiting fullscreen html5 video on chromium leaves rest of screen
Any magic required? Flipping in and out of the new hobbit trailer works
for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233734
Title:
[snb] exiting fullscreen html5 video on chromium leaves
*** This bug is a duplicate of bug 1098334 ***
https://bugs.launchpad.net/bugs/1098334
** This bug has been marked a duplicate of bug 1098334
[gen4 sna] Font corruption in Chromium tab bar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
My first thought (ok, second after going, no, no please don't let this
be a driver bug) is perhaps http://lists.x.org/archives/xorg-
devel/2011-June/023218.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1223332 ***
https://bugs.launchpad.net/bugs/1223332
** This bug is no longer a duplicate of bug 1046998
[sandybridge-m-gt2+ mesa] False GPU lockup IPEHR: 0x79050005 IPEHR:
0x0b140001 (Gnome Shell)
** This bug has been marked a duplicate of bug 1223332
*** This bug is a duplicate of bug 1223332 ***
https://bugs.launchpad.net/bugs/1223332
** This bug is no longer a duplicate of bug 1046998
[sandybridge-m-gt2+ mesa] False GPU lockup IPEHR: 0x79050005 IPEHR:
0x0b140001 (Gnome Shell)
** This bug has been marked a duplicate of bug 1223332
*** This bug is a duplicate of bug 1223332 ***
https://bugs.launchpad.net/bugs/1223332
** This bug is no longer a duplicate of bug 1046998
[sandybridge-m-gt2+ mesa] False GPU lockup IPEHR: 0x79050005 IPEHR:
0x0b140001 (Gnome Shell)
** This bug has been marked a duplicate of bug 1223332
*** This bug is a duplicate of bug 1223332 ***
https://bugs.launchpad.net/bugs/1223332
** This bug has been marked a duplicate of bug 1223332
[snb mesa blorp] False GPU lockup IPEHR: 0x7a02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1223332 ***
https://bugs.launchpad.net/bugs/1223332
** This bug has been marked a duplicate of bug 1223332
[snb mesa blorp] False GPU lockup IPEHR: 0x7a02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1223332 ***
https://bugs.launchpad.net/bugs/1223332
** This bug has been marked a duplicate of bug 1223332
[snb mesa blorp] False GPU lockup IPEHR: 0x7a02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1223332 ***
https://bugs.launchpad.net/bugs/1223332
** This bug is no longer a duplicate of bug 1226178
[snb mesa] GPU lockup IPEHR: 0x79050005
** This bug has been marked a duplicate of bug 1223332
[snb mesa blorp] False GPU lockup IPEHR: 0x7a02
*** This bug is a duplicate of bug 1223332 ***
https://bugs.launchpad.net/bugs/1223332
** This bug has been marked a duplicate of bug 1223332
[snb mesa blorp] False GPU lockup IPEHR: 0x7a02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1223332 ***
https://bugs.launchpad.net/bugs/1223332
** This bug is no longer a duplicate of bug 1046998
[sandybridge-m-gt2+ mesa] False GPU lockup IPEHR: 0x79050005 IPEHR:
0x0b140001 (Gnome Shell)
** This bug has been marked a duplicate of bug 1223332
*** This bug is a duplicate of bug 1223332 ***
https://bugs.launchpad.net/bugs/1223332
** This bug is no longer a duplicate of bug 1226178
[snb mesa] GPU lockup IPEHR: 0x79050005
** This bug has been marked a duplicate of bug 1223332
[snb mesa blorp] False GPU lockup IPEHR: 0x7a02
The hang looks to be a bug in specifying the tiled subsurface on i915g
(the offset is probably not sufficiently well aligned). The corruption
in the background is just nautilus not redrawing the root window (since
3.8).
** Summary changed:
- [i915g] False GPU lockup IPEHR: 0x7d8e0001
+ [i915g]
commit 81d00c51018464929cdb3755adb334cb9a89d166
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Sun Sep 29 14:29:06 2013 +0100
sna: Apply the non-relaxed fencing partial paranoia everywhere
This is required to ensure that the tiled offsets are tile-row aligned
*** This bug is a duplicate of bug 1223332 ***
https://bugs.launchpad.net/bugs/1223332
** This bug has been marked a duplicate of bug 1223332
[snb mesa blorp] False GPU lockup IPEHR: 0x7a02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That's because that would be NOT the same bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround
i915.semaphores=0
To
*** This bug is a duplicate of bug 1224106 ***
https://bugs.launchpad.net/bugs/1224106
** This bug is no longer a duplicate of bug 1217364
[xmir] Xorg crashed with SIGABRT in damage()
** This bug has been marked a duplicate of bug 1224106
[needs 2.21.15] Xorg crashed with SIGABRT in
*** This bug is a duplicate of bug 1224106 ***
https://bugs.launchpad.net/bugs/1224106
** This bug has been marked a duplicate of bug 1224106
[needs 2.21.15] Xorg crashed with SIGABRT in DRI2SwapBuffers()
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1224106 ***
https://bugs.launchpad.net/bugs/1224106
** This bug is no longer a duplicate of bug 1217364
[xmir] Xorg crashed with SIGABRT in damage()
** This bug has been marked a duplicate of bug 1224106
[needs 2.21.15] Xorg crashed with SIGABRT in
*** This bug is a duplicate of bug 1224106 ***
https://bugs.launchpad.net/bugs/1224106
** This bug is no longer a duplicate of bug 1217364
[xmir] Xorg crashed with SIGABRT in damage()
** This bug has been marked a duplicate of bug 1224106
[needs 2.21.15] Xorg crashed with SIGABRT in
601 - 700 of 4302 matches
Mail list logo
