Apparantly the wrong version of the patch went into 3.4-rc5, so there is a
follow up patch now:
drm/i915: Do no set Stencil Cache eviction LRA w/a on gen7+.
See http://lists.freedesktop.org/archives/intel-gfx/2012-May/017391.html
--
You received this bug notification because you are a member
This bug has been fixed in xserver upstream:
commit af88b43f9e604157b74270d609c08bdfa256a792
Author: Peter Hutterer peter.hutte...@who-t.net
Date: Fri Apr 27 16:31:17 2012 +1000
dix: don't emulate scroll events for non-existing axes (#47281)
No, you cannot use the -intel package from 11.10, because it is build
for an older xserver version.
Xorg log says:
[ 1010.456] BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes 2)'
That suggests this is a duplicate of bug 921236. There success is
reported by downgrading
A patch was submitted to intel-gfx yesterday: [Intel-gfx] [PATCH v2] drm/i915:
Set the Stencil Cache eviction policy to non-LRA mode.. I have tested this
patch on top of the precise kernel 3.2.0-24-generic. Googleearth no longer
freezes when zooming in.
The patch is currently on it's way to
0x0f14d268: 0x60020100: CONSTANT_BUFFER: valid
0x0f14d26c: 0x0f133587:offset: 0x0f133580, length: 512 bytes
0x0f14d270: HEAD 0x7b001804: 3DPRIMITIVE: tri fan sequential
This is almost certain
https://bugs.freedesktop.org/show_bug.cgi?id=38771, fixed in mesa git
master and 7.11
*** This bug is a duplicate of bug 774978 ***
https://bugs.launchpad.net/bugs/774978
[ 5758.687] 4: /usr/bin/X (_CallCallbacks+0x34) [0x432af4]
[ 5758.687] 5: /usr/bin/X (WriteToClient+0x21a) [0x461cca]
[ 5758.687] 6: /usr/lib/xorg/modules/extensions/libdri2.so
(ProcDRI2WaitMSCReply+0x52)
*** This bug is a duplicate of bug 774978 ***
https://bugs.launchpad.net/bugs/774978
[370186.294] 3: /usr/bin/X (_CallCallbacks+0x3e) [0x8074e1e]
[370186.294] 4: /usr/bin/X (WriteToClient+0x267) [0x80a7607]
[370186.294] 5: /usr/lib/xorg/modules/extensions/libdri2.so
*** This bug is a duplicate of bug 774978 ***
https://bugs.launchpad.net/bugs/774978
[47.040] 4: /usr/bin/X (_CallCallbacks+0x34) [0x432af4]
[47.040] 5: /usr/bin/X (WriteToClient+0x21a) [0x461c9a]
[47.040] 6: /usr/lib/xorg/modules/extensions/libdri2.so
(ProcDRI2WaitMSCReply+0x52)
*** This bug is a duplicate of bug 774978 ***
https://bugs.launchpad.net/bugs/774978
[ 8481.477] 3: /usr/bin/X (_CallCallbacks+0x3e) [0x8074e1e]
[ 8481.477] 4: /usr/bin/X (WriteToClient+0x267) [0x80a7607]
[ 8481.477] 5: /usr/lib/xorg/modules/extensions/libdri2.so
Marcelo, the record extension will still be loaded indeed. However, without
synaptics the extension is not activated.
You can check this by attaching gdb to Xorg (from a second pc) and setting a
breakpoint on RecordAReply. If the breakpoint is hit, record is active.
With synaptics installed (on
I have tracked down the crash a bit further, by adding debug prints when
input buffers are freed.
[ 18735.941] REQUEST: ClientIDX: 6, type: 0x89 data: 0xa len: 8 buffer:
0x7fba90fa8010 name: DRI2
[ 18735.943] Add buffer to FreeInputs, aci: 0x2e7d8c0 buffer: 0x7fba90fa8010
[ 18735.943] REQUEST:
*** This bug is a duplicate of bug 774978 ***
https://bugs.launchpad.net/bugs/774978
** Tags removed: patch
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/776749
Title:
I have tried running X under strace, but no success. I couldn't
reproduce the crash, probably because X became too slow. Log file when
calibre was running was 5 GB.
I also tried xtrace and valgrind without luck. xtrace only showed what
calibre was doing. Valgrind shows errors, but only before and
** Attachment added: stacktrace
https://bugs.launchpad.net/bugs/776749/+attachment/2110611/+files/calibre_X.stacktrace
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/776749
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Xserver frequently crashes when I start calibre and switch between different
ebooks in the ebook list.
This crash is quite reproducible, about 80% of the times I run calibre. The
crash happens both in unity and in classic
I noticed the refcount patch was applied in natty and can confirm
logging out has been working fine in natty for the past couple of weeks.
xorg-server (2:1.9.99.902-2ubuntu1) natty; urgency=low
...
* 215_glx_drawable_refcounting.diff:
- Refcount GLXDrawables to avoid use-after-free crashes.
A patch was posted by Chris Wilson today on the dri-devel mailing list
that fixes this crash for me:
glx: Refcnt the GLXDrawable to avoid use after free with multiple
FreeResource
Although there may be more than one resource handles pointing to the
Drawable, we only want to
I have been trying to debug this and think I found the problem:
- The crash is caused when an already freed drawable is used (drawable contents
are invalid)
- The crashing resource always has xid=0. If I prevent DrawableGone calls when
xid=0, the crash does not happen. XID=0 seems strange, as
CurrentDmesg shows:
[12436.390414] Out of memory: kill process 29463 (mutter) score 157749 or a
child
[12436.390430] Killed process 29463 (mutter) vsz:630996kB, anon-rss:13324kB,
file-rss:16868kB
So mutter was killed because you ran out of memory. It looks like mutter is
using a lot of RAM.
As you are using an intel 945 and the bug happens when you have an
extended desktop with width 2048 and there is the error message (EE)
intel(0): Failed to allocate framebuffer. this seems to be freedesktop
bug 28515 (libdrm) which is fixed in:
commit 726210f87d558d558022f35bc8c839e798a19f0c
Disassembling dixFreePrivates in gdb shows the crash is happening in:
if (items[i].size)
xfree(privates[i].value);
Also, Kubuntu resets/regenerates the Xserver on log-out, where Gnome starts a
new server on log-out.
The regeneration bit in the git commit
The xorg logs for both Manolo and Ride show you are using the old Jaunty kernel
(2.6.28) and drm is not properly working. Please make sure you boot with the
new Karmic kernel (2.6.31) and see if that solves the problem.
If the karmic kernel still has this problem, please attach xorg.0.log and
Log message:
Fatal server error:
Cannot run in framebuffer mode. Please specify busIDsfor all
framebuffer devices
is the same we have seen in Karmic in bug 383407. It was fixed in the
xserver:
xorg-server (2:1.6.1.901-2ubuntu2) karmic; urgency=low
* Add
This was most likely the same problem as bug 454029, which was fixed
with:
xserver-xorg-video-intel (2:2.9.0-1ubuntu2~xup~3) jaunty; urgency=low
* Reinstate 01_gen_pci_ids.diff for jaunty xserver (LP: #454029)
and ship the pci ids file
** Changed in: xserver-xorg-video-intel (Ubuntu)
The screenshot looks like the screenshot in
http://bugs.freedesktop.org/show_bug.cgi?id=24315 comment 2.
Robert, if you can confirm the upstream screenshots match what you are seeing,
it may be worth to add a tracker.
** Bug watch added: freedesktop.org Bugzilla #24315
*** This bug is a duplicate of bug 454029 ***
https://bugs.launchpad.net/bugs/454029
Fredrik: this issue was fixed today. If you install the latest version of the
intel driver, you should be fine again.
(xserver-xorg-video-intel 2:2.9.0-1ubuntu2~xup~3). See also bug 454029
** This bug has
*** This bug is a duplicate of bug 454029 ***
https://bugs.launchpad.net/bugs/454029
** This bug has been marked a duplicate of bug 454029
screen resolution messed up; no longer recognizes monitor type
--
Unknown display, resolution shoud be 1024*600 but only 800*600 allowed. (EEE PC
*** This bug is a duplicate of bug 454029 ***
https://bugs.launchpad.net/bugs/454029
** This bug has been marked a duplicate of bug 454029
screen resolution messed up; no longer recognizes monitor type
--
xserver-xorg-video-intel version 2.9.0 for jaunty in PPA broken on eeepc
From Xorg.0.log:
(II) Scanning /usr/share/xserver-xorg/pci directory for additional PCI ID's
supported by the drivers
(II) No matches found for this device in /usr/share/xserver-xorg/pci
The update is missing the list of pci ids for intel. Xserver 1.6.3 in jaunty
still needs those pci ids.
Erik, you are using an old kernel, which had problems to load drm correctly (as
shown in XorgLogOld.txt).
Can you please install the latest kernel (2.6.31-14-generic) and test if you
can still reproduce the problem?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New =
Thanks for confirming, Jeremy. I will close the bug then.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = Fix Released
--
[GM45] X Crashes Every Time I Close Zsnes
https://bugs.launchpad.net/bugs/433310
You received this bug notification because you are a member of
Closing the bug, as the problem was solved by a reinstall for both John
and Kieran.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed = Fix Released
--
[i965GM] Desktop effects could not be enabled
https://bugs.launchpad.net/bugs/410258
You received this bug notification
The partial stacktrace in Xorg log shows 3:
/usr/lib/dri/i965_dri.so(intelDestroyContext+0x10a)
A crash in intelDestroyContext on GM965 was recently fixed in mesa
(7.6.0~git20090817.7c422387-0ubuntu7) and now in mesa 7.6.0
Jeremy, could you please test if you still have this problem?
--
[GM45]
It seems you are all using the intel driver from the xorg-edgers ppa.
In this driver support for user mode setting has been dropped. This
means you now have to use a kernel with modesetting (KMS) enabled. The
easiest way to do this is to install the kernel from the same ppa and
reboot using that
The agp issue of bug 430694 was fixed in linux 2.6.31-12.41. David's logs show
he was using an older kernel.
David, could you please test with the latest kernel and see if that solves the
problem?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Incomplete
--
[i945] 945
Moving to xserver-xorg-video-ati based on info from log files.
** Package changed: xserver-xorg-video-vesa (Ubuntu) = xserver-xorg-
video-ati (Ubuntu)
--
Xserver crash: Logout when Firefox or Empathy is in action
https://bugs.launchpad.net/bugs/446648
You received this bug notification because
Francis: you have got the new xserver-xorg-video-intel package
(2.9.0-1ubuntu1) from karmic, which was uploaded just before you added
the ppa. So the fix is already in Karmic and there is no need anymore to
upload any logs. Therefore I will close this bug.
Most likely this fix solved your mouse
** Bug watch added: freedesktop.org Bugzilla #24383
https://bugs.freedesktop.org/show_bug.cgi?id=24383
** Also affects: xserver-xorg-video-intel via
https://bugs.freedesktop.org/show_bug.cgi?id=24383
Importance: Unknown
Status: Unknown
--
kdm does not restart X server (that
The kernel fix referred to above is now available in Karmic:
linux (2.6.31-12.39) karmic;
* agp/intel: Fix the pre-9xx chipset flush.
Please update your kernel to linux-image-2.6.31-12-generic and test.
There are already several confirmations this new kernel solves the
issue.
--
[i865] karmic:
Testing shows this problem only occurs with KMS active.
Debugging with gdb shows we get a new frontbuffer when we logout and the
xserver is reset. However, the new frontbuffer is not connected to the crtc .
in drmmode_set_mode_major we have:
if (drmmode-fb_id == 0) {
ret
This bug has been fixed upstream. The commit is included in mesa 7.6
branch.
commit 2921a2555d0a76fa649b23c31e3264bbc78b2ff5
Author: Ian Romanick ian.d.roman...@intel.com
Date: Wed Sep 16 07:39:58 2009 -0700
intel: Deassociated drawables from private context struct in
intelUnbindContext
If
Closing the -intel task, as the bug was fixed in mesa:
mesa (7.6.0~git20090817.7c422387-0ubuntu4) karmic; urgency=low
* Add 109_fix_relocation_delta_for_wm_surfaces.patch: Fix relocation
delta for WM surfaces. This was a regression introduced in
0f328c90dbc893e15005f2ab441d309c1c176245
This bug has been fixed upstream. The commit is included in mesa 7.6
branch.
commit 2921a2555d0a76fa649b23c31e3264bbc78b2ff5
Author: Ian Romanick ian.d.roman...@intel.com
Date: Wed Sep 16 07:39:58 2009 -0700
intel: Deassociated drawables from private context struct in
intelUnbindContext
mesa commit i965: Fix relocation delta for WM surfaces (5604b27b93),
solves the same (or at least similar) issue for me on Intel GM965. It
was the error kernel: [ 184.761959] PGTBL_ER: 0x0080 in syslog
that pointed me to that commit. Both the missing window borders and the
freeze are fixed
The most easy way to get logout/login working on intel in Kubuntu is to
set TerminateServer=true in kdmrc.
--- /etc/kde4/kdm/kdmrc.orig2009-09-17 00:06:11.209433377 +0200
+++ /etc/kde4/kdm/kdmrc 2009-09-17 00:02:03.920288377 +0200
@@ -493,7 +493,7 @@
# Restart instead of resetting the local
This issue was discussed on intel-gfx recently. The ringbuffer wraps
around in the middle of an instruction:
0x0001fff8: 0x1081: MI_STORE_DATA_INDEX
0x0001fffc: 0x0080:dword 1
Buffer size too small in MI_STORE_DATA_INDEX (2 3)
A fix has been committed in Eric Anholt's
Public bug reported:
This bug was originally reported upstream as
https://bugs.freedesktop.org/show_bug.cgi?id=22946
The upstream report was made running mesa, libdrm, xserver and -intel
from git. Now that mesa 7.6-devel arrived in Karmic, the same crash
happens in a pure Karmic installation
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/30978260/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/30978261/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/30978262/Dependencies.txt
**
The stacktrace on Karmic
** Attachment added: mesa_stacktrace.txt
http://launchpadlibrarian.net/30978301/mesa_stacktrace.txt
** Bug watch added: freedesktop.org Bugzilla #22946
https://bugs.freedesktop.org/show_bug.cgi?id=22946
** Also affects: mesa via
Those lines in xsession-errors confirm compiz sets LIBGL_ALWAYS_INDIRECT:
Checking for texture_from_pixmap: not present.
Trying again with indirect rendering:
Checking for texture_from_pixmap: present.
However, your X log shows texture_from_pixmap is supported by the driver:
(II) AIGLX: enabled
Hi George,
to debug this issue, we need a bit more information:
- please attach the file .xsession-errors (from your home directory)
- please run the command glxinfo glxinfo.txt and attach the file glxinfo.txt
Most likely LIBGL_ALWAYS_INDIRECT is set by compiz. Can you disable compiz and
let
In Karmic you are using KMS. With KMS the names of the outputs have changed.
VGA is now VGA1 and LVDS is now LVDS1.
These are the output names you have to use in xrandr commands.
So, most likely, xrandr --output VGA1 --right-of LVDS1 --auto will do something
now.
Please let us know if that
ACL handling has moved again, now from udev-extras into udev (in 143-1).
As xserver-xorg already recommends udev, this issue should be fixed now.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed = Fix Released
--
[i945gme] Xorg very slow after upgrade
Great! I will close the bug then.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = Fix Released
--
X server restarts when playing video, visualization
https://bugs.launchpad.net/bugs/368159
You received this bug notification because you are a member of Ubuntu-X,
Your Xorg log shows i915_dri.so is properly loaded and drm was opened.
Yet glxinfo shows you get software rendering. That looks like a
permission problem with /dev/dri/card0. Permissions are handled via ACL
and the ACL should be set by udev in Karmic. However, your udev log does
not show any ACL
freedesktop 22189 was marked duplicate of 21322. Updated the bug watch.
** Bug watch added: freedesktop.org Bugzilla #21322
https://bugs.freedesktop.org/show_bug.cgi?id=21322
** Changed in: xserver-xorg-video-intel
Status: Invalid = Unknown
** Changed in: xserver-xorg-video-intel
ProcVersion: Linux version 2.6.24-19-server
You are using a hardy server kernel, which does not have GEM.
Can you please install the jaunty generic kernel (2.6.28-11-generic) and boot
and test with that kernel?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed =
You are using the server kernel, which uses PAE. GEM is not compatible with PAE
and is therefore disabled.
That means you get the fake bufmgr, which is too small to handle video
correctly (fake bufmgr (1024 kB)).
Unfortunately, allocating more memory for the fake bufmgr was tried during
jaunty
*** This bug is a duplicate of bug 363821 ***
https://bugs.launchpad.net/bugs/363821
Blacklisted PCIID '8086:2a02' found
Compiz was disabled for GM965 in jaunty because of a major freeze bug. This is
not related to UXA.
See bug 363821 for the current status and suggestion how you can enable
You are using the intrepid kernel (2.6.27-11-generic x86_64), which does not
have GEM.
To play video in jaunty, you do need to use a gem enabled kernel.
Can you please test with the jaunty kernel (2.6.28-11-generic) and let us know
if that works?
** Changed in: xserver-xorg-video-intel (Ubuntu)
From Xorg log:
Current Operating System: Linux richardwolf 2.6.30-7-server #8-Ubuntu SMP Mon
May 25 15:03:02 UTC 2009 i686
That kernel is built with CONFIG_HIGHMEM64G=y and CONFIG_X86_PAE=y. Therefore
GEM is disabled.
Can you please test with the 2.6.30-7-generic kernel and see if that works?
Should be fixed by commit Fix segfault in DRI2 vblank syncing if the
region isn't onscreen, which handles the crtc=0x0 case.
** Package changed: xorg (Ubuntu) = xserver-xorg-video-intel (Ubuntu)
--
x server dies with a SIGSEGV when gnome screen saver blanks the display
The message (WW) intel(0): Failed to open DRM device in your X log suggests
kernel module i915 is not properly loaded.
Can you boot with kernel 2.6.30 and run the commands:
- lsmod lsmod.txt
- lshal lshal.txt
and attach the two files to this bug report?
Also, assuming i915 is indeed not
You could boot into 2.6.28, then install the set of packages you had when you
first filed this bug. After that, reboot in 2.6.30
Alternatively, you could try to set modeset=0 in /etc/modules and see if that
allows to start X with 2.6.30.
--
[945G/GZ] no direct rendering after upgrade to
*** This bug is a duplicate of bug 379504 ***
https://bugs.launchpad.net/bugs/379504
The cause of the problem is already known, see bug 379504
** This bug has been marked a duplicate of bug 379504
Xorg falls back to VESA on intel hardware
--
[i965GM] Karmic -intel 2.7.1-1ubuntu1: Xorg
Now the question is: Is something writing or reading beyond the end of
the exa offscreen buffer? Without the 32 MB unused memory after the exa
offscreen buffer, that would be beyond end of aperture. How can I find
what is doing that?
For further testing, I enabled DEBUG_MIGRATE in the xserver
Thanks for the confirmation lshardytest.
Marking fix committed as the fixed kernel is currently available in
jaunty-proposed.
** Package changed: xserver-xorg-video-intel (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Committed
--
[g41] UXA - Test =
67 matches
Mail list logo
