[Ubuntu-x-swat] [Bug 899531] [NEW] Xorg crash
Public bug reported: The crashes did not happened in 11.04. In 11.10 the system crashes nearly every day. Same Problem with Gnome 3. But LXDE seems to work properly. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu4 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,place,imgpng,unitymtgrabhandles,resize,gnomecompat,mousepoll,session,snap,wall,vpswitch,move,regex,animation,expo,winrules,fade,workarounds,ezoom,scale,unityshell] CompositorRunning: compiz Date: Sat Dec 3 09:09:58 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21c5] InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: LENOVO 021722G ProcEnviron: PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=1cf33934-292a-4fc1-a2e6-3bde580869b5 ro noplymouth SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 84ET21WW (1.05 ) dmi.board.name: 021722G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr84ET21WW(1.05):bd10/13/2010:svnLENOVO:pn021722G:pvrThinkPadEdge:rvnLENOVO:rn021722G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 021722G dmi.product.version: ThinkPad Edge dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6 version.ia32-libs: ia32-libs 20090808ubuntu26 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 crash oneiric regression-update 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/899531 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/899531/+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
[Ubuntu-x-swat] [Bug 899531] Re: Xorg crash
-- 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/899531 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/899531/+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
[Ubuntu-x-swat] [Bug 899531] Re: Xorg crash
** Tags removed: regression-update ** Tags added: regression-release -- 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/899531 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/899531/+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
[Ubuntu-x-swat] [Bug 870004] Re: Nvidia Driver on 11.10 (GT525M)
Hello, i did try it and the GUI won´t come up again. nvidia-config can´t find a nvidia card, so it´s still open in my opinion. But on the other hand...i will try ironhide, maybe then it will work. Apart from this, since the last python upgrade the software center won´t work anymore. BR Tim ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Incomplete = Opinion -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/870004 Title: Nvidia Driver on 11.10 (GT525M) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/870004/+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
[Ubuntu-x-swat] [Bug 820918] Re: The screen gets garbled after a few hours of use
I have been seeing this off and on since 10.10 as well. Doesn't matter which desktop environment, but I think it happens more with compiz. -- 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/820918 Title: The screen gets garbled after a few hours of use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/820918/+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
[Ubuntu-x-swat] [Bug 745608] Re: [915GM] font corruption on Intel GMA900
The font corruption not only affects some fonts but not others, and some letters, but not others, but some sizes and not others as well. if a webpage has unreadable fonts, increase the page magnification a few times and it will go away at higher pt sizes. For me, the desktop graphic also gets corrupted. ** Attachment added: Example https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/745608/+attachment/2617583/+files/Screenshot%20-%20031211%20-%2023%3A28%3A01.png -- 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/745608 Title: [915GM] font corruption on Intel GMA900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/745608/+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
[Ubuntu-x-swat] [Bug 745608] Re: [915GM] font corruption on Intel GMA900
Another example ** Attachment added: Example https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/745608/+attachment/2617584/+files/Screenshot%20-%20031211%20-%2023%3A36%3A55.png -- 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/745608 Title: [915GM] font corruption on Intel GMA900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/745608/+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
[Ubuntu-x-swat] [Bug 899559] [NEW] nvidia-173 173.14.30-0ubuntu8: nvidia-173 kernel module failed to build
*** This bug is a duplicate of bug 897681 *** https://bugs.launchpad.net/bugs/897681 Public bug reported: N Vidia firmware crashes ProblemType: Package DistroRelease: Ubuntu 12.04 Package: nvidia-173 173.14.30-0ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-2.6-generic 3.2.0-rc3 Uname: Linux 3.2.0-2-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 1.90-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz DKMSKernelVersion: 3.2.0-2-generic Date: Sat Dec 3 11:53:50 2011 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: nvidia-173, 173.14.30: added GraphicsCard: nVidia Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8245] Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 046d:c042 Logitech, Inc. G3 Laser Mouse MachineType: System manufacturer System Product Name PackageVersion: 173.14.30-0ubuntu8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-generic root=UUID=F45CB3FA5CB3B628 loop=/hostname/disks/root.disk ro quiet splash vt.handoff=7 SourcePackage: nvidia-graphics-drivers-173 Title: nvidia-173 173.14.30-0ubuntu8: nvidia-173 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2N4-SLI ACPI BIOS Revision 0301 dmi.board.name: M2N4-SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N4-SLIACPIBIOSRevision0301:bd07/14/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N4-SLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu7 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.27-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.10.4-1ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 ** Affects: nvidia-graphics-drivers-173 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 precise regression single-occurrence ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-173 in Ubuntu. https://bugs.launchpad.net/bugs/899559 Title: nvidia-173 173.14.30-0ubuntu8: nvidia-173 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/899559/+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
[Ubuntu-x-swat] [Bug 899559] Re: nvidia-173 173.14.30-0ubuntu8: nvidia-173 kernel module failed to build
*** This bug is a duplicate of bug 897681 *** https://bugs.launchpad.net/bugs/897681 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-173 in Ubuntu. https://bugs.launchpad.net/bugs/899559 Title: nvidia-173 173.14.30-0ubuntu8: nvidia-173 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/899559/+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
[Ubuntu-x-swat] [Bug 899559] Re: nvidia-173 173.14.30-0ubuntu8: nvidia-173 kernel module failed to build
*** This bug is a duplicate of bug 897681 *** https://bugs.launchpad.net/bugs/897681 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #897681, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** Attachment removed: Dependencies.txt https://bugs.launchpad.net/bugs/899559/+attachment/2617590/+files/Dependencies.txt ** This bug has been marked a duplicate of bug 897681 dkms attempts to install the wrong driver -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-173 in Ubuntu. https://bugs.launchpad.net/bugs/899559 Title: nvidia-173 173.14.30-0ubuntu8: nvidia-173 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/899559/+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
[Ubuntu-x-swat] [Bug 745608] Re: [915GM] font corruption on Intel GMA900
Your samples are far worse than what I experienced. To me only a few letters became barely readable because of strokes in them. However, it looks as if the freedesktop guys have been working on a solution in august 2011 (see remote bug watches). Let's hope that they were able to fix it. -- 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/745608 Title: [915GM] font corruption on Intel GMA900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/745608/+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
[Ubuntu-x-swat] [Bug 892544] Re: Unity slow after resume from suspend
Hi Daniel, I have done a lot of test on different hardware and I think the problem is in compiz or unity, a unity --reset or compiz --replace fixes the problem until next suspend resume, I think this problem is the same as the bug Bug #861061, with 11.04 this bug did not occur, I will wait for the correction the Bug #861061, to see if the problem goes away. Thanks. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/892544 Title: Unity slow after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/892544/+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
[Ubuntu-x-swat] [Bug 899585] [NEW] when display goes to a sleep mode, then wakes up. the backlight does not come back on
Public bug reported: brightness slider on display config widget is erratic and does't linearly increase and decrease rather flickers when siding between bright an dim ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu4 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,move,place,snap,vpswitch,mousepoll,regex,resize,gnomecompat,imgpng,animation,unitymtgrabhandles,session,wall,fade,workarounds,expo,scale,ezoom,unityshell] CompositorRunning: compiz Date: Sat Dec 3 15:06:31 2011 DistUpgraded: Log time: 2011-10-23 19:22:43.303681 DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: bcmwl, 5.100.82.38+bdcom, 2.6.38-11-generic, i686: installed bcmwl, 5.100.82.38+bdcom, 3.0.0-12-generic, i686: installed bcmwl, 5.100.82.38+bdcom, 3.0.0-13-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:361a] Subsystem: Hewlett-Packard Company Device [103c:361a] InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386 (20100429.4) MachineType: Hewlett-Packard HP Mini ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=abce34ac-224f-490f-9578-8b010d022bfd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to oneiric on 2011-11-07 (26 days ago) dmi.bios.date: 11/07/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 361A0 Ver. F.05 dmi.board.name: 361A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 02.0D dmi.chassis.asset.tag: CNU902287J dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr361A0Ver.F.05:bd11/07/2008:svnHewlett-Packard:pnHPMini:pvrF.05:rvnHewlett-Packard:rn361A:rvrKBCVersion02.0D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Mini dmi.product.version: F.05 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 oneiric regression-update 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/899585 Title: when display goes to a sleep mode, then wakes up. the backlight does not come back on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/899585/+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
[Ubuntu-x-swat] [Bug 899585] Re: when display goes to a sleep mode, then wakes up. the backlight does not come back on
-- 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/899585 Title: when display goes to a sleep mode, then wakes up. the backlight does not come back on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/899585/+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
[Ubuntu-x-swat] [Bug 899590] Re: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/899590 Title: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/899590/+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
[Ubuntu-x-swat] [Bug 899590] [NEW] package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
Public bug reported: $ ubuntu-bug fglrx-installer failed ProblemType: Package DistroRelease: Ubuntu 10.04 Package: fglrx 2:8.723.1-0ubuntu5 ProcVersionSignature: Ubuntu 2.6.32-35.78-generic 2.6.32.46+drm33.20 Uname: Linux 2.6.32-35-generic i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Sat Dec 3 14:18:04 2011 DkmsStatus: fglrx, 8.723.1, 2.6.32-35-generic, i686: installed ErrorMessage: fglrx kernel module failed to build InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release i386 (20110720.1) MachineType: Acer TravelMate 5520 PackageVersion: 2:8.723.1-0ubuntu5 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-35-generic root=UUID=d5a2073e-4528-4249-8aee-d49828fc103f ro noplymouth pcie_aspm=force SourcePackage: fglrx-installer Title: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build dmi.bios.date: 08/17/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.14 dmi.board.name: TravelMate 5520 dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.asset.tag: None dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.14:bd08/17/2007:svnAcer:pnTravelMate5520:pvr0100:rvnAcer:rnTravelMate5520:rvrRev:cvnAcer:ct1:cvrNone: dmi.product.name: TravelMate 5520 dmi.product.version: 0100 dmi.sys.vendor: Acer glxinfo: Error: command ['glxinfo'] failed with exit code -11: system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-35-generic ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/899590 Title: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/899590/+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
[Ubuntu-x-swat] [Bug 401107] Re: Software runs as root
Security vulnerabilities must not be ignored! Robert, Cant LightDM use AppArmor or PolicyKit? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/401107 Title: Software runs as root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/401107/+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
[Ubuntu-x-swat] [Bug 897821] Re: Null pointer dereference in drm_debugfs_remove_files
** Package changed: xserver-xorg-video-nouveau (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/897821 Title: Null pointer dereference in drm_debugfs_remove_files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/897821/+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
[Ubuntu-x-swat] [Bug 899531] Re: Xorg crash
*** This bug is a duplicate of bug 887794 *** https://bugs.launchpad.net/bugs/887794 ** This bug has been marked a duplicate of bug 887794 ubuntu log out automatically -- 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/899531 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/899531/+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
[Ubuntu-x-swat] [Bug 887794] Re: ubuntu log out automatically
I have the same problem: Bug #899531 (already marked as duplicate). Since I removed Ubuntu 11.04 and installed 11.10, the system crashes nearly everyday without any prior warning and the login-screen appears. The same behavior in Gnome 3. Only LXDE seems to work (no crashes since I installed it before 10 days). -- 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/887794 Title: ubuntu log out automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/887794/+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
[Ubuntu-x-swat] [Bug 883319] Re: xrandr --scale 1.2x1.2 restricts area in which mouse moves
I'll build one, if somebody could tell me how. I haven't had to undo a patch before, and am leery about breaking it and being hosed. I have bad luck with compiling core stuff lol ;) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale 1.2x1.2 restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/883319/+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
[Ubuntu-x-swat] [Bug 899669] [NEW] Screen Corruption and crash after Gnome Shell login
Public bug reported: Steps to Reproduce: 1. Boot Ubuntu 11.10 64-bit into Gnome Shell 2. Observe black flashing squares near Activities button Observed results: I'm on 11.10 Gnome Shell, and about once a day, there's a screen corruption around the Activities button right after boot: a random group of black squares flashing on and off. If I continue working, the corruption will get worse, and the top of the screen fills with garbage spreading from left to right. See attached screenshots. Eventually, Ubuntu crashes to the login screen. Only occurs right after login. If it doesn't happen then, it never happens, so right now, when I see it, I log out and back in and I'm good. Notes: My PC is a desktop. Hardware: CPU: AMD Phenom II X6 1090T Six Core Processor AM3 3.2GHZ Graphics: Gigabyte GeForce GTX 460 1GB Fermi 760MHZ Software: Ubuntu 11.10 64-bit Gnome Shell Nvidia 290.10 drivers ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 290.10 Wed Nov 16 17:39:29 PST 2011 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu4 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,move,water,regex,vpswitch,imgpng,place,mousepoll,grid,animation,resize,unitymtgrabhandles,wall,wobbly,session,workarounds,expo,fade,scale,ezoom,unityshell] CompositorRunning: None Date: Sat Dec 3 10:41:20 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: nvidia-current, 290.10, 3.0.0-13-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: nVidia Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:34fc] InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=e481fddc-5155-4fdf-b0fb-ef8e9a2c1e31 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 05/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.name: JW-A870T-UC3 dmi.board.vendor: JW Technology dmi.board.version: V1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnJWTechnology:rnJW-A870T-UC3:rvrV1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6 version.ia32-libs: ia32-libs 20090808ubuntu26 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption oneiric patch 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/899669 Title: Screen Corruption and crash after Gnome Shell login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/899669/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe :
[Ubuntu-x-swat] [Bug 899669] Re: Screen Corruption and crash after Gnome Shell login
** Attachment added: Screenshot at 2011-11-26 10:32:23.png https://bugs.launchpad.net/bugs/899669/+attachment/2618096/+files/Screenshot%20at%202011-11-26%2010%3A32%3A23.png -- 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/899669 Title: Screen Corruption and crash after Gnome Shell login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/899669/+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
[Ubuntu-x-swat] [Bug 899669] Re: Screen Corruption and crash after Gnome Shell login
This screenshot shows the garbage accumulating at the top of the screen when I continue working and e.g. typing text into Firefox. ** Attachment added: Screenshot at 2011-11-26 10:33:13.jpg https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/899669/+attachment/2618123/+files/Screenshot%20at%202011-11-26%2010%3A33%3A13.jpg -- 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/899669 Title: Screen Corruption and crash after Gnome Shell login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/899669/+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
[Ubuntu-x-swat] [Bug 781384] Re: active/inactive window decorations are wrong, do not update (only fglrx)
Can someone please mark this as effecting Unity-window-decorator? I can't figure it out right now . But I'm afraid if I don't leave this comment, I'll forget again. ** Also affects: compiz Importance: Undecided Status: New ** No longer affects: compiz -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/781384 Title: active/inactive window decorations are wrong, do not update (only fglrx) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/781384/+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
[Ubuntu-x-swat] [Bug 899341] Re: Lubuntu Pangolin A1 install boots to black screen
Bryce, thanks for looking at this. based on what you said, Installed lubuntu pangolin A1 from alternate CD on another partition. Worked fine. Original CD Live lubuntu pangolin A1 checked out O.K. on check disk for defects. Installed original CD live lubuntu pangolin A1 on another partition, same size. Working fine now. The bug must have been a fluke. (this is alpha time...) Can't reproduce the bug since it's working O.K. now. Thanks, Jerry -- 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/899341 Title: Lubuntu Pangolin A1 install boots to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/899341/+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
[Ubuntu-x-swat] [Bug 781384] Re: active/inactive window decorations are wrong, do not update (only fglrx)
** Also affects: unity-window-decorator Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/781384 Title: active/inactive window decorations are wrong, do not update (only fglrx) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-window-decorator/+bug/781384/+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
[Ubuntu-x-swat] [Bug 780358] Re: Random X crashes in Ubuntu 11.04
*** This bug is a duplicate of bug 774978 *** https://bugs.launchpad.net/bugs/774978 @ Taylor Do you mind sharing with us which plugins were problematic? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/780358 Title: Random X crashes in Ubuntu 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/780358/+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
[Ubuntu-x-swat] [Bug 888872] Re: Unity 3D desktop crashes in Oneiric using ATI Mobility Radeon X1600
@ Phil. V (philip.v) I found that LIBGL_DEBUG=verbose glxinfo reports some errors: libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/tls/r300_dri.so libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/r300_dri.so libGL: Can't open configuration file /etc/drirc: No such file or directory. libGL: Can't open configuration file /home/user/.drirc: No such file or directory. libGL: Can't open configuration file /etc/drirc: No such file or directory. libGL: Can't open configuration file /home/user/.drirc: No such file or directory. I did some digging around and found that http://dri.freedesktop.org/wiki/glxinfo mentions Surrounding these lines there may be additional messages indicating errors. In particular, if the driver is not found in the mentioned path, OpenGL will try to fall back to the software renderer called swrast_dri.so. This is an indication that the DRI drivers are not installed correctly. So it seems, although I don't know if it's related to the problem at hand, Ubuntu has a problem correctly installing DRI drivers. If it's not related I could open a bug on the matter. glxinfo | grep render direct rendering: Yes OpenGL renderer string: Gallium 0.4 on ATI RV530 GL_NV_conditional_render, GL_ARB_draw_elements_base_vertex, uname -r 3.0.0-13-generic -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/72 Title: Unity 3D desktop crashes in Oneiric using ATI Mobility Radeon X1600 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/72/+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
[Ubuntu-x-swat] [Bug 899725] [NEW] [945GM] After upgrading to Natty, intel driver won't load
Public bug reported: I've got a Mac Mini 1,1. lspci says 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) Maverick worked perfectly. After upgrading to Natty, X only starts with fbdev, not with the intel driver. Here are the relevant lines (in my opinion) of Xorg.0.log. Will post more info if needed: [ 53203.968] (II) LoadModule: intel [ 53203.968] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so [ 53203.969] (II) Module intel: vendor=X.Org Foundation [ 53203.969]compiled for 1.9.2.901, module version = 2.14.0 [ 53203.969]Module class: X.Org Video Driver [ 53203.969]ABI class: X.Org Video Driver, version 8.0 [ 53203.969] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge [ 53203.970] (--) using VT number 8 [ 53203.976] drmOpenDevice: node name is /dev/dri/card0 [ 53203.977] drmOpenDevice: open result is 9, (OK) [ 53203.977] drmOpenByBusid: Searching for BusID pci::00:02.0 [ 53203.977] drmOpenDevice: node name is /dev/dri/card0 [ 53203.977] drmOpenDevice: open result is 9, (OK) [ 53203.977] drmOpenByBusid: drmOpenMinor returns 9 [ 53203.977] drmOpenByBusid: Interface 1.4 failed, trying 1.1 [ 53203.977] drmOpenByBusid: drmGetBusid reports [ 53203.977] drmOpenDevice: node name is /dev/dri/card1 [ 53203.982] drmOpenByBusid: drmOpenMinor returns -1 [ 53203.982] drmOpenDevice: node name is /dev/dri/card2 [ 53203.987] drmOpenByBusid: drmOpenMinor returns -1 [ 53203.987] drmOpenDevice: node name is /dev/dri/card3 [ 53203.992] drmOpenByBusid: drmOpenMinor returns -1 [ 53203.992] drmOpenDevice: node name is /dev/dri/card4 [ 53203.998] drmOpenByBusid: drmOpenMinor returns -1 [ 53203.998] drmOpenDevice: node name is /dev/dri/card5 [ 53204.003] drmOpenByBusid: drmOpenMinor returns -1 [ 53204.003] drmOpenDevice: node name is /dev/dri/card6 [ 53204.008] drmOpenByBusid: drmOpenMinor returns -1 [ 53204.008] drmOpenDevice: node name is /dev/dri/card7 [ 53204.014] drmOpenByBusid: drmOpenMinor returns -1 [ 53204.014] drmOpenDevice: node name is /dev/dri/card8 [ 53204.019] drmOpenByBusid: drmOpenMinor returns -1 [ 53204.019] drmOpenDevice: node name is /dev/dri/card9 [ 53204.024] drmOpenByBusid: drmOpenMinor returns -1 [ 53204.024] drmOpenDevice: node name is /dev/dri/card10 [ 53204.030] drmOpenByBusid: drmOpenMinor returns -1 [ 53204.030] drmOpenDevice: node name is /dev/dri/card11 [ 53204.035] drmOpenByBusid: drmOpenMinor returns -1 [ 53204.035] drmOpenDevice: node name is /dev/dri/card12 [ 53204.040] drmOpenByBusid: drmOpenMinor returns -1 [ 53204.040] drmOpenDevice: node name is /dev/dri/card13 [ 53204.046] drmOpenByBusid: drmOpenMinor returns -1 [ 53204.046] drmOpenDevice: node name is /dev/dri/card14 [ 53204.051] drmOpenByBusid: drmOpenMinor returns -1 [ 53204.051] drmOpenDevice: node name is /dev/dri/card15 [ 53204.056] drmOpenByBusid: drmOpenMinor returns -1 [ 53204.056] drmOpenDevice: node name is /dev/dri/card0 [ 53204.056] drmOpenDevice: open result is 9, (OK) [ 53204.056] drmOpenDevice: node name is /dev/dri/card0 [ 53204.056] drmOpenDevice: open result is 9, (OK) [ 53204.056] drmGetBusid returned '' [ 53204.056] (EE) intel(0): [drm] failed to set drm interface version. [ 53204.057] (EE) intel(0): Failed to become DRM master. [ 53204.057] (==) intel(0): Depth 24, (--) framebuffer bpp 32 [ 53204.057] (==) intel(0): RGB weight 888 [ 53204.057] (==) intel(0): Default visual is TrueColor [ 53204.057] (**) intel(0): Option Tiling False [ 53204.057] (II) intel(0): Integrated Graphics Chipset: Intel(R) 945GM [ 53204.057] (--) intel(0): Chipset: 945GM [ 53204.057] (**) intel(0): Tiling disabled [ 53204.057] (**) intel(0): SwapBuffers wait enabled [ 53204.057] (==) intel(0): video overlay key set to 0x101fe [ 53204.057] (EE) intel(0): failed to get resources: Bad file descriptor [ 53204.057] (II) UnloadModule: intel [ 53204.057] (EE) Screen(s) found, but none have a usable configuration. [ 53204.057] Fatal server error: [ 53204.057] no screens found ** Affects: xserver-xorg-video-intel (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/899725 Title: [945GM] After upgrading to Natty, intel driver won't load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/899725/+subscriptions ___ Mailing list:
[Ubuntu-x-swat] [Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
@Seth Thanks for the driver on post #466. for over a year now I've been using the imps hack in /etc/modprobe.d With this, I am even now able to use touchpad indicator as it correctly sees the touchpad as a touchpad and not a ps2 mouse. Thank you!!! I'm running Ubuntu 11.04 on an Acer TimelineX 3820TG. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/550625 Title: Alps touchpad is recognized but synaptics clients and scrolling do not work To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/550625/+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
[Ubuntu-x-swat] [Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
@Seth, has your patch been included in the Ubuntu kernel 3.0.0-13? If not, will it be available in a Ubuntu kernel prior to 3.2? Thank you. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/550625 Title: Alps touchpad is recognized but synaptics clients and scrolling do not work To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/550625/+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 899341] Re: Lubuntu Pangolin A1 install boots to black screen
On Sat, Dec 03, 2011 at 07:10:01PM -, jerrylamos wrote: Bryce, thanks for looking at this. based on what you said, Installed lubuntu pangolin A1 from alternate CD on another partition. Worked fine. Original CD Live lubuntu pangolin A1 checked out O.K. on check disk for defects. Installed original CD live lubuntu pangolin A1 on another partition, same size. Working fine now. The bug must have been a fluke. (this is alpha time...) Can't reproduce the bug since it's working O.K. now. Thanks, Jerry Good to hear Jerry, thanks for following up. ___ 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 892967] Re: LibreOffice main screen has graphical corruption
I am having the same issue. Just updated to LibreOffice 3.4.4 OOO340m1 (Build:402). Ubuntu 11.10 Memory 3.6 GiB Processor Intel Core i5 CPU M 560@2.67GHzx 4 Graphics Intel Ironlake Mobile 64-bit ** Attachment added: LibreOffice Main Screen Corrupted https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/892967/+attachment/2618604/+files/Screenshot%20at%202011-12-03%2020%3A24%3A05.png -- 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/892967 Title: LibreOffice main screen has graphical corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/892967/+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
[Ubuntu-x-swat] [Bug 892544] Re: Unity slow after resume from suspend
I don't think the fix for bug 861061 will help you, but I will be making it available for testing some time today. So check back soon :) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/892544 Title: Unity slow after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/892544/+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
[Ubuntu-x-swat] [Bug 737755] Re: Natty: Cannot boot with proprietary NVIDIA driver for GeForce 8800 GT.
[Expired for nvidia-graphics-drivers (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/737755 Title: Natty: Cannot boot with proprietary NVIDIA driver for GeForce 8800 GT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/737755/+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
[Ubuntu-x-swat] [Bug 899590] Re: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
*** This bug is a duplicate of bug 601447 *** https://bugs.launchpad.net/bugs/601447 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 601447, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 601447 package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build [Error: kernel includes at ... do not match current kernel. they are versioned as instead of 2.6.32-23-generic. you might need to adjust your symlinks: ...] -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/899590 Title: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/899590/+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
[Ubuntu-x-swat] [Bug 601447] Re: package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build [Error: kernel includes at ... do not match current kernel. they are ve
** Summary changed: - package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build: kernel includes versioned as instead of 2.6.32-23-generic + package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build [Error: kernel includes at ... do not match current kernel. they are versioned as instead of 2.6.32-23-generic. you might need to adjust your symlinks: ...] -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/601447 Title: package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build [Error: kernel includes at ... do not match current kernel. they are versioned as instead of 2.6.32-23-generic. you might need to adjust your symlinks: ...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/601447/+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
[Ubuntu-x-swat] [Bug 868400] Re: Synaptics touchpad stops working
Hi All, For the last couple of weeks I worked around this bug by assigning the keyboard shortcut CTRL-F9 to the command: synclient TouchpadOff=0 but tonight that didn't work. I even typed that in at the terminal window to no avail. So then I went and got a USB mouse and when I connected it and clicked and moved around I found the touch pad worked again. I find that the bug often occurs just after booting up, or resuming. Rob -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/868400 Title: Synaptics touchpad stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/868400/+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
[Ubuntu-x-swat] [Bug 798868] Re: unity video tearing when moving windows in oneiric with nvidia-current
Experimental fixes for this and related performance bugs are now available for testing in ppa:vanvugt/compiz and ppa:vanvugt/unity. For the best results I recommend trying both together. But testing them individually is useful too. IMPORTANT NOTES: * The fixes in ppa:vanvugt/compiz REQUIRE that Sync To VBlank is ENABLED in CompizConfig Settings Manager (OpenGL section). This is the default setting when Ubuntu 11.10 is installed. * When using ppa:vanvugt/compiz you should DISABLE the workaround Force full screen redraws (buffer swap) on repaint in CompizConfig Settings Manager (Workarounds section). This is the default setting when Ubuntu 11.10 is installed. * I don't claim to have fixed all tearing. I only claim that the amount of tearing in oneiric with the fix is no longer worse than in natty. * nouveau: If you are using the nouveau driver for NVIDIA chips you will need to enable sync-to-vblank support in the driver options because nouveau has it disabled by default. You can do this by editing /etc/X11/xorg.conf and adding: Section Device Identifier My Graphics Option GLXVBlank on EndSection Then log out and in again for it to take effect. * fglrx (Catalyst): The fglrx driver also disables sync-to-vBlank support by default. To fix this: 1. Open Catalyst Control Center. 2. Go to 3D More Settings. 3. Set Wait for vertical refresh to On, unless application specifies. * Please don't try using the Benchmark plugin in compiz-plugins-extra because it is broken and misleading (bug 898548). Please leave feedback in the relevant bug reports. - Daniel --- ppa:vanvugt/compiz | https://launchpad.net/~vanvugt/+archive/compiz compiz (1:0.9.6+bzr20110929-0ubuntu6vv2) oneiric * Added proposed fix for inaccurate frame timing causing tearing and stuttering. (LP: #880707) (LP: #888039) (LP: #92599) (LP: #798868) (LP: #876575) ppa:vanvugt/unity | https://launchpad.net/~vanvugt/+archive/unity unity (4.24.0-0ubuntu2b1vv4) oneiric; urgency=low * Fix major performance regressions due to unnecessary UnityFBO binding (LP: #861061) (LP: #880707) UnityFBO was being bound even when not required. This caused major lag in glPaintOutput, which slowed down all rendering. This was seen in reduced framerates in apps (LP: #861061) and significantly worse screen tearing with Unity 4.x compared to 3.x (LP: #880707). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/798868 Title: unity video tearing when moving windows in oneiric with nvidia-current To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/798868/+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
[Ubuntu-x-swat] [Bug 92599] Re: Incorrect (low/stuttering) refresh rate with NVIDIA driver
Experimental fixes for this and related performance bugs are now available for testing in ppa:vanvugt/compiz and ppa:vanvugt/unity. For the best results I recommend trying both together. But testing them individually is useful too. IMPORTANT NOTES: * The fixes in ppa:vanvugt/compiz REQUIRE that Sync To VBlank is ENABLED in CompizConfig Settings Manager (OpenGL section). This is the default setting when Ubuntu 11.10 is installed. * When using ppa:vanvugt/compiz you should DISABLE the workaround Force full screen redraws (buffer swap) on repaint in CompizConfig Settings Manager (Workarounds section). This is the default setting when Ubuntu 11.10 is installed. * I don't claim to have fixed all tearing. I only claim that the amount of tearing in oneiric with the fix is no longer worse than in natty. * nouveau: If you are using the nouveau driver for NVIDIA chips you will need to enable sync-to-vblank support in the driver options because nouveau has it disabled by default. You can do this by editing /etc/X11/xorg.conf and adding: Section Device Identifier My Graphics Option GLXVBlank on EndSection Then log out and in again for it to take effect. * fglrx (Catalyst): The fglrx driver also disables sync-to-vBlank support by default. To fix this: 1. Open Catalyst Control Center. 2. Go to 3D More Settings. 3. Set Wait for vertical refresh to On, unless application specifies. * Please don't try using the Benchmark plugin in compiz-plugins-extra because it is broken and misleading (bug 898548). Please leave feedback in the relevant bug reports. - Daniel --- ppa:vanvugt/compiz | https://launchpad.net/~vanvugt/+archive/compiz compiz (1:0.9.6+bzr20110929-0ubuntu6vv2) oneiric * Added proposed fix for inaccurate frame timing causing tearing and stuttering. (LP: #880707) (LP: #888039) (LP: #92599) (LP: #798868) (LP: #876575) ppa:vanvugt/unity | https://launchpad.net/~vanvugt/+archive/unity unity (4.24.0-0ubuntu2b1vv4) oneiric; urgency=low * Fix major performance regressions due to unnecessary UnityFBO binding (LP: #861061) (LP: #880707) UnityFBO was being bound even when not required. This caused major lag in glPaintOutput, which slowed down all rendering. This was seen in reduced framerates in apps (LP: #861061) and significantly worse screen tearing with Unity 4.x compared to 3.x (LP: #880707). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/92599 Title: Incorrect (low/stuttering) refresh rate with NVIDIA driver To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/92599/+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
[Ubuntu-x-swat] [Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
** Also affects: touchpad-indicator Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/550625 Title: Alps touchpad is recognized but synaptics clients and scrolling do not work To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/550625/+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
[Ubuntu-x-swat] [Bug 553789]
Created attachment 39004 ./peek 10a000 1000 after and before the crash 07:00.0 VGA compatible controller: nVidia Corporation Device 0a65 (rev a2) here are my dumps note that before is actually after reboot - don't know how to capture right before the freeze -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
*** Bug 30817 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
Created attachment 39589 Before and after peek 10a000 on ION2 Here are 3 more peeks, before and after, using a different chipset as you said that might be interesting to you. 01:00.0 VGA compatible controller: nVidia Corporation GT218 [ION] (rev a2) (prog-if 00 [VGA controller]) Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at fd00 (32-bit, non-prefetchable) [size=16M] Memory at d000 (64-bit, prefetchable) [size=256M] Memory at ce00 (64-bit, prefetchable) [size=32M] I/O ports at dc00 [size=128] Expansion ROM at fe98 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 ? Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting ? Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 ? Kernel driver in use: nouveau I do see messages in the kernel, but as you mentioned it's a separate bug. They appear inconsistently during this failure. [drm] nouveau :01:00.0: PFIFO_DMA_PUSHER - Ch 2 and sometimes also: [drm] nouveau :01:00.0: PGRAPH_DATA_ERROR - Ch 2/2 Class 0x502d Mthd 0x0240 Data 0x:0x00086184 [drm] nouveau :01:00.0: PGRAPH_DATA_ERROR - INVALID_VALUE This is on openSUSE Factory, kernel 2.6.36-rc4 xorg-x11-server-7.5_1.9.0.902-69.3.x86_64 xorg-x11-driver-video-nouveau-0.0.16_20101010_8c8f15c-14.1.x86_64 libdrm-2.4.22-27.2.x86_64 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
Jeff, please try whether it is valid with packages from home:jobermayr. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
(In reply to comment #40) Jeff, please try whether it is valid with packages from home:jobermayr. I'm afraid so. Same symptoms. Is another dump needed or are the ones I've provided already sufficient? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
(In reply to comment #3) However, according to mwk, the data error is unlikely to be related to the hangs. Also he believes he might have the same problem using recent nouveau code. To confirm that, he would like to know the value of the 400700 register next time the machine hangs : $ wget http://0x04.net/~mwk/pgtest/{peek.c,libio.{c,h}} $ gcc peek.c libio.c -lpciaccess -o peek # ./peek 0x400700 Landed here from bug 33357 that might be a duplicate of this one. For n00bs like me the commands have changed a bit, I managed to figure out the first one to be: $ wget http://0x04.net/cgit/index.cgi/pgtest/{peek.c,libio.{c,h}} The second one gives me the following: $ gcc peek.c libio.c -lpciaccess -o peek peek.c:1:1: error: expected identifier or ‘(’ before ‘’ token peek.c:3:13: warning: character constant too long for its type peek.c:3:53: warning: multi-character character constant peek.c:3:63: warning: multi-character character constant peek.c:6:12: warning: character constant too long for its type peek.c:6:32: warning: character constant too long for its type peek.c:7:12: warning: character constant too long for its type peek.c:7:29: warning: character constant too long for its type peek.c:8:11: warning: character constant too long for its type peek.c:8:29: warning: character constant too long for its type peek.c:8:45: warning: character constant too long for its type peek.c:9:11: warning: character constant too long for its type peek.c:9:29: warning: character constant too long for its type peek.c:9:46: warning: character constant too long for its type peek.c:9:106: warning: character constant too long for its type peek.c:12:9: warning: multi-character character constant peek.c:12:26: warning: character constant too long for its type peek.c:14:11: warning: multi-character character constant peek.c:14:38: warning: character constant too long for its type peek.c:14:66: warning: character constant too long for its type peek.c:14:87: warning: character constant too long for its type peek.c:15:11: warning: multi-character character constant peek.c:15:26: warning: character constant too long for its type peek.c:15:66: warning: character constant too long for its type peek.c:15:80: warning: character constant too long for its type peek.c:15:131: warning: multi-character character constant peek.c:15:151: warning: multi-character character constant peek.c:15:164: error: empty character constant peek.c:16:27: warning: character constant too long for its type peek.c:17:23: warning: character constant too long for its type peek.c:17:37: error: empty character constant peek.c:17:46: warning: character constant too long for its type peek.c:18:15: warning: multi-character character constant peek.c:18:46: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘this’ peek.c:18:56: warning: character constant too long for its type peek.c:19:16: warning: character constant too long for its type peek.c:19:1: error: stray ‘\305’ in program peek.c:19:1: error: stray ‘\233’ in program peek.c:20:14: warning: multi-character character constant peek.c:21:10: warning: character constant too long for its type peek.c:21:24: warning: character constant too long for its type peek.c:21:69: warning: character constant too long for its type peek.c:21:116: warning: character constant too long for its type peek.c:21:161: warning: character constant too long for its type peek.c:21:208: warning: character constant too long for its type peek.c:21:259: warning: character constant too long for its type peek.c:21:306: warning: character constant too long for its type peek.c:21:362: warning: multi-character character constant peek.c:21:381: warning: character constant too long for its type peek.c:21:396: warning: multi-character character constant peek.c:21:409: warning: character constant too long for its type peek.c:22:14: warning: multi-character character constant peek.c:23:15: warning: multi-character character constant peek.c:24:15: warning: character constant too long for its type peek.c:25:15: warning: character constant too long for its type peek.c:27:14: warning: multi-character character constant peek.c:27:25: warning: multi-character character constant peek.c:27:37: warning: multi-character character constant peek.c:27:57: error: empty character constant peek.c:28:13: warning: character constant too long for its type peek.c:28:28: warning: character constant too long for its type peek.c:31:12: warning: character constant too long for its type peek.c:31:33: warning: character constant too long for its type peek.c:33:12: warning: character constant too long for its type peek.c:33:42: error: too many decimal points in number libio.c:1:1: error: expected identifier or ‘(’ before ‘’ token libio.c:3:13: warning: character constant too long for its type libio.c:3:53: warning: multi-character character constant libio.c:3:63: warning: multi-character character constant libio.c:6:12: warning: character constant too long for its
[Ubuntu-x-swat] [Bug 553789]
I'd say the current instructions to build the peek (and other utilities) are: git clone git://0x04.net/pgtest cd pgtest make -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
I have a GT220 and sometimes freezes randomly: [ 3675.146] Backtrace: [ 3675.153] 0: /usr/bin/X (xorg_backtrace+0x28) [0x460d18] [ 3675.153] 1: /usr/bin/X (0x40+0x63509) [0x463509] [ 3675.153] 2: /lib64/libc.so.6 (0x34eca0+0x32a20) [0x34eca32a20] [ 3675.153] 3: /usr/lib64/xorg/modules/extensions/libdri2.so (DRI2CloseScreen+0x24) [0x7fb95ba39a14] [ 3675.153] 4: /usr/lib64/xorg/modules/drivers/nouveau_drv.so (0x7fb95b809000+0xd6ab) [0x7fb95b8166ab] [ 3675.154] 5: /usr/bin/X (0x40+0xa3b49) [0x4a3b49] [ 3675.154] 6: /usr/bin/X (0x40+0x15daec) [0x55daec] [ 3675.154] 7: /usr/bin/X (0x40+0x2193c) [0x42193c] [ 3675.154] 8: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x34eca1ec5d] [ 3675.154] 9: /usr/bin/X (0x40+0x21449) [0x421449] [ 3675.154] Segmentation fault at address 0x10 [ 3675.154] Fatal server error: [ 3675.154] Caught signal 11 (Segmentation fault). Server aborting [ 3675.154] [ 3675.154] Please consult the Fedora Project support at http://bodhi.fedoraproject.org/ for help. [ 3675.154] Please also check the log file at /var/log/Xorg.0.log for additional information. [ 3675.154] [ 3675.157] (II) NOUVEAU(0): NVLeaveVT is called. That error is a bit old. Ok, i read about the random lockus some time ago. The interesting thing is that at some point i started to use (i still do) use the nVIDIA (P)drivers, and to my surprise, it also has random gpu lockus (granted, it is another piece of software) But when i put my new ati HD5670 and found to also random freeze... I run F13. I never had issues with Slackware 13.1 and nvidia(P). The OtherOS never freezed. with any card. For F13 i must use pcie_aspm=off, because of issues with the sata controller. But pcie_aspm=off also seems to set the pcie bus into gen1, (it halves the link speed and the de-emphasys, and also changes. I do not know if it is normal to pcie_aspm=off to do that and other thins that do. For example the nvidia(p) report that the card is at gen1 speed. (the mb is Gen2 and the card is also Gen2) M4N72-E Is expected for the nouvau driver to work with any pcie configuration, different link/speed aspm/no_aspm/ ? I know that it may not be related, but i do not know if subtle different pcie configurations (or pcie driver bugs) may lead to the vga to behave in that way. Thanks in advance. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
Created attachment 43519 before and after peek on nv40 from Lenovo T410 Here is peek before and after free, on kernel 2.6.38rc5, on Lenovo T410 laptop with integrated nividia GPU: 01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 2142 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at cc00 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at d000 (64-bit, prefetchable) [size=256M] Region 3: Memory at ce00 (64-bit, prefetchable) [size=32M] Region 5: I/O ports at 2000 [size=128] [virtual] Expansion ROM at cd00 [disabled] [size=512K] Capabilities: access denied Kernel driver in use: nouveau -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
My Xorg was also blocking - only the mouse pointer keeps moving, but no other thing happends. I solved the problem (for now), by removing the comment for the option NoAccel and setting the value to true. I'm using the xorg.conf generated with Xorg -configure with just that change, and everything seem to be working. I'm even using the composite from xfce4 (for the real transparent xfce4-terminal), and it's working ok - maybe not as fast as with accelaration. For me it was very simple to reproduce the error. As soon as gdm was active (the default theme on debian - the one with the stars and the star rocket), a click on any menu would block everything but the mouse movement. Here is the log for my X when it was blocking. Anything else I can do to help solve this? X.Org X Server 1.9.4 Release Date: 2011-02-04 [ 147.356] X Protocol Version 11, Revision 0 [ 147.356] Build Operating System: Linux 2.6.32.28-dsa-ia32 i686 Debian [ 147.356] Current Operating System: Linux voyager 2.6.37-1-686 #1 SMP Tue Feb 15 18:21:50 UTC 2011 i686 [ 147.356] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.37-1-686 root=UUID=b69dfdff-c215-473f-9f91-1680b2773ef1 ro single [ 147.356] Build Date: 17 February 2011 01:25:01AM [ 147.356] xorg-server 2:1.9.4-2 (Cyril Brulebois k...@debian.org) [ 147.356] Current version of pixman: 0.21.4 [ 147.356]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 147.356] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 147.356] (==) Log file: /var/log/Xorg.0.log, Time: Fri Feb 18 03:17:25 2011 [ 147.356] (==) Using config file: /etc/X11/xorg.conf [ 147.356] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 147.373] (==) ServerLayout X.org Configured [ 147.373] (**) |--Screen Screen0 (0) [ 147.373] (**) | |--Monitor Monitor0 [ 147.374] (**) | |--Device Card0 [ 147.374] (**) |--Input Device Mouse0 [ 147.374] (**) |--Input Device Keyboard0 [ 147.374] (==) Automatically adding devices [ 147.374] (==) Automatically enabling devices [ 147.452] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 147.452]Entry deleted from font path. [ 147.541] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 147.541]Entry deleted from font path. [ 147.541] (**) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins, /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins [ 147.541] (**) ModulePath set to /usr/lib/xorg/modules [ 147.541] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. [ 147.541] (WW) Disabling Mouse0 [ 147.541] (II) Loader magic: 0x81f7140 [ 147.541] (II) Module ABI versions: [ 147.541]X.Org ANSI C Emulation: 0.4 [ 147.541]X.Org Video Driver: 8.0 [ 147.541]X.Org XInput driver : 11.0 [ 147.541]X.Org Server Extension : 4.0 [ 147.542] (--) PCI:*(0:2:0:0) 10de:086f:1043:16b2 rev 177, Mem @ 0xfd00/16777216, 0xe000/268435456, 0xde00/33554432, I/O @ 0xdc00/128, BIOS @ 0x/131072 [ 147.542] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) [ 147.542] (II) extmod will be loaded. This was enabled by default and also specified in the config file. [ 147.542] (II) dbe will be loaded. This was enabled by default and also specified in the config file. [ 147.542] (II) glx will be loaded. This was enabled by default and also specified in the config file. [ 147.542] (II) record will be loaded. This was enabled by default and also specified in the config file. [ 147.542] (II) dri will be loaded. This was enabled by default and also specified in the config file. [ 147.542] (II) dri2 will be loaded. This was enabled by default and also specified in the config file. [ 147.542] (II) LoadModule: dri [ 147.592] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so [ 147.624] (II) Module dri: vendor=X.Org Foundation [ 147.624]compiled for 1.9.4, module version = 1.0.0 [ 147.624]ABI class: X.Org Server Extension, version 4.0 [ 147.624] (II) Loading extension XFree86-DRI [ 147.624] (II) LoadModule: dri2 [ 147.624] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so [ 147.631] (II) Module dri2:
[Ubuntu-x-swat] [Bug 553789]
*** Bug 33357 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
Is there anything the non-programmer can do t -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
FWIW you can see a peek of my frozen nVidia Corporation GT216 [GeForce GT 230M] (rev a2) at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/553789/+attachment/1863113/+files/peek-696104.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
Created attachment 43864 peek_10a000_1000-tschwinge.tar.bz2 Marcin, in case you need further data, see the peek_10a000_1000-tschwinge.tar.bz2 which I'm just attaching. The files' names should be explanatory. I ran each of the invokations three times. I will now switch to using nouveau.noaccel=1, but please tell if you need further data or need something tested. This system is a DELL PRECISION M4500, the graphics card's lspci output: 01:00.0 VGA compatible controller: nVidia Corporation GT216 [Quadro FX 880M] (rev a2) I hit this while setting up the system, roughly one hour after finishing a fresh Ubuntu 10.10 maverick installation, while browsing in Firfox some web pages about how to get suspend / hibernate / resume working reliably -- oh the joy of installing GNU/Linux systems on new hardware. :-) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
I have been using the git sources for two weeks, and updated to 2.6.39 yesterday: since somewhere after 25c68aef4e6abcc3c10f593fc565c342ebe2ded8 the lockups disappeared - and I hope they wont return. great work, thank you -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
I am sorry, the last comment was probably unclear: Hardware: Thinkpad T410, NVS 3100M (nva8?) Kernel: vanilla 2.6.39+ from kernel.org + nouveau tree merged -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
For anyone still experiencing this bug, here is a possible workaround (thanks to ColdFeetBob for pointing it out) Modify* /xserver/mi/mieq.c and rebuild xserver * Increase the #define QUEUE_SIZE 512 to 1024, 2048 or 4096 [1] Note that this is *not* a proper fix as you can see in the discussion [2], and it isn't recommended for unexperienced users [1] http://www.nvnews.net/vbulletin/showpost.php?p=2398370postcount=2 [2] https://bugs.freedesktop.org/show_bug.cgi?id=15473 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
I can confirm I didn't had any freeze using 2.6.39 kernel on Lenovo T410 for 3 days (I had several freezes per hour before), using GNOME Shell. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
(In reply to comment #54) I can confirm I didn't had any freeze using 2.6.39 kernel on Lenovo T410 for 3 days (I had several freezes per hour before), using GNOME Shell. Frederic, you forgot to mention that it's now terribly unstable. I have regular crashes like below, especially on: VT switching, Suspend-to-RAM, etc. Details: (II) NOUVEAU(0): NVLeaveVT is called. Backtrace: 0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x45de88] 1: /usr/bin/Xorg (0x40+0x62449) [0x462449] 2: /lib64/libpthread.so.0 (0x7fc7e6fb2000+0xefc0) [0x7fc7e6fc0fc0] 3: /lib64/libc.so.6 (0x7fc7e5f0+0x7427c) [0x7fc7e5f7427c] 4: /lib64/libc.so.6 (__libc_malloc+0x70) [0x7fc7e5f76600] 5: /usr/lib64/X11/modules/libexa.so (0x7fc7e3297000+0x8d44) [0x7fc7e329fd44] 6: /usr/lib64/X11/modules/libexa.so (0x7fc7e3297000+0x53c2) [0x7fc7e329c3c2] 7: /usr/bin/Xorg (0x40+0xa4a20) [0x4a4a20] 8: /usr/bin/Xorg (ChangeWindowAttributes+0x2e3) [0x455e23] 9: /usr/bin/Xorg (0x40+0x27c38) [0x427c38] 10: /usr/bin/Xorg (0x40+0x2db61) [0x42db61] 11: /usr/bin/Xorg (0x40+0x215ce) [0x4215ce] 12: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7fc7e5f1ec5d] 13: /usr/bin/Xorg (0x40+0x21179) [0x421179] Segmentation fault at address (nil) Fatal server error: Caught signal 11 (Segmentation fault). Server aborting -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
(In reply to comment #55) (In reply to comment #54) I can confirm I didn't had any freeze using 2.6.39 kernel on Lenovo T410 for 3 days (I had several freezes per hour before), using GNOME Shell. Frederic, you forgot to mention that it's now terribly unstable. I have regular crashes like below, especially on: VT switching, Suspend-to-RAM, etc. Details: (II) NOUVEAU(0): NVLeaveVT is called. Not even remotely related. And from the backtrace, probably not nouveau's fault either. Backtrace: 0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x45de88] 1: /usr/bin/Xorg (0x40+0x62449) [0x462449] 2: /lib64/libpthread.so.0 (0x7fc7e6fb2000+0xefc0) [0x7fc7e6fc0fc0] 3: /lib64/libc.so.6 (0x7fc7e5f0+0x7427c) [0x7fc7e5f7427c] 4: /lib64/libc.so.6 (__libc_malloc+0x70) [0x7fc7e5f76600] 5: /usr/lib64/X11/modules/libexa.so (0x7fc7e3297000+0x8d44) [0x7fc7e329fd44] 6: /usr/lib64/X11/modules/libexa.so (0x7fc7e3297000+0x53c2) [0x7fc7e329c3c2] 7: /usr/bin/Xorg (0x40+0xa4a20) [0x4a4a20] 8: /usr/bin/Xorg (ChangeWindowAttributes+0x2e3) [0x455e23] 9: /usr/bin/Xorg (0x40+0x27c38) [0x427c38] 10: /usr/bin/Xorg (0x40+0x2db61) [0x42db61] 11: /usr/bin/Xorg (0x40+0x215ce) [0x4215ce] 12: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7fc7e5f1ec5d] 13: /usr/bin/Xorg (0x40+0x21179) [0x421179] Segmentation fault at address (nil) Fatal server error: Caught signal 11 (Segmentation fault). Server aborting -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
I didn't forgot anything : nouveau is rock stable with 2.6.39.x kernel on my T410 (no issue with VT switch. I didn't test suspend-to-ram). Your issues are a different bug, I think (X crash, no gpu lockup). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
Uuggh, this seems to be a serious problem, even when using nvidia.ko. Why? Because xorg seems to probe drivers on startup, and somehow managing to load the nouveau module even when I want to use the nvidia module. The nouveau module then fails to unload properly (use count is always at least 1, and stays 1 even after changing to runlevel 3 and killing xorg). I could reliably hang the system just by logging out from kdm. Syslog is full of nouveau problems - why, given that I am using nvidia? When renaming all instances of nouveau.ko under /lib/modules the hangs disappeared. This has always been there and seems to have zilch effect: ls -l /etc/modprobe.d/nvidia.conf -rw-r--r-- 1 root root 18 2011-04-29 22:55 /etc/modprobe.d/nvidia.conf cat /etc/modprobe.d/nvidia.conf blacklist nouveau Symptoms are random freezes requiring a hardware reset, but always involving some graphics operation. I can detect no other hardware malfunction, and lockup behaviour is not characteristic of general hardware faults (e.g. ram, cpu, disk). My reset button is really polished now ;-(( System details: openSUSE 11.4 with all updates installed, currently that is kernel kernel-desktop-2.6.37.6-0.5.1.x86_64 xorg-x11-server-7.6_1.9.3-15.24.2.x86_64 The problem seems worse with kernel-desktop-2.6.39.2-36.1.x86_64 01:00.0 VGA compatible controller: nVidia Corporation GT216 [GeForce GT 220] (rev a2) Mobo is Gigabyte GA-880GA-UD3H with NB/SB: AMD 880G / SB850 USB 2.0 + 3.0, SATA 3Gb + 6Gb (prob not relevant) The chipset also contains an integrated ATI Radeon HD 4250 (which works fine on the OSS radeon driver, with the limits of the driver). Phenom II X6 1090T CPU -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
(In reply to comment #58) Uuggh, this seems to be a serious problem, even when using nvidia.ko. Why? Because xorg seems to probe drivers on startup, and somehow managing to load the nouveau module even when I want to use the nvidia module. The nouveau module then fails to unload properly (use count is always at least 1, and stays 1 even after changing to runlevel 3 and killing xorg). Your problem has nothing to do with this bug report. You are (or the X server is) trying to use nouveau and nvidia drivers at the same time, which is known to cause havoc and should not be attempted. All the fallout you described fits perfectly. The simple fix for you is to define Driver nvidia in your xorg.conf. That prevents probing of any drivers and uses only what you want. If you feel there is bad behavior in the X server, when it probes different drivers, you should file a bug against the X server. But first, make sure your distribution has not patched the X server driver probing code, e.g. by adding drivers not present in the original driver list. If they have, you should complain to your distribution. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
On , bugzilla-dae...@freedesktop.org wrote: https://bugs.freedesktop.org/show_bug.cgi?id=26980 --- Comment #58 from Volker Kuhlmann list0...@paradise.net.nz 2011-07-13 04:03:19 PDT --- Uuggh, this seems to be a serious problem, even when using nvidia.ko. Why? Because xorg seems to probe drivers on startup, and somehow managing to load the nouveau module even when I want to use the nvidia module. The nouveau module then fails to unload properly (use count is always at least 1, and stays 1 even after changing to runlevel 3 and killing xorg). I could reliably hang the system just by logging out from kdm. Syslog is full of nouveau problems - why, given that I am using nvidia? When renaming all instances of nouveau.ko under /lib/modules the hangs disappeared. This has always been there and seems to have zilch effect: ls -l /etc/modprobe.d/nvidia.conf -rw-r--r-- 1 root root 18 2011-04-29 22:55 /etc/modprobe.d/nvidia.conf cat /etc/modprobe.d/nvidia.conf blacklist nouveau Symptoms are random freezes requiring a hardware reset, but always involving some graphics operation. I can detect no other hardware malfunction, and lockup behaviour is not characteristic of general hardware faults (eg ram, cpu, disk). My reset button is really polished now ;-(( System details: openSUSE 11.4 with all updates installed, currently that is kernel kernel-desktop-2.6.37.6-0.5.1.x86_64 xorg-x11-server-7.6_1.9.3-15.24.2.x86_64 The problem seems worse with kernel-desktop-2.6.39.2-36.1.x86_64 01:00.0 VGA compatible controller: nVidia Corporation GT216 [GeForce GT 220] (rev a2) Mobo is Gigabyte GA-880GA-UD3H with NB/SB: AMD 880G / SB850 USB 2.0 + 3.0, SATA 3Gb + 6Gb (prob not relevant) The chipset also contains an integrated ATI Radeon HD 4250 (which works fine on the OSS radeon driver, with the limits of the driver). Phenom II X6 1090T CPU Delete nouveau.ko. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
Using 3.0.4, this bug is very much still there (or at least the backgrace looks very similar). Happy to help provide more information or debug if pointed in the right direction. (gdb) bt #0 0x7f5af04f3007 in ioctl () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f5aeea8f878 in drmIoctl (fd=9, request=1074291842, arg=0x7fff50cac510) at /usr/src/debug/x11-libs/libdrm-2.4.26/libdrm-2.4.26/xf86drm.c:167 #2 0x7f5aeea91c2b in drmCommandWrite ( fd=optimized out, drmCommandIndex=optimized out, data=optimized out, size=optimized out) at /usr/src/debug/x11-libs/libdrm-2.4.26/libdrm-2.4.26/xf86drm.c:2422 #3 0x7f5aee44311d in nouveau_bo_wait (bo=0x1b75420, cpu_write=optimized out, no_wait=optimized out, no_block=optimized out) at /usr/src/debug/x11-libs/libdrm-2.4.26/libdrm-2.4.26/nouveau/nouveau_bo.c:390 #4 0x7f5aee443703 in nouveau_bo_map_range ( bo=0x1b75420, delta=0, size=optimized out, flags=4) at /usr/src/debug/x11-libs/libdrm-2.4.26/libdrm-2.4.26/nouveau/nouveau_bo.c:433 #5 0x7f5aee64d2b5 in NVAccelDownloadM2MF ( dst_pitch=3740, dst=0x2c96644 , h=20, w=1, y=optimized out, x=237, pspix=0x29275f0) at /usr/src/debug/x11-drivers/xf86-video-nouveau-0.0.16_pre20110801/xf86-video-nouveau-0.0.16_pre20110801/src/nouveau_exa.c:132 #6 nouveau_exa_download_from_screen (pspix=0x29275f0, x=237, y=348, w=1, h=20, dst=0x2c96644 , dst_pitch=3740) at /usr/src/debug/x11-drivers/xf86-video-nouveau-0.0.16_pre20110801/xf86-video-nouveau-0.0.16_pre20110801/src/nouveau_exa.c:386 #7 0x7f5aed9f81ee in exaCopyDirty ( migrate=optimized out, pValidDst=0x2927680, pValidSrc=0x2927690, transfer=0x7f5aee64cd80 nouveau_exa_download_from_screen, fallback_index=1, sync=0x7f5aed9f69b0 exaWaitSync) at /usr/src/debug/x11-base/xorg-server-1.10.4/xorg-server-1.10.4/exa/exa_migration_classic.c:220 #8 0x7f5aed9fac41 in exaPrepareAccessReg_mixed ( pPixmap=0x29275f0, index=0, pReg=0x0) at /usr/src/debug/x11-base/xorg-server-1.10.4/xorg-server-1.10.4/exa/exa_migration_mixed.c:254 #9 0x7f5aeda061d0 in ExaPrepareCompositeReg ( height=20, width=1, yDst=31, xDst=234, yMask=0, xMask=0, ySrc=0, xSrc=0, pDst=0x28a94e0, pMask=0x0, pSrc=0x28a9e20, op=57 '9', pScreen=optimized out) at /usr/src/debug/x11-base/xorg-server-1.10.4/xorg-server-1.10.4/exa/exa_unaccel.c:600 #10 ExaCheckComposite (op=57 '9', pSrc=0x28a9e20, pMask=0x0, pDst=0x28a94e0, xSrc=0, ySrc=0, xMask=0, yMask=0, xDst=234, yDst=31, width=1, height=20) at /usr/src/debug/x11-base/xorg-server-1.10.4/xorg-server-1.10.4/exa/exa_unaccel.c:625 #11 0x7f5aeda02189 in exaComposite (op=57 '9', pSrc=0x28a9e20, pMask=0x0, pDst=0x28a94e0, xSrc=optimized out, ySrc=optimized out, xMask=0, yMask=0, xDst=optimized out, yDst=optimized out, width=1, height=20) at /usr/src/debug/x11-base/xorg-server-1.10.4/xorg-server-1.10.4/exa/exa_render.c:1066 #12 0x004db50a in damageComposite (op=57 '9', pSrc=0x28a9e20, pMask=0x0, pDst=0x28a94e0, xSrc=0, ySrc=0, xMask=0, yMask=0, xDst=234, yDst=31, width=1, height=20) at /usr/src/debug/x11-base/xorg-server-1.10.4/xorg-server-1.10.4/miext/damage/damage.c:617 #13 0x0056b4a8 in miCompositeRects (op=57 '9', pDst=0x28a94e0, color=optimized out, nRect=optimized out, rects=0x29ebd84) at /usr/src/debug/x11-base/xorg-server-1.10.4/xorg-server-1.10.4/render/mirect.c:168 #14 0x004d47f3 in ProcRenderFillRectangles ( client=0x2595fb0) at /usr/src/debug/x11-base/xorg-server-1.10.4/xorg-server-1.10.4/render/render.c:1481 #15 0x00431aa1 in Dispatch () at /usr/src/debug/x11-base/xorg-server-1.10.4/xorg-serve---Type return to continue, or q return to quit--- r-1.10.4/dix/dispatch.c:431 #16 0x00425a95 in main (argc=optimized out, argv=0x7fff50cacd48, envp=optimized out) at /usr/src/debug/x11-base/xorg-server-1.10.4/xorg-server-1.10.4/dix/main.c:287 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
(In reply to comment #61) Using 3.0.4, this bug is very much still there (or at least the backgrace looks very similar). Happy to help provide more information or debug if pointed in the right direction. Any GPU hang etc will have similar backtraces from X's point of view, and it's not usually useful in itself to see what's happening. Did you have any output in your kernel log from when this occurred? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
(In reply to comment #62) [...] Did you have any output in your kernel log from when this occurred? There was no output after the initial module load messages. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
(In reply to comment #63) (In reply to comment #62) [...] Did you have any output in your kernel log from when this occurred? There was no output after the initial module load messages. Are you able to install envytools (http://nouveau.git.sourceforge.net/git/gitweb.cgi?p=nouveau/envytools;a=summary) and run nvapeek 0x400700 4 while the GPU is hung? Also, how new are all your userspace components (xf86-video-nouveau, libdrm, mesa etc)? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
I experimented this bug not long ago - right now, Im not sure it is exactly the same, since it's not really random but it happens everytime I run Supertux. I recovered the folloving kernel log lines rebooting from another partition after the freeze. kernel 3.0.4, Arch Linux, x86_64, fully updated nouveau-dri 7.11-2 lspci: 01:00.0 VGA compatible controller: nVidia Corporation GT215 [GeForce GT 240] (rev a2) (prog-if 00 [VGA controller]) kernel.log: Sep 11 08:44:25 faye kernel: [ 1297.836589] [drm] nouveau :01:00.0: vm flush timeout: engine 0 Sep 11 08:44:25 faye kernel: [ 1298.301418] [drm] nouveau :01:00.0: PFIFO_INTR 0x0040 - Ch 2 Sep 11 08:44:27 faye kernel: [ 1299.629024] [drm] nouveau :01:00.0: PFIFO_INTR 0x0440 - Ch 2 Sep 11 08:44:27 faye kernel: [ 1300.956673] [drm] nouveau :01:00.0: PFIFO_INTR 0x0440 - Ch 2 Sep 11 08:44:27 faye kernel: [ 1300.956719] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. Sep 11 08:44:29 faye kernel: [ 1302.284342] [drm] nouveau :01:00.0: PFIFO_INTR 0x0040 - Ch 2 Sep 11 08:44:29 faye kernel: [ 1299.632344] [drm] nouveau :01:00.0: vm flush timeout: engine 5 Sep 11 08:44:31 faye kernel: [ 1302.960046] [drm] nouveau :01:00.0: PGRAPH TLB flush idle timeout fail: 0x00c00f01 0x0209 0x1600 0x Sep 11 08:44:32 faye kernel: [ 1303.611794] [drm] nouveau :01:00.0: vm flush timeout: engine 5 Sep 11 08:44:34 faye kernel: [ 1303.615050] [drm] nouveau :01:00.0: vm flush timeout: engine 5 Sep 11 08:44:53 faye kernel: [ 1302.960046] [drm] nouveau :01:00.0: vm flush timeout: engine 0 Sep 11 08:44:53 faye kernel: [ 1305.614198] [drm] nouveau :01:00.0: PFIFO_INTR 0x0040 - Ch 2 Sep 11 08:44:53 faye kernel: [ 1307.613341] [drm] nouveau :01:00.0: PGRAPH TLB flush idle timeout fail: 0x00c00f01 0x0209 0x1600 0x Sep 11 08:44:53 faye kernel: [ 1310.944310] [drm] nouveau :01:00.0: vm flush timeout: engine 5 Sep 11 08:44:53 faye kernel: [ 1307.613341] [drm] nouveau :01:00.0: vm flush timeout: engine 0 Sep 11 08:44:53 faye kernel: [ 1314.940910] [drm] nouveau :01:00.0: PRAMIN flush timeout Sep 11 08:44:53 faye kernel: [ 1310.941070] [drm] nouveau :01:00.0: vm flush timeout: engine 0 Sep 11 08:44:53 faye kernel: [ 1316.266913] [drm] nouveau :01:00.0: vm flush timeout: engine 5 Sep 11 08:44:53 faye kernel: [ 1312.943555] [drm] nouveau :01:00.0: PGRAPH TLB flush idle timeout fail: 0x00c00f01 0x0209 0x1600 0x Sep 11 08:44:53 faye kernel: [ 1312.943555] [drm] nouveau :01:00.0: vm flush timeout: engine 0 Sep 11 08:44:55 faye kernel: [ 1318.264271] [drm] nouveau :01:00.0: PFIFO_INTR 0x04c0 - Ch 2 Sep 11 08:44:55 faye kernel: [ 1322.259717] psmouse.c: resync failed, issuing reconnect request Sep 11 08:44:55 faye kernel: [ 1322.256898] [drm] nouveau :01:00.0: PGRAPH TLB flush idle timeout fail: 0x00c00f01 0x0209 0x1600 0x Sep 11 08:44:55 faye kernel: [ 1322.256898] [drm] nouveau :01:00.0: vm flush timeout: engine 0 Sep 11 08:44:55 faye kernel: [ 1323.596565] [drm] nouveau :01:00.0: PFIFO_INTR 0x0040 - Ch 2 Sep 11 08:44:55 faye kernel: [ 1326.270583] [drm] nouveau :01:00.0: PRAMIN flush timeout Sep 11 08:44:55 faye kernel: [ 1328.923088] hrtimer: interrupt took 2607527851 ns Sep 11 08:44:55 faye kernel: [ 1328.923099] [drm] nouveau :01:00.0: PFIFO_INTR 0x00c0 - Ch 2 Sep 11 08:44:55 faye kernel: [ 1328.926536] [drm] nouveau :01:00.0: vm flush timeout: engine 5 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
(In reply to comment #64) (In reply to comment #63) (In reply to comment #62) [...] Did you have any output in your kernel log from when this occurred? There was no output after the initial module load messages. Are you able to install envytools (http://nouveau.git.sourceforge.net/git/gitweb.cgi?p=nouveau/envytools;a=summary) and run nvapeek 0x400700 4 while the GPU is hung? All I get is a '...'. Also, how new are all your userspace components (xf86-video-nouveau, libdrm, mesa etc)? mesa - 7.11 libdrm - 2.4.26 xf86-video-nouveau - 0.0.16_pre20110801 (that's the Gentoo package, which is presumably a snapshot from that date) For what it's worth, kernel's 3.0.4, and the GPU is a 9400M (PCI id 10de:0863). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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
[Ubuntu-x-swat] [Bug 553789]
This bug was fixed in 2.6.39 ( http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=2b4cebe4e165b0ef30a138e4cf602538dea15583 ), so I'm closing this bug report. ColdFeetBob, Arun Raghavan: you are experiencing different bugs. If you still can reproduce them please read http://nouveau.freedesktop.org/wiki/Bugs and open *new* bug reports. Thanks. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+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