Bug#519221: libpixman-1-0: libpixman in testing (0.14.0) causes terminal to be unusably slow (with regression test)
Thanks for your reply; Two days ago I switched video cards with another computer, and I no longer see this problem. I will try to reproduce it on the other machine, or, at worst, switch the cards back for this test, but because of this there will be a slight delay before I can give you results. Should I be doing anything in particular on my computer while this profiler runs? How long should I let it run before I click the profile button? Are there any other tests you want me to run while I have my old card? Thanks, Alex. 2009/5/19 Julien Cristau : > On Tue, Mar 10, 2009 at 20:06:23 -0600, Arren Lex wrote: > >> I am tracking testing. Recently after the release of lenny I noticed >> that my terminal emulator >> (konsole) became almost unusably slow. The lines refresh about twice >> as fast as I can read them >> -- that is, when I do 'ls', I can almost follow along as the output appears! >> > Hi Arren, > > Søren (upstream maintainer of pixman, CCed) would like to see sysprof > output with pixman 0.10.0 and 0.12.0, or pixman 0.12.0 with and without > sse2 optimization. Would you be willing to provide that? > > Thanks in advance, > Julien > -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#519221: libpixman -- bug recently submitted related to your patch
Hey, André; Has anything interesting happened in the last ten days? :) Were you able to get your test setup to reproduce this problem? 2009/3/14 Arren Lex : > Hello, Andre: > > Earlier, I provided my xorg configuration and Xorg.0.log (they were > not addressed to you, but you can find them on the bug's page). They > may help you to set up an environment. > There is no colour depth specified in my xorg configuration, so it's > whatever it defaults to -- I guess 24? > > I have a laptop running debian (intel video drivers) where this bug > does not appear. Therefore, it looks like something particular to my > configuration. I hope you can reproduce it on your test setup, but if > not, I am happy to try anything you suggest or apply any patches. > > Thanks for all your help, > Arren > > 2009/3/14 André Tupinambá : >> Hi Arren, >> >> The SSE2 code is really faster than C equivalent, but performs better >> with images larger than 16 pixels wide. Since to get the SSE2 best >> performance we need to align the destination address in 16 bytes. So >> all operations are made in three loops, one for the alignment, one for >> the bulk operation and the last one for operate the last pixels. But >> with small images, all operations are done within the alignment and >> tail loops. That is what is going on on this case, I guess. >> >> I'm creating and environment to trying to get this bug. Which color >> depth are you using? >> >> Regards. >> André Tupinambá >> >> On Wed, Mar 11, 2009 at 8:06 PM, Arren Lex wrote: >>> Sorry, I left out this piece of possibly useful information: >>> >>> I have a dual-monitor setup -- one is 1280x1024 and one is 1680x1050. >>> I usually run konsole maximized across the larger monitor, and it is >>> terribly slow like that. When I make the konsole window smaller, the >>> problem becomes less noticeable (but even when the window is very >>> small, you can easily tell the problem is still there because the text >>> makes waves as it scrolls). This behaviour leads me to think it might >>> be falling back to software rendering for painting the text now. Is >>> that possible? >>> >> > -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#519221: libpixman -- bug recently submitted related to your patch
Hello, Andre: Earlier, I provided my xorg configuration and Xorg.0.log (they were not addressed to you, but you can find them on the bug's page). They may help you to set up an environment. There is no colour depth specified in my xorg configuration, so it's whatever it defaults to -- I guess 24? I have a laptop running debian (intel video drivers) where this bug does not appear. Therefore, it looks like something particular to my configuration. I hope you can reproduce it on your test setup, but if not, I am happy to try anything you suggest or apply any patches. Thanks for all your help, Arren 2009/3/14 André Tupinambá : > Hi Arren, > > The SSE2 code is really faster than C equivalent, but performs better > with images larger than 16 pixels wide. Since to get the SSE2 best > performance we need to align the destination address in 16 bytes. So > all operations are made in three loops, one for the alignment, one for > the bulk operation and the last one for operate the last pixels. But > with small images, all operations are done within the alignment and > tail loops. That is what is going on on this case, I guess. > > I'm creating and environment to trying to get this bug. Which color > depth are you using? > > Regards. > André Tupinambá > > On Wed, Mar 11, 2009 at 8:06 PM, Arren Lex wrote: >> Sorry, I left out this piece of possibly useful information: >> >> I have a dual-monitor setup -- one is 1280x1024 and one is 1680x1050. >> I usually run konsole maximized across the larger monitor, and it is >> terribly slow like that. When I make the konsole window smaller, the >> problem becomes less noticeable (but even when the window is very >> small, you can easily tell the problem is still there because the text >> makes waves as it scrolls). This behaviour leads me to think it might >> be falling back to software rendering for painting the text now. Is >> that possible? >> > -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#519221: libpixman -- bug recently submitted related to your patch
I forgot to CC the bug in this conversation. The following is Michel's response and my reply: >> The 2D acceleration engine supports a 4096x4096 desktop and I am well >> within that limit. Also, I don't see why using a terminal emulator >> should depend on 3D acceleration. > >For text rendering, which these days is usually implemented using a >RENDER extension Composite operation. > >> Furthermore, this setup worked perfectly before that pixman patch. If >> it is related to my 3D virtual desktop size, why is it that an sse2 >> patch in pixman triggered the problem? > >It didn't; apparently the software rendering speed was just good enough >for you before. I'm just saying that you might get even better >performance than before with hardware acceleration, but of course the >pixman performance regression should be addressed regardless. > > Earthling Michel Dänzer |http://www.vmware.com > Libre software enthusiast | Debian, X and DRI developer Ah, I misunderstood the intent of your reply. I am quite content with what I had before; if we can fix the pixman regression and I can have a snappy console again, I will be happy, regardless of what is doing the rendering. :) I have never experienced performance problems and would much rather continue to work as I have than to run below native resolution of my monitors to fit in the 3D desktop buffer, purchase a new video card, or rearrange my monitor setup. Arren -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#519221: libpixman -- bug recently submitted related to your patch
Hello, Michel; > This is likely your first problem. The 3D engine of your card can only > handle coordinates up to 2560x2560. I don't understand how this could be a factor. I am well aware that part of my screen is out of the 3D engine's domain, but this is not a problem for me as I don't do anything that requires 3D acceleration. The 2D acceleration engine supports a 4096x4096 desktop and I am well within that limit. Also, I don't see why using a terminal emulator should depend on 3D acceleration. Furthermore, this setup worked perfectly before that pixman patch. If it is related to my 3D virtual desktop size, why is it that an sse2 patch in pixman triggered the problem? > However, due to peculiarities in the way KDE/Qt4 render text, I suspect > you may still be hitting other fallback paths which have only been fixed > in newer xserver upstream. I am using kde3 at the moment. Thanks, Arren -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#519221: libpixman -- bug recently submitted related to your patch
Sorry, I left out this piece of possibly useful information: I have a dual-monitor setup -- one is 1280x1024 and one is 1680x1050. I usually run konsole maximized across the larger monitor, and it is terribly slow like that. When I make the konsole window smaller, the problem becomes less noticeable (but even when the window is very small, you can easily tell the problem is still there because the text makes waves as it scrolls). This behaviour leads me to think it might be falling back to software rendering for painting the text now. Is that possible? -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#519221: libpixman -- bug recently submitted related to your patch
Thank you for your response. I have compiled the latest git of pixman with the --disable-sse2 flag and it works perfectly. The problems are gone when I disable that flag. Here is some more information about my system in case any of it is helpful: - AMD Opteron dual-core CPU, 2.4 GHz, supporting with flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy. - I am running a 32-bit OS, although the CPU supports 64. - ATI X300SE PCI-E video card, using the free and open-source radeon driver for 3D acceleration. I believe this driver only supports some of openGL 1.2. - Kernel 2.6.26 - 1GB ram - Terminal emulator is konsole from KDE 3.5; pseudo-transparency is turned on (that is, it paints the desktop background as the terminal background to make it "appear" transparent) I hope we can find the source of this problem. :) Is it possible to take out only some of the sse2 modifications so we can determine which optimization is causing problems? Thanks for your time, Arren 2009/3/11 André Tupinambá : > Hi Arren, > > This is a old patch, about add SSE2 implementation for many compose > operations. This code was first released in pixman 0.12.0. I really > don't know what is going on, I need to investigate this. > > Just in case, a good test is run the pixman configure with > --disable-sse2, to disable this code, keeping all other pixman > implementation and modifications. > > BTW, I care about :) > > []'s > André Tupinambá > > PS: Sorry about any English mistakes, I'm Brazillian and English isn't > my first language. > > On Wed, Mar 11, 2009 at 12:11 AM, Arren Lex wrote: >> Hello; >> >> I have recently submitted a libpixman bug introduced by a regression >> caused by one of your patches. The bug report is available here -- >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519221 >> >> I don't know if you care about this; I was just hoping you may have >> had some insight as to what causes it, or ideas how to fix it. :) I >> want my terminal back! >> >> If you want, you can comment on the bug report by emailing responses >> to 519...@bugs.debian.org >> >> Thanks a lot for your time, >> Arren Lex >> > -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#519221: libpixman-1-0: libpixman in testing (0.14.0) causes terminal to be unusably slow (with regression test)
Package: libpixman-1-0 Version: 0.14.0-1 Severity: important I am tracking testing. Recently after the release of lenny I noticed that my terminal emulator (konsole) became almost unusably slow. The lines refresh about twice as fast as I can read them -- that is, when I do 'ls', I can almost follow along as the output appears! After some testing I have narrowed it to libpixman-1-0. I checked out the git and did a bisect, and determined the problem is the following commit: 92ef26dfed3337831dd5156bfe0d20b132a26a29 is first bad commit commit 92ef26dfed3337831dd5156bfe0d20b132a26a29 Author: André Tupinambá Date: Wed Apr 23 00:18:39 2008 -0400 Add SSE2 implementations of many compositing operations. :100644 100644 0f52b87fa20e215a1cbd7e77928686c8c5686940 637f835221631b0f3d79d8f0f3b256883d34770b M configure.ac :04 04 8a345622711e2e9c7a357a702635bb1e052bf10a 8844fa5f04805106ede92dab9db61f2fd95bacea M pixman This happened a bit after the version 0.11.1 tag (lenny has 0.10.0 and squeeze has 0.14.0). I hope this can be fixed, as it makes my terminal incredibly frustrating to use. -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (1001, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libpixman-1-0 depends on: ii libc6 2.7-18 GNU C Library: Shared libraries libpixman-1-0 recommends no packages. libpixman-1-0 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#479870: Info received (Bug#479870: Info received (Bug#479870: xserver-xorg-video-ati: Frequent system lockups since upgrade))
Sorry! Forget what I said. I just got a freeze with the latest git drivers, I guess this is still a problem. It just took much longer to appear than before. I guess this bug is still open. I've been regression-testing it using git bisect, and I think I found the commit that broke it, but in light of this unexpected freeze I think I need to keep testing the revision I think is good to make sure. 2008/5/18 Debian Bug Tracking System <[EMAIL PROTECTED]>: > > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian X Strike Force > > If you wish to submit further information on this problem, please > send it to [EMAIL PROTECTED], as before. > > Please do not send mail to [EMAIL PROTECTED] unless you wish > to report a problem with the Bug-tracking system. > > > -- > 479870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479870 > Debian Bug Tracking System > Contact [EMAIL PROTECTED] with problems > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479870: Info received (Bug#479870: xserver-xorg-video-ati: Frequent system lockups since upgrade)
The git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati repository is the one I tested, and yes, the May 12 checkout seems to be good already. 2008/5/18 Brice Goglin <[EMAIL PROTECTED]>: > Arren Lex wrote: >> I've checked and discovered that this problem is fixed in >> freedesktop's git. :) Hope this fix gets down to testing soon. >> > > Which git repo ? The one from the xf86-video-ati driver ? If so, is the > fix in the latest experimental package (from May 12th)? > > Brice > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479870: Info received (Bug#479870: xserver-xorg-video-ati: Frequent system lockups since upgrade)
I've checked and discovered that this problem is fixed in freedesktop's git. :) Hope this fix gets down to testing soon. 2008/5/13 Debian Bug Tracking System <[EMAIL PROTECTED]>: > > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian X Strike Force > > If you wish to submit further information on this problem, please > send it to [EMAIL PROTECTED], as before. > > Please do not send mail to [EMAIL PROTECTED] unless you wish > to report a problem with the Bug-tracking system. > > > -- > 479870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479870 > Debian Bug Tracking System > Contact [EMAIL PROTECTED] with problems > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479870: xserver-xorg-video-ati: Frequent system lockups since upgrade
> Do either of the following options help? > > Option "AGPMode" "1" > Option "BusType" "PCI" > > Also, this issue could be mesa or drm related. what versions where > you running previously? > > Alex > Sorry for the long wait, I managed to downgrade xserver-xorg-video-ati from the old versions I had in /var/cache/apt/archives after a lot of messing with dependencies, and I didn't want to upgrade again until I got my hands on another hard drive and imaged my root partition. Neither of those options helps. AGPMode "1" doesn't seem to have any effect, and "BusType" "PCI" just disables acceleration, causing the following in dmesg: [drm] Setting GART location based on new memory map [drm:radeon_do_init_cp] *ERROR* Cannot use PCI Express without GART in FB memory Both of these tests were done in exa mode, since you didn't specify. Let me know if I should use xaa. I don't know what versions of mesa and drm I was running previously, but I do know that that the following packages are the *only* ones I downgraded (according to dpkg.log), and downgrading fixed my problem. Upgrading these packages caused it again. xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev xserver-xorg-input-kbd xserver-xorg-input-mouse xserver-xorg-video-all xserver-xorg-video-ati Thanks for your reply, and again, sorry for the delay! ~ Arren -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479870: xserver-xorg-video-ati: Frequent system lockups since upgrade
Subject: xserver-xorg-video-ati: Frequent system lockups since upgrade Package: xserver-xorg-video-ati Version: 1:6.8.1~git20080417.c5d62fa0-1 Severity: normal *** Please type your report below this line *** I run lenny (testing), which has recently gotten the new 1:6.8.0-1 pacakage. Since then, every game of Frets on Fire ends with total system lockup -- no RSEIUB, no SSH, no switching to VT, no capslock light; I have to use the reset button. This has never happened to me before; the driver version prior to this always performed perfectly no matter how long I played. Now, sometimes it takes 10 seconds, sometimes it takes 30 minutes, but it will freeze. I tried the experimental package to see if the problem was fixed, but it was not. It occurs in either exa or xaa mode. The xorg.conf below uses exa, to use xaa I simply comment out the unindented exa lines in the device section. If there is any more debugging output I can provide, please let me know. The card is: 02:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Unknown device 0082 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: radeonfb -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2008-04-23 13:25 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1674940 2008-04-29 12:37 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 02:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 1878 2008-05-06 21:59 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ExplorerPS/2" Option "ZAxisMapping" "4 5" Option "Buttons" "6" EndSection Section "Device" Identifier "ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]" Driver "ati" BusID "PCI:2:0:0" Option "GARTSize" "64" Option "AccelMethod" "exa" Option "MigrationHeuristic" "greedy" Option "ExaNoComposite" "false" EndSection Section "Monitor" Identifier "SyncMaster" Option "DPMS" HorizSync 30-65 VertRefresh 50-75 EndSection Section "Screen" Identifier "Default Screen" Device "ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]" Monitor "SyncMaster" DefaultDepth24 SubSection "Display" Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "DRI" Mode0666 EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 48521 2008-05-06 23:02 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the "xorg" product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. X.Org X Serve
