Re: Xorg Crashes ... Ryan Daly
Thanks, Tim McConnell On Wed, 2010-01-06 at 11:27 -0800, xorg-requ...@lists.freedesktop.org wrote: What is the model of the Nvidia card? Also what do you have installed as far as software versions (xorg, that sort of thing)? I know in Fedora there are different versions of the Nvidia drivers that you have to get from a separate repo ( I think Debian calls them non free contribs, wouldn't know about any version of Unbuntu), to me it sounds like you have the wrong drivers installed. > > Message: 3 > Date: Wed, 06 Jan 2010 10:31:14 -0800 > From: "Justin P. Mattock" > Subject: Re: Xorg crashes... > To: Ryan Daly > Cc: xorg@lists.freedesktop.org > Message-ID: <4b44d6f2.2040...@gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 01/06/10 08:56, Ryan Daly wrote: > > On 01/06/2010 10:53 AM, Jeremy Huddleston wrote: > >> On Jan 6, 2010, at 10:50, Ryan Daly wrote: > >> > >>>> not sure whats going on, but by > >>>> looking at the log I see some userspace tools > >>>> erroring out(which should not keep the screen from > >>>> going forward), but I also see something about > >>>> fglrx not found.. could either mean that you > >>>> haven't the xorg module, as well as the kernel module, > >>>> or the fglrx module is crapping out with the > >>>> xserver version(had this a while ago with fglrx, > >>>> ended up switching to radeon); > >>>> > >>>> hope this helps. > >>>> > >>>> Justin P. Mattock > >>>> > >>> Justin - thanks for your reply. > >>> > >>> Is fglrx ATI specific? I have a nVidia card. I'm not sure how they all > >>> play together, though. > >> > >> fglrx is the closed-source ATI driver > >> > > > > OK. That rules that out then... > > > > The backtrace is pretty consistent with the following few lines: > > > > Program received signal SIGTERM, Terminated. > > 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 > > (gdb) backtrace r full > > #0 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 > > No symbol table info available. > > #1 0x7f1466f61516 in ?? () from > > /usr/lib/xorg/modules/input//evdev_drv.so > > No symbol table info available. > > #2 0x00447723 in DisableDevice (dev=0x18a33a0) at > > ../../dix/devices.c:407 > > > > Are those lines pointing to a device or to the card possibly? > > > > I'm running the same version of Ubuntu on three different machines, and > > I'm only experiencing the Xorg restarts on one system. I'm at a loss... > > > > yeah.. fglrx is specific to > ati chipsets(but could be wrong). > > In your case If you have nvidia > you probably should be using > nv, nouveau, or the proprietary module. > > if you can does changing your xorg.conf > to use vesa/vga have the xserver start properly? > > > Justin P. Mattock > > > > -- > > Message: 4 > Date: Wed, 06 Jan 2010 13:47:14 -0500 > From: Ryan Daly > Subject: Re: Xorg crashes... > To: "Justin P. Mattock" > Cc: xorg@lists.freedesktop.org > Message-ID: <4b44dab2.3090...@ctc.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On 01/06/2010 01:31 PM, Justin P. Mattock wrote: > >>> fglrx is the closed-source ATI driver > >>> > >> > >> OK. That rules that out then... > >> > >> The backtrace is pretty consistent with the following few lines: > >> > >> Program received signal SIGTERM, Terminated. > >> 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 > >> (gdb) backtrace r full > >> #0 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 > >> No symbol table info available. > >> #1 0x7f1466f61516 in ?? () from > >> /usr/lib/xorg/modules/input//evdev_drv.so > >> No symbol table info available. > >> #2 0x00447723 in DisableDevice (dev=0x18a33a0) at > >> ../../dix/devices.c:407 > >> > >> Are those lines pointing to a device or to the card possibly? > >> > >> I'm running the same version of Ubuntu on three different machines, and > >> I'm only experiencing the Xorg restarts on one system. I'm at a loss... > >> > > > > yeah.. fglrx is specific to > > ati chipsets(but could be wrong). > > > > In your case I
Re: kernel: [drm:drm_wait_vblank] *ERROR* failed to acquire vblank counter, -22 flood in /var/log/messages
> Disable "sync to vblank" in compiz Thanks for reminding me. I tried that and it had no effect on the issue so I uninstalled all packages for compiz and rebooted and reinstalled compiz and forgot to try that again. It did solve the issue this time. Thanks for the help. Thanks, Tim McConnell On Tue, 2009-09-22 at 13:04 +0200, drago01 wrote: > > > > On Tue, Sep 22, 2009 at 12:19 PM, Tim McConnell > wrote: > > To which versions? I have libdrm-2.4.11-2.fc11.i586 and > xorg-x11-server-Xorg.i586 0:1.6.4-0.1.fc11 with > xorg-x11-server-common.i586 0:1.6.4-0.1.fc11 > installed. > > > > > > Disable "sync to vblank" in compiz ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: kernel: [drm:drm_wait_vblank] *ERROR* failed to acquire vblank counter, -22 flood in /var/log/messages
To which versions? I have libdrm-2.4.11-2.fc11.i586 and xorg-x11-server-Xorg.i586 0:1.6.4-0.1.fc11 with xorg-x11-server-common.i586 0:1.6.4-0.1.fc11 installed. Thanks, Tim McConnell On Tue, 2009-09-22 at 02:03 +0100, Sergio Monteiro Basto wrote: > On Mon, 2009-09-21 at 18:35 -0600, Tim McConnell wrote: > > I would love any suggestions to find and resolve the problem. > Update libdrm and xorg-server > > ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
kernel: [drm:drm_wait_vblank] *ERROR* failed to acquire vblank counter, -22 flood in /var/log/messages
Hi list, I am running 2.6.30.5-43.fc11.i586 #1 SMP Thu Aug 27 21:18:54 EDT 2009 i686 i686 i386 GNU/Linux with virtualization and compiz in GNOME. I have noticed that my messages file is getting flooded with the error kernel: [drm:drm_wait_vblank] *ERROR* failed to acquire vblank counter, -22. I noticed this when my system started shutting down after 45 minutes. I ran the top command and found a program called kerneloops was running my CPU at 100%. I ran dmesg and found a bunch of the drm errors. I then looked at /var/log/messages to try to see where the drm errors were coming from. I can't tell but the drm errors are popping up multiple times per second as you can see in this snippet from the messages file: Sep 20 04:56:27 kernel: [drm:drm_wait_vblank] *ERROR* failed to acquire vblank counter, -22 Sep 20 04:56:27 kernel: [drm:drm_wait_vblank] *ERROR* failed to acquire vblank counter, -22 Sep 20 04:56:27 kernel: [drm:drm_wait_vblank] *ERROR* failed to acquire vblank counter, -22 Sep 20 04:56:27 kernel: [drm:drm_wait_vblank] *ERROR* failed to acquire vblank counter, -22 Sep 20 04:56:27 kernel: [drm:drm_wait_vblank] *ERROR* failed to acquire vblank counter, -22 Sep 20 04:56:27 kernel: [drm:drm_wait_vblank] *ERROR* failed to acquire vblank counter, -22 Sep 20 04:56:27 kernel: [drm:drm_wait_vblank] *ERROR* failed to acquire vblank counter, -22 Sep 20 04:56:27 kernel: [drm:drm_wait_vblank] *ERROR* failed to acquire vblank counter, -22 As you can guess it makes the file huge, 466.0 MB at the time I am writing this e-mail. The only thing I can find for errors is in /var/log/Xorg.1.log and it shows a backtrace of: Backtrace: 0: /usr/bin/Xorg(xorg_backtrace+0x3b) [0x812d37b] 1: /usr/bin/Xorg(xf86SigHandler+0x9e) [0x80c096e] 2: [0x854400] 3: /usr/lib/dri/i915_dri.so(intelDestroyContext+0x104) [0x424388] 4: /usr/lib/dri/i915_dri.so [0x406476] 5: /usr/lib/xorg/modules/extensions//libglx.so [0xd5d009] 6: /usr/lib/xorg/modules/extensions//libglx.so(__glXFreeContext+0x91) [0xd51151] 7: /usr/lib/xorg/modules/extensions//libglx.so [0xd51577] 8: /usr/bin/Xorg(CallCallbacks+0x56) [0x808ae86] 9: /usr/bin/Xorg(CloseDownClient+0x67) [0x8080e97] 10: /usr/bin/Xorg(Dispatch+0x1d8) [0x8086538] 11: /usr/bin/Xorg(main+0x395) [0x806bb55] 12: /lib/libc.so.6(__libc_start_main+0xe6) [0x274a66] 13: /usr/bin/Xorg [0x806b001] Fatal server error: Caught signal 11. Server aborting Please consult the The X.Org Foundation support at http://wiki.x.org The files Xorg.old and Xorg.log show nothing. I ran a strace on compiz and nothing shows in that. I also ran it on kqemu and it showed nothing. The bugs https://bugzilla.redhat.com/show_bug.cgi?id=494838 and https://bugzilla.redhat.com/show_bug.cgi?id=524394 have been filed against this problem and in Fedora Forums this post was created http://forums.fedoraforum.org/showthread.php?t=230131 which most posters in the thread state downgrading X11 resolves this issue it didn't help me any. I would love any suggestions to find and resolve the problem. I have tried removing all of the compiz packages to see if that helped and it changed nothing. The strange thing is, other than the flooding of the messages file the system seems to be working fine, desktop effects seem to function correctly and so does my virtual machines. Please help. Thanks, Tim McConnell ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
