You are not logged in.

Pages: 1

#1 2016-05-04 11:34:39

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,367

X reporting BadAlloc (insufficient resources for operation)

Not sure if this is more an X problem or hardware (i915).
I close all big memory hogging problems like Firefox, but it still gives same messages.
So far restarting X clears up temporarily, until I get this message again.

I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#2 2016-05-04 14:05:47

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,804

Re: X reporting BadAlloc (insufficient resources for operation)

You must be frustrated -- given your experience, generally you would give us more to go on tongue

How about the Xorf log, relevant journal stuff, and console output (assuming this is where the error message was delivered)?

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2016-05-04 14:17:35

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,367

Re: X reporting BadAlloc (insufficient resources for operation)

Apparently I'll get an error from using mplayer or ffplay.
When I use vlc, I get an error about it not being able to find a non-existent i915_driver.so.
I can't even build mplayer-vaapi from AUR since it doesn't recognize the gpg signature as valid.  I guess mplayer-vaapi came back into the AUR, but the last time I tried to build it, it had libraries that didn't link.
I maybe running high on memory usage with firefox, but even after closing it, the error persists. 
Nothing interesting in Xorg.0.log

I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#4 2016-05-04 14:24:21

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,559
Website

Re: X reporting BadAlloc (insufficient resources for operation)

Ewaller is very good at tactfully making needed points - but in cases like these that has the risk of failing to get the message across.  You have far more than enough experience to know how to gather relevant data and ask good questions.  We can also fully understand the frustration can make it hard to collect your thoughts well and organize data for your post - thus ewaller's gentle reminder that this is still required here.  That message didn't seem to sink in.  Case in point:

nomorewindows wrote:

Apparently I'll get an error ... I get an error about it not being able to find a non-existent i915_driver.so

Apparently?  What is the error?  Not what is it "about" what is the exact error?  What have your web searches for that error turned up?  What about the non-existent library?  Did you check the repos for it?  Did you check what package it used to be in?  Did you check ldd output?  Did you rebuild AUR packages after ABI changes?  Did you read "How to ask questions the smart way"?

Moving to N.C. based on the absence of required information and lack of O.P. effort even after being prompted.  (I'm less subtle than ewaller, but there's still a hint here to take as there are worse places for a thread than the N.C).

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#5 2016-05-04 20:52:29

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,367

Re: X reporting BadAlloc (insufficient resources for operation)

I'll have to wait until it does it again, but ffplay gave one like this:

X Error of failed request:  BadAlloc (insufficient resources for operation)
  Major opcode of failed request:  140 (XVideo)
  Minor opcode of failed request:  19 ()
  Serial number of failed request:  85
  Current serial number in output stream:  86

Vlc gave one like it's looking for a libva-intel driver for i915, but one doesn't exist, only for i965_drv_video.so Which obviously I don't have.
/etc/X11/xorg.conf  that has been used for quite awhile so that awesome will work right with dual monitor setup (if one attached).

Section "ServerLayout"
	Identifier     "X.org Configured"
	Screen      0  "Screen0" 0 0
	Screen      1  "Screen1" RightOf "Screen0"
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
	ModulePath   "/usr/lib/xorg/modules"
	FontPath     "/usr/share/fonts/misc/"
	FontPath     "/usr/share/fonts/TTF/"
	FontPath     "/usr/share/fonts/OTF/"
	FontPath     "/usr/share/fonts/Type1/"
	FontPath     "/usr/share/fonts/100dpi/"
	FontPath     "/usr/share/fonts/75dpi/"
EndSection

Section "Module"
	Load  "glx"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option "XkbRules" "base"
	Option "XkbModel" "pc105"
	Option "XkbLayout" "us"
	Option "XkbVariant" ",dvorak"
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "auto"
	Option	    "Device" "/dev/input/mice"
	Option	    "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
	Identifier   "VGA1"
	VendorName   "Monitor Vendor"
	ModelName    "Monitor Model"
	Option "RightOf" "LVDS1"
EndSection

