Still persists on 12.04
--
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/702090
Title:
i965gm GPU lockup if vesafb is left loaded (EIR: 0x0010 PGTBL_ER:
0x0100) -
[3.317473] [drm] capturing error event; look for more information in
/debug/dri/0/i915_error_state
[3.318779] render error detected, EIR: 0x0010
[3.318783] IPEIR: 0x
[3.318785] IPEHR: 0x
[3.318788] INSTDONE: 0xfffe
[3.318790] INSTPS:
I am still having issues with X crashing (especially when am on a skype
video call or watching video with vlc) I reported a bug report here
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/769977 haven't gotten any reply there yet. maybe its
associated with the bug ported
Ubeer, probably easiest if you file a new bug. Either use apport if it
pops up a dialog, or manually collect the gpu dump and i915 errors file.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
I still have crashes with the latest packages. Here is the output of the
dmesg commands:
dmesg | grep 'Linux version'
Linux version 2.6.38-7-generic (buildd@rothera) (gcc version 4.5.2
(Ubuntu/Linaro 4.5.2-6ubuntu4) ) #37-Ubuntu SMP Mon Mar 21 14:19:35 UTC 2011
(Ubuntu 2.6.38-7.37-generic
** Changed in: xserver-xorg-video-intel
Status: Confirmed = Fix Released
--
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/702090
Title:
i965gm GPU lockup if vesafb is
On Tue, Mar 15, 2011 at 3:40 PM, Bryce Harrington 702...@bugs.launchpad.net
wrote:
Has anyone tried testing apw's PPA (ppa:apw/purple)?
I don't know if we can put the fix into Ubuntu until someone tests it
and confirms it does fix the issue.
We've not been able to reproduce this bug
hello sir i have uninstall ubuntu 11.04 from my laptop because i was new
user of linux OS if you say then i can try again in a part of my laptop's
HD for bug fixing .
On Sat, Mar 19, 2011 at 4:45 PM, Colin Watson
cjwat...@canonical.comwrote:
I believe this is fixed in the latest linux upload
bug 715093 has bad patch - see comment #10 on bug 715093
--
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/702090
Title:
i965gm GPU lockup if vesafb is left loaded (EIR:
I believe this is fixed in the latest linux upload (the relevant change
was to make vesafb modular again):
linux (2.6.38-7.36) natty; urgency=low
[ Andy Whitcroft ]
* Revert SAUCE: KLUDGE: work around failed 'shrink-wrap' compiler
optimisation
* purge last vestiges of maverick
*
** Branch linked: lp:~apw/plymouth/fallback-framebuffer
** Branch linked: lp:~apw/module-init-tools/fallback-framebuffer
** Branch linked: lp:~apw/udev/fallback-framebuffer
** Branch linked: lp:~apw/gdm/fallback-framebuffer
--
You received this bug notification because you are a member of
** Branch linked: lp:~apw/module-init-tools/fallback-framebuffer-release
--
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/702090
Title:
i965gm GPU lockup if vesafb is left
This bug was fixed in the package udev - 166-0ubuntu4
---
udev (166-0ubuntu4) natty; urgency=low
[ Scott Moser ]
* do not create persistent net rules for Eucalyuptus addresses (LP: #719418)
[ Andy Whitcroft ]
* debian/udev.udev-fallback-graphics.upstart: add a new fallback
This bug was fixed in the package module-init-tools - 3.12-1ubuntu4
---
module-init-tools (3.12-1ubuntu4) natty; urgency=low
* debian/modprobe.d/blacklist-framebuffer.conf: re-enable vesafb so that
we can load it as a fallback. (LP: #702090)
-- Andy Whitcroft
This bug was fixed in the package plymouth - 0.8.2-2ubuntu18
---
plymouth (0.8.2-2ubuntu18) natty; urgency=low
[ Colin Watson ]
* Split nouveau patches out from misc-changes.patch.
* If plymouth:force-drm is found on the kernel command line, use the drm
renderer even on
Opening a bug task on kdebase-workspace: udevtrigger needs to be
replaced with udev-fallback-graphics in kdm.upstart, as was done in gdm.
** Also affects: kdebase-workspace (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
This bug was fixed in the package gdm - 2.32.0-0ubuntu12
---
gdm (2.32.0-0ubuntu12) natty; urgency=low
* Make splash dependant on either a graphics device appearing or
udev-graphics-fallback completing. (LP: #702090)
-- Andy Whitcroft a...@canonical.com Fri, 18 Mar 2011
** Branch linked: lp:ubuntu/gdm
--
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/702090
Title:
i965gm GPU lockup if vesafb is left loaded (EIR: 0x0010 PGTBL_ER:
** Changed in: kdebase-workspace (Ubuntu Natty)
Status: New = In Progress
** Changed in: kdebase-workspace (Ubuntu Natty)
Assignee: (unassigned) = Scott Kitterman (kitterman)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
This bug was fixed in the package kdebase-workspace - 4:4.6.1-0ubuntu2
---
kdebase-workspace (4:4.6.1-0ubuntu2) natty; urgency=low
[ Felix Geyer ]
* Emit upstart login-session-start and desktop-session-start events.
(LP: #715093)
- Add
[Closing X task now that the fix is rolled out to the various
components]
** Changed in: xserver-xorg-video-intel (Ubuntu Natty)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel
@Bryce:
had followed your indications in comment #73, no more error in kernel logs and
apport stopped complaining about crashes.
Thanks!
@Lokinhincens:
There is a new bug in gdm that prevent it from showing up, I have it too:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/735805
--
You
[Even though this isn't an -intel bug, I'm leaving the task open and
setting it to In Progress just for triaging purposes since the auto-
generated bugs get filed against -intel. It can be closed once the fix
begins getting deployed to the various packages.]
** Also affects: plymouth (Ubuntu)
On Tue, Mar 15, 2011 at 3:40 PM, Bryce Harrington 702...@bugs.launchpad.net
wrote:
Has anyone tried testing apw's PPA (ppa:apw/purple)?
I don't know if we can put the fix into Ubuntu until someone tests it
and confirms it does fix the issue.
We've not been able to reproduce this bug
Has anyone tried testing apw's PPA (ppa:apw/purple)?
I don't know if we can put the fix into Ubuntu until someone tests it
and confirms it does fix the issue.
We've not been able to reproduce this bug synthetically ourselves, so we
really do need help from a subscriber of this bug report to test
Tank you so much, I check that, cheers
2011/3/15 Bob Murphy 702...@bugs.launchpad.net
On Tue, Mar 15, 2011 at 3:40 PM, Bryce Harrington
702...@bugs.launchpad.net
wrote:
Has anyone tried testing apw's PPA (ppa:apw/purple)?
I don't know if we can put the fix into Ubuntu until someone
On Tue, Mar 15, 2011 at 08:00:42PM -, Bob Murphy wrote:
On Tue, Mar 15, 2011 at 3:40 PM, Bryce Harrington 702...@bugs.launchpad.net
wrote:
Has anyone tried testing apw's PPA (ppa:apw/purple)?
I don't know if we can put the fix into Ubuntu until someone tests it
and confirms it
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
--
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/702090
Title:
i965gm GPU lockup if vesafb is left
Hello Travis and everyone reporting dupes!
A possible fix for this bug has been created and is available for
testing. Please follow these steps to test:
A. Verify you still have the bug. Run this command:
$ dmesg | egrep drm.*ERROR
This should display something like this:
[
** Changed in: linux (Ubuntu Natty)
Status: New = Triaged
--
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/702090
Title:
i965gm GPU lockup if vesafb is left loaded
Too late for a3, moving to beta-1
** Changed in: linux (Ubuntu Natty)
Milestone: natty-alpha-3 = ubuntu-11.04-beta-1
--
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/702090
How do you disable it?
On Sat, Feb 26, 2011 at 6:48 PM, Mike Austin
702...@bugs.launchpad.netwrote:
Disabling vesafb makes this problem go away.
Yes, this fixes it for me on my Sony VAIO Z i5, which has both the Intel
gpu and a nvidia 330M.
--
You received this bug notification because you
Disabling vesafb makes this problem go away.
Yes, this fixes it for me on my Sony VAIO Z i5, which has both the Intel gpu
and a nvidia 330M.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
Is anyone able to reproduce this bug reliably? If so, please test this
kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/
This includes the following patch which sounds like it addresses the problem
(it's a false positive gpu hang check):
Nope, new kernel didn't help; it actually made things worse. I've
attached my dmesg showing the BUG message. When booting I end up seeing
the text output from the boot process with a mouse cursor on top of it.
If it switch to another VT then back to VT 7 everything paints
correctly.
** Changed
** Attachment added: dmesg.log
https://bugs.launchpad.net/ubuntu/natty/+source/linux/+bug/702090/+attachment/1866776/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
** Changed in: linux (Ubuntu Natty)
Importance: High = Critical
** Changed in: linux (Ubuntu Natty)
Milestone: None = natty-alpha-3
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
Clean up the priority of the kernel side bug to reflect the status
already assigned. Explicitly assign this to the kernel team.
** Changed in: linux (Ubuntu Natty)
Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team)
** Changed in: linux (Ubuntu Natty)
Importance:
** Changed in: xserver-xorg-video-intel
Status: Unknown = Confirmed
** Changed in: xserver-xorg-video-intel
Importance: Unknown = High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
** Description changed:
- Binary package hint: xserver-xorg-video-intel
-
- I'm assuming this is because my suspend failed but I also had a black
- screen on boot until X started so perhaps it was something plymouth
- related.
+ [Problem]
+ The vesafb driver, used in the kernel as a default
Fwiw, after hearing from upstream and chatting with apw, it seems this
bug (or rather, class of bugs) is due to vesafb being present during
boot. As I gather from apw, this is believed to need to be loaded
because of plymouth and/or for fallback if kms/drm doesn't load or isn't
available, however
** Bug watch added: freedesktop.org Bugzilla #34018
http://bugs.freedesktop.org/show_bug.cgi?id=34018
** Also affects: xserver-xorg-video-intel via
http://bugs.freedesktop.org/show_bug.cgi?id=34018
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Travis Watkins - thanks for filing #702090 with updated X stuff. I've
forwarded both this bug and 702090 upstream to
http://bugs.freedesktop.org/show_bug.cgi?id=34018 - please subscribe
yourself to this bug, in case they need further information or wish you
to test something. Thanks ahead of
43 matches
Mail list logo
