From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 56A08C433E0 for ; Thu, 7 Jan 2021 17:05:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 184F9233CE for ; Thu, 7 Jan 2021 17:05:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727673AbhAGRFo (ORCPT ); Thu, 7 Jan 2021 12:05:44 -0500 Received: from mx2.suse.de ([195.135.220.15]:46894 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727453AbhAGRFo (ORCPT ); Thu, 7 Jan 2021 12:05:44 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1610039097; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=MMfq/PKouT6ktPEQMdn1ZCdmFrDqGcaa8I0x2b98/NQ=; b=l8DMIk0AM0Lx8ZD6OSuzfMbW4nKMZ6WKVw4MmA4GAuTcv53Hdenl9On+h9HXtdA+/xAPXr cUe6J95cuctNrrZP/mnhnUDsoh5ySn3oqhO7saQZKtELu73+m19Bk2rkzJscpvzBePRNTR 6UYUcPdDBWuo/CrWCbGlTwdwN74UYKg= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 626DDAD57; Thu, 7 Jan 2021 17:04:57 +0000 (UTC) Date: Thu, 7 Jan 2021 18:04:56 +0100 From: Petr Mladek To: Vineet Gupta Cc: John Ogness , Sergey Senozhatsky , Steven Rostedt , Linus Torvalds , Guenter Roeck , Shreyas Joshi , shreyasjoshi15@gmail.com, Greg Kroah-Hartman , Sergey Senozhatsky , linux-kernel@vger.kernel.org, buildroot@busybox.net, Thomas Petazzoni , linux-arch@vger.kernel.org, arcml Subject: Re: ARC no console output (was Re: [PATCH 1/2] init/console: Use ttynull as a fallback when there is no console) Message-ID: References: <20201111135450.11214-1-pmladek@suse.com> <20201111135450.11214-2-pmladek@suse.com> <8735zdm86m.fsf@jogness.linutronix.de> <50ade852-c598-6476-1f4b-9a3f8d11d143@synopsys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50ade852-c598-6476-1f4b-9a3f8d11d143@synopsys.com> Precedence: bulk List-ID: X-Mailing-List: linux-arch@vger.kernel.org On Thu 2021-01-07 08:43:16, Vineet Gupta wrote: > Hi John, > > On 1/7/21 1:02 AM, John Ogness wrote: > > Hi Vineet, > > > > On 2021-01-06, Vineet Gupta wrote: > > > This breaks ARC booting (no output on console). > > > > Could you provide the kernel boot arguments that you use? This series is > > partly about addressing users that have used boot arguments that are > > technically incorrect (even if had worked). Seeing the boot arguments of > > users that are not experiencing problems may help to reveal some of the > > unusual console usages until now. > > > Kernel command line: earlycon=uart8250,mmio32,0xf0005000,115200n8 > console=ttyS0,115200n8 debug print-fatal-signals=1 This is strange, the problematic patch should use ttynull only as a fallback. It should not be used when a particular console is defined on the command line. The only explanation would be that ttyS0 gets registered too late and ttynull is added as a fallback in the meantime. Anyway, I propose the revert the problematic patch for 5.11-rc3, see https://lore.kernel.org/lkml/20210107164400.17904-2-pmladek@suse.com/ This mystery is a good reason to avoid bigger changes at this stage. Best Regards, Petr