[Ubuntu-x-swat] [Bug 1243311] Re: GPU lockup when using 2 video cards
I've tried this driver again, and this time it was only able to detect one screen. I'll try with a development version next time I reboot. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1243311 Title: GPU lockup when using 2 video cards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1243311/+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 1243311] [NEW] GPU lockup when using 2 video cards
Public bug reported: My system has a Radeon HD 7750 and Radeon HD 6450, together driving 4 displays: Left: VGA on 7750 via DisplayPort adaptor, 1280x1024 Middle: DVI on 7750, 1920x1080 Right: HDMI on 7750, 1680x1050 Top (above Middle): VGA on 6450, 1280x1024 With only Left, Middle and Right enabled, everything works fine. When I try to enable the top display by running: $ xrandr --output VGA-1-0 --above DVI-0 --mode 1280x1024 then the top screen only displays noise, and the entire system will lock up for about 10 seconds at a time, then run again for 10 seconds (and the top screen goes blank), then lock up again, repeating until the top screen is disabled again. syslog and kern.log report one of the GPUs is locking up. With the proprietary driver fglrx, I can run all 4 displays, but it requires the use of Xinerama, so I have no RandR or compositing, which stinks. With the open source driver RandR and compositing work fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 22 12:59:19 2013 InstallationDate: Installed on 2013-10-22 (0 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1243311 Title: GPU lockup when using 2 video cards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1243311/+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 1243311] Re: GPU lockup when using 2 video cards
** Attachment added: syslog reporting GPU lockup https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1243311/+attachment/3887591/+files/gpu-lockup.syslog.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1243311 Title: GPU lockup when using 2 video cards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1243311/+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 1243311] Re: GPU lockup when using 2 video cards
Further research: when attempting to place the top screen in any other position (left, right, or below other displays), it displays the same noise, but the system doesn't hang. Syslog and kern.log are spammed with a new message: Oct 22 13:08:28 guilmon kernel: [ 1105.381816] radeon :02:00.0: couldn't schedule ib Oct 22 13:08:28 guilmon kernel: [ 1105.381824] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1243311 Title: GPU lockup when using 2 video cards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1243311/+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 1243311] Re: GPU lockup when using 2 video cards
** Attachment added: Xorg.0.log of issue https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1243311/+attachment/3887593/+files/gpu-lockup.Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1243311 Title: GPU lockup when using 2 video cards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1243311/+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 1243311] Re: GPU lockup when using 2 video cards
** Attachment added: kern.log reporting GPU lockup https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1243311/+attachment/3887592/+files/gpu-lockup.kern.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1243311 Title: GPU lockup when using 2 video cards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1243311/+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 1184063] Re: With nonrectangular multi-monitor arrangements, display region is wrong
Actually, I guess it's not even non-rectangular configurations that cause this issue - after changing them to a wide rectangular configuration, DVI-1 still displays the region from 1280x1024+0+0 (which is now also displayed on the topmost screen), while xrandr still claims it's 1920x1080+2560+0. The cursor isn't huge anymore though. So this just seems to be some issue with handling multi-monitor configurations. Again the cursor moves across all screens correctly, but the windows don't. Also another correction, the previous version I was using was 12.10, not 12.04. Both configurations worked fine there. (Except that Awesome WM would place windows off screen, but that's another bug...) I tried running xcompmgr to see if that would make any difference, but there's no change. ** Summary changed: - With nonrectangular multi-monitor arrangements, display region is wrong + [HD5770] Multi-monitor display region is wrong (worked in 12.10) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1184063 Title: [HD5770] Multi-monitor display region is wrong (worked in 12.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1184063/+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 1184063] [NEW] With nonrectangular multi-monitor arrangements, display region is wrong
Public bug reported: In Lubuntu 13.04, I have an unusual display configuration: three monitors arranged horizontally and a fourth centred above them. This worked fine in 12.04; after upgrading, the middle display is not working correctly. xrandr --output DVI-1 --mode 1920x1080 --rate 60 \ --output HDMI-0--mode 1680x1050 --rate 60 --right-of DVI-1 \ --output DVI-0 --mode 1280x1024 --rate 60 --left-of DVI-1 \ --output DisplayPort-0 --mode 1280x1024 --rate 60 --above DVI-1 Despite what xrandr claims, and no matter what I tell it, the middle display (DVI-1) remains at 1280x1024 and displays windows from the region 1280x1024+0+0, i.e. the region above the leftmost display (DVI-0) that shouldn't be displayed. Windows in the region 1920x1080+1280+1024, i.e. the region DVI-1 actually occupies, are not shown anywhere. The other screens display correctly. (This can only be seen by dragging a window partway off of the topmost or leftmost screen into this region, since the mouse does move correctly and won't enter this region.) Additionally, if xrandr is used to turn DVI-1 off, it will not be able to turn it back on again. Like the region issue, it will claim the display is on when it is not. Additionally, the mouse cursor appears about twice as large as normal. It does, however, move across the screens correctly. Related: http://askubuntu.com/questions/299744/lubuntu-13-04-cannot-set- display-resolution-windows-invisible-huge-mouse-curso All of these things were working correctly on the same machine in 12.04. I hadn't tried 12.10. ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1184063 Title: With nonrectangular multi-monitor arrangements, display region is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1184063/+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 1184063] Re: With nonrectangular multi-monitor arrangements, display region is wrong
I should probably also mention that all four displays are connected to an ATI HD 5700. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1184063 Title: With nonrectangular multi-monitor arrangements, display region is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1184063/+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 1184063] Re: With nonrectangular multi-monitor arrangements, display region is wrong
apport information ** Tags added: apport-collected raring ** Description changed: In Lubuntu 13.04, I have an unusual display configuration: three monitors arranged horizontally and a fourth centred above them. This worked fine in 12.04; after upgrading, the middle display is not working correctly. xrandr --output DVI-1 --mode 1920x1080 --rate 60 \ --output HDMI-0--mode 1680x1050 --rate 60 --right-of DVI-1 \ --output DVI-0 --mode 1280x1024 --rate 60 --left-of DVI-1 \ --output DisplayPort-0 --mode 1280x1024 --rate 60 --above DVI-1 Despite what xrandr claims, and no matter what I tell it, the middle display (DVI-1) remains at 1280x1024 and displays windows from the region 1280x1024+0+0, i.e. the region above the leftmost display (DVI-0) that shouldn't be displayed. Windows in the region 1920x1080+1280+1024, i.e. the region DVI-1 actually occupies, are not shown anywhere. The other screens display correctly. (This can only be seen by dragging a window partway off of the topmost or leftmost screen into this region, since the mouse does move correctly and won't enter this region.) Additionally, if xrandr is used to turn DVI-1 off, it will not be able to turn it back on again. Like the region issue, it will claim the display is on when it is not. Additionally, the mouse cursor appears about twice as large as normal. It does, however, move across the screens correctly. Related: http://askubuntu.com/questions/299744/lubuntu-13-04-cannot-set- display-resolution-windows-invisible-huge-mouse-curso - All of these things were working correctly on the same machine in 12.04. - I hadn't tried 12.10. + All of these things were working correctly on the same machine in 12.04. I hadn't tried 12.10. + --- + ApportVersion: 2.9.2-0ubuntu8 + Architecture: amd64 + DistroRelease: Ubuntu 13.04 + InstallationDate: Installed on 2013-05-25 (0 days ago) + InstallationMedia: Lubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) + MarkForUpload: True + Package: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_CA:en + TERM=xterm + PATH=(custom, no user) + LANG=en_CA.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 + Tags: raring + Uname: Linux 3.8.0-22-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1184063/+attachment/3686305/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1184063 Title: With nonrectangular multi-monitor arrangements, display region is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1184063/+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 1009350] Re: GPU lockup followed by syslog spamming
Failures are getting more frequent and varied... this is more likely a hardware issue. But I guess spamming the system log like that isn't a good thing either, so there's still a minor bug there. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1009350 Title: GPU lockup followed by syslog spamming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1009350/+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 1009350] [NEW] GPU lockup followed by syslog spamming
Public bug reported: Yesterday while my system was not being used, the GPU suddenly crashed, as indicated by syslog: Jun 5 08:11:46 akira kernel: [41332.336031] radeon :02:00.0: GPU lockup CP stall for more than 1msec Jun 5 08:11:47 akira kernel: [41332.336040] GPU lockup (waiting for 0x00525B27 last fence id 0x00525B26) Jun 5 08:11:47 akira kernel: [41332.511050] radeon: wait for empty RBBM fifo failed ! Bad things might happen. Jun 5 08:11:47 akira kernel: [41332.686023] Failed to wait GUI idle while programming pipes. Bad things might happen. Jun 5 08:11:47 akira kernel: [41332.692142] radeon :02:00.0: (r300_asic_reset:412) RBBM_STATUS=0x84014100 Jun 5 08:11:47 akira kernel: [41333.193215] radeon :02:00.0: (r300_asic_reset:431) RBBM_STATUS=0x84014100 Jun 5 08:11:47 akira kernel: [41333.690278] radeon :02:00.0: (r300_asic_reset:443) RBBM_STATUS=0x84004100 Jun 5 08:11:47 akira kernel: [41333.690311] radeon :02:00.0: restoring config space at offset 0x1 (was 0x13, writing 0x17) Jun 5 08:11:47 akira kernel: [41333.690334] radeon :02:00.0: failed to reset GPU Jun 5 08:11:47 akira kernel: [41333.690340] radeon :02:00.0: GPU reset failed Jun 5 08:11:47 akira kernel: [41333.899666] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(6). Jun 5 08:11:47 akira kernel: [41333.899672] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! The last two messages repeat several times per second, inflating the syslog to a nice 850MB until it was finally rebooted (which required a hard shutdown, as it appeared to just lock up at a blank screen after the usual shutdown process). The last thing I was doing with it was watching video in VLC. Of note is that I stopped xcompmgr shortly after starting the video as it was causing a lot of frames to drop (which is unusual as well). I tried to report this using ubuntu-bug, but only get timeout errors when submitting it. ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1009350 Title: GPU lockup followed by syslog spamming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1009350/+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 807359] Re: Disabling IRQ #24 message followed by extremely slow redrawing
Oddly enough doing nothing for 60 days hasn't fixed this. An interesting side effect when this happens is that mouse clicks lag severely or get dropped entirely. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/807359 Title: Disabling IRQ #24 message followed by extremely slow redrawing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/807359/+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 555641] Re: MASTER: max texture size prevents compiz from running
*** This bug is a duplicate of bug 824099 *** https://bugs.launchpad.net/bugs/824099 I think bug #824099 might be related to framebuffer size (plugging in the extra screen makes the display area bigger) and may well be the same issue as bug #789385, whereas this bug relates to max texture size. The former limits the size of your total display area, whereas the latter limits the size of individual windows (which unfortunately includes the root window which occupies the entire display area anyway). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/555641 Title: MASTER: max texture size prevents compiz from running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/555641/+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 808903] [NEW] Screen capture crashes X
Public bug reported: Just run any program that captures the screen (xcfe4-screenshoter, gtk- recordmydesktop), and X crashes a few seconds later. Capturing individual windows works fine. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xorg 1:7.6+4ubuntu3.1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jul 11 10:55:10 2011 DistUpgraded: Fresh install DistroCodename: natty DistroVariant: ubuntu GraphicsCard: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] [1002:5b60] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited Radeon X300 (PCIE) [174b:0500] Subsystem: PC Partner Limited Radeon X300SE [174b:0501] InstallationMedia: Xubuntu 11.04 Natty Narwhal - Release amd64 (20110426.1) MachineType: System manufacturer System name ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 Renderer: Unknown SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS A8V-E DELUXE ACPI BIOS Revision 1008 dmi.board.name: A8V-E DELUXE dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: ASUS dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8V-EDELUXEACPIBIOSRevision1008:bd06/24/2005:svnSystemmanufacturer:pnSystemname:pvr1.XX:rvnASUSTekComputerINC.:rnA8V-EDELUXE:rvr1.XX:cvnASUS:ct3:cvrChassisVersion: dmi.product.name: System name dmi.product.version: 1.XX dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 version.ia32-libs: ia32-libs 20090808ubuntu13 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash natty ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/808903 Title: Screen capture crashes X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/808903/+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 808903] Re: Screen capture crashes X
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/808903 Title: Screen capture crashes X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/808903/+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 807359] [NEW] Disabling IRQ #24 message followed by extremely slow redrawing
Public bug reported: Occasionally I get a message in kern.log: Jul 7 22:21:10 akira kernel: [86591.720160] irq 24: nobody cared (try booting with the irqpoll option) Jul 7 22:21:10 akira kernel: [86591.720167] Pid: 5016, comm: kworker/0:4 Not tainted 2.6.38-8-generic #42-Ubuntu Jul 7 22:21:10 akira kernel: [86591.720170] Call Trace: Jul 7 22:21:10 akira kernel: [86591.720172] IRQ [810d511b] ? __report_bad_irq.clone.2+0x2b/0xa0 Jul 7 22:21:10 akira kernel: [86591.720184] [810d551a] ? note_interrupt+0x19a/0x1e0 Jul 7 22:21:10 akira kernel: [86591.720189] [8106d589] ? __do_softirq+0xf9/0x1c0 Jul 7 22:21:10 akira kernel: [86591.720192] [810d640d] ? handle_fasteoi_irq+0xdd/0x110 Jul 7 22:21:10 akira kernel: [86591.720196] [8100e9c2] ? handle_irq+0x22/0x40 Jul 7 22:21:10 akira kernel: [86591.720201] [815caebd] ? do_IRQ+0x5d/0xe0 Jul 7 22:21:10 akira kernel: [86591.720242] [a0111f09] ? radeon_ttm_bo_destroy+0xa9/0xc0 [radeon] Jul 7 22:21:10 akira kernel: [86591.720246] [815c3213] ? ret_from_intr+0x0/0x15 Jul 7 22:21:10 akira kernel: [86591.720248] EOI [a00cbf50] ? ttm_bo_release_list+0x0/0x100 [ttm] Jul 7 22:21:10 akira kernel: [86591.720262] [81044837] ? __phys_addr+0x27/0x50 Jul 7 22:21:10 akira kernel: [86591.720266] [81156420] ? kfree+0x30/0x120 Jul 7 22:21:10 akira kernel: [86591.720283] [a0111f09] ? radeon_ttm_bo_destroy+0xa9/0xc0 [radeon] Jul 7 22:21:10 akira kernel: [86591.720291] [a00cbffc] ? ttm_bo_release_list+0xac/0x100 [ttm] Jul 7 22:21:10 akira kernel: [86591.720298] [a00cbf50] ? ttm_bo_release_list+0x0/0x100 [ttm] Jul 7 22:21:10 akira kernel: [86591.720303] [812de357] ? kref_put+0x37/0x70 Jul 7 22:21:10 akira kernel: [86591.720310] [a00cd111] ? ttm_bo_delayed_delete+0xd1/0x140 [ttm] Jul 7 22:21:10 akira kernel: [86591.720317] [a00cd180] ? ttm_bo_delayed_workqueue+0x0/0x40 [ttm] Jul 7 22:21:10 akira kernel: [86591.720325] [a00cd19f] ? ttm_bo_delayed_workqueue+0x1f/0x40 [ttm] Jul 7 22:21:10 akira kernel: [86591.720329] [8108269d] ? process_one_work+0x11d/0x420 Jul 7 22:21:10 akira kernel: [86591.720333] [81083298] ? worker_thread+0x168/0x360 Jul 7 22:21:10 akira kernel: [86591.720337] [81083130] ? worker_thread+0x0/0x360 Jul 7 22:21:10 akira kernel: [86591.720341] [810877e6] ? kthread+0x96/0xa0 Jul 7 22:21:10 akira kernel: [86591.720344] [8100ce24] ? kernel_thread_helper+0x4/0x10 Jul 7 22:21:10 akira kernel: [86591.720348] [81087750] ? kthread+0x0/0xa0 Jul 7 22:21:10 akira kernel: [86591.720351] [8100ce20] ? kernel_thread_helper+0x0/0x10 Jul 7 22:21:10 akira kernel: [86591.720353] handlers: Jul 7 22:21:10 akira kernel: [86591.720354] [a012ac20] (radeon_driver_irq_handler_kms+0x0/0x20 [radeon]) Jul 7 22:21:10 akira kernel: [86591.720375] Disabling IRQ #24 After this, some applications (e.g. XChat) redraw extremely slowly. (I can actually see each pixel appear on the screen one at a time!) Only fix seems to be to reboot. Others (e.g. Firefox) keep working normally. A message also appears when performing certain actions such as switching between VT and X: Jul 7 03:07:07 akira kernel: [17348.458285] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id This first started about two weeks ago. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xorg 1:7.6+4ubuntu3.1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Fri Jul 8 00:05:03 2011 DistUpgraded: Fresh install DistroCodename: natty DistroVariant: ubuntu GraphicsCard: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] [1002:5b60] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited Radeon X300 (PCIE) [174b:0500] Subsystem: PC Partner Limited Radeon X300SE [174b:0501] InstallationMedia: Xubuntu 11.04 Natty Narwhal - Release amd64 (20110426.1) MachineType: System manufacturer System name ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS A8V-E DELUXE ACPI BIOS Revision 1008 dmi.board.name: A8V-E DELUXE dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: ASUS dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8V-EDELUXEACPIBIOSRevision1008:bd06/24/2005:svnSystemmanufacturer:pnSystemname:pvr1.XX:rvnASUSTekComputerINC.:rnA8V-EDELUXE:rvr1.XX:cvnASUS:ct3:cvrChassisVersion: dmi.product.name: System name
[Ubuntu-x-swat] [Bug 807359] Re: Disabling IRQ #24 message followed by extremely slow redrawing
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/807359 Title: Disabling IRQ #24 message followed by extremely slow redrawing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/807359/+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 745839] Re: [Xpress 200M] compiz crashed with SIGSEGV in pthread_mutex_lock() due to compiz loading on rez texture size
Actually it looks like what I was experiencing was Bug #789385 - a very similar and related issue, but not the same bug. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/745839 Title: [Xpress 200M] compiz crashed with SIGSEGV in pthread_mutex_lock() due to compiz loading on rez texture size ___ 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 782552] [NEW] [xorg-edgers] Xorg crash (SIGSEGV) when taking screenshot
Public bug reported: Binary package hint: xorg Any time I try to capture a screenshot of the entire screen, with any program, Xorg crashes. Screenshots of individual windows work OK. Even using select a region with the Screenshot plugin for Xfce4-panel causes a crash as soon as I click the button (before ever getting to select anything). This is the first time I've tried to take a screenshot since installing this system so I don't know if the issue exists in older versions of X. I'll try reverting to official packages and see if it still crashes. Before this I was using an entirely different machine, with an nVidia card and x86 CPU, so I can't really say if it's ever worked on this system. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xorg 1:7.6+4ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DRM.card0.VGA.1: status: connected enabled: enabled dpms: On modes: 1680x1050 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1152x864 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 720x400 edid-base64: AP///wAebTZWJsQDAAQRAQNqLx146tQlpFVJmycTUFSna4CVD5UAgYCBQHFPAQEBAQEBfC6QoGAaHkAwIDYA2SgRAAAaITmQMGIaJ0BosDYA2SgRAAAc/QA4SxxTDwAKICAgICAg/ABMMjI2V0EKICAgICAgAOE= Date: Sat May 14 02:31:08 2011 DistUpgraded: Fresh install DistroCodename: natty DistroVariant: ubuntu GraphicsCard: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] [1002:5b60] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited Radeon X300 (PCIE) [174b:0500] Subsystem: PC Partner Limited Radeon X300SE [174b:0501] InstallationMedia: Xubuntu 11.04 Natty Narwhal - Release amd64 (20110426.1) MachineType: System manufacturer System name ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 Renderer: Unknown SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS A8V-E DELUXE ACPI BIOS Revision 1008 dmi.board.name: A8V-E DELUXE dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: ASUS dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8V-EDELUXEACPIBIOSRevision1008:bd06/24/2005:svnSystemmanufacturer:pnSystemname:pvr1.XX:rvnASUSTekComputerINC.:rnA8V-EDELUXE:rvr1.XX:cvnASUS:ct3:cvrChassisVersion: dmi.product.name: System name dmi.product.version: 1.XX dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2 version.ia32-libs: ia32-libs 20090808ubuntu13 version.libdrm2: libdrm2 2.4.25+git20110415.ba11501b-0ubuntu0sarvatt version.libgl1-mesa-dri: libgl1-mesa-dri 7.11.0+git20110512.32a95cb7-0ubuntu0sarvatt version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11.0+git20110512.32a95cb7-0ubuntu0sarvatt version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99+git20110508.90abffbd-0ubuntu0sarvatt version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.0+git20110511.895a46e8-0ubuntu0sarvatt version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110323.8378443b-0ubuntu0sarvatt ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash natty regression-update ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/782552 Title: [xorg-edgers] Xorg crash (SIGSEGV) when taking screenshot ___ 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 782552] Re: [xorg-edgers] Xorg crash (SIGSEGV) when taking screenshot
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/782552 Title: [xorg-edgers] Xorg crash (SIGSEGV) when taking screenshot ___ 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 782552] Re: [xorg-edgers] Xorg crash (SIGSEGV) when taking screenshot
Just tested, this occurs with the X server shipped with Natty as well, so this isn't an xorg-edgers issue. ** Summary changed: - [xorg-edgers] Xorg crash (SIGSEGV) when taking screenshot + Xorg crash (SIGSEGV) when taking screenshot ** Tags removed: edgers -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/782552 Title: Xorg crash (SIGSEGV) when taking screenshot ___ 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 745839] Re: [Xpress 200M] compiz crashed with SIGSEGV in pthread_mutex_lock() due to compiz loading on rez texture size
This issue has an interesting symptom on my Radeon X300SE. Compiz appears to be starting normally, but just as it finishes the screen turns into a jumbled mess of my desktop wallpaper. More interesting is if I enable Enhanced Zoom Desktop and zoom in or out, the screen alternates between that jumbled mess and the wallpaper itself - not zoomed, and with nothing else present (no windows, panels etc), but also not distorted at all. Trying to take a screenshot crashes the X server so I've attached a photo instead. The system still works just fine; I can even grab windows and move them around with the still-visible cursor (which still changes when over a text field, etc) - I just can't see them, nor anything other than this jumbled mess (or the intact wallpaper if I try to zoom). It also displays a fairly self-explanatory error message in the terminal: r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state! I wonder if a possible workaround is to not draw the root window, but draw one fake root window for each display (or each 2048x2048 region of the display area), copying from the real one or just displaying the desktop wallpaper on it, and not allow any window to be larger than that size? It seems like only the root window is likely to ever get that big in most setups, and there's not really much reason I know of not to split it into multiple windows, which would avoid creating such large textures. (A better idea of course is to split windows into multiple textures, but that requires xrandr 1.4.) Anyway I just wanted to note that odd symptom and the error message in case anyone else had been asking about it. ** Attachment added: Photo of corrupted wallpaper https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/745839/+attachment/2126637/+files/IMG_20110513_015325.jpg -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/745839 Title: [Xpress 200M] compiz crashed with SIGSEGV in pthread_mutex_lock() due to compiz loading on rez texture size ___ 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
