Bug#278724: Info received (was Bug#278724: [nv] system hang when using gv, xmms, or lopster on NV5 [Aladdin TNT2] rev 0x20)
Ennio-Sr wrote: Hi! in my last mesage relating to the captioned bug I wrote (Nov. 24, 2004): -- I'm glad to inform you that changing the Section Screen DefaultDepth from 24 to 16 the problem seems to have disappeared: at least I could run my famous test (i.e. gv foo.txt) many times without locking the system :-) Although I think you could reasonably close the bug, one question remains: I had not set that value to 24 and, if I recall well, when I configured X in old Woody and tried to run it with the wrong value, some 'goblin' would come out from within the X Window System and tell me that depth 24 was not supported by my video card! -- Despite that I did experiment many other hanging-up, but still I had no clue as to what was happening, so I didn't report them. To-day, after my PC froze again, I took different steps which may possibly throw some light on the subject. I had all six consoles opened as follows: F1 - root (idle) F2 - user (idle) F3 - user (idle) F6 - user --start x -- running lopster (on F7) F5 - user --startx -- :1 -- running speedy (on F8) then I opened F4 - user --startx -- :2 -- running mplayer -vo xv -autosync 1 file.mpg (on F9) after half minute watching on F9, the screen (and the PC) froze. I ssh-ed in with my laptop and run top, which showed an XFree86 abosrbing from 60 to 94,6% of CPU! Instead of rebooting (as in past occasions) I killed the above high absorbing XFree86 process and nothing changed; killed .xinitrc running on tty4 (running mplayer on F9, the screen the PC had frozen on) and nothing happened; killed .xinitrc on tty5 (running speedy on F8) and saw a black line across my F9 screen: something had happened! While trying all the CTRL-ALT+F1 through F6 I could see part of the F9 screen progressively full of garbage blacking-out the window ... finally, CTRL-ALT+F7 showed me the window where lopster was running and after that I could re-gain control of my PC! While still having the laptop connected via ssh I tried to reproduce the hanging-up doing again the same steps and watching from top running on the laptop what went on on the PC: the speedy-preloader took almost 45% CPU and about 49% was taken by XFree86 when I launched mplayer ...; after a while (i.e. whan F9 window froze), XFree86 was absorbing up to 96,5% CPU. What I can conclude from my un-technical point of view is that it's the CPU's lack of resources to cause the freezing and wonder whether there could be a sort of pre-warning as to avoid it. Thanks for your attention and for your wonderful work. Regards, Ennio TRY IT!! https://www.scientificlinux.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#278724: Info received (was Bug#278724: [nv] system hang when using gv, xmms, or lopster on NV5 [Aladdin TNT2] rev 0x20)
Hi! in my last mesage relating to the captioned bug I wrote (Nov. 24, 2004): -- I'm glad to inform you that changing the Section Screen DefaultDepth from 24 to 16 the problem seems to have disappeared: at least I could run my famous test (i.e. gv foo.txt) many times without locking the system :-) Although I think you could reasonably close the bug, one question remains: I had not set that value to 24 and, if I recall well, when I configured X in old Woody and tried to run it with the wrong value, some 'goblin' would come out from within the X Window System and tell me that depth 24 was not supported by my video card! -- Despite that I did experiment many other hanging-up, but still I had no clue as to what was happening, so I didn't report them. To-day, after my PC froze again, I took different steps which may possibly throw some light on the subject. I had all six consoles opened as follows: F1 - root (idle) F2 - user (idle) F3 - user (idle) F6 - user --start x -- running lopster (on F7) F5 - user --startx -- :1 -- running speedy (on F8) then I opened F4 - user --startx -- :2 -- running mplayer -vo xv -autosync 1 file.mpg (on F9) after half minute watching on F9, the screen (and the PC) froze. I ssh-ed in with my laptop and run top, which showed an XFree86 abosrbing from 60 to 94,6% of CPU! Instead of rebooting (as in past occasions) I killed the above high absorbing XFree86 process and nothing changed; killed .xinitrc running on tty4 (running mplayer on F9, the screen the PC had frozen on) and nothing happened; killed .xinitrc on tty5 (running speedy on F8) and saw a black line across my F9 screen: something had happened! While trying all the CTRL-ALT+F1 through F6 I could see part of the F9 screen progressively full of garbage blacking-out the window ... finally, CTRL-ALT+F7 showed me the window where lopster was running and after that I could re-gain control of my PC! While still having the laptop connected via ssh I tried to reproduce the hanging-up doing again the same steps and watching from top running on the laptop what went on on the PC: the speedy-preloader took almost 45% CPU and about 49% was taken by XFree86 when I launched mplayer ...; after a while (i.e. whan F9 window froze), XFree86 was absorbing up to 96,5% CPU. What I can conclude from my un-technical point of view is that it's the CPU's lack of resources to cause the freezing and wonder whether there could be a sort of pre-warning as to avoid it. Thanks for your attention and for your wonderful work. Regards, Ennio -- [Perche' usare Win$ozz (dico io) se ...anche uno sciocco sa farlo. \\?// Fa' qualche cosa di cui non sei capace! (diceva Henry Miller) ](°|°) [Why use Win$ozz (I say) if ... even a fool can do that. )=( Do something you aren't good at! (as Henry Miller used to say) ]
Processed: Re: Bug#278724: Info received (was Bug#278724: [nv] system hang when using gv, xmms, or lopster on NV5 [Aladdin TNT2] rev 0x20)
Processing commands for [EMAIL PROTECTED]: retitle 278724 xserver-xfree86: [nv] system hang when using gv, xmms, or lopster at depth 24 on NV5 [Aladdin TNT2] rev 32 [depth 16 works] Bug#278724: xserver-xfree86: [nv] system hang when using gv, xmms, or lopster on NV5 [Aladdin TNT2] rev 0x20 Changed Bug title. tag 278724 - moreinfo Bug#278724: xserver-xfree86: [nv] system hang when using gv, xmms, or lopster at depth 24 on NV5 [Aladdin TNT2] rev 32 [depth 16 works] Tags were: upstream moreinfo Tags removed: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#278724: Info received (was Bug#278724: [nv] system hang when using gv, xmms, or lopster on NV5 [Aladdin TNT2] rev 0x20)
retitle 278724 xserver-xfree86: [nv] system hang when using gv, xmms, or lopster at depth 24 on NV5 [Aladdin TNT2] rev 32 [depth 16 works] tag 278724 - moreinfo thanks On Wed, Nov 24, 2004 at 11:57:51AM +0100, Ennio-Sr wrote: I'm glad to inform you that changing the Section Screen DefaultDepth from 24 to 16 the problem seems to have disappeared: at least I could run my famous test (i.e. gv foo.txt) many times without locking the system :-) Glad to hear that you have found a workaround! I'm sorry the Debian X mailing list was not more helpful to you. Although I think you could reasonably close the bug, one question remains: I had not set that value to 24 and, if I recall well, when I configured X in old Woody and tried to run it with the wrong value, some 'goblin' would come out from within the X Window System and tell me that depth 24 was not supported by my video card! I don't think the bug should be closed. If this model of display adapter just flat out won't work at depth 24, the driver should reject it and the X server should refuse to start. Better still, someone should fix depth 24 support in the driver. Thanks for following up! -- G. Branden Robinson| To be is to do -- Plato Debian GNU/Linux | To do is to be -- Aristotle [EMAIL PROTECTED] | Do be do be do -- Sinatra http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#278724: Info received (was Bug#278724: [nv] system hang when using gv, xmms, or lopster on NV5 [Aladdin TNT2] rev 0x20)
As I was tired of suffering continuous system blocks - reminding me of bad 'old times' when I used another OS - I downgraded xserver-common, xserver-xfree86 and xfree86-common to 4.1.01 woody4 and all the reported problems disappeared :-) May be you can get some comparison info from the following XFree86.0.log, taken after the downgrade. I notice that it's loading GLcore now (provided it does mean something): --- quote This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to XFree86@XFree86.Org and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.1.0.1 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 21 December 2001 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Build Operating System: Linux 2.6.9-rc1 i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Sat Nov 20 21:15:31 2004 (==) Using config file: /etc/X11/XF86Config-4 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Philips 107 Sx (**) | |--Device NVIDIA Corporation NV5 [Aladdin TNT2] (**) |--Input Device Generic Keyboard (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout it (**) XKB: layout: it (==) Keyboard: CustomKeycode disabled (**) |--Input Device Configured Mouse (WW) The directory /usr/lib/X11/fonts/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/lib/X11/fonts/CID does not exist. Entry deleted from font path. (**) FontPath set to unix/:7101,unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi,/usr/lib/X11/fonts/truetype (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (WW) Open APM failed (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.4 XFree86 XInput driver : 0.2 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.2 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.4 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 10b9,1621 card , rev 04 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 10b9,5247 card , rev 01 class 06,04,00 hdr 01 (II) PCI: 00:02:0: chip 10b9,5237 card , rev 03 class 0c,03,10 hdr 00 (II) PCI: 00:07:0: chip 10b9,1533 card , rev c3 class 06,01,00 hdr 00 (II) PCI: 00:0c:0: chip 13f6,0111 card 13f6,0111 rev 10 class 04,01,00 hdr 80 (II) PCI: 00:0c:1: chip 13f6,0211 card 13f6,0211 rev 10 class 07,80,00 hdr 00 (II) PCI: 00:0e:0: chip 1039,0900 card , rev 02 class 02,00,00 hdr 00 (II) PCI: 00:0f:0: chip 10b9,5229 card 10b9,5229 rev c2 class 01,01,fa hdr 00 (II) PCI: 00:14:0: chip 10ec,8139 card 10ec,8139 rev 10 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 10de,00a0 card , rev 20 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.4 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 00x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 00x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 00x - 0x (0x0) MX[B] (II) Bus
