** Changed in: xserver-xorg-video-intel
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/354688
Title:
crash in drm_intel_gem_bo_start_gtt_access
--
ubuntu-bugs
** Changed in: xserver-xorg-video-intel
Importance: Medium = Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/354688
Title:
crash in drm_intel_gem_bo_start_gtt_access
--
ubuntu-bugs
Changing back to confirmed, there is not yet a fix (bug still occurs in a new
install) there is a workaround as mentioned in
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/354688/comments/16
** Changed in: xserver-xorg-video-intel (Ubuntu Jaunty)
Status: Fix
The crash bug *is* fixed. Other issues should be filed as separate
reports (if they aren't already).
** Changed in: xserver-xorg-video-intel (Ubuntu Jaunty)
Status: Confirmed = Fix Released
--
crash in drm_intel_gem_bo_start_gtt_access
https://bugs.launchpad.net/bugs/354688
You received
new bug for video playback failure in Jaunty:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/371275
--
crash in drm_intel_gem_bo_start_gtt_access
https://bugs.launchpad.net/bugs/354688
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I just installed this update:
replacing: xserver-xorg-video-intel 2:2.6.3-0ubuntu9 (with
.../xserver-xorg-video-intel_2%3a2.6.3-0ubuntu9.1_amd64.deb
It does NOT solve this bug, though I'am not sure it should but at least you now
it is still there in the xserver-xorg-video-intel_2%3a2.6.3-0
I confirm João's comment above. With the official jaunty release
2.6.3-0ubuntu9, video players crash when directed to use xv. Telling
gstreamer not to use xv works around it.
In my case, video in vlc/mplayer/totem works fine initially, but if one
forces a repaint of the screen, X will crash.
** Changed in: xserver-xorg-video-intel
Status: Confirmed = Fix Released
--
crash in drm_intel_gem_bo_start_gtt_access
https://bugs.launchpad.net/bugs/354688
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I also can't play any video format at any video player (totem, kaffeine,
mplayer, vlc, miro...). The outputs are the same presented by IcedEarth.
Workaround to get it working: open gstreamer-properties. Then, Video
tab, Default Output section. Change the Plugin from Autodetect to X
Window System
in the server kernel we still have this problem but with generic and rt
kernel it works fine here i have attached my lspci and other stuff
anyway for me now there is not this problem anymore
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/356088
--
crash in
Me too, as in regard to Bug #351869. I have updated to the new xserver-
xorg-video-intel this morning, (2:2.6.3-0ubuntu8) still unable to play
video in VLC, totem etc.
Totem:
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was
The issue I reported in bug 353023 is still not quite fixed. I don't get
any crashes anymore, but I still can't play video, neither in mplayer
nor in totem. Should I file a new bug about that?
I'm attaching my new Xorg.0.log file.
** Attachment added: Xorg.0.log (with 2:2.6.3-0ubuntu7)
Hi Steve, actually what I meant was I needed a full backtrace, like what
Albert attached, sorry I wasn't more specific... been a long week.
Albert, thanks muchly for the analysis and patch. It looks good and
I'll upload it tomorrow. Meanwhile please do see if you can get
upstream's comment on
** Changed in: xserver-xorg-video-intel (Ubuntu Jaunty)
Assignee: (unassigned) = Canonical Desktop Team (canonical-desktop-team)
--
crash in drm_intel_gem_bo_start_gtt_access
https://bugs.launchpad.net/bugs/354688
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug was fixed in the package xserver-xorg-video-intel -
2:2.6.3-0ubuntu7
---
xserver-xorg-video-intel (2:2.6.3-0ubuntu7) jaunty; urgency=low
* Add 119_drm_bo_unreference_needs_null.patch:
- The first time through the Xv code, an allocated buffer is
unreferenced but
** Changed in: xserver-xorg-video-intel
Status: Unknown = Confirmed
--
crash in drm_intel_gem_bo_start_gtt_access
https://bugs.launchpad.net/bugs/354688
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Nice to see this one fixed.
** Changed in: xserver-xorg-video-intel (Ubuntu Jaunty)
Assignee: Canonical Desktop Team (canonical-desktop-team) = Bryce
Harrington (bryceharrington)
--
crash in drm_intel_gem_bo_start_gtt_access
https://bugs.launchpad.net/bugs/354688
You received this bug
I was able to reproduce this on my 945 and got a full backtrace.
** Attachment added: totem-crash.txt
http://launchpadlibrarian.net/24835744/totem-crash.txt
--
crash in drm_intel_gem_bo_start_gtt_access
https://bugs.launchpad.net/bugs/354688
You received this bug notification because you are
The problem is in xxv-intel, src/i830_video.c
In I830PutImage:
if (pPriv-buf == NULL) {
pPriv-buf = drm_intel_bo_alloc(pI830-bufmgr,
xv buffer, alloc_size, 4096);
if (pPriv-buf == NULL)
return BadAlloc;
if
** Bug watch added: freedesktop.org Bugzilla #21060
https://bugs.freedesktop.org/show_bug.cgi?id=21060
** Also affects: xserver-xorg-video-intel via
https://bugs.freedesktop.org/show_bug.cgi?id=21060
Importance: Unknown
Status: Unknown
--
crash in
A backtrace from gdb looks the same as the backtrace included in the bug
description. Is there more specific information that you're looking
for?
I had a closer look at the disassembly, the segfault is actually in the
line
ret = ioctl(bufmgr_gem-fd, DRM_IOCTL_I915_GEM_SET_DOMAIN,
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/24765054/Dependencies.txt
** Attachment added: LsHal.txt
http://launchpadlibrarian.net/24765055/LsHal.txt
** Attachment added: LsMod.txt
http://launchpadlibrarian.net/24765057/LsMod.txt
** Attachment added: LsPci.txt
Readily reproducible for me here, so if more info is needed, let me
know.
The crash appears (based on a disassembly of the function with gdb -
nothing so proper as catching a crash in action) to be happening at the
line
set_domain.handle = bo_gem-gem_handle;
when dereferencing bo_gem.
**
** Changed in: xorg (Ubuntu)
Importance: Undecided = High
** Changed in: xorg (Ubuntu)
Status: New = Confirmed
** Also affects: xorg (Ubuntu Jaunty)
Importance: High
Status: Confirmed
--
crash in drm_intel_gem_bo_start_gtt_access
https://bugs.launchpad.net/bugs/354688
You
Please have a look at that bug:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/354735
Maybe is the same one?
--
crash in drm_intel_gem_bo_start_gtt_access
https://bugs.launchpad.net/bugs/354688
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
No, these bugs don't appear to have any relation to one another.
--
crash in drm_intel_gem_bo_start_gtt_access
https://bugs.launchpad.net/bugs/354688
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Have twiddled a few knobs, and:
(EE) intel(0): Cannot support DRI with frame buffer width 2048.
this message in Xorg.0.log appears to be key. If I lower the virtual
res in xorg.conf, I don't get the crash. If I subsequently set NoAccel,
I still don't get the crash. It's only when I have my
Steve, thanks for chasing it down in gdb, but could you also put a trace
onto this bug report?
Heh, of course as fate would have it, there's three exact instances of
that line. Smells like a nullptr deref but a full backtrace would help
in sorting it out.
--
crash in
28 matches
Mail list logo
