Hi! actually:
13302 glxgears CALL ioctl(0x4,0xc0106471 ,0x7fffffffc760) 13302 glxgears RET ioctl -1 errno 22 Invalid argument 13302 glxgears CALL ioctl(0x4,0xc010645b ,0x7fffffffc6c0) 13302 glxgears RET ioctl 0 13302 glxgears CALL ioctl(0x4,0xc020645e ,0x7fffffffc710) 13302 glxgears RET ioctl 0 13302 glxgears CALL ioctl(0x4,0x800c645f ,0x7fffffffc730) 13302 glxgears RET ioctl 0 13302 glxgears CALL ioctl(0x4,0xc010645b ,0x7fffffffc6e0) 13302 glxgears RET ioctl 0 13302 glxgears CALL ioctl(0x4,0xc008646d ,0x7fffffffc870) 13302 glxgears RET ioctl -1 errno 22 Invalid argument the last one seems to indeed be DRM_IOCTL_I915_GEM_CONTEXT_CREATE .. I shouldn't rely on kdump actually finding the symbol for arbitrary ioctls Christoph -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
