Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751434AbbLUIVo (ORCPT ); Mon, 21 Dec 2015 03:21:44 -0500 Received: from edison.jonmasters.org ([173.255.233.168]:57831 "EHLO edison.jonmasters.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751006AbbLUIVl (ORCPT ); Mon, 21 Dec 2015 03:21:41 -0500 X-Greylist: delayed 1627 seconds by postgrey-1.27 at vger.kernel.org; Mon, 21 Dec 2015 03:21:41 EST Message-ID: <5677B03F.1030506@jonmasters.org> Date: Mon, 21 Dec 2015 02:54:39 -0500 From: Jon Masters User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Greg Kroah-Hartman , Masahiro Yamada CC: linux-serial@vger.kernel.org, Linux Kernel Mailing List , Peter Hurley , Rob Herring References: <20151128000451.GB22297@kroah.com> <20151130171034.GA14366@kroah.com> In-Reply-To: <20151130171034.GA14366@kroah.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 74.92.29.237 X-SA-Exim-Mail-From: jonathan@jonmasters.org Subject: Re: The console log is doubled if earlycon is enabled X-SA-Exim-Version: 4.2.1 (built Sun, 08 Nov 2009 07:31:22 +0000) X-SA-Exim-Scanned: Yes (on edison.jonmasters.org) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1335 Lines: 38 On 11/30/15, 12:10 PM, Greg Kroah-Hartman wrote: > On Mon, Nov 30, 2015 at 02:53:49PM +0900, Masahiro Yamada wrote: >> 2015-11-28 9:04 GMT+09:00 Greg Kroah-Hartman : >>> On Fri, Nov 27, 2015 at 07:21:06PM +0900, Masahiro Yamada wrote: >>>> Hi, >>>> >>>> >>>> If I add "earlycon" to the kernel parameter, the log message >>>> on the earlycon is also displayed to the regular console. >>>> In other words, the same log messages are displayed twice. >>>> >>>> I noticed this problem on v4.4-rc1. >>>> It has not been fixed in the mainline yet, I think. >>>> >>>> Anybody who has a clue? >>>> (I have not done git-bisect yet.) >>> >>> Can you do 'git bisect'? >> >> >> The same problem happened on v4.3. >> (I think I just did not notice the problem before.) >> >> So, the bad commit is not in the last merge window. > > Is it ok for 4.2? 4.1? Finding out where this started to "fail" would > be good to know... Just as a data point, on our internal systems earlycon is known good in combination with regular console (provided by SPCR ACPI patch) on 4.2. Jon. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/