Section "Monitor"
	Identifier   "LVDS1"
	VendorName   "Monitor Vendor"
	ModelName    "Monitor Model"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
        ### <percent>: "<f>%"
        ### [arg]: arg optional
        #Option     "NoAccel"            	# [<bool>]
        #Option     "AccelMethod"        	# <str>
        #Option     "Backlight"          	# <str>
        #Option     "DRI"                	# <str>
        #Option     "ColorKey"           	# <i>
        #Option     "VideoKey"           	# <i>
        #Option     "Tiling"             	# [<bool>]
        #Option     "LinearFramebuffer"  	# [<bool>]
        #Option     "VSync"              	# [<bool>]
        #Option     "PageFlip"           	# [<bool>]
        #Option     "SwapbuffersWait"    	# [<bool>]
        #Option     "TripleBuffer"       	# [<bool>]
        #Option     "XvPreferOverlay"    	# [<bool>]
        #Option     "HotPlug"            	# [<bool>]
        #Option     "ReprobeOutputs"     	# [<bool>]
        #Option     "XvMC"               	# [<bool>]
        #Option     "ZaphodHeads"        	# <str>
        #Option     "VirtualHeads"       	# <i>
        #Option     "TearFree"           	# [<bool>]
        #Option     "PerCrtcPixmaps"     	# [<bool>]
        #Option     "FallbackDebug"      	# [<bool>]
        #Option     "DebugFlushBatches"  	# [<bool>]
        #Option     "DebugFlushCaches"   	# [<bool>]
        #Option     "DebugWait"          	# [<bool>]
        #Option     "BufferCache"        	# [<bool>]
	Identifier  "Card0"
	Driver      "intel"
	BusID       "PCI:0:2:0"
	Option "AccelMethod" "uxa"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
        ### <percent>: "<f>%"
        ### [arg]: arg optional
        #Option     "NoAccel"            	# [<bool>]
        #Option     "AccelMethod"        	# <str>
        #Option     "Backlight"          	# <str>
        #Option     "DRI"                	# <str>
        #Option     "ColorKey"           	# <i>
        #Option     "VideoKey"           	# <i>
        #Option     "Tiling"             	# [<bool>]
        #Option     "LinearFramebuffer"  	# [<bool>]
        #Option     "VSync"              	# [<bool>]
        #Option     "PageFlip"           	# [<bool>]
        #Option     "SwapbuffersWait"    	# [<bool>]
        #Option     "TripleBuffer"       	# [<bool>]
        #Option     "XvPreferOverlay"    	# [<bool>]
        #Option     "HotPlug"            	# [<bool>]
        #Option     "ReprobeOutputs"     	# [<bool>]
        #Option     "XvMC"               	# [<bool>]
        #Option     "ZaphodHeads"        	# <str>
        #Option     "VirtualHeads"       	# <i>
        #Option     "TearFree"           	# [<bool>]
        #Option     "PerCrtcPixmaps"     	# [<bool>]
        #Option     "FallbackDebug"      	# [<bool>]
        #Option     "DebugFlushBatches"  	# [<bool>]
        #Option     "DebugFlushCaches"   	# [<bool>]
        #Option     "DebugWait"          	# [<bool>]
        #Option     "BufferCache"        	# [<bool>]
	Identifier  "Card1"
	Driver      "intel"
	BusID       "PCI:0:2:1"
 	Option "AccelMethod" "uxa"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "VGA1"
	SubSection "Display"
		Viewport   1280 800
		Depth     24
	EndSubSection
EndSection

Section "Screen"
	Identifier "Screen1"
	Device     "Card1"
	Monitor    "LVDS1"
	SubSection "Display"
		Viewport   1280 1024
		Depth     24
	EndSubSection
EndSection

I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#6 2016-05-06 02:01:16

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,367

Re: X reporting BadAlloc (insufficient resources for operation)

VLC:

libva info: VA-API version 0.39.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i915_drv_video.so
libva info: va_openDriver() returns -a
Segmentation fault (core dumped)

Mplayer:

X11 error: BadAlloc (insufficient resources for operation)

ffplay:

X Error of failed request: BadAlloc (insufficient resources for operation)
   Major opcode of failed request: 150 (XVideo)
   Minor opcode of failed request: 19 ()
   Serial number of failed request : 54
   Current serial number in output stream: 55

Xorg.0.log doesn't show any errors pertaining to this.
dmesg:

vlc[xxxx]: sefault at 60 ip 00007fd4d7aefb5e sp 00007fd4d4515860 error 4 in i915_dri.so [7fd4d77b50000+606000]

According to journalctl -xb
plugin-container (of firefox) and vlc are both showing messages from systemd-coredump stack traces. 
plugin-container:

libxul.so
libevent-2.0.so.5
libpthread.so.0
libc.so.6
libflashplayer.so
libgdk-x11-2.0.so.0
libX11.so.6
libglib-2.0.so.0
i915_dri.so
libvdpau_va_gl.so.1 (this shouldn't be here, not using nvidia)
libnspr4.so

vlc:

i915_dri.so
libvdpau_va_gl.so.1
libpthread.so.0
libc.so.6
libpulse.so.0
libpulsecommon-8.0.so
libvlccore.so.8
libdbus_plugin.so
libglib-2.0.so.0
libQtGui.so.4
libQtCore.so.4
libqt4_plugin.so
libavformat_plugin.so
libavcodec.so.56

There's a couple modules that are failing in both.
vainfo:

libva info: VA-API version 0.39.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i915_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error), exit

i915_drv_video.so is not in libva-intel
i915_dri.so coming from mesa, an xorg driver
plugin-container and vlc are both crashing from usage of i915_dri.so.
The faulting module makes vaapi, vlc, plugin-container all make funny reports/error messages.

I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

Pages: 1

Board footer

Powered by FluxBB