Bug#596064: xserver-xorg: /usr/bin/X hangs (CPU 100%) on nVidia Corporation GT218 [GeForce 310]
On Fri, Sep 10, 2010 at 18:43:34 +0300, Timo Juhani Lindfors wrote: > Somebody who understand these ioctls() should try to figure out why it > never succeeds. > Likely because the GPU is hung from some earlier command, so you're stuck waiting for it? Cheers, Julien signature.asc Description: Digital signature
Bug#596064: xserver-xorg: /usr/bin/X hangs (CPU 100%) on nVidia Corporation GT218 [GeForce 310]
On 2010-09-10 17:43 +0200, Timo Juhani Lindfors wrote: > Hector Oron writes: >> I finally got it ! :) > > Thanks, this confirms my suspicion: > > ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) > --- SIGALRM (Alarm clock) @ 0 (0) --- > rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) > ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) > --- SIGALRM (Alarm clock) @ 0 (0) --- > rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) > ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) > --- SIGALRM (Alarm clock) @ 0 (0) --- > rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) > ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) > --- SIGALRM (Alarm clock) @ 0 (0) --- > rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) > ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) > --- SIGALRM (Alarm clock) @ 0 (0) --- > rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) > ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) > --- SIGALRM (Alarm clock) @ 0 (0) --- > rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) > ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) > --- SIGALRM (Alarm clock) @ 0 (0) --- > rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) > ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) > --- SIGALRM (Alarm clock) @ 0 (0) --- > rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) > ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) > --- SIGALRM (Alarm clock) @ 0 (0) --- > rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) > > Somebody who understand these ioctls() should try to figure out why it > never succeeds. I cannot claim to understand this, but it seems to be related to https://bugs.freedesktop.org/show_bug.cgi?id=26980. Sven -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87bp85bnnz@turtle.gmx.de
Bug#596064: xserver-xorg: /usr/bin/X hangs (CPU 100%) on nVidia Corporation GT218 [GeForce 310]
Hector Oron writes: > I finally got it ! :) Thanks, this confirms my suspicion: ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) ioctl(9, 0x40086485, 0x7fffa426f020) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) Somebody who understand these ioctls() should try to figure out why it never succeeds. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/84zkvpbo49@sauna.l.org
Bug#596064: xserver-xorg: /usr/bin/X hangs (CPU 100%) on nVidia Corporation GT218 [GeForce 310]
Hello Timo, > Thanks for your report (I'm not a maintainer, just happened to be > following the bug reports). After you have started X, can you login > from some other computer with ssh and run "sudo strace -p $(pidof X) > -o X.strace -s4096 -f -tt"? Then do something to trigger the bug but > note that you should not enter any passwords or sensitive > information. When X crashes, use "tail -n 5 X.strace | gzip -9 > > X.strace.gz" and send X.strace.gz to this bug report so that we see > the last 5 system calls made by the server. I have been trying to reproduce, but since I removed nouveau driver (I put it back), I have not been able to reproduce it. Cheers, -- Héctor Orón "Our Sun unleashes tremendous flares expelling hot gas into the Solar System, which one day will disconnect us." -- Day DVB-T stop working nicely Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlkti=vnvb-knetwr_otwfqbt8_yjnsmx3vzk�...@mail.gmail.com
Bug#596064: xserver-xorg: /usr/bin/X hangs (CPU 100%) on nVidia Corporation GT218 [GeForce 310]
Hector Oron writes: > X server makes CPU go at 100%. It is usually reproducible when I > open iceweasel and look into some webpage which triggers gnash, it > also happens on chromium-browser, but not so often. I blame > nouveau driver, but you might know better. Some info I am able to > provide is: Thanks for your report (I'm not a maintainer, just happened to be following the bug reports). After you have started X, can you login from some other computer with ssh and run "sudo strace -p $(pidof X) -o X.strace -s4096 -f -tt"? Then do something to trigger the bug but note that you should not enter any passwords or sensitive information. When X crashes, use "tail -n 5 X.strace | gzip -9 > X.strace.gz" and send X.strace.gz to this bug report so that we see the last 5 system calls made by the server. My very wild guess is that it is stuck in that ioctl and input events keep accumulating until miEventQueue fills up. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/84fwxkgza1@sauna.l.org
Bug#596064: xserver-xorg: /usr/bin/X hangs (CPU 100%) on nVidia Corporation GT218 [GeForce 310]
Package: xserver-xorg Version: 1:7.5+7 Severity: important Hello, X server makes CPU go at 100%. It is usually reproducible when I open iceweasel and look into some webpage which triggers gnash, it also happens on chromium-browser, but not so often. I blame nouveau driver, but you might know better. Some info I am able to provide is: $ diff -Naur Xorg.0.log /var/log/Xorg.0.log # (where Xorg.0.log is the faulty one) --- Xorg.0.log 2010-09-08 12:53:18.0 +0100 +++ /var/log/Xorg.0.log 2010-09-08 13:19:10.0 +0100 @@ -13,7 +13,7 @@ Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. -(==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 8 11:33:52 2010 +(==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 8 13:19:07 2010 (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (==) No Layout section. Using the first Screen section. @@ -448,30 +448,3 @@ (II) Macintosh mouse button emulation: initialized for relative axes. (II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/mouse0) (II) No input driver/identifier specified (ignoring) -[mi] EQ overflowing. The server is probably stuck in an infinite loop. - -Backtrace: -0: /usr/bin/X (xorg_backtrace+0x28) [0x49efe8] -1: /usr/bin/X (mieqEnqueue+0x1f4) [0x49d164] -2: /usr/bin/X (xf86PostMotionEventP+0xc4) [0x47c164] -3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f2ca02ef000+0x52ef) [0x7f2ca02f42ef] -4: /usr/bin/X (0x40+0x6bf57) [0x46bf57] -5: /usr/bin/X (0x40+0x10adf3) [0x50adf3] -6: /lib/libpthread.so.0 (0x7f2ca5a21000+0xef60) [0x7f2ca5a2ff60] -7: /lib/libc.so.6 (ioctl+0x7) [0x7f2ca45cee27] -8: /usr/lib/libdrm.so.2 (drmIoctl+0x28) [0x7f2ca2975838] -9: /usr/lib/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f2ca2975abb] -10: /usr/lib/libdrm_nouveau.so.1 (0x7f2ca233a000+0x32dd) [0x7f2ca233d2dd] -11: /usr/lib/libdrm_nouveau.so.1 (nouveau_bo_map_range+0xfc) [0x7f2ca233d51c] -12: /usr/lib/libdrm_nouveau.so.1 (0x7f2ca233a000+0x24c6) [0x7f2ca233c4c6] -13: /usr/lib/libdrm_nouveau.so.1 (nouveau_pushbuf_flush+0x29c) [0x7f2ca233c85c] -14: /usr/lib/xorg/modules/libexa.so (0x7f2ca149e000+0x9695) [0x7f2ca14a7695] -15: /usr/lib/xorg/modules/libexa.so (0x7f2ca149e000+0xa22a) [0x7f2ca14a822a] -16: /usr/bin/X (0x40+0xd038b) [0x4d038b] -17: /usr/lib/xorg/modules/libexa.so (0x7f2ca149e000+0xb510) [0x7f2ca14a9510] -18: /usr/bin/X (0x40+0xcfd9a) [0x4cfd9a] -19: /usr/bin/X (0x40+0xc6e9e) [0x4c6e9e] -20: /usr/bin/X (0x40+0x34634) [0x434634] -21: /usr/bin/X (0x40+0x25bca) [0x425bca] -22: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f2ca4525c4d] -23: /usr/bin/X (0x40+0x25779) [0x425779] $ cat /etc/X11/xorg.conf # xorg.conf (X.Org 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 "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "gb" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" EndSection Section "Device" Identifier "Configured Video Device" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" EndSection $ lspci 00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11) 00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11) 00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11) 00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11) 00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11) 00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11) 00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11) 00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11) 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06) 00:1a.0 USB Controller: Int
