[Bug 966294] Re: gstreamer hangs when accessing webcam (on specific hardware)
Pedro, I'm sure you are experiencing a bug and that you want to report it so that it can be fixed. However, in order to do that, please file a new bug instead of commenting on a bug report for a bug that has already been fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966294 Title: gstreamer hangs when accessing webcam (on specific hardware) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/966294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] Re: [Precise] Installation freezes after Who are you? (Ubiquity hangs in ubi-webcam.py)
migiel, the login/user photo screen is supposed to be _after_ the who are you screen. It is the loading of that page (which you don't get to see) which triggers the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Installation freezes after Who are you? (Ubiquity hangs in ubi-webcam.py) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 950952] Re: Ubuntu 12.04 install freezes at completion of Who are you?
*** This bug is a duplicate of bug 909179 *** https://bugs.launchpad.net/bugs/909179 ** This bug is no longer a duplicate of bug 933105 Installer hangs when entering account information ** This bug has been marked a duplicate of bug 909179 [Precise] Ubiquity hangs in ubi-webcam.py -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950952 Title: Ubuntu 12.04 install freezes at completion of Who are you? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/950952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933105] Re: Installer hangs when entering account information
*** This bug is a duplicate of bug 909179 *** https://bugs.launchpad.net/bugs/909179 ** This bug has been marked a duplicate of bug 909179 [Precise] Ubiquity hangs in ubi-webcam.py -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933105 Title: Installer hangs when entering account information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/933105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] Re: [Precise] Installation freezes after Who are you? (Ubiquity hangs in ubi-webcam.py)
** Summary changed: - [Precise] Ubiquity hangs in ubi-webcam.py + [Precise] Installation freezes after Who are you? (Ubiquity hangs in ubi-webcam.py) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Installation freezes after Who are you? (Ubiquity hangs in ubi-webcam.py) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] Re: [Precise] Installation freezes after Who are you? (Ubiquity hangs in ubi-webcam.py)
Thanks Michael. I have marked bug #933105 and bug #950952 as duplicates of this bug. Apologies for making the title of this bug report so much geared towards the developers who could fix the bug that regular users experiencing it would not recognize that they were affected by it. I hope the new title fixes this. I would like to highlight Michaels's workaround (from https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/933105/comments/15) here as well: Before starting the installer, run the following command in a terminal: sudo rm /usr/lib/ubiquity/plugins/ubi-webcam.py In my opinion (and other's as well: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/869239/comments/5), while the webcam/set login image feature is cool, it should be considered for removal if it causes problems. It also adds another step to the installation process which is hardly necessary and adds workload during the installation process. ** Description changed: During installation, after entering the user information, the installer slows down to a crawl and the status bar (which says Copying files) stops. Upon switching VT to 2 and back to 7, the window contents is not updated. Checking with top, the ubiquity process first uses 100 % CPU and eats memory, and after a while it uses e 750 M (of 1 G) of real memory and 3.5 G (of 4.0 G) of virtual memory causing massive swapping. - - The information uploaded with apport-collect is from the same LiveUSB - session after I killed the ubiquity process an hour or two after it - first hung. Apport wanted to submit a bug report automatically when the - unity session started, but that bug report was wrongly judged to be a - duplicate of bug 652916. The hang occurs when loading the page titled ubiquity/text/webcam_heading_label after the comment '# This page is just a UI page' in gtk_ui.py. This invokes plugin_get_current_page() in ubi-webcam.py, where the call self.faceselector.webcam_play() never returns. In UbiquityDebug.txt, the following error message occurs twice: Error opening file for reading: Permission denied - I have traced the origin to ubi-webcam.py as well, in __init__(): They come from the calls - Gst.init(sys.argv) + I have traced the origin to ubi-webcam.py as well, in __init__(): They come from the calls + Gst.init(sys.argv) (sys.argv here resolves to ['/usr/lib/ubiquity/bin/ubiquity']) and self.faceselector = gtkwidgets.FaceSelector() + + Workaround: + + Before starting the installer, run the following command in a terminal: + sudo rm /usr/lib/ubiquity/plugins/ubi-webcam.py ApportVersion: 1.90-0ubuntu1 Architecture: amd64 CasperVersion: 1.296DistroRelease: Ubuntu 12.04 LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20111227) Package: ubiquity 2.9.10 PackageArchitecture: amd64 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7 Tags: precise running-unity ubiquity-2.9.10 Uname: Linux 3.2.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Installation freezes after Who are you? (Ubiquity hangs in ubi-webcam.py) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] Re: [Precise] Ubiquity uses up all memory and hangs during installation
I tried again using 'ubiquity --debug --pdb'. Same thing happened, but now hopefully the apport-collected files will contain more useful information. ** Description changed: During installation, after entering the user information, the installer slows down to a crawl and the status bar (which says Copying files) stops. Upon switching VT to 2 and back to 7, the window contents is not updated. Checking with top, the ubiquity process uses 70-95% CPU and after a while 750 M (of 1 G) of real memory and 3.5 G (of 4.0 G) of virtual memory. The information uploaded with apport-collect is from the same LiveUSB session after I killed the ubiquity process an hour or two after it first hung. Apport wanted to submit a bug report automatically when the unity session started, but that bug report was wrongly judged to be a duplicate of bug 652916. --- ApportVersion: 1.90-0ubuntu1 Architecture: amd64 CasperVersion: 1.296 DistroRelease: Ubuntu 12.04 LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20111227) Package: ubiquity 2.9.10 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7 Tags: precise running-unity ubiquity-2.9.10 Uname: Linux 3.2.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + --- + ApportVersion: 1.90-0ubuntu1 + Architecture: amd64 + CasperVersion: 1.296 + DistroRelease: Ubuntu 12.04 + LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20111227) + Package: ubiquity 2.9.10 + PackageArchitecture: amd64 + ProcEnviron: + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7 + Tags: precise running-unity ubiquity-2.9.10 + Uname: Linux 3.2.0-7-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity uses up all memory and hangs during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/909179/+attachment/2649227/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity uses up all memory and hangs during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] UbiquityDebug.txt
apport information ** Attachment added: UbiquityDebug.txt https://bugs.launchpad.net/bugs/909179/+attachment/2649228/+files/UbiquityDebug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity uses up all memory and hangs during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] UbiquityDm.txt
apport information ** Attachment added: UbiquityDm.txt https://bugs.launchpad.net/bugs/909179/+attachment/2649229/+files/UbiquityDm.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity uses up all memory and hangs during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] UbiquityPartman.txt
apport information ** Attachment added: UbiquityPartman.txt https://bugs.launchpad.net/bugs/909179/+attachment/2649230/+files/UbiquityPartman.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity uses up all memory and hangs during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] UbiquitySyslog.txt
apport information ** Attachment added: UbiquitySyslog.txt https://bugs.launchpad.net/bugs/909179/+attachment/2649231/+files/UbiquitySyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity uses up all memory and hangs during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] Casper.txt
apport information ** Attachment added: Casper.txt https://bugs.launchpad.net/bugs/909179/+attachment/2649226/+files/Casper.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity uses up all memory and hangs during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] Re: [Precise] Ubiquity hangs in ubi-webcam.py
** Summary changed: - [Precise] Ubiquity uses up all memory and hangs during installation + [Precise] Ubiquity hangs in ubi-webcam.py -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity hangs in ubi-webcam.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] Re: [Precise] Ubiquity hangs in ubi-webcam.py
** Description changed: During installation, after entering the user information, the installer slows down to a crawl and the status bar (which says Copying files) stops. Upon switching VT to 2 and back to 7, the window contents is not - updated. Checking with top, the ubiquity process uses 70-95% CPU and - after a while 750 M (of 1 G) of real memory and 3.5 G (of 4.0 G) of - virtual memory. + updated. Checking with top, the ubiquity process first uses 100 % CPU + and eats memory, and after a while it uses e 750 M (of 1 G) of real + memory and 3.5 G (of 4.0 G) of virtual memory causing massive swapping. The information uploaded with apport-collect is from the same LiveUSB session after I killed the ubiquity process an hour or two after it first hung. Apport wanted to submit a bug report automatically when the unity session started, but that bug report was wrongly judged to be a duplicate of bug 652916. - --- + The hang occurs when loading the page titled + ubiquity/text/webcam_heading_label after the comment '# This page is + just a UI page' in gtk_ui.py. This invokes plugin_get_current_page() in + ubi-webcam.py, where the call self.faceselector.webcam_play() never + returns. + + In UbiquityDebug.txt, the following error message occurs twice: + Error opening file for reading: Permission denied + I have traced the origin to ubi-webcam.py as well, in __init__(): They come from the calls + Gst.init(sys.argv) + (sys.argv here resolves to ['/usr/lib/ubiquity/bin/ubiquity']) + and + self.faceselector = gtkwidgets.FaceSelector() + ApportVersion: 1.90-0ubuntu1 Architecture: amd64 - CasperVersion: 1.296 - DistroRelease: Ubuntu 12.04 + CasperVersion: 1.296DistroRelease: Ubuntu 12.04 LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20111227) Package: ubiquity 2.9.10 PackageArchitecture: amd64 ProcEnviron: + PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7 Tags: precise running-unity ubiquity-2.9.10 Uname: Linux 3.2.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo - --- - ApportVersion: 1.90-0ubuntu1 - Architecture: amd64 - CasperVersion: 1.296 - DistroRelease: Ubuntu 12.04 - LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20111227) - Package: ubiquity 2.9.10 - PackageArchitecture: amd64 - ProcEnviron: - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash - ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7 - Tags: precise running-unity ubiquity-2.9.10 - Uname: Linux 3.2.0-7-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity hangs in ubi-webcam.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] [NEW] [Precise] Ubiquity uses up all memory and hangs during installation
Public bug reported: During installation, after entering the user information, the installer slows down to a crawl and the status bar (which says Copying files) stops. Upon switching VT to 2 and back to 7, the window contents is not updated. Checking with top, the ubiquity process uses 70-95% CPU and after a while 750 M (of 1 G) of real memory and 3.5 G (of 4.0 G) of virtual memory. The information uploaded with apport-collect is from the same LiveUSB session after I killed the ubiquity process an hour or two after it first hung. Apport wanted to submit a bug report automatically when the unity session started, but that bug report was wrongly judged to be a duplicate of bug 652916. --- ApportVersion: 1.90-0ubuntu1 Architecture: amd64 CasperVersion: 1.296 DistroRelease: Ubuntu 12.04 LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20111227) Package: ubiquity 2.9.10 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7 Tags: precise running-unity ubiquity-2.9.10 Uname: Linux 3.2.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected precise running-unity ubiquity-2.9.10 ** Tags added: apport-collected precise running-unity ubiquity-2.9.10 ** Description changed: - During installation, after entering the user information, the installer - slows down to a crawl and the status bar (which says Copying files) - stops. Upon switching VT to 2 and back to 7, the window contents is not - updated. Checking with top, the ubiquity process uses 70-95% CPU and - after a while 750 M (of 1 G) of real memory and 3.5 G (of 4.0 G) of - virtual memory. + During installation, after entering the user information, the installer slows down to a crawl and the status bar (which says Copying files) stops. Upon switching VT to 2 and back to 7, the window contents is not updated. Checking with top, the ubiquity process uses 70-95% CPU and after a while 750 M (of 1 G) of real memory and 3.5 G (of 4.0 G) of virtual memory. + --- + ApportVersion: 1.90-0ubuntu1 + Architecture: amd64 + CasperVersion: 1.296 + DistroRelease: Ubuntu 12.04 + LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20111227) + Package: ubiquity 2.9.10 + PackageArchitecture: amd64 + ProcEnviron: + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7 + Tags: precise running-unity ubiquity-2.9.10 + Uname: Linux 3.2.0-7-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity uses up all memory and hangs during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] Casper.txt
apport information ** Attachment added: Casper.txt https://bugs.launchpad.net/bugs/909179/+attachment/2648634/+files/Casper.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity uses up all memory and hangs during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/909179/+attachment/2648635/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity uses up all memory and hangs during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] UbiquityDebug.txt
apport information ** Attachment added: UbiquityDebug.txt https://bugs.launchpad.net/bugs/909179/+attachment/2648636/+files/UbiquityDebug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity uses up all memory and hangs during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] UbiquityPartman.txt
apport information ** Attachment added: UbiquityPartman.txt https://bugs.launchpad.net/bugs/909179/+attachment/2648638/+files/UbiquityPartman.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity uses up all memory and hangs during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] UbiquityDm.txt
apport information ** Attachment added: UbiquityDm.txt https://bugs.launchpad.net/bugs/909179/+attachment/2648637/+files/UbiquityDm.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity uses up all memory and hangs during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] UbiquitySyslog.txt
apport information ** Attachment added: UbiquitySyslog.txt https://bugs.launchpad.net/bugs/909179/+attachment/2648639/+files/UbiquitySyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity uses up all memory and hangs during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909179] Re: [Precise] Ubiquity uses up all memory and hangs during installation
** Description changed: - During installation, after entering the user information, the installer slows down to a crawl and the status bar (which says Copying files) stops. Upon switching VT to 2 and back to 7, the window contents is not updated. Checking with top, the ubiquity process uses 70-95% CPU and after a while 750 M (of 1 G) of real memory and 3.5 G (of 4.0 G) of virtual memory. - --- + During installation, after entering the user information, the installer + slows down to a crawl and the status bar (which says Copying files) + stops. Upon switching VT to 2 and back to 7, the window contents is not + updated. Checking with top, the ubiquity process uses 70-95% CPU and + after a while 750 M (of 1 G) of real memory and 3.5 G (of 4.0 G) of + virtual memory. + + The information uploaded with apport-collect is from the same LiveUSB + session after I killed the ubiquity process an hour or two after it + first hung. Apport wanted to submit a bug report automatically when the + unity session started, but that bug report was wrongly judged to be a + duplicate of bug 652916. + + --- ApportVersion: 1.90-0ubuntu1 Architecture: amd64 CasperVersion: 1.296 DistroRelease: Ubuntu 12.04 LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20111227) Package: ubiquity 2.9.10 PackageArchitecture: amd64 ProcEnviron: - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7 Tags: precise running-unity ubiquity-2.9.10 Uname: Linux 3.2.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909179 Title: [Precise] Ubiquity uses up all memory and hangs during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/909179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 456257] Re: Could libtiff.so.3 be provided as a symlink to libtiff.so.4?
The reason that the soname is different in Debian and upstream is explained in /usr/share/doc/libtiff4/README.Debian: This version of libtiff is installed with a different shared library soname from the upstream version. This is because an accidental change to the library's ABI was introduced somewhere between 3.5.7 and 3.6.1. There are no source-level incompatibilities between 3.5.7 and the current version, so any application that worked with 3.5.7 should work fine when recompiled with the libtiff4 packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/456257 Title: Could libtiff.so.3 be provided as a symlink to libtiff.so.4? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/456257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 488319] Re: Reboot hangs on Dell Optiplex 760 (workaround: reboot=bios)
Phil, this bug report has been closed, and comments on closed bug reports are not monitored by developers. In order to get someone to look at this, file a new bug report using the ubuntu-bug command. Use this bug report as a model and collect the same information that I have attached here. I don't have access to the 760s anymore, so I won't be able to test. It is best if you can also test with the current development version, since that is where this is most likely to be fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/488319 Title: Reboot hangs on Dell Optiplex 760 (workaround: reboot=bios) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/488319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 541511] Re: MASTER: [i855] GPU lockup (apport-crash)
This is a master bug report, and no more logs are required despite the automated message. Besides, the upstream bug report has been closed as FIXED RESOLVED. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Changed in: linux (Ubuntu Lucid) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/541511 Title: MASTER: [i855] GPU lockup (apport-crash) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/541511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 793616] Re: lucid and maverick are incompatible with latest iOS
I have tested 0.9.7-1ubuntu1.1, and now my iPhone (with iOS 4.2.1) is detected. It wasn't before upgrading from 0.9.7-1ubuntu1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/793616 Title: lucid and maverick are incompatible with latest iOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/793616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605124] Re: [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/605124 Title: [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 541492] Re: MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?)
Note that the upstream 845G bug report has been reopened. It turned out that the fixes (which are contained in Brian's PPA kernel) are insufficient to fix the 845G-specific problem completely. The kernel will probably improve stability on 845G, but I think adding results from 845G to the upstream bug https://bugs.freedesktop.org/show_bug.cgi?id=27187 will only be considered as noise. The upstream bug for the 845G-specific issue is http://bugs.freedesktop.org/show_bug.cgi?id=26345. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/541492 Title: MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 541511] Re: MASTER: [i855] GPU lockup (apport-crash)
I have previously used the instructions at https://wiki.ubuntu.com/KernelTeam/GitKernelBuild . Instead of getting the vanilla upstream kernel in #2, I would use the drm-intel-next head from git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git. Then you would need to apply the patch before going on. If you have a faster newer computer, I would recommend building on that one, because compiling a kernel on the computers that have an 855GM chipset tends to be slow. You will need to use the 32-bit version of Ubuntu on that machine, though. It is probably better to use Maverick than Lucid for testing this. Natty even better. With Natty, you should be able to steal most of the kernel configuration from the drm-intel-next mainline build in step 4 (see https://wiki.ubuntu.com/Kernel/MainlineBuilds). I haven't done this in quite a while, so I don't remember all there is to it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/541511 Title: MASTER: [i855] GPU lockup (apport-crash) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 541511] Re: MASTER: [i855] GPU lockup (apport-crash)
There is a (yet another) new kernel patch in the upstream bug report that has the potential to fix this bug once and for all: https://bugs.freedesktop.org/show_bug.cgi?id=27187#c281 I don't have the resources (full hard drive and other limitations) to build a Ubuntu kernel package with this patch. If anybody has the possibility to put a test kernel in a PPA (or some other place), that would be nice. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/541511 Title: MASTER: [i855] GPU lockup (apport-crash) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 541492] Re: MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?)
Note that the new patch upstream fixes the 845G-specific part of this bug. The 845G also suffers from the same i8xx incoherency that the 855GM suffers from (LP bug 541511). There is a patch for that as well at https://bugs.freedesktop.org/show_bug.cgi?id=27187#c281, but this has not been commited yet and probably needs more testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/541492 Title: MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 541492] Re: MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?)
For completeness, I should add that the upstream fix introduces another bug which may cause some corruption. This one is fixed in this commit: commit dc3bfebcf77d943b7e8495d30d0ee3d01b3042a5 Author: Chris Wilson ch...@chris-wilson.co.uk Date: Thu Dec 30 18:02:21 2010 + drm/i915: Don't skip ring flushes if only invalidating Commit 15056d2 tried to optimize away a flush if there were no outstanding writes on a ring (in order to prevent a too-early-flush during ring init). However, this has the unfortunate side-effect of eliminating the texture cache invalidation, and so causing rendering artefacts. Reported-by: Alexey Fisher bug-tr...@fisher-privat.net Signed-off-by: Chris Wilson ch...@chris-wilson.co.uk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/541492 Title: MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 426929] Re: [i945g] X11 black screen until vnc connection made
Why was this closed. Because you hope it's fixed? Same issue on Fedora 12: I do hope it is fixed, but that was not the reason I closed the bug report. It is an unfortunate reality that there is not enough people with enough time to handle ubuntu and specifically xserver-xorg-video-intel bug reports in a timely manner. At the time I closed the bug report the information in the bug report was not up-to-date, so even if somebody would start to look at it, they would have to start from scratch by asking if the bug was still present and get updated logs etc. In many cases the original bug reporter is not around to provide that information, and it stops there, and if he is around, the easiest way to provide the updated information is to file a new bug report with the ubuntu-bug command. Closing this bug was a part of a clean-up to close bug reports that was no longer useful, so that it was easier to find the ones where a developer or triager may take action. Keep in mind that the main purpose of a bug report is to help fix bugs in ubuntu, much more than documenting them. -- [i945g] X11 black screen until vnc connection made https://bugs.launchpad.net/bugs/426929 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596819] Re: Failsafe X displays variable name instead of file name for debugging tarball
I agree that it is not worth the trouble putting this through as an SRU. -- Failsafe X displays variable name instead of file name for debugging tarball https://bugs.launchpad.net/bugs/596819 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 528467] Re: [i855] GPU hung (drm i915 intel) on Lucid Lynx
On Mon, Aug 9, 2010 at 1:59 AM, Warren E. Downs wrote: Regarding ppa kernel.ubuntu.com/~kernel-ppa/mainline/, I tried adding the source but it wasn't recognized. I noticed that there is no 'dists' directory under it like apt expects. Is there another source or do I have to install the kernel manually (which I can do but I hate the maintenance headache when I update packages later). kernel.ubuntu.com/~kernel-ppa/ is not a normal PPA, so you cannot add it to /etc/apt/sources or sources.d. You have to install them manually, but since the kernels install in parallel with the other kernels you have, there is not really any maintenance headache. See https://wiki.ubuntu.com/Kernel/MainlineBuilds . -- [i855] GPU hung (drm i915 intel) on Lucid Lynx https://bugs.launchpad.net/bugs/528467 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 609717] Re: [pineviewgm] GPU lockup b8b07b00 (PGTBL_ER: 0x00000003)
** Summary changed: - [IGDgm] GPU lockup b8b07b00 (PGTBL_ER: 0x0003) + [pineviewgm] GPU lockup b8b07b00 (PGTBL_ER: 0x0003) ** Tags added: pineviewgm -- [pineviewgm] GPU lockup b8b07b00 (PGTBL_ER: 0x0003) https://bugs.launchpad.net/bugs/609717 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607207] Re: [pineviewgm] GPU lockup f7eb055d (PGTBL_ER: 0x00000003)
** Summary changed: - [IGDgm] GPU lockup f7eb055d (PGTBL_ER: 0x0003) + [pineviewgm] GPU lockup f7eb055d (PGTBL_ER: 0x0003) ** Tags added: pineviewgm -- [pineviewgm] GPU lockup f7eb055d (PGTBL_ER: 0x0003) https://bugs.launchpad.net/bugs/607207 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 608434] Re: Dual monitor instability - reverts to low graphics mode
** Tags added: 915gm ** Summary changed: - Dual monitor instability - reverts to low graphics mode + [915gm] Dual monitor instability - reverts to low graphics mode -- [915gm] Dual monitor instability - reverts to low graphics mode https://bugs.launchpad.net/bugs/608434 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611951] Re: [i945gm] GPU lockup d0c69edf
** Tags added: 945gm -- [i945gm] GPU lockup d0c69edf https://bugs.launchpad.net/bugs/611951 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611951] Re: [i945gm] GPU lockup d0c69edf
Running intel_error_decode on the attached i915_error_state.txt shows that there is a page table error and that the ringbuffer is completely empty: Time: 1280551135 s 109870 us PCI ID: 0x27a2 EIR: 0x0010 PGTBL_ER: 0x0001 INSTPM: 0x IPEIR: 0x IPEHR: 0x INSTDONE: 0x7fc0 busy: Secondary ring 3 busy: Secondary ring 2 busy: Secondary ring 1 busy: Secondary ring 0 busy: Primary ring 1 busy: Primary ring 0 ACTHD: 0x seqno: 0x ringbuffer at 0x0d4b8000: 0x0d4b8000: 0x: MI_NOOP 0x0d4b8004: 0x: MI_NOOP 0x0d4b8008: 0x: MI_NOOP 0x0d4d7ff4: 0x: MI_NOOP 0x0d4d7ff8: 0x: MI_NOOP 0x0d4d7ffc: 0x: MI_NOOP ** Summary changed: - [i945gm] GPU lockup d0c69edf + [i945gm] GPU lockup d0c69edf (PGTBL_ER: 0x0001) -- [i945gm] GPU lockup d0c69edf (PGTBL_ER: 0x0001) https://bugs.launchpad.net/bugs/611951 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611951] Re: [i945gm] GPU lockup d0c69edf (PGTBL_ER: 0x00000001)
** Tags added: resume suspend -- [i945gm] GPU lockup d0c69edf (PGTBL_ER: 0x0001) https://bugs.launchpad.net/bugs/611951 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611951] Re: [i945gm] GPU lockup d0c69edf (PGTBL_ER: 0x00000001)
I have forwarded this bug the intel developers at https://bugs.freedesktop.org/show_bug.cgi?id=29345 . Please register at bugs.freedesktop.org, add yourself to the CC: field of that bug report, and respond to any requests made by the intel developers. If you need help with fulfilling any of these requests, you may ask for help here. There are a couple of things you may do to enhance the upstream bug report: * Verify that the problem exists with the very latest and greatest xorg/libdrm etc. You can do this by using the xorg-edgers PPA at https://launchpad.net/~xorg-edgers/+archive/ppa . * Verify that the problem exists with the very latest and greatest kernel. The current Maverick kernel is pretty up-to-date, but it is comforting for the developers to know that the problem exists in a non-distribution-specific kernel. You can test both the latest drm-intel-next kernel and the latest 2.6.35-rcX (now rc6, and the next is probably the 2.6.35 release itself). Look at the mainline builds page at https://wiki.ubuntu.com/Kernel/MainlineBuilds . * Use drm.debug=0x02 kernel parameter to get a more verbose dmesg output. It may include more details about what went wrong during suspend. Attach resulting dmesg output before and after suspend. * Grab the output of `sudo intel_reg_dumper` before suspend and after resume. There may be important differences there (but probably not). Instead of relying on apport to tell you that there is a GPU error, you can see it in the dmesg output: [17706.150645] render error detected, EIR: 0x0010 [17706.150645] page table error [17706.150645] PGTBL_ER: 0x0001 [17706.150645] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x0010, masking [17706.150703] render error detected, EIR: 0x0010 [17706.150703] page table error [17706.150703] PGTBL_ER: 0x0001 Actually, it would be nice if you could let the computer be suspended for a few minutes, so that is easier to distinguish what happens on suspend and what happens on the following resume. ** Bug watch added: freedesktop.org Bugzilla #29345 http://bugs.freedesktop.org/show_bug.cgi?id=29345 ** Also affects: xserver-xorg-video-intel via http://bugs.freedesktop.org/show_bug.cgi?id=29345 Importance: Unknown Status: Unknown -- [i945gm] GPU lockup d0c69edf (PGTBL_ER: 0x0001) https://bugs.launchpad.net/bugs/611951 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 611951] Re: [i945gm] GPU lockup d0c69edf (PGTBL_ER: 0x00000001)
** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Triaged ** Changed in: xserver-xorg-video-intel (Ubuntu) Importance: Undecided = Low -- [i945gm] GPU lockup d0c69edf (PGTBL_ER: 0x0001) https://bugs.launchpad.net/bugs/611951 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 610387] Re: [arrandale] Lucid - Intel Integrated Graphics freezes when external monitor is plugged in
** Summary changed: - Lucid - Intel Integrated Graphics freezes when external monitor is plugged in + [arrandale] Lucid - Intel Integrated Graphics freezes when external monitor is plugged in -- [arrandale] Lucid - Intel Integrated Graphics freezes when external monitor is plugged in https://bugs.launchpad.net/bugs/610387 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 610387] Re: [arrandale] Lucid - Intel Integrated Graphics freezes when external monitor is plugged in
** Tags added: arrandale dual-head freeze ** Tags removed: freezing monitor syncmaster -- [arrandale] Lucid - Intel Integrated Graphics freezes when external monitor is plugged in https://bugs.launchpad.net/bugs/610387 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607783] Re: [arrandale] VGA port not working on Dell Latitude E6510
The eDP issue should be completely decoupled from this. Howerver, following the redhat bug report to the upstream bug report mentions this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=28911, which is likely to be the same issue. There is an experimental patch at comment #4 in that bug report, and I'm sure it will be useful if you could test that. The patch probably applies to the latest 2.6.35-rcX kernel (if not, drm-intel-next). If you're not up to patching and building yourself (following instructions at [1]) you can ask someone at the IRC channel #ubuntu-kernel on freenode [2] to build a test-kernel with that patch. [1]: https://wiki.ubuntu.com/KernelTeam/GitKernelBuild [2]: https://lists.ubuntu.com/archives/kernel-team/2010-June/011358.html ** Bug watch added: freedesktop.org Bugzilla #28911 http://bugs.freedesktop.org/show_bug.cgi?id=28911 -- [arrandale] VGA port not working on Dell Latitude E6510 https://bugs.launchpad.net/bugs/607783 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607783] Re: [arrandale] VGA port not working on Dell Latitude E6510
To get the drm-intel kernel tree instead of Linus' tree, instead of git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git use git clone git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel.git drm-intel-next is the head of that tree (called master in Linus' tree), i.e. what you get when you clone. If you have Linus' tree already, it is possible to use that as a reference so that you don't have to download so much. Never tried that, but should be --reference option (see man git-clone). You can see all git repositories hosted at git.kernel.org at http://git.kernel.org. The patch is in mailbox format, and therefore the git am command can be used (see man git-am) to apply the patch. -- [arrandale] VGA port not working on Dell Latitude E6510 https://bugs.launchpad.net/bugs/607783 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607783] Re: [arrandale] VGA port not working on Dell Latitude E6510
Great troubleshooting, Corona! I don't know enough kernel stuff to know if this means that the dell-wmi is the troublemaker or it simply needs an update to silence an innocent message. Hopefully the kernel people know that better, so I think it's time that I send this over there. I am not sure if this belong to the intel graphics developers or someone involved with wmi drivers. Maybe Chris Wilson is still watching and knows what this means. -- [arrandale] VGA port not working on Dell Latitude E6510 https://bugs.launchpad.net/bugs/607783 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607783] Re: [arrandale] VGA port not working on Dell Latitude E6510
** Description changed: Binary package hint: xserver-xorg-video-intel I cannot hook up an external monitor or beamer to my Dell Latitude E6510 using the VGA port. When I open the monitors dialogue, the screen goes black if there is a VGA cable plugged in. Only alt-sysrq-REISUB works to restart the computer. The chip is an intel one (intel core i5), not nvidia. I tried the xorg-edgers PPA to see if newer packages fix the problem, but that is not the case. + + Using netconsole, these messages are shown on the console when the monitor goes black: + [ 117.623294] dell-wmi: Received unknown WMI event (0x11) + [ 117.686469] dell-wmi: Received unknown WMI event (0x11) ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg-video-intel 2:2.9.1-3ubuntu5 ProcVersionSignature: Ubuntu 2.6.35-7.11~lucid1-generic 2.6.35-rc4 Uname: Linux 2.6.35-7-generic i686 Architecture: i386 CheckboxSubmission: 9f21fd2185c4c78c7747514ec103f65b CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Tue Jul 20 15:58:38 2010 DkmsStatus: Error: [Errno 2] No such file or directory InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) MachineType: Dell Inc. Latitude E6510 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-7-generic root=UUID=c17d1179-45a9-4a75-99f5-b85563d6f6c8 ro splash quiet quiet splash i915.modeset=1 acpi_sleep=s3_bios SourcePackage: xserver-xorg-video-intel dmi.bios.date: 05/28/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd05/28/2010:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.35-7-generic ** Package changed: xserver-xorg-video-intel (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed = New -- [arrandale] VGA port not working on Dell Latitude E6510 https://bugs.launchpad.net/bugs/607783 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607783] Re: [arrandale] VGA port not working on Dell Latitude E6510
Just to confirm: The dell-wmi messages do not show up when the monitor is plugged in, but only when xrandr is run and the monitor goes black? If you let it stand for a couple of minutes before hitting Sysrq-REISUB, does the BUG: Soft lockup line show up eventually, without you rebooting? Otherwise, my knowledge is exhausted on this one, and I hope someone with more kernel knowledge can bring this to the attention of the right upstream. -- [arrandale] VGA port not working on Dell Latitude E6510 https://bugs.launchpad.net/bugs/607783 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 469820] Re: [gm45] system locks up at random intervals, except mouse
Following upstream and closing this bug report. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Confirmed = Fix Released -- [gm45] system locks up at random intervals, except mouse https://bugs.launchpad.net/bugs/469820 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 607783] Re: [arrandale] VGA port not working on Dell Latitude E6510
- When I plug in the VGA cable and switch to VT1, the screen goes black, even when I don't run `xrandr -q` first, so that doesn't give any additional info. What if you switch to VT1 and then plug in the monitor? Possibly it will hang when you switch back to X. If that is the case, what if you do `sleep 30; xrandr -q` and then switch to VT1 and plug in the monitor and wait until the sleep times out? It may be a long shot, but it is possible that the kernel will print some panic messages on VT1. Otherwise, I saw that Jeremy Foshee just wrote a wiki page with how to setup Netconsole. You may be able to capture some panic information by using that. http://wiki.ubuntu.com/Kernel/Netconsole -- [arrandale] VGA port not working on Dell Latitude E6510 https://bugs.launchpad.net/bugs/607783 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607783] Re: [arrandale] VGA port not working on Dell Latitude E6510
Chris, good to see that this is on your radar. I wasn't aware that you were also following Ubuntu bug reports. I was simply hoping that the kernel triagers would know better how to extract some useful information about the black screen (which takes down the ssh connection) before forwarding it upstream to you guys. -- [arrandale] VGA port not working on Dell Latitude E6510 https://bugs.launchpad.net/bugs/607783 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607344] Re: i845g crash issue not present in Maverick
*** This bug is a duplicate of bug 604885 *** https://bugs.launchpad.net/bugs/604885 Marking this as a duplicate to bug 604855, since this is troubleshooting information for that bug report. ** This bug has been marked a duplicate of bug 604885 No main text between the two lateral frames in firefox -- i845g crash issue not present in Maverick https://bugs.launchpad.net/bugs/607344 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607363] Re: [i845] GPU lockup fe9851ff (PGTBL_ER: 0x00000049)
*** This bug is a duplicate of bug 541492 *** https://bugs.launchpad.net/bugs/541492 We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel developers are still scratching their head about this. This is what Chris Wilson writes: We have big issues with GEM on i8xx. i845 is even more troublesome as it has some errata that we fail to workaround that affect reprogramming the GTT. My presumption is that this is the very same bug, and the current workaround is to use UMS+EXA. (from http://bugs.freedesktop.org/show_bug.cgi?id=29006#c1) We have a master bug report for this issue at bug 541492. Marking as a duplicate of that. ** Bug watch added: freedesktop.org Bugzilla #29006 http://bugs.freedesktop.org/show_bug.cgi?id=29006 ** This bug has been marked a duplicate of bug 541492 MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) -- [i845] GPU lockup fe9851ff (PGTBL_ER: 0x0049) https://bugs.launchpad.net/bugs/607363 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605244] Re: [i845] GPU lockup 8d4447c9 (PGTBL_ER: 0x00000049)
*** This bug is a duplicate of bug 541492 *** https://bugs.launchpad.net/bugs/541492 We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel developers are still scratching their head about this. This is what Chris Wilson writes: We have big issues with GEM on i8xx. i845 is even more troublesome as it has some errata that we fail to workaround that affect reprogramming the GTT. My presumption is that this is the very same bug, and the current workaround is to use UMS+EXA. (from http://bugs.freedesktop.org/show_bug.cgi?id=29006#c1) We have a master bug report for this issue at bug 541492. Marking as a duplicate of that. ** Bug watch added: freedesktop.org Bugzilla #29006 http://bugs.freedesktop.org/show_bug.cgi?id=29006 ** This bug has been marked a duplicate of bug 541492 MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) -- [i845] GPU lockup 8d4447c9 (PGTBL_ER: 0x0049) https://bugs.launchpad.net/bugs/605244 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605242] Re: [i845] GPU lockup 8d4447c9 (PGTBL_ER: 0x00000049)
*** This bug is a duplicate of bug 541492 *** https://bugs.launchpad.net/bugs/541492 We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel developers are still scratching their head about this. This is what Chris Wilson writes: We have big issues with GEM on i8xx. i845 is even more troublesome as it has some errata that we fail to workaround that affect reprogramming the GTT. My presumption is that this is the very same bug, and the current workaround is to use UMS+EXA. (from http://bugs.freedesktop.org/show_bug.cgi?id=29006#c1) We have a master bug report for this issue at bug 541492. Marking as a duplicate of that. ** Bug watch added: freedesktop.org Bugzilla #29006 http://bugs.freedesktop.org/show_bug.cgi?id=29006 ** This bug has been marked a duplicate of bug 541492 MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) -- [i845] GPU lockup 8d4447c9 (PGTBL_ER: 0x0049) https://bugs.launchpad.net/bugs/605242 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604494] Re: [i845] GPU lockup ee7bcc9e (PGTBL_ER: 0x00000049)
*** This bug is a duplicate of bug 541492 *** https://bugs.launchpad.net/bugs/541492 We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel developers are still scratching their head about this. This is what Chris Wilson writes: We have big issues with GEM on i8xx. i845 is even more troublesome as it has some errata that we fail to workaround that affect reprogramming the GTT. My presumption is that this is the very same bug, and the current workaround is to use UMS+EXA. (from http://bugs.freedesktop.org/show_bug.cgi?id=29006#c1) We have a master bug report for this issue at bug 541492. Marking as a duplicate of that. ** Bug watch added: freedesktop.org Bugzilla #29006 http://bugs.freedesktop.org/show_bug.cgi?id=29006 ** This bug has been marked a duplicate of bug 541492 MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) -- [i845] GPU lockup ee7bcc9e (PGTBL_ER: 0x0049) https://bugs.launchpad.net/bugs/604494 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604493] Re: [i845] GPU lockup ddeb6f12 (PGTBL_ER: 0x00000049)
*** This bug is a duplicate of bug 541492 *** https://bugs.launchpad.net/bugs/541492 We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel developers are still scratching their head about this. This is what Chris Wilson writes: We have big issues with GEM on i8xx. i845 is even more troublesome as it has some errata that we fail to workaround that affect reprogramming the GTT. My presumption is that this is the very same bug, and the current workaround is to use UMS+EXA. (from http://bugs.freedesktop.org/show_bug.cgi?id=29006#c1) We have a master bug report for this issue at bug 541492. Marking as a duplicate of that. ** Bug watch added: freedesktop.org Bugzilla #29006 http://bugs.freedesktop.org/show_bug.cgi?id=29006 ** This bug has been marked a duplicate of bug 541492 MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) -- [i845] GPU lockup ddeb6f12 (PGTBL_ER: 0x0049) https://bugs.launchpad.net/bugs/604493 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604323] Re: [i845] GPU lockup 40ce8caf (PGTBL_ER: 0x00000049)
*** This bug is a duplicate of bug 541492 *** https://bugs.launchpad.net/bugs/541492 We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel developers are still scratching their head about this. This is what Chris Wilson writes: We have big issues with GEM on i8xx. i845 is even more troublesome as it has some errata that we fail to workaround that affect reprogramming the GTT. My presumption is that this is the very same bug, and the current workaround is to use UMS+EXA. (from http://bugs.freedesktop.org/show_bug.cgi?id=29006#c1) We have a master bug report for this issue at bug 541492. Marking as a duplicate of that. ** Bug watch added: freedesktop.org Bugzilla #29006 http://bugs.freedesktop.org/show_bug.cgi?id=29006 ** This bug has been marked a duplicate of bug 541492 MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) -- [i845] GPU lockup 40ce8caf (PGTBL_ER: 0x0049) https://bugs.launchpad.net/bugs/604323 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604146] Re: [i845] GPU lockup 05722769 (PGTBL_ER: 0x00000049)
*** This bug is a duplicate of bug 541492 *** https://bugs.launchpad.net/bugs/541492 We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel developers are still scratching their head about this. This is what Chris Wilson writes: We have big issues with GEM on i8xx. i845 is even more troublesome as it has some errata that we fail to workaround that affect reprogramming the GTT. My presumption is that this is the very same bug, and the current workaround is to use UMS+EXA. (from http://bugs.freedesktop.org/show_bug.cgi?id=29006#c1) We have a master bug report for this issue at bug 541492. Marking as a duplicate of that. ** Bug watch added: freedesktop.org Bugzilla #29006 http://bugs.freedesktop.org/show_bug.cgi?id=29006 ** This bug has been marked a duplicate of bug 541492 MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) -- [i845] GPU lockup 05722769 (PGTBL_ER: 0x0049) https://bugs.launchpad.net/bugs/604146 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 602768] Re: [i845] GPU lockup 40ce8caf (PGTBL_ER: 0x00000049)
*** This bug is a duplicate of bug 541492 *** https://bugs.launchpad.net/bugs/541492 We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel developers are still scratching their head about this. This is what Chris Wilson writes: We have big issues with GEM on i8xx. i845 is even more troublesome as it has some errata that we fail to workaround that affect reprogramming the GTT. My presumption is that this is the very same bug, and the current workaround is to use UMS+EXA. (from http://bugs.freedesktop.org/show_bug.cgi?id=29006#c1) We have a master bug report for this issue at bug 541492. Marking as a duplicate of that. ** Bug watch added: freedesktop.org Bugzilla #29006 http://bugs.freedesktop.org/show_bug.cgi?id=29006 ** This bug has been marked a duplicate of bug 541492 MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) -- [i845] GPU lockup 40ce8caf (PGTBL_ER: 0x0049) https://bugs.launchpad.net/bugs/602768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 601167] Re: [i845] GPU lockup 40ce8caf (PGTBL_ER: 0x00000049)
*** This bug is a duplicate of bug 541492 *** https://bugs.launchpad.net/bugs/541492 We do see a lot of PGTBL_ER: 0x0049 on 845G chipsets. The intel developers are still scratching their head about this. This is what Chris Wilson writes: We have big issues with GEM on i8xx. i845 is even more troublesome as it has some errata that we fail to workaround that affect reprogramming the GTT. My presumption is that this is the very same bug, and the current workaround is to use UMS+EXA. (from http://bugs.freedesktop.org/show_bug.cgi?id=29006#c1) We have a master bug report for this issue at bug 541492. Marking as a duplicate of that. ** Bug watch added: freedesktop.org Bugzilla #29006 http://bugs.freedesktop.org/show_bug.cgi?id=29006 ** This bug has been marked a duplicate of bug 541492 MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) -- [i845] GPU lockup 40ce8caf (PGTBL_ER: 0x0049) https://bugs.launchpad.net/bugs/601167 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607783] Re: [arrandale] VGA port not working on Dell Latitude E6510
** Summary changed: - VGA port not working on Dell Latitude E6510 (arrandale, Intel Core i5) + [arrandale] VGA port not working on Dell Latitude E6510 ** Tags added: arrandale dual-head ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Confirmed ** Changed in: xserver-xorg-video-intel (Ubuntu) Importance: Undecided = Medium -- [arrandale] VGA port not working on Dell Latitude E6510 https://bugs.launchpad.net/bugs/607783 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607783] Re: [arrandale] VGA port not working on Dell Latitude E6510
In addition to bug 596082, there is also bug 599626 which is very similar. In that case I gave up and moved to the linux package, since I couldn't find a way to extract relevant logs. That hasn't been touched for the last two weeks, though, but I'm afraid this may go the same way eventually. Here are a few things you may try: - The things I asked for in the other two bug reports, in case it actually works for you. - If you can trigger the bug using `xrandr -q` instead of opening the monitor dialog, could you try if you get any messages on-screen by running `sleep 5; xrandr -q` and switching to VT1 with Ctrl-Alt-F1 before 5 seconds? Maybe some messages will show up on screen then. -- [arrandale] VGA port not working on Dell Latitude E6510 https://bugs.launchpad.net/bugs/607783 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 535640] Re: [gm45] GPU lockup de05bf80bf83cd22541cb55f1a2ee99e (xorg crash when opening the laptop lid)
Dmitry, the Ubuntu bug already has status 'Fix Released'. The upstream task should be updated automatically from the upstream task. Btw, I don't think it was the commit you mentioned that fixed this particular bug, since it has also been working in Maverick before that commit. That commit probably fixes bug 603064, though. -- [gm45] GPU lockup de05bf80bf83cd22541cb55f1a2ee99e (xorg crash when opening the laptop lid) https://bugs.launchpad.net/bugs/535640 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605440] Re: BUG: unable to handle kernel NULL pointer dereference at 00000008
** Tags added: grub-gfxpayload -- BUG: unable to handle kernel NULL pointer dereference at 0008 https://bugs.launchpad.net/bugs/605440 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605124] Re: [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
Robert, with the upgrade to kernel 2.6.35-8.13, xorg doesn't have problems, but the kernel oops still happens. Results from testing with 2.6.35-8.13: vesafb=fubar doesn't seem to change anything (it still get kernel oops sometimes, but not always) gfxpayload=text seems to stop the problems. I have booted several times with this option today, and still haven't had a kernel oops. -- [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor https://bugs.launchpad.net/bugs/605124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596082] Re: [arrandale] Dell Latitude E6510 unable to use second external vga monitor
Corona, most bug reports will never be assigned to anyone. After screening and finding the most relevant symptoms, we report in to the upstream developers who then look at and hopefully fix the bug. Then the fix is pulled into ubuntu, either by a regular driver update or a patch. This bug report is stale, since the original reporter has not answered by request in comment #1. If you can reproduce this in Maverick, Corona, it is better that you make your own bug report. For graphics related bugs, we only want input (on syndromes etc.) from the original reporter, since different bugs may have the exact same symptoms. It is also way easier to communicate with one person than having many people throw in their findings. I'm marking this bug as Incomplete, since the original reporter has not responded. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Confirmed = Incomplete -- [arrandale] Dell Latitude E6510 unable to use second external vga monitor https://bugs.launchpad.net/bugs/596082 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 475429] Re: [i945] X Freezes when compiz enabled
Thank you, takashi. I have reopened the upstream bug report and copied your comment and dmesg there. There will probably be more questions in the upstream bug report. Please answer those there directly. -- [i945] X Freezes when compiz enabled https://bugs.launchpad.net/bugs/475429 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605440] Re: BUG: unable to handle kernel NULL pointer dereference at 00000008
I thought 2.6.35-6.8 and other -rc3 based kernels were safe, but now I got a oops from -6.8 too. dmesg is attached. Unlike with 2.6.35-7, xorg works fine after this one, and I wouldn't have noticed it if I were not checking dmesg output or see the apport crash indicator. ** Attachment added: dmesg-2.6.35-6.txt http://launchpadlibrarian.net/52019485/dmesg-2.6.35-6.txt ** Description changed: This bug may be the underlying problem of bug 605124, which I have reported upstream as https://bugs.freedesktop.org/show_bug.cgi?id=29048 . I had written some more relevant information here, but I was struck by bug 553946 for the second time today, and can't remember what it was :-( I have tried several kernels, but it is hard to say anything for sure, since the frequency of this problem varies with kernel build and possibly the mood of ureadahead (i.e. how fast it is able to make the boot go). 2.6.35-7: Where I initially had the problem. Sometimes I only get this oops message in the dmesg output and everything else works fine, but often I get an the oops from bug 605124 and Xorg starts in low-graphics mode. - 2.6.35-6: I have booted this 3-4 times and haven't had any problems yet. + 2.6.35-6: I have had this oops once now with this kernel. See comment #2. 2.6.35-rc5 (mainline build): I get this oops every now and then, but it does not affect Xorg or anything else as far as I can see. 2.6.35-rc4 (mainline build): I get this oops every now and then, but it does not affect Xorg or anything else as far as I can see. The laptop keyboard and pointer does not work with this build, but USB mouse and keyboard does. 2.6.35-rc3 (mainline build): I have tried to trigger the problem here several times without success. ureadahead sayd it would reprofile on next boot when I installed this, but it always returned exit status 5 on boot with this kernel, which may mean the boots were slower. 2010-06-15 mainline build: I have tried to trigger the problem here several times without success, but I alternated with -rc5 for comparison and in 8 boots on each, none of them had problems. 2010-06-30 mainline build: Like -rc4, laptop keyboard doesn't work and at this time I didn't have an external keyboard available. ProblemType: KernelOops DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.35-7-generic 2.6.35-7.12 Regression: Yes Reproducible: No ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4 Uname: Linux 2.6.35-7-generic i686 AcpiTables: Error: [Errno 13] Permission denied AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Annotation: Your system might become unstable now and might need to be restarted. Architecture: i386 ArecordDevices: - List of CAPTURE Hardware Devices - card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] -Subdevices: 2/2 -Subdevice #0: subdevice #0 -Subdevice #1: subdevice #1 + List of CAPTURE Hardware Devices + card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] + Subdevices: 2/2 + Subdevice #0: subdevice #0 + Subdevice #1: subdevice #1 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: gom1456 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: gom1456 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: - Card hw:0 'Intel'/'HDA Intel at 0xf822 irq 46' -Mixer name : 'Analog Devices AD1984' -Components : 'HDA:11d41984,17aa20dd,00100400' -Controls : 31 -Simple ctrls : 19 + Card hw:0 'Intel'/'HDA Intel at 0xf822 irq 46' + Mixer name : 'Analog Devices AD1984' + Components : 'HDA:11d41984,17aa20dd,00100400' + Controls : 31 + Simple ctrls : 19 Card29.Amixer.info: - Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7RHT16WW-1.02' -Mixer name : 'ThinkPad EC 7RHT16WW-1.02' -Components : '' -Controls : 1 -Simple ctrls : 1 + Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7RHT16WW-1.02' + Mixer name : 'ThinkPad EC 7RHT16WW-1.02' + Components : '' + Controls : 1 + Simple ctrls : 1 Card29.Amixer.values: - Simple mixer control 'Console',0 -Capabilities: pswitch pswitch-joined penum -Playback channels: Mono -Mono: Playback [on] + Simple mixer control 'Console',0 + Capabilities: pswitch pswitch-joined penum + Playback channels: Mono + Mono: Playback [on] Date: Wed Jul 14 15:45:18 2010 Failure: oops Frequency: Once a day. HibernationDevice: RESUME=UUID=e938f4f3-2a95-49cf-96c1-b8bda2c16dce InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha i386 (20100630.2) MachineType: LENOVO 7764CTO PccardctlIdent: - Socket 0: -no product info available + Socket 0: + no product info available PccardctlStatus: - Socket 0: -no card + Socket 0: + no card
[Bug 475429] Re: [i945] X Freezes when compiz enabled
Tomas, the question in comment #59 was meant for the original reporter of the bug, takashi torigoe (sorry for not specifying that). These kind of bugs may look exactly the same but have totally different underlying causes, so your freeze may be an unrelated bug. If you are the experiencing freezes in Maverick, please file a new bug report about it. In the bug reporting process Launchpad is pretty eager to lead you towards possible duplicates. While that makes sense for most packages, you can ignore that for graphics-related bugs. We (and the upstream developers) would rather have many duplicate bug reports than people contributing their information to a bug reports which turns out to be different from their bug. There is some automatic freeze-detection set up in Maverick, which may tell you about the problem and offer to send a bug report. If that does not happen, please file a new bug report with the ubuntu-bug command, which will gather a lot of useful information for you. I see you have a new Launchpad account. Welcome! I hope you can contribute to making Ubuntu better. -- [i945] X Freezes when compiz enabled https://bugs.launchpad.net/bugs/475429 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379157] Re: [i945G] Samsung TV not detected on VGA output (no screens)
Following upstream and closing since patches can't be tested. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Triaged = Invalid -- [i945G] Samsung TV not detected on VGA output (no screens) https://bugs.launchpad.net/bugs/379157 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605300] [NEW] ureadahead man page does not include exit status
Public bug reported: Binary package hint: ureadahead The man page for ureadahead does not include exit status. It should be unnecessary to browse internet forums to find out what exit status 5 means (or 4 for that sake). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: ureadahead 0.100.0-5 ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4 Uname: Linux 2.6.35-7-generic i686 Architecture: i386 Date: Wed Jul 14 09:07:50 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha i386 (20100630.2) PackDump: Error: command ['ureadahead', '--dump'] failed with exit code 4: ureadahead:/var/lib/ureadahead/pack: Permission denied ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: ureadahead ** Affects: ureadahead (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- ureadahead man page does not include exit status https://bugs.launchpad.net/bugs/605300 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605300] Re: ureadahead man page does not include exit status
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/51911656/Dependencies.txt -- ureadahead man page does not include exit status https://bugs.launchpad.net/bugs/605300 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605301] [NEW] ureadahead conf file format is undocumented
Public bug reported: Binary package hint: ureadahead The format and options of /etc/init/ureadahead.conf /etc/init/ureadahead-other.conf are not documented in any file in the ureadahead package. I suppose the best place to include it is in a common man page for ureadahead.conf and ureadahead-other.conf (assuming it is the same format). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: ureadahead 0.100.0-5 ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4 Uname: Linux 2.6.35-7-generic i686 Architecture: i386 Date: Wed Jul 14 09:20:34 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha i386 (20100630.2) PackDump: Error: command ['ureadahead', '--dump'] failed with exit code 4: ureadahead:/var/lib/ureadahead/pack: Permission denied ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: ureadahead ** Affects: ureadahead (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- ureadahead conf file format is undocumented https://bugs.launchpad.net/bugs/605301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605301] Re: ureadahead conf file format is undocumented
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/51911990/Dependencies.txt -- ureadahead conf file format is undocumented https://bugs.launchpad.net/bugs/605301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605124] Re: [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
** Bug watch added: freedesktop.org Bugzilla #29048 http://bugs.freedesktop.org/show_bug.cgi?id=29048 ** Also affects: xserver-xorg-video-intel via http://bugs.freedesktop.org/show_bug.cgi?id=29048 Importance: Unknown Status: Unknown -- [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor https://bugs.launchpad.net/bugs/605124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605440] [NEW] BUG: unable to handle kernel NULL pointer dereference at 00000008
Public bug reported: This bug may be the underlying problem of bug 605124, which I have reported upstream as https://bugs.freedesktop.org/show_bug.cgi?id=29048 . I had written some more relevant information here, but I was struck by bug 553946 for the second time today, and can't remember what it was :-( I have tried several kernels, but it is hard to say anything for sure, since the frequency of this problem varies with kernel build and possibly the mood of ureadahead (i.e. how fast it is able to make the boot go). 2.6.35-7: Where I initially had the problem. Sometimes I only get this oops message in the dmesg output and everything else works fine, but often I get an the oops from bug 605124 and Xorg starts in low-graphics mode. 2.6.35-6: I have booted this 3-4 times and haven't had any problems yet. 2.6.35-rc5 (mainline build): I get this oops every now and then, but it does not affect Xorg or anything else as far as I can see. 2.6.35-rc4 (mainline build): I get this oops every now and then, but it does not affect Xorg or anything else as far as I can see. The laptop keyboard and pointer does not work with this build, but USB mouse and keyboard does. 2.6.35-rc3 (mainline build): I have tried to trigger the problem here several times without success. ureadahead sayd it would reprofile on next boot when I installed this, but it always returned exit status 5 on boot with this kernel, which may mean the boots were slower. 2010-06-15 mainline build: I have tried to trigger the problem here several times without success, but I alternated with -rc5 for comparison and in 8 boots on each, none of them had problems. 2010-06-30 mainline build: Like -rc4, laptop keyboard doesn't work and at this time I didn't have an external keyboard available. ProblemType: KernelOops DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.35-7-generic 2.6.35-7.12 Regression: Yes Reproducible: No ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4 Uname: Linux 2.6.35-7-generic i686 AcpiTables: Error: [Errno 13] Permission denied AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Annotation: Your system might become unstable now and might need to be restarted. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gom1456 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf822 irq 46' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20dd,00100400' Controls : 31 Simple ctrls : 19 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7RHT16WW-1.02' Mixer name : 'ThinkPad EC 7RHT16WW-1.02' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Wed Jul 14 15:45:18 2010 Failure: oops Frequency: Once a day. HibernationDevice: RESUME=UUID=e938f4f3-2a95-49cf-96c1-b8bda2c16dce InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha i386 (20100630.2) MachineType: LENOVO 7764CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-7-generic root=UUID=460f28a3-969c-409a-ab57-6070e2c7288e ro quiet splash RelatedPackageVersions: linux-firmware 1.37 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at 0008 dmi.bios.date: 11/27/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7SET36WW (1.22 ) dmi.board.name: 7764CTO 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:bvr7SET36WW(1.22):bd11/27/2008:svnLENOVO:pn7764CTO:pvrThinkPadX61Tablet:rvnLENOVO:rn7764CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7764CTO dmi.product.version: ThinkPad X61 Tablet dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops graphics i386 kernel-oops maverick needs-upstream-testing regression-potential -- BUG: unable to handle kernel NULL pointer dereference at 0008 https://bugs.launchpad.net/bugs/605440 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605440] Re: BUG: unable to handle kernel NULL pointer dereference at 00000008
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/51926646/AlsaDevices.txt ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/51926647/AplayDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/51926648/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/51926649/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt http://launchpadlibrarian.net/51926650/Card0.Codecs.codec.0.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/51926651/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/51926652/Dependencies.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/51926653/IwConfig.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/51926654/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/51926655/Lsusb.txt ** Attachment added: OopsText.txt http://launchpadlibrarian.net/51926656/OopsText.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/51926657/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/51926658/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/51926659/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/51926660/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/51926661/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/51926662/UdevLog.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/51926663/WifiSyslog.txt -- BUG: unable to handle kernel NULL pointer dereference at 0008 https://bugs.launchpad.net/bugs/605440 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 535640] Re: [gm45] GPU lockup de05bf80bf83cd22541cb55f1a2ee99e (xorg crash when opening the laptop lid)
The patch that fixed (or rather worked around) this problem in Lucid has not been applied upstream because the developers figure it is not necessary anymore due to some other fixes. The Maverick kernel has been without this patch for quite some time now. Could someone that was affected with this bug test Maverick to verify that this bug has not come back and we can close this bug report? -- [gm45] GPU lockup de05bf80bf83cd22541cb55f1a2ee99e (xorg crash when opening the laptop lid) https://bugs.launchpad.net/bugs/535640 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 535640] Re: [gm45] GPU lockup de05bf80bf83cd22541cb55f1a2ee99e (xorg crash when opening the laptop lid)
Thank you for testing Nicolò. I will close the upstream bug report. -- [gm45] GPU lockup de05bf80bf83cd22541cb55f1a2ee99e (xorg crash when opening the laptop lid) https://bugs.launchpad.net/bugs/535640 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596819] Re: Failsafe X displays variable name instead of file name for debugging tarball
I can now confirm this myself. I have installed a Maverick partition and got a no screens when booting with an external monitor attached and X in low-graphics mode. Thanks to Glen for already finding out where the failsafeX-backup-tar went. ** Description changed: Binary package hint: xorg As reported in https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- video-intel/+bug/589940/comments/3 , when failsafe X is triggered by using the nomodeset kernel option on intel hardware (which leads to an expected failure on Maverick), the failsafe X dialog displays: Relevant configuration and log files have been saved to: - $xorg_backup_file + $xorg_backup_file In this particular case the expected behaviour is that $xorg_backup_file should have been expanded to /var/log/failsafeX-backup-100619201009.tar. - - I haven't tried to reproduce this, since I currently don't have Maverick - installation up and running. -- Failsafe X displays variable name instead of file name for debugging tarball https://bugs.launchpad.net/bugs/596819 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596819] Re: Failsafe X displays variable name instead of file name for debugging tarball
The problem is in line 177 of debian/local/Failsafe/failsafeXinit. There is an \ before the $ in $xorg_backup_file which shouldn't be there. Since there is an eval_gettext at the beginning, the varable name was probably supposed to be part of the preceding string. So either remove the \ or do everything in one string as in the attached diff, which I have tested (at least in English). I hope this is close enough to a patch. ** Patch added: failsafeXinit.diff http://launchpadlibrarian.net/51879671/failsafeXinit.diff ** Changed in: xorg (Ubuntu) Status: Confirmed = Triaged ** Changed in: xorg (Ubuntu) Importance: Undecided = Low -- Failsafe X displays variable name instead of file name for debugging tarball https://bugs.launchpad.net/bugs/596819 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605124] [NEW] [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
Public bug reported: Binary package hint: xserver-xorg-video-intel I just installed Maverick on a partition yesterday. Sometimes (i.e. 2 out of 5 or 6 times so far) when booting with an external monitor attached I get a no screens error in the log and get xorg in low- graphics mode. I haven't seen this so far when booting without an external monitor, but I haven't tried many times yet. I booted with kernel option drm.debug=0x04 so there should be verbose mode setting information in the dmesg output. :0.log says: (EE) intel(0): [drm] failed to set drm interface version. (EE) intel(0): Failed to become DRM master. [...] DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [9] param: 4, val: 0 (EE) intel(0): failed to get resources: Bad file descriptor (EE) intel(0): Kernel modesetting setup failed (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: xorg 1:7.5+6ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4 Uname: Linux 2.6.35-7-generic i686 Architecture: i386 DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1400x1050 1280x1024 1024x768 800x600 640x480 edid-base64: AP///wAwrgVQAQOAGRJ46q9AlVZKjyUgUFQhCACBgAEBAQEBAQEBAQEBAQEBICF4yFAaCkAUdCUA9bgZEAAADwCQQzITAgAJ5QAA/gBIVjEyMVAwMS0xMDEKAHU= DRM.card0.VGA.1: status: connected enabled: enabled dpms: On modes: 1920x1200 1600x1200 1680x1050 1280x1024 1440x900 1280x960 1280x800 1024x768 800x600 800x600 640x480 edid-base64: AP///wBMLYYFNDJZTS4TAQMONCB4Ku6Ro1RMmSYPUFQjCACpQIGAgUCBAJUAswABAQEBKDyAoHCwI0AwIDYABkQhAAAa/QA4PB5REQAKICAgICAg/ABTeW5jTWFzdGVyCiAg/wBIOVhTQjA2MjMzCiAgAAU= Date: Tue Jul 13 19:35:12 2010 DkmsStatus: Error: [Errno 2] No such file or directory InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha i386 (20100630.2) MachineType: LENOVO 7764CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-7-generic root=UUID=460f28a3-969c-409a-ab57-6070e2c7288e ro quiet splash drm.debug=0x04 ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: xorg Symptom: display XorgConf: dmi.bios.date: 11/27/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7SET36WW (1.22 ) dmi.board.name: 7764CTO 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:bvr7SET36WW(1.22):bd11/27/2008:svnLENOVO:pn7764CTO:pvrThinkPadX61Tablet:rvnLENOVO:rn7764CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7764CTO dmi.product.version: ThinkPad X61 Tablet dmi.sys.vendor: LENOVO glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: maverick architecture: i686 kernel: 2.6.35-7-generic ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: 965gm maverick no-screens -- [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor https://bugs.launchpad.net/bugs/605124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605124] Re: [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/51880252/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/51880253/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/51880254/Dependencies.txt ** Attachment added: GdmLog.txt http://launchpadlibrarian.net/51880255/GdmLog.txt ** Attachment added: GdmLog1.txt http://launchpadlibrarian.net/51880256/GdmLog1.txt ** Attachment added: GdmLog2.txt http://launchpadlibrarian.net/51880257/GdmLog2.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/51880258/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/51880259/Lsusb.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/51880260/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/51880261/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/51880262/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/51880263/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/51880264/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/51880265/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/51880266/UdevLog.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/51880267/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/51880268/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/51880269/Xrandr.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/51880270/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/51880271/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/51880272/xkbcomp.txt ** Tags added: maverick -- [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor https://bugs.launchpad.net/bugs/605124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605124] Re: [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
** Attachment added: dmesg with 0x04 when the problem does not occur http://launchpadlibrarian.net/51882987/dmesg-fine.txt -- [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor https://bugs.launchpad.net/bugs/605124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605124] Re: [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
** Attachment added: Xorg.0.log from when the problem does not occur http://launchpadlibrarian.net/51883077/Xorg.0.log.old -- [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor https://bugs.launchpad.net/bugs/605124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605124] Re: [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
It turns out that this can happen also without an external monitor attached, so I will remove that part of the description. I will upload dmesg and Xorg.0.log, for a bad and fine session. ** Attachment added: dmesg with 0x04 without problem and without external monitor http://launchpadlibrarian.net/51883798/dmesg-noexternal-fine.txt -- [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor https://bugs.launchpad.net/bugs/605124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605124] Re: [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
** Attachment added: Xorg.0.log without external monitor and without problem http://launchpadlibrarian.net/51883838/Xorg.0.log -- [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor https://bugs.launchpad.net/bugs/605124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605124] Re: [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
** Attachment added: /var/log/gdm/:0.log without problem http://launchpadlibrarian.net/51884021/%3A0.log -- [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor https://bugs.launchpad.net/bugs/605124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605124] Re: [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
** Attachment added: dmesg with 0x04 with problem and without external monitor http://launchpadlibrarian.net/51885206/dmesg-noexternal-bug.txt -- [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor https://bugs.launchpad.net/bugs/605124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605124] Re: [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
** Attachment added: Xorg.5.log without external monitor with problem http://launchpadlibrarian.net/51885483/Xorg.5.log -- [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor https://bugs.launchpad.net/bugs/605124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605124] Re: [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
** Attachment added: /var/log/gdm/:5.log with problem http://launchpadlibrarian.net/51885543/%3A5.log -- [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor https://bugs.launchpad.net/bugs/605124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605124] Re: [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
** Description changed: Binary package hint: xserver-xorg-video-intel I just installed Maverick on a partition yesterday. Sometimes (i.e. 2 out of 5 or 6 times so far) when booting with an external monitor attached I get a no screens error in the log and get xorg in low- graphics mode. I haven't seen this so far when booting without an external monitor, but I haven't tried many times yet. I booted with kernel option drm.debug=0x04 so there should be verbose mode setting information in the dmesg output. + + When the problem occurs, dmesg says: + + [ 11.287021] BUG: unable to handle kernel NULL pointer dereference at (null) + [ 11.287368] IP: [c05cb14a] __mutex_lock_slowpath+0x9a/0x140 + [ 11.287647] *pde = 7ce57067 + [ 11.287790] Oops: 0002 [#1] SMP + [ 11.287957] last sysfs file: /sys/module/snd_rawmidi/initstate + [ 11.288226] Modules linked in: snd_rawmidi(+) i915(+) snd_seq_midi_event snd_seq drm_kms_helper iwlcore snd_timer mac80211 snd_seq_device drm snd yenta_socket pcmcia_rsrc intel_agp cfg80211 psmouse tpm_tis serio_raw pcmcia_core nvram i2c_algo_bit video tpm tpm_bios soundcore snd_page_alloc agpgart output lp parport usbhid hid firewire_ohci sdhci_pci firewire_core ahci sdhci led_class crc_itu_t e1000e libahci + [ 11.289012] + [ 11.289012] Pid: 370, comm: plymouthd Not tainted 2.6.35-7-generic #12-Ubuntu 7764CTO/7764CTO + [ 11.289012] EIP: 0060:[c05cb14a] EFLAGS: 00010246 CPU: 1 + [ 11.289012] EIP is at __mutex_lock_slowpath+0x9a/0x140 + [ 11.289012] EAX: EBX: f40aaa90 ECX: f40aaa98 EDX: f6a77ec0 + [ 11.289012] ESI: f40aaa94 EDI: f40aaa90 EBP: f6a77ed8 ESP: f6a77eb4 + [ 11.289012] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 + [ 11.289012] Process plymouthd (pid: 370, ti=f6a76000 task=f70fe580 task.ti=f6a76000) + [ 11.289012] Stack: + [ 11.289012] f6a77ec4 f70fe580 f40aaa98 f40aaa98 f6a77ed8 f40aaa90 f45be700 + [ 11.289012] 0 f40aaa90 f6a77ee8 c05cb095 f45be700 f45be700 f6a77efc f8393dc3 f45be700 + [ 11.289012] 0 f45be760 f40aa800 f6a77f44 f838b337 0001 f839be25 f839b220 f839d590 + [ 11.289012] Call Trace: + [ 11.289012] [c05cb095] ? mutex_lock+0x25/0x40 + [ 11.289012] [f8393dc3] ? drm_fb_release+0x23/0x70 [drm] + [ 11.289012] [f838b337] ? drm_release+0x3e7/0x4c0 [drm] + [ 11.289012] [c021a13f] ? __fput+0xdf/0x1f0 + [ 11.289012] [c021a26d] ? fput+0x1d/0x30 + [ 11.289012] [c0216b5c] ? filp_close+0x4c/0x80 + [ 11.289012] [c0216c05] ? sys_close+0x75/0xc0 + [ 11.289012] [c05cc7dc] ? syscall_call+0x7/0xb + [ 11.289012] Code: 83 79 18 63 7f b3 8d 76 00 8d 73 04 89 f0 e8 5e 11 00 00 8d 53 08 89 55 e4 8d 55 e8 8b 43 0c 89 53 0c 8b 4d e4 89 45 ec 89 4d e8 89 10 8b 45 e0 ba ff ff ff ff 89 45 f0 89 d0 87 03 83 f8 01 74 + [ 11.289012] EIP: [c05cb14a] __mutex_lock_slowpath+0x9a/0x140 SS:ESP 0068:f6a77eb4 + [ 11.289012] CR2: + [ 11.383770] ---[ end trace b880c9a6dbf71a43 ]--- + :0.log says: (EE) intel(0): [drm] failed to set drm interface version. (EE) intel(0): Failed to become DRM master. [...] DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [9] param: 4, val: 0 (EE) intel(0): failed to get resources: Bad file descriptor (EE) intel(0): Kernel modesetting setup failed (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: xorg 1:7.5+6ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4 Uname: Linux 2.6.35-7-generic i686 Architecture: i386 DRM.card0.LVDS.1: - status: connected - enabled: enabled - dpms: On - modes: 1400x1050 1280x1024 1024x768 800x600 640x480 - edid-base64: AP///wAwrgVQAQOAGRJ46q9AlVZKjyUgUFQhCACBgAEBAQEBAQEBAQEBAQEBICF4yFAaCkAUdCUA9bgZEAAADwCQQzITAgAJ5QAA/gBIVjEyMVAwMS0xMDEKAHU= + status: connected + enabled: enabled + dpms: On + modes: 1400x1050 1280x1024 1024x768 800x600 640x480 + edid-base64: AP///wAwrgVQAQOAGRJ46q9AlVZKjyUgUFQhCACBgAEBAQEBAQEBAQEBAQEBICF4yFAaCkAUdCUA9bgZEAAADwCQQzITAgAJ5QAA/gBIVjEyMVAwMS0xMDEKAHU= DRM.card0.VGA.1: - status: connected - enabled: enabled - dpms: On - modes: 1920x1200 1600x1200 1680x1050 1280x1024 1440x900 1280x960 1280x800 1024x768 800x600 800x600 640x480 - edid-base64: AP///wBMLYYFNDJZTS4TAQMONCB4Ku6Ro1RMmSYPUFQjCACpQIGAgUCBAJUAswABAQEBKDyAoHCwI0AwIDYABkQhAAAa/QA4PB5REQAKICAgICAg/ABTeW5jTWFzdGVyCiAg/wBIOVhTQjA2MjMzCiAgAAU= + status: connected + enabled: enabled + dpms: On + modes: 1920x1200 1600x1200 1680x1050 1280x1024 1440x900 1280x960 1280x800 1024x768 800x600 800x600 640x480 + edid-base64:
[Bug 605124] Re: [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
I saw the line Pid: 343, comm: plymouthd Not tainted 2.6.35-7-generic #12-Ubuntu 7764CTO/7764CTO in the dmesg output, so I tried to remove the kernel options quiet splash, but to no avail. dmesg looks the same to me, but is attached. ** Attachment added: dmesg with drm.debug=0x04 without quiet splash with problem http://launchpadlibrarian.net/51886315/dmesg-noexternal-bug.txt -- [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor https://bugs.launchpad.net/bugs/605124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605124] Re: [965gm] No screens on startup: DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
** Description changed: Binary package hint: xserver-xorg-video-intel I just installed Maverick on a partition yesterday. Sometimes (i.e. 2 - out of 5 or 6 times so far) when booting with an external monitor - attached I get a no screens error in the log and get xorg in low- - graphics mode. I haven't seen this so far when booting without an - external monitor, but I haven't tried many times yet. I booted with - kernel option drm.debug=0x04 so there should be verbose mode setting - information in the dmesg output. + out of 5 or 6 times so far) when booting I get a no screens error in + the log and get xorg in low-graphics mode. I booted with kernel option + drm.debug=0x04 so there should be verbose mode setting information in + the dmesg output. When the problem occurs, dmesg says: [ 11.287021] BUG: unable to handle kernel NULL pointer dereference at (null) [ 11.287368] IP: [c05cb14a] __mutex_lock_slowpath+0x9a/0x140 - [ 11.287647] *pde = 7ce57067 - [ 11.287790] Oops: 0002 [#1] SMP + [ 11.287647] *pde = 7ce57067 + [ 11.287790] Oops: 0002 [#1] SMP [ 11.287957] last sysfs file: /sys/module/snd_rawmidi/initstate [ 11.288226] Modules linked in: snd_rawmidi(+) i915(+) snd_seq_midi_event snd_seq drm_kms_helper iwlcore snd_timer mac80211 snd_seq_device drm snd yenta_socket pcmcia_rsrc intel_agp cfg80211 psmouse tpm_tis serio_raw pcmcia_core nvram i2c_algo_bit video tpm tpm_bios soundcore snd_page_alloc agpgart output lp parport usbhid hid firewire_ohci sdhci_pci firewire_core ahci sdhci led_class crc_itu_t e1000e libahci - [ 11.289012] + [ 11.289012] [ 11.289012] Pid: 370, comm: plymouthd Not tainted 2.6.35-7-generic #12-Ubuntu 7764CTO/7764CTO [ 11.289012] EIP: 0060:[c05cb14a] EFLAGS: 00010246 CPU: 1 [ 11.289012] EIP is at __mutex_lock_slowpath+0x9a/0x140 [ 11.289012] EAX: EBX: f40aaa90 ECX: f40aaa98 EDX: f6a77ec0 [ 11.289012] ESI: f40aaa94 EDI: f40aaa90 EBP: f6a77ed8 ESP: f6a77eb4 [ 11.289012] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 11.289012] Process plymouthd (pid: 370, ti=f6a76000 task=f70fe580 task.ti=f6a76000) [ 11.289012] Stack: [ 11.289012] f6a77ec4 f70fe580 f40aaa98 f40aaa98 f6a77ed8 f40aaa90 f45be700 [ 11.289012] 0 f40aaa90 f6a77ee8 c05cb095 f45be700 f45be700 f6a77efc f8393dc3 f45be700 [ 11.289012] 0 f45be760 f40aa800 f6a77f44 f838b337 0001 f839be25 f839b220 f839d590 [ 11.289012] Call Trace: [ 11.289012] [c05cb095] ? mutex_lock+0x25/0x40 [ 11.289012] [f8393dc3] ? drm_fb_release+0x23/0x70 [drm] [ 11.289012] [f838b337] ? drm_release+0x3e7/0x4c0 [drm] [ 11.289012] [c021a13f] ? __fput+0xdf/0x1f0 [ 11.289012] [c021a26d] ? fput+0x1d/0x30 [ 11.289012] [c0216b5c] ? filp_close+0x4c/0x80 [ 11.289012] [c0216c05] ? sys_close+0x75/0xc0 [ 11.289012] [c05cc7dc] ? syscall_call+0x7/0xb - [ 11.289012] Code: 83 79 18 63 7f b3 8d 76 00 8d 73 04 89 f0 e8 5e 11 00 00 8d 53 08 89 55 e4 8d 55 e8 8b 43 0c 89 53 0c 8b 4d e4 89 45 ec 89 4d e8 89 10 8b 45 e0 ba ff ff ff ff 89 45 f0 89 d0 87 03 83 f8 01 74 + [ 11.289012] Code: 83 79 18 63 7f b3 8d 76 00 8d 73 04 89 f0 e8 5e 11 00 00 8d 53 08 89 55 e4 8d 55 e8 8b 43 0c 89 53 0c 8b 4d e4 89 45 ec 89 4d e8 89 10 8b 45 e0 ba ff ff ff ff 89 45 f0 89 d0 87 03 83 f8 01 74 [ 11.289012] EIP: [c05cb14a] __mutex_lock_slowpath+0x9a/0x140 SS:ESP 0068:f6a77eb4 [ 11.289012] CR2: [ 11.383770] ---[ end trace b880c9a6dbf71a43 ]--- - :0.log says: (EE) intel(0): [drm] failed to set drm interface version. (EE) intel(0): Failed to become DRM master. [...] DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [9] param: 4, val: 0 (EE) intel(0): failed to get resources: Bad file descriptor (EE) intel(0): Kernel modesetting setup failed (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: xorg 1:7.5+6ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4 Uname: Linux 2.6.35-7-generic i686 Architecture: i386 DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1400x1050 1280x1024 1024x768 800x600 640x480 edid-base64: AP///wAwrgVQAQOAGRJ46q9AlVZKjyUgUFQhCACBgAEBAQEBAQEBAQEBAQEBICF4yFAaCkAUdCUA9bgZEAAADwCQQzITAgAJ5QAA/gBIVjEyMVAwMS0xMDEKAHU= DRM.card0.VGA.1: status: connected enabled: enabled dpms: On modes: 1920x1200 1600x1200 1680x1050 1280x1024 1440x900 1280x960 1280x800 1024x768 800x600 800x600 640x480 edid-base64: AP///wBMLYYFNDJZTS4TAQMONCB4Ku6Ro1RMmSYPUFQjCACpQIGAgUCBAJUAswABAQEBKDyAoHCwI0AwIDYABkQhAAAa/QA4PB5REQAKICAgICAg/ABTeW5jTWFzdGVyCiAg/wBIOVhTQjA2MjMzCiAgAAU= Date: Tue Jul 13 19:35:12
[Bug 603064] Re: [i965gm] GPU lockup 77c6dfe5
Robert Hooker wrote in comment #3: It looks like our friend bug #535640 is back as the patch fixing that is not upstream yet. I suppose we talk about: SAUCE: drm/i915: don't change DRM configuration when releasing load detect pipe It looks like that patch is not going to end up upstream. See [1] and [2]. The patch was removed from Maverick's git after Chase Douglas got someone to verify that it was no longer required [3]. [1]: http://lists.freedesktop.org/archives/intel-gfx/2010-July/007383.html [2]: https://bugs.freedesktop.org/show_bug.cgi?id=27146#c19 [3]: https://lists.ubuntu.com/archives/kernel-team/2010-May/010602.html ** Bug watch added: freedesktop.org Bugzilla #27146 http://bugs.freedesktop.org/show_bug.cgi?id=27146 -- [i965gm] GPU lockup 77c6dfe5 https://bugs.launchpad.net/bugs/603064 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 475429] Re: [i945] X Freezes when compiz enabled
According to the upstream bug report, two commits to the kernel should fix this bug. The commits are included in the current Maverick kernel. Could you verify that this now works in Maverick? -- [i945] X Freezes when compiz enabled https://bugs.launchpad.net/bugs/475429 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
