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=-6.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, 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 B2FA2C432BE for ; Tue, 31 Aug 2021 03:19:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 8B29460FED for ; Tue, 31 Aug 2021 03:19:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239470AbhHaDTB (ORCPT ); Mon, 30 Aug 2021 23:19:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56048 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231776AbhHaDS7 (ORCPT ); Mon, 30 Aug 2021 23:18:59 -0400 Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D699AC061575 for ; Mon, 30 Aug 2021 20:18:04 -0700 (PDT) Received: by mail-pg1-x536.google.com with SMTP id e7so15393985pgk.2 for ; Mon, 30 Aug 2021 20:18:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=MHOGIKnTugS13OtVhVAw/dgLV35w9vlE4iezk8tgDSo=; b=LHioZtFps30H7Whej1ENLJTaN2XoBiRa5+P5hiWslhRsZ8P+bxzJUOmoncWBc1X0sX wTs5InF9aLDd8m/0TrE2r8ys2kDo765nZI6pTZJaUPAxMoJ0Ib+ZODJXh8TTdRoaefPQ jddMhevO16/P2aZVb4nO2Yja1HV2rHBLt8cBw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=MHOGIKnTugS13OtVhVAw/dgLV35w9vlE4iezk8tgDSo=; b=YSybddw++XE8dgFF0lUZqQA+0SJcfABJ4zwayI6Xzf+YSGCm+Nhn7m0+HHx5i1K9WJ lZdEwbvG3AfHSYcStbPPDvsJ5+n56QCddGCh4ya9CKQ/LCQLjQFnLb9iHGUabyuGgx4L rwtyGtw8JQc17XcD1IILx0okaa4o8hsEV4H1pexEBBqc6phJedB9iePz2JOCweBN2/Fd wGhoxsTeAUBOxhXwxmtDZwnprEk72EdldVtlxgQvqmdSRowNZqOXab+DFbHGcL0Bx6Ha cJ1FiZEoJuVeWVNVBjykz1UTU20TqycEnV3dIAJNktSKTvDcmK2qKxvtunHEs/uGGdyA Jarg== X-Gm-Message-State: AOAM530FUHe64OJGihqLxf/GvWHOH0xU4blHBfHD5kMALCTgTeRNDgS5 IBmWAQr7BAtVbaJGEErb+TPVxg== X-Google-Smtp-Source: ABdhPJzsYEZTu67g6hoFHaQ2rw6OtW+6QLC5AKuqY27yUnJARsyEw0b0gx1bIxwhM/exByfH4SPYmg== X-Received: by 2002:a65:44c6:: with SMTP id g6mr24556398pgs.442.1630379884279; Mon, 30 Aug 2021 20:18:04 -0700 (PDT) Received: from google.com ([2409:10:2e40:5100:6d52:87b8:b55b:8800]) by smtp.gmail.com with ESMTPSA id u6sm17979862pgr.3.2021.08.30.20.18.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 30 Aug 2021 20:18:03 -0700 (PDT) Date: Tue, 31 Aug 2021 12:17:59 +0900 From: Sergey Senozhatsky To: Linus Torvalds Cc: Petr Mladek , Sergey Senozhatsky , Steven Rostedt , John Ogness , Linux Kernel Mailing List Subject: Re: kernel hang during reboot when cmdline include a non-exist console device Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (21/08/30 19:53), Linus Torvalds wrote: > > There's a bugzilla for this, but let's just move it to reguilar email, > unless some of you want to track it that way. > > The bugzilla entry says > > "When reboot， the capslock key of thinkpad x1 starts blinking" > > which sounds like there's an oops that just isn't showing, quite > possibly because the console has already been shut down. > > I didn't test this out, and would sincerely hope that somebody else is > willing to follow up on it since I'm in the busiest part of the merge > window. [..] > > https://bugzilla.kernel.org/show_bug.cgi?id=214201 I think normally wrong/empty console boot argument should not cause problems. We have a huge number of devices that use console="", for instance. But on some hardware this triggers panic(), very early on. I have the same symptoms on my laptop, and so far haven't been able to figure out how to track it down, but I need to re-start my investigation. In the meantime, we had a series [0] but ended up reverting it. I think we need to revisit it, namely the part that starts with [1]. [0] https://lore.kernel.org/lkml/20201111135450.11214-1-pmladek@suse.com/ [1] https://lore.kernel.org/lkml/X%2FfWGjYI5LapMdGW@jagdpanzerIV.localdomain/