From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 In-Reply-To: <20140221202127.GA28780@kroah.com> References: <20140220235118.191692546@linuxfoundation.org> <20140220235119.236520201@linuxfoundation.org> <20140221202127.GA28780@kroah.com> From: Ray Strode Date: Fri, 21 Feb 2014 17:18:02 -0500 Message-ID: Subject: Re: [PATCH 3.13 35/99] tty: Set correct tty name in active sysfs attribute To: Greg Kroah-Hartman Cc: Josh Boyer , "Linux-Kernel@Vger. Kernel. Org" , "stable@vger.kernel.org" , Lennart Poettering , Kay Sievers , Jiri Slaby , David Herrmann , Werner Fink , Hannes Reinecke Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: Hi, On Fri, Feb 21, 2014 at 3:21 PM, Greg Kroah-Hartman wrote: > Ray, Josh, can I get some more information about this? Is this broken > in Linus's tree? Or did I get the backport wrong here? I don't think it's a problem with the backport specifically. To be honest, i'm not even 100% sure it is that patch. It was just the only patch that touched that code recently so it seemed likely. I didn't do builds to check for sure. > What is the value of the file before and after this patch? "tty0" in the past and "tty1" now > And what is plymouth doing with this file value, it was incorrect > before, what was it using the value for? See the other (3.11) thread for my initial message, but basically plymouth had code something like this pseudocode: /* disable splash if there are serial consoles */ if (!contents_of_file_equals("/sys/class/tty/console/active", "tty0")) { disable_splash_and_force_verbose_messages(); } since the file started saying tty1 that code started disabling the splash for everyone in rawhide.