[Ubuntu-x-swat] [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-X, which is subscribed to xserver-xorg-video-intel in 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 ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. https://bugs.launchpad.net/bugs/605124 Title: [965gm] "No screens" on startup: "DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor" ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. https://bugs.launchpad.net/bugs/541492 Title: MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. https://bugs.launchpad.net/bugs/541511 Title: MASTER: [i855] GPU lockup (apport-crash) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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 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 Signed-off-by: Chris Wilson -- You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. https://bugs.launchpad.net/bugs/541492 Title: MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. https://bugs.launchpad.net/bugs/541492 Title: MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. https://bugs.launchpad.net/bugs/541511 Title: MASTER: [i855] GPU lockup (apport-crash) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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: [] __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:[] 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] [] ? mutex_lock+0x25/0x40 [ 11.289012] [] ? drm_fb_release+0x23/0x70 [drm] [ 11.289012] [] ? drm_release+0x3e7/0x4c0 [drm] [ 11.289012] [] ? __fput+0xdf/0x1f0 [ 11.289012] [] ? fput+0x1d/0x30 [ 11.289012] [] ? filp_close+0x4c/0x80 [ 11.289012] [] ? sys_close+0x75/0xc0 [ 11.289012] [] ? 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: [] __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 2010 DkmsStatus: Error: [Errno 2] No such file or directory Installation
[Ubuntu-x-swat] [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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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: [] __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:[] 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] [] ? mutex_lock+0x25/0x40 + [ 11.289012] [] ? drm_fb_release+0x23/0x70 [drm] + [ 11.289012] [] ? drm_release+0x3e7/0x4c0 [drm] + [ 11.289012] [] ? __fput+0xdf/0x1f0 + [ 11.289012] [] ? fput+0x1d/0x30 + [ 11.289012] [] ? filp_close+0x4c/0x80 + [ 11.289012] [] ? sys_close+0x75/0xc0 + [ 11.289012] [] ? 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: [] __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: AP///wBMLYYFNDJZTS4TAQMONCB4Ku6Ro1RMmSYPUFQjCACpQIGAgUCBAJUAswABAQEBKDyAoHCwI0AwIDYABkQhAAAa/QA4PB5REQAKICAgICAg/ABTeW5jTWFzdGVyCiAg/wBIOVhTQjA2MjMzCiAgA
[Ubuntu-x-swat] [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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 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-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 601366] Re: [arrandale] Xorg freeze
** Summary changed: - Xorg freeze + [arrandale] Xorg freeze ** Tags added: arrandale -- [arrandale] Xorg freeze https://bugs.launchpad.net/bugs/601366 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 602899] Re: [i915] Xserver crash
If the GPU locks up, the output of intel_error_decode is often more interesting than intel_gpu_dump (unless the kernel hasn't noticed yet). If X is able to restart properly, it indicates that the GPU is working which may be because its state has been reset. dmesg is most interesting with drm.debug=0x02 (which turns on the drm driver debugging. Not sure if that is what you used. ** Summary changed: - [i915] Xserver crash + [gm45] Xserver crash ** Tags added: gm45 -- [gm45] Xserver crash https://bugs.launchpad.net/bugs/602899 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 589940] Re: [arrandale] maverick alpha 1 live doesn't display desktop
I take it that the original problem is now fixed, and I therefore close this bug report. The missing effects in KWin may be a bug in KWin, mesa, and others and you may file a new bug report for that. ** Changed in: xserver-xorg-video-intel (Ubuntu) Importance: Undecided => High ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Incomplete => Fix Released -- [arrandale] maverick alpha 1 live doesn't display desktop https://bugs.launchpad.net/bugs/589940 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 602736] Re: [gm45] GPU lockup 1e86c0de
Looking a little closer at the timing, I notice something strange. In the automatically collected information there is: Date: Tue Jul 6 21:01:05 2010 which is when the GPU error happened and the logs should have been collected. You reported the bug the next day (2010-07-07 - doesn't say what time of day), so this indicates that the information may have been collected in the evening when shutting down and you have been offered to submit the bug report when apport noticed the files in /var/crash/ the next day. However, XorgLog says: [15.344] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 7 15:03:57 2010 So this file seems to be far newer than it should be. But it explains why there is no trace in it about what happened the evening before. To add to the confusion, i915_error_state has the number of seconds since epoch in the first line, which should translate into Tue, 06 Jul 2010 18:33:31 GMT (according to http://www.epochconverter.com/). It seems that our GPU error bug reporting mixes up some things. -- [gm45] GPU lockup 1e86c0de https://bugs.launchpad.net/bugs/602736 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 601530] Re: drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 150858 at 150857)
I think Bryce adds those tags automatically, so he may not see this. However, it's partly correct: system: distro: Ubuntu codename: maverick architecture: i686 kernel: 2.6.32-21-generic This is the Lucid kernel running on a Maverick system. I guess Bryce's script looks at the kernel to decide the Ubuntu release. Is this an upgrade that didn't go quite well? ** Summary changed: - drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 150858 at 150857) + [965gm] drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 150858 at 150857) -- [965gm] drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 150858 at 150857) https://bugs.launchpad.net/bugs/601530 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 602736] Re: [gm45] GPU lockup 1e86c0de
Andreas, with the script /usr/share/apport/apport-gpu-error-intel.py we are (ab)using the crash report system to automatically collect information about a GPU error. So it is not really the application apport-gpu-error-intel.py that has crashed. Often a GPU error will cause the computer to freeze or behave erratically in other ways. This makes it hard to collect any information manually and this is why this automatic information collection is useful. Sometimes the GPU error can happen during the shutdown of the computer and may therefore not be noticed. Apport will in both cases notice the crash report next time it boots and will offer to submit a bug report. Did you notice any strange behaviour before apport offered to report this bug? Has this only happened once or does it happen regularly? ** Attachment added: "Gzipped result of intel_error_decode i915_error_state" http://launchpadlibrarian.net/51619510/intel_error_decode.txt.gz -- [gm45] GPU lockup 1e86c0de https://bugs.launchpad.net/bugs/602736 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 589940] Re: [arrandale] maverick alpha 1 live doesn't display desktop
The newest Ubuntu kernels (2.6.35-7) are based on -rc4 and therefore include the eDP patch. Could you verify that the display problem is gone with this kernel? If this kernel introduces the keyboard and trackpad problem, please file a new bug report for that. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Confirmed => Incomplete -- [arrandale] maverick alpha 1 live doesn't display desktop https://bugs.launchpad.net/bugs/589940 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 599452] Re: [pineviewgm] X crash after restore from hibernate
Good to hear that this is now working with the new kernel. I'm not sure which of the patches listed in the changelog could have fixed it. PGTBL_ER being anything but zero means that the graphics hardware has detected a page table error, i.e. some kind of corruption in the table that maps GPU memory addresses to physical memory addresses. This is a pretty serious bug and previously it would cause the monitor to freeze completely, requiring a reboot. Xorg is now able to recover more gracefully, but it still means that the GPU doesn't get to do what it is supposed to do. If this is a real issue and we can catch this now, there may be enough time for the intel developers to fix this before Maverick is released. Closer to the release we may get tons of bug reports about the problem, but it will be harder to get fixed since the kernel has stabilized and is behind what the upstream developers are working on and there may not be enough time for a fix. I'm closing this bug report, since the original issue is gone. But I would appreciate a new bug report for Maverick if the low-graphics fallback is triggered there. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Confirmed => Fix Released -- [pineviewgm] X crash after restore from hibernate https://bugs.launchpad.net/bugs/599452 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 599626] Re: [arrandale] X freezes after plugging in external monitor and selecting System>Preferences>Monitors
Bonne, try to be very explicit in your comments. When you say in comment #15 "but it gives exactly the same results" I interpret that as "same results as with the current Ubuntu kernel", not "same result as the LiveCD". I hope that is correct. There have been cases before where a problem does not occur when using a LiveCD simply because it is slower. This happens when one task does not have the time to complete before another task tries to use the result. I am not sure if this is such a problem. You may try a fresh install from the LiveCD without upgrading to check. There have been similar problems with some Sony Vaio laptops before, but if I remember correctly those computers froze instantly when an external monitor was connected, even if xorg was not running. Since you need to run `xrandr -q` (which is essentially what starting gnome-display- properties does) to trigger the freeze, this is more xorg related. Nevertheless, the xrandr call triggers the kernel to talk to the monitor and this is probably what causes the freeze. Since this isn't a GPU hang but some other kernel failure, I will move this bug to the kernel where triagers know better how to extract information form various kernel error conditions. ** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- [arrandale] X freezes after plugging in external monitor and selecting System>Preferences>Monitors https://bugs.launchpad.net/bugs/599626 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 596742] Re: [pineviewgm] Backlight changes at random, brightness applet doesn't work
Yorkim, I just got an EEE PC 1005P which had a similar issue. It happened both in Windows 7 and Ubuntu 10.04. Updating the BIOS from version 901 to 1103 fixed the problem. You may try to update the BIOS and see if it fixes the problem. On bug 513921 there are some suggestions for how to override the BIOS (e.g. acpi_osi=Linux on the kernel command line). -- [pineviewgm] Backlight changes at random, brightness applet doesn't work https://bugs.launchpad.net/bugs/596742 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 596742] Re: [pineviewgm] Backlight changes at random, brightness applet doesn't work
Never mind the acpi_osi option, since I see that you already use that (and acpi_backlight). -- [pineviewgm] Backlight changes at random, brightness applet doesn't work https://bugs.launchpad.net/bugs/596742 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 599452] Re: [pineviewgm] X crash after restore from hibernate
It seems that you tested the mainline build of 2.6.35-rc1, while 2.6.35-rc3 was the newest at that point (now it's -rc4). That could be the source of the other problems. There was a discussion on the intel-gfx mailing list about hibernation causing memory corruption on intel hardware last week. It resulted in this commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=985b823b919273fe1327d56d2196b4f92e5d0fae This is now included in 2.6.35-rc4 (and should also make its way to a Lucid update at some point). Could you test the mainline build of 2.6.35-rc4 with and/or without xorg-edgers? It is possible that something unrelated caused the low-graphics mode to be triggered (since as far as I understand it didn't take a hibernate cycle to trigger it). The intel_error_decode output you uploaded contains PGTBL_ER: 0x03 which is something I would worry about in a more stable configuration. I would be interested to know if this happens in Maverick as well. Could you try a LiveCD/USB on your computer and see if it goes into low-graphics mode? -- [pineviewgm] X crash after restore from hibernate https://bugs.launchpad.net/bugs/599452 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 589940] Re: [arrandale] maverick alpha 1 live doesn't display desktop
Good that the display now lights up. If I understand you correctly you have a working computer if you use an external mouse and keyboard. The mouse/keyboard problem is probably unrelated to the original problem. It may be related to using a daily build (it is possible that the mainline build of -rc4 is better) or that there are some out-of-tree drivers in the Ubuntu kernel that is not in the mainline kernel. Anyway, the Maverick kernel will be rebased to include all patches from 2.6.35-rc4 soon. At that point this bug should be fixed in Ubuntu. You can see when the ubuntu kernel was last updated at https://launchpad.net/ubuntu/+source/linux . If the next Ubuntu Maverick kernel breaks your keyboard and trackpad, please file a new bug report at that point. -- [arrandale] maverick alpha 1 live doesn't display desktop https://bugs.launchpad.net/bugs/589940 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 598177] Re: [gm45] Xorg freeze with dual monitors.
Okay, let us hope that the problem has really been fixed. I will close this bug report, since we cannot go any further with it. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Incomplete => Invalid -- [gm45] Xorg freeze with dual monitors. https://bugs.launchpad.net/bugs/598177 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 599626] Re: [arrandale] X freezes after plugging in external monitor and selecting System>Preferences>Monitors
Bonne, what exactly do you mean by "it worked the second time"? Do you mean that there was no freeze or that it froze but did not bring the network down? If it froze, the logs show that this is not a GPU hang as I first suspected. Do you connect to the computer via wireless? The wireless networking is started from X, so if X goes down it may take the wireless connection with it. For debugging X issues it is better to be connected via an ethernet cable. What you write in commen #6: BUG: soft lockup - CPU#0 stuck for 61s! [plymouthd:409] indicates that this may have something to do with plymouth. Could you remove the boot option "splash" (in the same way as you added drm.debug=0x02) and see if that changes the result of any of the tests? -- [arrandale] X freezes after plugging in external monitor and selecting System>Preferences>Monitors https://bugs.launchpad.net/bugs/599626 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 589940] Re: [arrandale] maverick alpha 1 live doesn't display desktop
I thought I would have to get a patched kernel image built for you to test this, but v4 of the patch is now commited and has found its way to the latest daily ubuntu mainline build already [1] (see [2] for more information about the mainline builds). It will also be included when 2.6.35-rc4 is released. So when you get your test partition up and running, you can test the latest daily mainline ubild or the mainline build of 2.6.35-rc4 where hopefully this problem is fixed (it is reported on the mailing list that it does not solve the problem for at least one eDP laptop). [1]: http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2010-07-02-maverick/ [2]: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds -- [arrandale] maverick alpha 1 live doesn't display desktop https://bugs.launchpad.net/bugs/589940 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 592044] Re: [g41] Blank screen after upgrade and reboot [Ubuntu 10.10alpha1 ]
Thank you for finding out what the real problem was. I will close this bug report. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Invalid -- [g41] Blank screen after upgrade and reboot [Ubuntu 10.10alpha1 ] https://bugs.launchpad.net/bugs/592044 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 598177] Re: [gm45] Xorg freeze with dual monitors.
There has been some progress upstream with respect to GPU hangs after Lucid was released. We would like to find out if this is one of those bugs or if it is still present in the latest code. In the former case we may test patches and see if it is possible to find one or more that fixes the problem. In the latter case, we will report the problem to the intel developers. In order to test the newer code, please add the xorg-edgers PPA [1] and the newest 2.6.35-rcX mainline kernel from [2] (see also [3]). Note that since this is very recent code it may contain other bugs. Install the package ppa-purge from xorg-edgers PPA to remove it again with the command `sudo ppa-purge -p xorg-edgers`. If the computer still freezes with the newest code, please install the openssh-server package which enables ssh login. Add the kernel parameter drm.debug=0x02 [4]. When the computer freezes, ssh in from another computer and run the following commands (copy and paste if you want): datestr=$(date +%Y%m%d) mkdir dri_debug-$datestr cd dri_debug-$datestr intel_error_decode >intel_error_decode.txt dmesg > dmesg.txt cp /var/log/Xorg.0.log . Then attach the files in dri_debug_2010MMDD (where MM and DD are month and date) to this bug report. In Maverick we will hopefully start generating bug reports with this information automatically soon. There is some general information about this kind of bugs at [5]. [1]: https://launchpad.net/~xorg-edgers/+archive/ppa [2]: http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D [3]: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds [4]: You can bring up the boot menu by holding shift during boot. Select the kernel and press 'e' to edit the kernel command line and Ctrl+X to boot with that command line. Another way is to add it in /etc/default/grub, add it to GRUB_CMDLINE_LINUX_DEFAULT and run `sudo update grub`. [5]: https://wiki.ubuntu.com/X/Troubleshooting/Freeze ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete -- [gm45] Xorg freeze with dual monitors. https://bugs.launchpad.net/bugs/598177 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 599017] Re: [gm45] Xorg freeze on Firefox on one particular page
There has been some progress upstream with respect to GPU hangs after Lucid was released. We would like to find out if this is one of those bugs or if it is still present in the latest code. In the former case we may test patches and see if it is possible to find one or more that fixes the problem. In the latter case, we will report the problem to the intel developers. In order to test the newer code, please add the xorg-edgers PPA [1] and the newest 2.6.35-rcX mainline kernel from [2] (see also [3]). Note that since this is very recent code it may contain other bugs. Install the package ppa-purge from xorg-edgers PPA to remove it again with the command `sudo ppa-purge -p xorg-edgers`. If the computer still freezes with the newest code, please install the openssh-server package which enables ssh login. Add the kernel parameter drm.debug=0x02 [4]. When the computer freezes, ssh in from another computer and run the following commands (copy and paste if you want): datestr=$(date +%Y%m%d) mkdir dri_debug-$datestr cd dri_debug-$datestr intel_error_decode >intel_error_decode.txt dmesg > dmesg.txt cp /var/log/Xorg.0.log . Then attach the files in dri_debug_2010MMDD (where MM and DD are month and date) to this bug report. In Maverick we will hopefully start generating bug reports with this information automatically soon. There is some general information about this kind of bugs at [5]. [1]: https://launchpad.net/~xorg-edgers/+archive/ppa [2]: http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D [3]: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds [4]: You can bring up the boot menu by holding shift during boot. Select the kernel and press 'e' to edit the kernel command line and Ctrl+X to boot with that command line. Another way is to add it in /etc/default/grub, add it to GRUB_CMDLINE_LINUX_DEFAULT and run `sudo update grub`. [5]: https://wiki.ubuntu.com/X/Troubleshooting/Freeze ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete -- [gm45] Xorg freeze on Firefox on one particular page https://bugs.launchpad.net/bugs/599017 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 599690] Re: [945gm] x.org crash while watching flash video
There has been some progress upstream with respect to GPU hangs after Lucid was released. We would like to find out if this is one of those bugs or if it is still present in the latest code. In the former case we may test patches and see if it is possible to find one or more that fixes the problem. In the latter case, we will report the problem to the intel developers. In order to test the newer code, please add the xorg-edgers PPA [1] and the newest 2.6.35-rcX mainline kernel from [2] (see also [3]). Note that since this is very recent code it may contain other bugs. Install the package ppa-purge from xorg-edgers PPA to remove it again with the command `sudo ppa-purge -p xorg-edgers`. If the computer still freezes with the newest code, please install the openssh-server package which enables ssh login. Add the kernel parameter drm.debug=0x02 [4]. When the computer freezes, ssh in from another computer and run the following commands (copy and paste if you want): datestr=$(date +%Y%m%d) mkdir dri_debug-$datestr cd dri_debug-$datestr intel_error_decode >intel_error_decode.txt dmesg > dmesg.txt cp /var/log/Xorg.0.log . Then attach the files in dri_debug_2010MMDD (where MM and DD are month and date) to this bug report. In Maverick we will hopefully start generating bug reports with this information automatically soon. There is some general information about this kind of bugs at [5]. [1]: https://launchpad.net/~xorg-edgers/+archive/ppa [2]: http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D [3]: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds [4]: You can bring up the boot menu by holding shift during boot. Select the kernel and press 'e' to edit the kernel command line and Ctrl+X to boot with that command line. Another way is to add it in /etc/default/grub, add it to GRUB_CMDLINE_LINUX_DEFAULT and run `sudo update grub`. [5]: https://wiki.ubuntu.com/X/Troubleshooting/Freeze ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete -- [945gm] x.org crash while watching flash video https://bugs.launchpad.net/bugs/599690 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 599452] Re: [pineviewgm] X crash after restore from hibernate
There has been some progress upstream with respect to GPU hangs after Lucid was released. We would like to find out if this is one of those bugs or if it is still present in the latest code. In the former case we may test patches and see if it is possible to find one or more that fixes the problem. In the latter case, we will report the problem to the intel developers. In order to test the newer code, please add the xorg-edgers PPA [1] and the newest 2.6.35-rcX mainline kernel from [2] (see also [3]). Note that since this is very recent code it may contain other bugs. Install the package ppa-purge from xorg-edgers PPA to remove it again with the command `sudo ppa-purge -p xorg-edgers`. If the computer still freezes with the newest code, please install the openssh-server package which enables ssh login. Add the kernel parameter drm.debug=0x02 [4]. When the computer freezes, ssh in from another computer and run the following commands (copy and paste if you want): datestr=$(date +%Y%m%d) mkdir dri_debug-$datestr cd dri_debug-$datestr intel_error_decode >intel_error_decode.txt dmesg > dmesg.txt cp /var/log/Xorg.0.log . Then attach the files in dri_debug_2010MMDD (where MM and DD are month and date) to this bug report. In Maverick we will hopefully start generating bug reports with this information automatically soon. There is some general information about this kind of bugs at [5]. [1]: https://launchpad.net/~xorg-edgers/+archive/ppa [2]: http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D [3]: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds [4]: You can bring up the boot menu by holding shift during boot. Select the kernel and press 'e' to edit the kernel command line and Ctrl+X to boot with that command line. Another way is to add it in /etc/default/grub, add it to GRUB_CMDLINE_LINUX_DEFAULT and run `sudo update grub`. [5]: https://wiki.ubuntu.com/X/Troubleshooting/Freeze -- [pineviewgm] X crash after restore from hibernate https://bugs.launchpad.net/bugs/599452 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 599149] Re: [945GM] Xorg freeze
There has been some progress upstream with respect to GPU hangs after Lucid was released. We would like to find out if this is one of those bugs or if it is still present in the latest code. In the former case we may test patches and see if it is possible to find one or more that fixes the problem. In the latter case, we will report the problem to the intel developers. In order to test the newer code, please add the xorg-edgers PPA [1] and the newest 2.6.35-rcX mainline kernel from [2] (see also [3]). Note that since this is very recent code it may contain other bugs. Install the package ppa-purge from xorg-edgers PPA to remove it again with the command `sudo ppa-purge -p xorg-edgers`. If the computer still freezes with the newest code, please install the openssh-server package which enables ssh login. Add the kernel parameter drm.debug=0x02 [4]. When the computer freezes, ssh in from another computer and run the following commands (copy and paste if you want): datestr=$(date +%Y%m%d) mkdir dri_debug-$datestr cd dri_debug-$datestr intel_error_decode >intel_error_decode.txt dmesg > dmesg.txt cp /var/log/Xorg.0.log . Then attach the files in dri_debug_2010MMDD (where MM and DD are month and date) to this bug report. In Maverick we will hopefully start generating bug reports with this information automatically soon. There is some general information about this kind of bugs at [5]. [1]: https://launchpad.net/~xorg-edgers/+archive/ppa [2]: http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D [3]: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds [4]: You can bring up the boot menu by holding shift during boot. Select the kernel and press 'e' to edit the kernel command line and Ctrl+X to boot with that command line. Another way is to add it in /etc/default/grub, add it to GRUB_CMDLINE_LINUX_DEFAULT and run `sudo update grub`. [5]: https://wiki.ubuntu.com/X/Troubleshooting/Freeze ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete -- [945GM] Xorg freeze https://bugs.launchpad.net/bugs/599149 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 599626] Re: [arrandale] X freezes after plugging in external monitor and selecting System>Preferences>Monitors
There has been some progress upstream with respect to GPU hangs after Lucid was released. We would like to find out if this is one of those bugs or if it is still present in the latest code. In the former case we may test patches and see if it is possible to find one or more that fixes the problem. In the latter case, we will report the problem to the intel developers. In order to test the newer code, please add the xorg-edgers PPA [1] and the newest 2.6.35-rcX mainline kernel from [2] (see also [3]). Note that since this is very recent code it may contain other bugs. Install the package ppa-purge from xorg-edgers PPA to remove it again with the command `sudo ppa-purge -p xorg-edgers`. If the computer still freezes with the newest code, please install the openssh-server package which enables ssh login. Add the kernel parameter drm.debug=0x02 [4]. When the computer freezes, ssh in from another computer and run the following commands (copy and paste if you want): datestr=$(date +%Y%m%d) mkdir dri_debug-$datestr cd dri_debug-$datestr intel_error_decode >intel_error_decode.txt dmesg > dmesg.txt cp /var/log/Xorg.0.log . Then attach the files in dri_debug_2010MMDD (where MM and DD are month and date) to this bug report. In Maverick we will hopefully start generating bug reports with this information automatically soon. There is some general information about this kind of bugs at [5]. [1]: https://launchpad.net/~xorg-edgers/+archive/ppa [2]: http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D [3]: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds [4]: You can bring up the boot menu by holding shift during boot. Select the kernel and press 'e' to edit the kernel command line and Ctrl+X to boot with that command line. Another way is to add it in /etc/default/grub, add it to GRUB_CMDLINE_LINUX_DEFAULT and run `sudo update grub`. [5]: https://wiki.ubuntu.com/X/Troubleshooting/Freeze ** Changed in: xserver-xorg-video-intel (Ubuntu) Importance: Undecided => High ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete -- [arrandale] X freezes after plugging in external monitor and selecting System>Preferences>Monitors https://bugs.launchpad.net/bugs/599626 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 599360] Re: [Intel Arrandale] Screen flickers
** Tags added: arrandale ** Tags added: flicker -- [Intel Arrandale] Screen flickers https://bugs.launchpad.net/bugs/599360 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 599690] Re: [945gm] x.org crash while watching flash video
** Summary changed: - x.org crash while watching flash video + [945gm] x.org crash while watching flash video ** Tags added: 945gm ** Tags added: freeze ** Tags removed: 945gm -- [945gm] x.org crash while watching flash video https://bugs.launchpad.net/bugs/599690 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 599017] Re: [gm45] Xorg freeze on Firefox on one particular page
** Summary changed: - Xorg freeze on Firefox on one particular page + [gm45] Xorg freeze on Firefox on one particular page ** Tags added: freeze gm45 -- [gm45] Xorg freeze on Firefox on one particular page https://bugs.launchpad.net/bugs/599017 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 599047] Re: Xorg freeze
** Tags added: gm45 ** Summary changed: - Xorg freeze + [gm45] 2x Print-Screen makes individual windows or whole desktop freeze -- [gm45] 2x Print-Screen makes individual windows or whole desktop freeze https://bugs.launchpad.net/bugs/599047 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 599149] Re: [945GM] Xorg freeze
** Summary changed: - Xorg freeze Intel 945GM + [945GM] Xorg freeze -- [945GM] Xorg freeze https://bugs.launchpad.net/bugs/599149 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 599626] Re: [arrandale] X freezes after plugging in external monitor and selecting System>Preferences>Monitors
Bonne, this bug is probably not related to any bug reports which is not for the Arrandale processor family. In tests 1a and 1b, can you replace using gnome display manager by running the command `xrandr -q`? (The answer is probably yes, but I would like it confirmed.) Can you run the command `xrandr -q --verbose > ~/xrandr.txt` after connecting the external monitor (which will probably freeze your computer). Then next time you boot the computer, check if there is anything in the file xrandr.txt in your home directory. If there is, upload it here. -- [arrandale] X freezes after plugging in external monitor and selecting System>Preferences>Monitors https://bugs.launchpad.net/bugs/599626 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 599626] Re: X freezes after plugging in external monitor and selecting System>Preferences>Monitors
** Tags added: arrandale freeze ** Summary changed: - X freezes after plugging in external monitor and selecting System>Preferences>Monitors + [arrandale] X freezes after plugging in external monitor and selecting System>Preferences>Monitors ** Tags added: dual-head regression-update -- [arrandale] X freezes after plugging in external monitor and selecting System>Preferences>Monitors https://bugs.launchpad.net/bugs/599626 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 592044] Re: [g41] Blank screen after upgrade and reboot [Ubuntu 10.10alpha1 ]
Good! There are a few more things I am a little confused about. I assume the files from comment #1 are uploaded from the NX-session. Is the XorgLog.txt from an X-session that you run in the NX-client or a non-working X-session that should have displayed on the VGA monitor? Usually when the computer starts with black screen, X also starts but does not display what it should (you may hear the startup sound if you have sound on and working) . Could you boot and log in using ssh (not the nx-client) and check the timestamps of /var/log/Xorg.*.log to see if any of them are generated during this boot. Then attach that file here. This should make sure that we get the right log. There are a number of vboxdrv messages in your dmesg. Are you running a virtual machine? Does disabling this change anything? -- [g41] Blank screen after upgrade and reboot [Ubuntu 10.10alpha1 ] https://bugs.launchpad.net/bugs/592044 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 589940] Re: [arrandale] maverick alpha 1 live doesn't display desktop
The initial kernel patch broke another laptop with eDP panel, so there is still some discussion on the mailing list about how to fix this. There is a version 2 of the patch out, but that didn't fix it on another computer which was fixed by version 1. I hope they sort it out soon, and then we can get a kernel with the final patch built for testing. Or if you feel like building kernels and testing, you can try both versions of the patch and report your findings on the mailing list (assuming it works with at least one of them). -- [arrandale] maverick alpha 1 live doesn't display desktop https://bugs.launchpad.net/bugs/589940 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 592044] Re: [g41] Blank screen after upgrade and reboot [Ubuntu 10.10alpha1 ]
zvaral, the output of dmesg in comment #4 is without drm.debug=0x04. You can see the boot parameter at the end of like 4 in that file: [0.00] Command line: BOOT_IMAGE=/vmlinuz-2.6.35-6-generic root=UUID=abc11909-dd1a-460a-ba4c-53c7c1ebbdb8 ro There should have been a drm.debug=0x04 in the end of that line. Please try again and let me know if you get any problems. Another thing: Can you confirm that your Samsung SyncMaster monitor is connected on the VGA port with a VGA cable (that is what the logs say, but sometimes the bug is that the computer gets this wrong). And yet another: Could you run `DISPLAY=:0.0 xrandr -q --verbose` and attach output here? That should give a saner output than what is in Xrandr.txt in comment #1. -- [g41] Blank screen after upgrade and reboot [Ubuntu 10.10alpha1 ] https://bugs.launchpad.net/bugs/592044 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 598948] Re: [GM45] 3D Poor graphics performance
** Summary changed: - 3D Poor graphics performance on Intel GM45 Express + [GM45] 3D Poor graphics performance ** Tags added: gm45 performance -- [GM45] 3D Poor graphics performance https://bugs.launchpad.net/bugs/598948 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 598481] Re: [i815] video unusable after 10.04 installation
** Summary changed: - video unusable after 10.04 installation + [i815] video unusable after 10.04 installation ** Tags added: i815 -- [i815] video unusable after 10.04 installation https://bugs.launchpad.net/bugs/598481 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 592044] Re: [g41] Blank screen after upgrade and reboot [Ubuntu 10.10alpha1 ]
zvaral, could you boot with the kernel parameter drm.debug=0x04 and remove "quiet splash" just to simplify the boot process. Then upload the output of dmesg. We would also like the output of intel_reg_dumper and a video bios dump taken according to https://wiki.ubuntu.com/DebuggingXorg#Obtaining%20the%20video%20BIOS . Your Xrandr.txt (output of `xrandr -q --verbose`) also looks strange, but I suppose that is because you reported the bug from a remote connection. Susan, I agree that your wishlist suggestion may be a good idea, but I don't think this is a good place to raise it is not likely to be read by the people who put these things into place. The "standard" place to raise ubuntu suggestions is at http://brainstorm.ubuntu.com, but for something like this maybe a mailing list like kernel- t...@lists.ubuntu.com might be appropriate(?) https://lists.ubuntu.com/mailman/listinfo/kernel-team -- [g41] Blank screen after upgrade and reboot [Ubuntu 10.10alpha1 ] https://bugs.launchpad.net/bugs/592044 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 595182] Re: [gm45] xorg intel crashing when screensaver starts
** Summary changed: - xorg intel crashing when screensaver starts + [gm45] xorg intel crashing when screensaver starts -- [gm45] xorg intel crashing when screensaver starts https://bugs.launchpad.net/bugs/595182 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
