[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANaxB-zX4GkExeCzwgYZVDVZE47DHOCnRiYe86difk4fRMK=9A@mail.gmail.com>
Date: Wed, 27 May 2015 08:57:47 +0300
From: Andrey Wagin <avagin@...il.com>
To: Scot Doyle <lkml14@...tdoyle.com>
Cc: Tomi Valkeinen <tomi.valkeinen@...com>,
Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jslaby@...e.cz>,
Michael Kerrisk <mtk.manpages@...il.com>,
Pavel Machek <pavel@....cz>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
LKML <linux-kernel@...r.kernel.org>, linux-fbdev@...r.kernel.org,
linux-api@...r.kernel.org, linux-man@...r.kernel.org
Subject: Re: [PATCH 2/2] fbcon: use the cursor blink interval provided by vt
2015-02-27 22:15 GMT+03:00 Scot Doyle <lkml14@...tdoyle.com>:
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists