Re: [Ubuntu-x-swat] [Bug 768184] Re: [i965gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x01800020) - Black screen (dpms?)
Not really, my intel devices have finally been working smoothly for a while now... but the nVidia ones went bezerk with the proprietary drivers... a whole other history, but very similar issue 2011/10/25 Bryce Harrington <768...@bugs.launchpad.net> > Hi, just checking back in for status. Have you seen more of these > lockups since the release or within the last few weeks? > > ** Changed in: xserver-xorg-video-intel (Ubuntu) > Status: Triaged => Incomplete > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (767425). > https://bugs.launchpad.net/bugs/768184 > > Title: > [i965gm] GPU lockup (ESR: 0x0001 IPEHR: 0x01800020) - Black screen > (dpms?) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/768184/+subscriptions > -- Fábio Leitão ..-. .- -... .. --- .-.. . .. - .- --- ...-.- -- 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/768184 Title: [i965gm] GPU lockup (ESR: 0x0001 IPEHR: 0x01800020) - Black screen (dpms?) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/768184/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 768581] Re: Unity froze when anything else went fullscreen (even screensaver) for more than 30 minutes
Not exactly... but there are a few times that Unity still sucks (ignoring mouse events, etc.) 2011/11/5 Fabio Marconi > Hello > Are you encountering again this problem? > Thansk > Fabio > --- > Ubuntu Bug Squad volunteer triager > http://wiki.ubuntu.com/BugSquad > > ** Changed in: ubuntu > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/768581 > > Title: > Unity froze when anything else went fullscreen (even screensaver) for > more than 30 minutes > > To manage notifications about this bug go to: > https://bugs.launchpad.net/unity/+bug/768581/+subscriptions > -- Fábio Leitão ..-. .- -... .. --- .-.. . .. - .- --- ...-.- -- 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/768581 Title: Unity froze when anything else went fullscreen (even screensaver) for more than 30 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/768581/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 768581] Re: Unity froze when anything else went fullscreen (even screensaver) for more than 30 minutes
Ok 2011/11/6 Fabio Marconi > Hello PresuntoRJ > This seems surely something related to a temporarily xorg-server freeze. > So I close this report asking you that the next time you're experiencing a > freeze to type in a terminal > ubuntu-bug xorg > that will open a new bug report with automatically attached all the > diagnostic needed files, so you've just to insert a small description of > the problem > Thanks > Fabio > --- > Ubuntu Bug Squad volunteer triager > http://wiki.ubuntu.com/BugSquad > > ** Changed in: ubuntu >Status: Incomplete => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/768581 > > Title: > Unity froze when anything else went fullscreen (even screensaver) for > more than 30 minutes > > To manage notifications about this bug go to: > https://bugs.launchpad.net/unity/+bug/768581/+subscriptions > -- Fábio Leitão ..-. .- -... .. --- .-.. . .. - .- --- ...-.- -- 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/768581 Title: Unity froze when anything else went fullscreen (even screensaver) for more than 30 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/768581/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 768184] Re: [i965gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x01800020) - Black screen (dpms?)
Not recently... How could I go on testing it again? On Mar 14, 2012 2:03 PM, "Bryce Harrington" <768...@bugs.launchpad.net> wrote: > Thanks Colin. There's been several fixes to game-related lockups in the > Intel mesa tree recently; I'll bet that did it for you. > > Who else can re-test? I'd especially like to hear from anyone that had > encountered the IPEHR 0x01800020 error. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (767425). > https://bugs.launchpad.net/bugs/768184 > > Title: > [i965gm] GPU lockup (ESR: 0x0001 IPEHR: 0x01800020) - Black screen > (dpms?) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/768184/+subscriptions > -- 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/768184 Title: [i965gm] GPU lockup (ESR: 0x0001 IPEHR: 0x01800020) - Black screen (dpms?) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/768184/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 272606] Re: ABNT2 Numpad Keyboard keys misbehaving
Thank you for your report, but in the ABNT2 keyboard (pt-BR), you are
supposed to get a [,] (coma) instead of a [.] (dot) at the numerical
keyboard.
We do not dot a decimal number in portugues... we PUT A COMA.
This is the expected behavior. Do NOT try to fix what aint broken.
By the way, it works for me at karmic koala (9.10) under evry single
application I could test, including Firefox, Google Chrome, OpenOffice
(all), Gedit.
2009/10/21 Fabio M. P. Bugnon
> I can confirm this bug in a beta Karmic Koala with all the updates.
>
> Please note, however, that this "coma" [,] instead of "dot" [.], as far
> as I could tell, only happens in OpenOffice, but not on other
> applications, such as Gedit, Firefox or even in Terminal for they
> correctly handle the dot [.] sign of the dot [.] key.
>
> I was going to try the fix Herbert suggested, but could not find the
> line mentioned but only:
>
> key{ [ KP_Decimal] };
>
> Which means -- at least according to my understand, please correct me if
> I'm wrong -- that the fix mentioned by Timo Aaltonen has already been
> applied. But I still get "comas" [,] while pressing the "dot" [.] key at
> the numeric side of the keyboard.
>
> I'm not sure how I could help with this matter, but please advice and I
> would be willing to provide further info and/or attach my config or log
> files.
>
> Thank you
>
>
> uname -a
> Linux fabio-desktop 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01
> UTC 2009 x86_64 GNU/Linux
>
>
> ** Attachment added: "inet"
> http://launchpadlibrarian.net/34120500/inet
>
> --
> ABNT2 Numpad Keyboard keys misbehaving
> https://bugs.launchpad.net/bugs/272606
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
--
Fábio Leitão
..-. .- -... .. --- .-.. . .. - .- --- ...-.-
Fabio LeiJao
h0x46 h0x61 h0x62 h0x69 h0x6F h0x20 h0x4C h0x65 h0x69 h0x74 h0x61 h0x6F
--
ABNT2 Numpad Keyboard keys misbehaving
https://bugs.launchpad.net/bugs/272606
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in ubuntu.
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 272606] Re: ABNT2 Numpad Keyboard keys misbehaving
I am sorry I did not understand it properly before, there was a similar issue in a previous release. I have tested now in my system as described and I actually do get the same problem you have (i.e in the numeric keypad the dot gives a coma when typed in the OpenOffice suite) 2009/10/22 Fabio M. P. Bugnon > Sorry - I might have not stressed out the circumstances clearly: > > The problem -- as previously noted [Leonardo Couto wrote on 2008-11-17] > -- is that in ABNT2 (or in "some" ABNT2 - even if this shouldn't be > possible, right?) we have BOTH keys: the coma [,] and the dot [.]. > > So, even if we do use comas as decimal separator in pt_BR I guess one > could expect -- since we have both keys -- that [.] act like [.] and [,] > as [,] ;). Even because we do (or some of us at least) use dots as > thousands separator, so it's good to have it at hand when typing big > figures. > > Furthermore, as mentioned, they actually already do work as expected > (coma-coma, dot-dot) in most -- if not all -- applications, except for > OpenOffice. > > The layout showing both keys was attached by Leonardo Couto and could be > seen at http://launchpadlibrarian.net/19709373/output1.pdf > > -- > ABNT2 Numpad Keyboard keys misbehaving > https://bugs.launchpad.net/bugs/272606 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > -- Fábio Leitão ..-. .- -... .. --- .-.. . .. - .- --- ...-.- Fabio LeiJao h0x46 h0x61 h0x62 h0x69 h0x6F h0x20 h0x4C h0x65 h0x69 h0x74 h0x61 h0x6F -- ABNT2 Numpad Keyboard keys misbehaving https://bugs.launchpad.net/bugs/272606 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 767425] [NEW] [i965gm] GPU lockup
Public bug reported: Binary package hint: xserver-xorg-video-intel Not sure if its a xorg problem, since it could also be in gdm or something else. I keep my system up-to-date while testing (just run an apt-get upgrade) and have been testing banshee when the screen went black ... I could not regain access to the system locally with Ctrl+Alt+Bckspc (set to kill X), or even Ctlr+Alt+F2... I had to ssh to this box, but killing gdm or xorg was not enough ... eventually I gave up and rebooted it, so I could post this bug report. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: xserver-xorg-video-intel 2:2.14.0-4ubuntu7 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 Architecture: i386 Chipset: i965gm CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1280x800 edid-base64: AP///wBMozM2AAAPAQOAIRV4Cof1lFdPjCcnUFQBAQEBAQEBAQEBAQEBAQEB7hoAgFAgEDAQMBMAS88QAAAZDwAAACOHAmQC/gBTQU1TVU5HCiAgICAg/gBMVE4xNTRYMy1MMDYKAHA= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: Date: Wed Apr 20 13:53:50 2011 DistUpgraded: Log time: 2011-04-09 18:13:48.268164 DistroCodename: natty DistroVariant: ubuntu DkmsStatus: virtualbox-ose, 4.0.4, 2.6.38-8-generic, i686: installed ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:383e] Subsystem: Lenovo Device [17aa:383e] InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) InterpreterPath: /usr/bin/python2.7 MachineType: LENOVO 0769AAP ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic-pae root=UUID=4b092518-b996-429c-b41e-9bf39183163c ro quiet splash vt.handoff=7 ProcKernelCmdLine_: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic-pae root=UUID=4b092518-b996-429c-b41e-9bf39183163c ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.6+4ubuntu3 libdrm2 2.4.23-1ubuntu6 xserver-xorg-video-intel 2:2.14.0-4ubuntu7 Renderer: Unknown SourcePackage: xserver-xorg-video-intel Title: [i965gm] GPU lockup UpgradeStatus: Upgraded to natty on 2011-04-10 (10 days ago) UserGroups: dmi.bios.date: 06/11/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 68ET37WW dmi.board.name: IEL10 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769AAP:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 0769AAP dmi.product.version: 3000 N200 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash compiz-0.9 freeze i386 natty ubuntu -- 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/767425 Title: [i965gm] GPU lockup ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 767425] Re: [i965gm] GPU lockup
-- 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/767425 Title: [i965gm] GPU lockup ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 767425] Re: [i965gm] GPU lockup (IPEHR: 0x08000000)
This has never happened in Maverick, or any other Ubuntu release before that (since 8.04 on this same box), only in Natty, and at least twice (the second time is the one I have filed the bug) 2011/4/20 Bryce Harrington <767...@bugs.launchpad.net> > Have you encountered other system freezes like this one since upgrading > to natty? Did you experience freezes like this on maverick? Are you > able to reproduce this freeze reliably? > > ** Changed in: xserver-xorg-video-intel (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/767425 > > Title: > [i965gm] GPU lockup (IPEHR: 0x0800) > > To unsubscribe from this bug, go to: > > https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/767425/+subscribe > -- Fábio Leitão ..-. .- -... .. --- .-.. . .. - .- --- ...-.- -- 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/767425 Title: [i965gm] GPU lockup (IPEHR: 0x0800) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 768560] [NEW] X wont start since the upgrade to 2.6.35-29-generic-pae
Public bug reported: Binary package hint: xorg I am not sure if its a bug on xorg it self, or in the nvidia drivers, or kernel, or some other important component, but since the upgrade my X wont start when I boot on the newer kernel (I can get to a shell via Ctrl+F2, and try to startx, but it also fails). It was working perfectly before, and I can still choose to boot with the previous kernels (2.6.35-28-generic-pae or 2.6.35-28-generic) during the grub menu ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: xorg 1:7.5+6ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic-pae 2.6.35.11 Uname: Linux 2.6.35-28-generic-pae i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 260.19.06 Mon Sep 13 06:35:06 PDT 2010 GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) Architecture: i386 CheckboxSubmission: 8ffa75e1b233799807120f5ed7003ee9 CheckboxSystem: cc699a849d78f423c8e1f0dfc5139850 Date: Thu Apr 21 16:35:47 2011 DkmsStatus: nvidia-current, 260.19.06, 2.6.35-28-generic, i686: installed nvidia-current, 260.19.06, 2.6.35-28-generic-pae, i686: installed ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-28-generic-pae root=UUID=a4f0e57d-069d-44aa-b722-929ad172638e ro vga=788 quiet quiet splash nomodeset video=uvesafb:mode_option=1024x768-24,mtrr=3,scroll=ywrap ProcEnviron: LANGUAGE=pt_BR:en LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: xorg dmi.bios.date: 09/30/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: P01 dmi.board.name: M61PMV dmi.board.version: FAB 1.0 dmi.chassis.asset.tag: Unknow dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrP01:bd09/30/2008:svn:pnM61PMV:pvrFAB1.0:rvn:rnM61PMV:rvrFAB1.0:cvn:ct3:cvr: dmi.product.name: M61PMV dmi.product.version: FAB 1.0 system: distro: Ubuntu codename: maverick architecture: i686 kernel: 2.6.35-28-generic-pae ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/768560 Title: X wont start since the upgrade to 2.6.35-29-generic-pae ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 768560] Re: X wont start since the upgrade to 2.6.35-29-generic-pae
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/768560 Title: X wont start since the upgrade to 2.6.35-29-generic-pae ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 768579] [NEW] x froze when anything but Unity went to fullscreen (even screensaver)
Public bug reported: Binary package hint: xorg My system keeps freezing if I leave it alone for a long time, usually more than thirty minutes, enough for the screensaver to kick in, and many subsystems (desktopcouch-se, zeitgeist-datahub, ...) becomes zombie processes, rendering the box unusable... I have found out it is not a screensaver specific issue, since I can have anything in full screen (like a banshee session, playing some music, or gedit with a text) and force the screensaver to never load, that after a while (again, more than thirty minutes), the box will freeze. I cannot kill X with Ctrl+Alt+Bckspc (which I have set previously), but I can still get to a shell via Ctrl+Alt+F2, then I can get log files, kill gdm-binary, and startx (startx wont start Unity completely, complaining I dont have enough hardware to run it, and get me to a Ubuntu-Classic session) At least I have managed to post this bug with apport. This happens every single time I am AFK with anything but Unity fullscreen ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xorg 1:7.6+4ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: None DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1280x800 edid-base64: AP///wBMozM2AAAPAQOAIRV4Cof1lFdPjCcnUFQBAQEBAQEBAQEBAQEBAQEB7hoAgFAgEDAQMBMAS88QAAAZDwAAACOHAmQC/gBTQU1TVU5HCiAgICAg/gBMVE4xNTRYMy1MMDYKAHA= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: Date: Thu Apr 21 17:00:04 2011 DistUpgraded: Log time: 2011-04-09 18:13:48.268164 DistroCodename: natty DistroVariant: ubuntu DkmsStatus: virtualbox-ose, 4.0.4, 2.6.38-8-generic-pae, i686: installed virtualbox-ose, 4.0.4, 2.6.38-8-generic, i686: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:383e] Subsystem: Lenovo Device [17aa:383e] InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: LENOVO 0769AAP ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic-pae root=UUID=4b092518-b996-429c-b41e-9bf39183163c ro quiet splash vt.handoff=7 Renderer: Unknown SourcePackage: xorg UpgradeStatus: Upgraded to natty on 2011-04-10 (11 days ago) dmi.bios.date: 06/11/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 68ET37WW dmi.board.name: IEL10 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769AAP:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 0769AAP dmi.product.version: 3000 N200 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/768579 Title: x froze when anything but Unity went to fullscreen (even screensaver) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 768579] Re: x froze when anything but Unity went to fullscreen (even screensaver)
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/768579 Title: x froze when anything but Unity went to fullscreen (even screensaver) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 767425] Re: [i965gm] GPU lockup (IPEHR: 0x08000000)
I have just downloaded the newer kernel there (form the current folder) linux-image-2.6.38-996-generic_2.6.38-996.201103251543_i386.deb and its headers (all and i386)... lets see how the do. ;) Is this some specially compiled debug version of the kernel? Or just with some newer patches? -- 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/767425 Title: [i965gm] GPU lockup (IPEHR: 0x0800) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 767425] Re: [i965gm] GPU lockup (IPEHR: 0x08000000)
Just downloaded and installed the lastest Kernel available there as current (linux- image-2.6.38-996-generic_2.6.38-996.201103251543_i386.deb) and its headers (all and i386)... lets see how they do ;) Is this a specially built kernel with debug enabled? or just some newer patches? It seems to boot alright, but (as a notebook that I keep my hands on) the machine felt a little warmer ... I wanted to check the temperature (in case the kernel was forcing something odd with the CPUs) but I have found out I am unable to collect temperature with acpi tools now (it used to work just fine, even with landscape-sysinfo, and its also gone) I can still see the speed step its keeping the processor though, via indicator-cpufreq, and it seemes quiet usual (the occasional oscillation to top speed, and then back to slowest or some middle clock) The battery information seems coherent too, the detection of power source and the estimated percentage (currently 97%) to discharge when not connected... but it does not show the estimated time to discharge or recharge (as it used to). Not sure if its kernel related or a incredible coincidence (since it was only the kernel that I have updated now). By the way, it still feels really warm, almost hot. -- 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/767425 Title: [i965gm] GPU lockup (IPEHR: 0x0800) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 767425] Re: [i965gm] GPU lockup (IPEHR: 0x08000000)
Oddly, I get to check the temperatures in Ubuntu-Classic (gnome) via the sensors-applet (some how they can still get temperatures from CPU and HDD) and it is quite hot CPU=63C and HDD=53C, not sure if I can read the GPU on this machine... but I think that is what is heating up the system... the fan is running, not at full throttle (?) and I can cope with the overheat for a while, with an external ventilation forcing air into the notebook ;) but I hope its not the new default state -- 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/767425 Title: [i965gm] GPU lockup (IPEHR: 0x0800) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 767425] Re: [i965gm] GPU lockup (IPEHR: 0x08000000)
Everything else seems pretty ok, so far... and no new freezes yet -- 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/767425 Title: [i965gm] GPU lockup (IPEHR: 0x0800) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 768581] Re: Unity froze when anything else went fullscreen (even screensaver) for more than 30 minutes
never happened (so far) 2011/4/24 Bilal Akhtar > Possibly related to X. Do you face the same problem in the Ubuntu > Classic session? > > ** Changed in: unity > Status: New => Incomplete > > ** Changed in: unity (Ubuntu) > Status: New => Incomplete > > ** Also affects: xorg (Ubuntu) > Importance: Undecided > Status: New > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/768581 > > Title: > Unity froze when anything else went fullscreen (even screensaver) for > more than 30 minutes > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/unity/+bug/768581/+subscribe > -- Fábio Leitão ..-. .- -... .. --- .-.. . .. - .- --- ...-.- -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/768581 Title: Unity froze when anything else went fullscreen (even screensaver) for more than 30 minutes ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 768581] Re: Unity froze when anything else went fullscreen (even screensaver) for more than 30 minutes
just tested on Ubuntu Classic (gnome) for a while, and bam ! it also crashed if I let the screensaver holds the fullscreen for more than 30 minutes... it also happened to banshee in full screen... what ever is drawn wont erase, and I dont get to use the desktop anymore... I have to reboot via Ctrl+Alt+F2 and sudo reboot 2011/4/24 bugbot <768...@bugs.launchpad.net> > ** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/768581 > > Title: > Unity froze when anything else went fullscreen (even screensaver) for > more than 30 minutes > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/unity/+bug/768581/+subscribe > -- Fábio Leitão ..-. .- -... .. --- .-.. . .. - .- --- ...-.- -- 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/768581 Title: Unity froze when anything else went fullscreen (even screensaver) for more than 30 minutes ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 768581] Re: Unity froze when anything else went fullscreen (even screensaver) for more than 30 minutes
Cause it is not the package we thought about, does not mean the issue is invalid, cause I keep getting the system in a frozen state 2011/4/25 Bryce Harrington <768...@bugs.launchpad.net> > You've got some weird wireless error messages in your dmesg. > > Anyway, this sounds more like a power manager issue than X. X failures > generally don't result in zombie processes, that sounds more like > plumbing layer misbehavior. > > Also I notice you have VirtualBox installed, which could cause problems: > > [ 4177.752515] warning: `VirtualBox' uses 32-bit capabilities (legacy > support in use) > > Anyway, not looking likely to be an X issue. Reopen if you can narrow > to a test case that demonstrates something X specifically is failing on, > or error messages in an X log or something. > > ** Changed in: xserver-xorg-video-intel (Ubuntu) > Status: New => Invalid > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/768581 > > Title: > Unity froze when anything else went fullscreen (even screensaver) for > more than 30 minutes > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/unity/+bug/768581/+subscribe > -- Fábio Leitão ..-. .- -... .. --- .-.. . .. - .- --- ...-.- -- 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/768581 Title: Unity froze when anything else went fullscreen (even screensaver) for more than 30 minutes ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 771837] [NEW] xorg died (gracefully to login) but without ado
Public bug reported: Binary package hint: xorg I was using it normally (firefox, chrome, banshee, and also reading a PDF) when suddenly the X turned off, back to a textual background (as I would expected if I have pressed Ctrl+Alt+Bckspc, but I have not) and shortly after I was presented with the login screen again (gdm?) ... it has happened at least five time the last two weeks, but I was not sure if it was related with other issues I was also facing during the beta testing, but now I am sure it had nothing to do with anything else I was doing. The system is fully up to date (checked just after the issue, to be sure). I do not had a real step-by-step to reproduce the problem, as it seems to happen kind of out of the blue. Sice the first few times I have experience this issue I have installed a current kernel (not from apt-get) to try to solve something else (it did not seemed to have any influence on the current problem, as it happened before and after the upgrade anyway). I also suspect it might have something to do with intel drivers in xorg, but I am not skilled in x enough to even try this theory. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xorg 1:7.6+4ubuntu3 Uname: Linux 2.6.38-996-generic i686 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz DRM.card0.LVDS.1: status: unknown enabled: enabled dpms: On modes: 1280x800 edid-base64: AP///wBMozM2AAAPAQOAIRV4Cof1lFdPjCcnUFQBAQEBAQEBAQEBAQEBAQEB7hoAgFAgEDAQMBMAS88QAAAZDwAAACOHAmQC/gBTQU1TVU5HCiAgICAg/gBMVE4xNTRYMy1MMDYKAHA= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: Date: Wed Apr 27 10:54:51 2011 DistUpgraded: Log time: 2011-04-09 18:13:48.268164 DistroCodename: natty DistroVariant: ubuntu DkmsStatus: virtualbox-ose, 4.0.4, 2.6.38-996-generic, i686: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:383e] Subsystem: Lenovo Device [17aa:383e] InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: LENOVO 0769AAP ProcEnviron: LANGUAGE=pt_BR:en LANG=en_US.UTF-8 LC_MESSAGES=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-996-generic root=UUID=4b092518-b996-429c-b41e-9bf39183163c ro quiet splash vt.handoff=7 Renderer: Unknown SourcePackage: xorg UpgradeStatus: Upgraded to natty on 2011-04-10 (17 days ago) dmi.bios.date: 06/11/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 68ET37WW dmi.board.name: IEL10 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769AAP:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 0769AAP dmi.product.version: 3000 N200 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 natty running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/771837 Title: xorg died (gracefully to login) but without ado ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 771837] Re: xorg died (gracefully to login) but without ado
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/771837 Title: xorg died (gracefully to login) but without ado ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 768560] Re: X wont start since the upgrade to 2.6.35-29-generic-pae
I have managed to boot and get the GUI running when I attempted to fully remove the kernel and header files (linux-image-2.6.35-29-generic-pae, linux-image-2.6.35-29-generic, linux-headers-2.6.35-29-generic-pae, linux-headers-2.6.35-29-generic and linux-headers-2.6.35-29) and then reinstalling them, which has forced the dkms to readjust accordingly (what seems vital to nvidia drivers to work properly). I am not sure now if the dkms trigger have failed during the original attempt to upgrade (i do not remember), but it seems plausible. I am not sure yet if there are anything else missing on my system (I have been using the last kernel before that since the glitch presented) but I am typing right now from Google Chrome running just fine under Gnome, so it looks mostly fine. I will come back with more as I find out. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in Ubuntu. https://bugs.launchpad.net/bugs/768560 Title: X wont start since the upgrade to 2.6.35-29-generic-pae ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 768560] Re: X wont start since the upgrade to 2.6.35-29-generic-pae
by the way, I did apt-get autoremove -purge with the packages to really get rid of them ;) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in Ubuntu. https://bugs.launchpad.net/bugs/768560 Title: X wont start since the upgrade to 2.6.35-29-generic-pae ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 768560] Re: X wont start since the upgrade to 2.6.35-29-generic-pae
I am not upgrading this machine to natty soon, its a production desktop... I can only upgrade the production workstation to natty once its running at least smoothly on my "test" systems, after the official release, cause I cannot risk not having this one working fine. Sorry. on the other hand, I do have other equipments, and in two of them I already have natty running... unfortunately, those do not have nviadia cards on them (one has Intel 965gm, which their own bunch of bugs ;), and one AsusEeePc 1005Ha ) so dkms is not an issue in any natty I have tested so far. if I do get my hands on a box with nvidia, I will jump in to test natty on it (prefereably, upgrading it from maverick) 2011/4/28 bugbot <768...@bugs.launchpad.net> > Hey PresuntoRJ, > > > Hi, have you had a chance to test if this bug is still present in natty? > > If it does (and if you're the original reporter), please boot into natty > and run the command: > > apport-collect > > which will update the bug with fresh logs and tag the bug as affecting > natty. (It is best to run this right after reproducing the problem.) > > > ** Changed in: nvidia-graphics-drivers-180 (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/768560 > > Title: > X wont start since the upgrade to 2.6.35-29-generic-pae > > To unsubscribe from this bug, go to: > > https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/768560/+subscribe > -- Fábio Leitão ..-. .- -... .. --- .-.. . .. - .- --- ...-.- -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in Ubuntu. https://bugs.launchpad.net/bugs/768560 Title: X wont start since the upgrade to 2.6.35-29-generic-pae ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 771837] Re: xorg died (gracefully to login) but without ado
how can I understand when the issue is on the xorg driver (intel or otherwise)? I had no clue when I have inspected my log files, at least, nothing obvious, where I was looking... :-p 2011/4/28 bugbot <771...@bugs.launchpad.net> > ** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/771837 > > Title: > xorg died (gracefully to login) but without ado > > To unsubscribe from this bug, go to: > > https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/771837/+subscribe > -- Fábio Leitão ..-. .- -... .. --- .-.. . .. - .- --- ...-.- -- 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/771837 Title: xorg died (gracefully to login) but without ado ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 771837] Re: xorg died (gracefully to login) but without ado
can I do it via byobu on the local system (so I can reatach the screen in case of crash) or should I do it via ssh from a different machine? I really do not know how long it would take to actually hit gold here, so think I cannot keep using two systems at once for several days... any ideas? every time I enter gdb and try to attach the runnig Xorg pid, it freezes... if I try to run if with the -keeptty -dumbSched options, it tells me Xorg is already running (of course)... if I kill it, it simply respawns... the guide seems pretty useless cause if you follow the steps there, you cannot get any backtrace whatsoever. How can I ever get X to run inside gdb? (I know I could sudo /etc/init.d/gdm stop, but the only time it is mentioned there, is totally unrelated with the steps to get the backtrace) that said, I did manage to start inside gdb and pretty much as soon as I have loged in, it halted with a SIGUSR1 adn wont resume no matter what I try... I am not sure what I am doing wrong or if that could be related with the issue: (gdb) run -keeptty -dumbSched Starting program: /usr/bin/Xorg -keeptty -dumbSched [Thread debugging using libthread_db enabled] X.Org X Server 1.10.1 Release Date: 2011-04-15 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.24-29-server i686 Ubuntu Current Operating System: Linux fpc 2.6.38-996-generic #201103251543 SMP Fri Mar 25 17:11:59 UTC 2011 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-996-generic root=UUID=4b092518-b996-429c-b41e-9bf39183163c ro quiet splash vt.handoff=7 Build Date: 19 April 2011 03:33:17PM xorg-server 2:1.10.1-1ubuntu1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.20.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 28 20:10:11 2011 (==) Using system config directory "/usr/share/X11/xorg.conf.d" Program received signal SIGUSR1, User defined signal 1. 0xb7fe1424 in __kernel_vsyscall () 2011/4/28 Bryce Harrington <771...@bugs.launchpad.net> > Hi PresuntoRJ, of course you're not expected to know such details. ;-) > > The 'xorg' package is a general inbox, and bugbot takes care of figuring > out your video driver, symptoms, and so on, and moves the bug to the > right location. > > Your system appears to be encountering a segmentation fault in the X > server, resulting in it crashing. gdm restarts an X session which is > why you're returned to the login screen each time. > > The "out of the blue" nature of it is troubling. X segmentation faults > are pretty rare and tend to occur only under specific circumstances. So > there are *usually* steps to reproduce them. When there isn't, I start > suspecting hardware faults such as bad memory chips. But let's assume > it to be a software bug in X first. > > Can you collect a full backtrace? This will help tell me where in the > code exactly that the crash is happening. Directions for doing this are > at http://wiki.ubuntu.com/X/Backtracing > > ** Changed in: xserver-xorg-video-intel (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/771837 > > Title: > xorg died (gracefully to login) but without ado > > To unsubscribe from this bug, go to: > > https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/771837/+subscribe > -- Fábio Leitão ..-. .- -... .. --- .-.. . .. - .- --- ...-.- -- 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/771837 Title: xorg died (gracefully to login) but without ado ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 768579] Re: x froze when anything but Unity went to fullscreen (even screensaver)
Next time it freezes, I will collet the data and post on this bug. Not sure how my box will be affected with a recent kernel upgrade, though. 2011/5/3 Bryce Harrington <768...@bugs.launchpad.net> > For X freeze bugs on Intel, you need to collect the output of 'dmesg' > and your /sys/kernel/debug/dri/0/i915_error_state file. Both of these > must be collected while the machine is locked up (e.g. by sshing into > the sick machine over ethernet). > > ** Changed in: xserver-xorg-video-intel (Ubuntu) > Importance: Undecided => High > > ** Changed in: xserver-xorg-video-intel (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/768579 > > Title: > x froze when anything but Unity went to fullscreen (even screensaver) > > To unsubscribe from this bug, go to: > > https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/768579/+subscribe > -- Fábio Leitão ..-. .- -... .. --- .-.. . .. - .- --- ...-.- -- 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/768579 Title: x froze when anything but Unity went to fullscreen (even screensaver) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 768184] Re: [i965gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x01800020)
I think I can post a dmesg and i915_error_state files the next time my machine freezes, but I am not sure how it will react with a recent kernel upgrade to 2.6.38-9 2011/5/3 Bryce Harrington <768...@bugs.launchpad.net> > [I've marked this bug for inclusion in our oneiric bug queue. While > technically this bug has not been re-confirmed against oneiric, I feel > it is worth continued development attention. We will need to ask that > it be re-confirmed once oneiric is further along, perhaps once we get > closer to alpha.] > > -- > You received this bug notification because you are a direct subscriber > of a duplicate bug (767425). > https://bugs.launchpad.net/bugs/768184 > > Title: > [i965gm] GPU lockup (ESR: 0x0001 IPEHR: 0x01800020) > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/768184/+subscribe > -- Fábio Leitão ..-. .- -... .. --- .-.. . .. - .- --- ...-.- -- 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/768184 Title: [i965gm] GPU lockup (ESR: 0x0001 IPEHR: 0x01800020) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 767436] Re: compiz crashed with SIGSEGV in brw_validate_state()
Similarly to other intel related bugs, I will try to post the collected data when my box freezes again... not sure how it will behave with a newly upgraded kernel, though... 2011/5/3 Bryce Harrington <767...@bugs.launchpad.net> > You should also check your dmesg and > /sys/kernel/debug/dri/0/i915_error_state when you ssh into it when it's > down, in the case that the issue is a gpu lockup. > > ** Changed in: xserver-xorg-video-intel (Ubuntu) > Status: New => Confirmed > > ** Changed in: xserver-xorg-video-intel (Ubuntu) > Importance: Undecided => Medium > > ** Changed in: xserver-xorg-video-intel (Ubuntu) > Importance: Medium => High > > ** Changed in: xserver-xorg-video-intel (Ubuntu) > Status: Confirmed => Incomplete > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/767436 > > Title: > compiz crashed with SIGSEGV in brw_validate_state() > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/null/+bug/767436/+subscribe > -- Fábio Leitão ..-. .- -... .. --- .-.. . .. - .- --- ...-.- -- 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/767436 Title: compiz crashed with SIGSEGV in brw_validate_state() ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 768581] Re: Unity froze when anything else went fullscreen (even screensaver) for more than 30 minutes
I have been trying to get reproduce the bug to capture dmesg, i915_error_state and even dtraces from my gdm session, but I am not sure what triggers it yet. So far, it seems that it freezes when the screensaver was running for some time BECAUSE IT HAD TURNED MY SCREEN OFF due to energy policy... I had since disengaged the energy control option to never turn my screen off again, so far it has not frozen my system again. I suspect that this could be the root cause, but I am not sure how to prove it, or what packages could be involved to further the investigation. It also seems to happen only on my systems with intel video boards (Mobile GM965/GL960 Lenovo Laptop and Mobile 945GME Express Asus netbook). -- 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/768581 Title: Unity froze when anything else went fullscreen (even screensaver) for more than 30 minutes ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 771837] Re: xorg died (gracefully to login) but without ado
I have been trying to get reproduce the bug to capture dmesg, i915_error_state and even dtraces from my gdm session, but I am not sure what triggers it yet. So far, it seems that it freezes when the screensaver is about to run, when idle for some time. I had since disengaged the screensaver, and the energy control option to never turn my screen off again, so far it has not frozen or logged out my system again. I suspect that this could be the root cause, but I am not sure how to prove it, or what packages could be involved to further the investigation. -- 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/771837 Title: xorg died (gracefully to login) but without ado ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 768184] Re: [i965gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x01800020)
I have been trying to get reproduce the bug to capture dmesg, i915_error_state and even backtraces from my gdm session, but I am not sure what triggers it yet. So far, it seems that it freezes when the screensaver was running for some time BECAUSE IT HAD TURNED MY SCREEN OFF due to energy policy... I had since disengaged the energy control option to never turn my screen off again, so far it has not frozen my system again. I suspect that this could be the root cause, but I am not sure how to prove it, or what packages could be involved to further the investigation. It also seems to happen only on my systems with intel video boards (Mobile GM965/GL960 Lenovo Laptop and Mobile 945GME Express Asus netbook). -- 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/768184 Title: [i965gm] GPU lockup (ESR: 0x0001 IPEHR: 0x01800020) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 767436] Re: compiz crashed with SIGSEGV in brw_validate_state()
I have been trying to get reproduce the bug to capture dmesg, i915_error_state and even backtraces from my gdm session, but I am not sure what triggers it yet. So far, it seems that it freezes when the screensaver was running for some time BECAUSE IT HAD TURNED MY SCREEN OFF due to energy policy... I had since disengaged the energy control option to never turn my screen off again, so far it has not frozen my system again. I suspect that this could be the root cause, but I am not sure how to prove it, or what packages could be involved to further the investigation. It also seems to happen only on my systems with intel video boards (Mobile GM965/GL960 Lenovo Laptop and Mobile 945GME Express Asus netbook). -- 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/767436 Title: compiz crashed with SIGSEGV in brw_validate_state() ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 768560] Re: X wont start since the upgrade to 2.6.35-29-generic-pae
I have since upgraded this machine to Natty (32) and it failed catastrophically... so much it was not showing the grub menu due to an impossible high resolution, not showing plymouth during boot, and basically unusable... Hopefully I had a full back up (plus my home was on another disk) and could wipe it clean and start over with Natty (64)... It is mostly working fine, though Plymouth only shows when I turn it off (never when I turn it on), and compiz seems to have a bad memory leak when under Unity, and I had to set Grub to show as console since the graphic version was still not showing (probably still cause of an impossible high resolution, but at least it shows). None of this issues existed up to Maverick (have been using Ubuntu on this machine since 8.04) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in Ubuntu. https://bugs.launchpad.net/bugs/768560 Title: X wont start since the upgrade to 2.6.35-29-generic-pae ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 771837] Re: xorg died (gracefully to login) but without ado
humpft... it just happened again, no heads up, while using the machine (not at idle, screen saver, or screen off)... ** Attachment added: "dmesg jsut after the issue happened" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/771837/+attachment/2130385/+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. https://bugs.launchpad.net/bugs/771837 Title: xorg died (gracefully to login) but without ado ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 771837] Re: xorg died (gracefully to login) but without ado
** Attachment added: "Current xorg log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/771837/+attachment/2130390/+files/Xorg.0.log -- 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/771837 Title: xorg died (gracefully to login) but without ado ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 771837] Re: xorg died (gracefully to login) but without ado
** Attachment added: "previous xorg log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/771837/+attachment/2130391/+files/Xorg.0.log.old -- 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/771837 Title: xorg died (gracefully to login) but without ado ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 771837] Re: xorg died (gracefully to login) but without ado
** Attachment added: "old xorg log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/771837/+attachment/2130392/+files/Xorg.1.log -- 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/771837 Title: xorg died (gracefully to login) but without ado ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 771837] Re: xorg died (gracefully to login) but without ado
I have never been able to reproduce the bug on a debug session... every attept to backtrace seems impossible to complete, locking up my system even further... the wiki guides do not help at all :-( -- 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/771837 Title: xorg died (gracefully to login) but without ado ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
