From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrey Wagin Date: Wed, 27 May 2015 05:57:47 +0000 Subject: Re: [PATCH 2/2] fbcon: use the cursor blink interval provided by vt Message-Id: List-Id: References: <20150225094946.GA24627@amd> <20150226220243.GC9935@amd> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Scot Doyle Cc: Tomi Valkeinen , Jean-Christophe Plagniol-Villard , Greg Kroah-Hartman , Jiri Slaby , Michael Kerrisk , Pavel Machek , Geert Uytterhoeven , LKML , linux-fbdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org 2015-02-27 22:15 GMT+03:00 Scot Doyle : > vt now provides a cursor blink interval via vc_data. Use this > interval instead of the currently hardcoded 200 msecs. Store it in > fbcon_ops to avoid locking the console in cursor_timer_handler(). I regularly execute criu tests on linux-next. For this, I use virtual machine from the digitalocean clould. The current version of linux-next hangs after a few seconds. I use git bisect to find the commit where the problem is appeaed. And it looks like the problem is in this patch. When the kernel hangs, it doesn't report anything on the screen and there is nothing suspicious in logs after reboot. I will try to reproduce the problem in my local enviroment to get more information. There is my config file: https://github.com/avagin/criu-jenkins-digitalocean/blob/d95d9e30a7da8755c47b290630bac7ee1fe7132d/jenkins-scripts/config Thanks, Andrew