Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp5949616ybv; Tue, 18 Feb 2020 07:03:25 -0800 (PST) X-Google-Smtp-Source: APXvYqzAgCXsoy2ZCbl7i4Si8HZ76LqrTJOTByZc+KTnvUknsHZrr8363GxjZ0jU4bJli4Bpu8Xe X-Received: by 2002:a9d:7498:: with SMTP id t24mr16506748otk.290.1582038205550; Tue, 18 Feb 2020 07:03:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582038205; cv=none; d=google.com; s=arc-20160816; b=EzCT3HTTFRx0imPUxtOlVimxQgks47FF/2ZhEA5eIGg6bPV7+v4gWF9VEFQ2DeMJrz Go8BlA5DH5RSj3oXMl0fofEBqL5VedB2f2viaZvIkaiPT+001U6xul0jnVDTmsNjYkFA LqbwAK4gyP2KQxLwr7q0/70em0f3AlciSeh0dHPE5zI2F6RnSH7qWdsWIAAaX8snKa2I iD+fh3lGHebI8kMiUFQ1w93yfaY628Uv3FHgqNhZzCrK1r3NdI/UPH3UjRD2ACQPRx29 TJjTsA8KoWA9nURjbAl/rzkUwiG2f8qoZR1OSvM9B0UpYDx3HTd3Rqhm11B+mFgYbGMN 28tw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=HJfcFNRrxaseqh0MI06QIPRDxGzs9DjP03SD1GsDMy0=; b=PAkLPqR8q235KlAd7ox71btvZH6c89b+4xf62ygxFqTqNV+vGGZuyDjb1xKCallsa0 QUdnoOod+d66FNXlKCkc85ZP86nHPg4IL1Q9EXU+15hUjk0FWZ+Vfh7WoNVrzzCdWMxP 8ishc2DsYE1E7t96fB3NiGVFj2T8s4MuZFP/eZhWk7d6wj0LB5ZnTIDO87zBxgmYcAN3 MlBz1mEte/1tqHPvTTRZEMoI3OaKt1zvRqWckkzQ+byipUd5CU5i7BjbNpgHN3fs72kc 9cXa5H+M8/4PLZrH7rd8r+BslRn8pe8f0C36Uhb/0FaYCHQYRiqwVl0uxOWNgNX+5gfP 4eEA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i6si1942930otp.5.2020.02.18.07.03.10; Tue, 18 Feb 2020 07:03:25 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726841AbgBRPB0 (ORCPT + 99 others); Tue, 18 Feb 2020 10:01:26 -0500 Received: from bmailout1.hostsharing.net ([83.223.95.100]:52481 "EHLO bmailout1.hostsharing.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726667AbgBRPB0 (ORCPT ); Tue, 18 Feb 2020 10:01:26 -0500 Received: from h08.hostsharing.net (h08.hostsharing.net [83.223.95.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.hostsharing.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by bmailout1.hostsharing.net (Postfix) with ESMTPS id 3B2DA30004511; Tue, 18 Feb 2020 16:01:24 +0100 (CET) Received: by h08.hostsharing.net (Postfix, from userid 100393) id 1084E14BA9C; Tue, 18 Feb 2020 16:01:24 +0100 (CET) Date: Tue, 18 Feb 2020 16:01:24 +0100 From: Lukas Wunner To: Nicholas Johnson Cc: Bjorn Helgaas , "linux-kernel@vger.kernel.org" , "linux-pci@vger.kernel.org" Subject: Re: Stack trace when removing Thunderbolt devices while kernel shutting down Message-ID: <20200218150124.stvsj2rozxrgxw2h@wunner.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 18, 2020 at 02:18:40PM +0000, Nicholas Johnson wrote: > If I surprise remove Thunderbolt 3 devices just as the kernel is > shutting down, I get stack dumps, when those devices would not normally > cause stack dumps if the kernel were not shutting down. > > Because the kernel is shutting down, it makes it difficult to capture > the logs without a serial console. Hold a camera in front of the screen and try to capture the messages as an MP4 movie which can be uploaded to YouTube or something. If the output moves too fast to capture it, artificially slow it down by adding a udelay() to call_console_drivers() in kernel/printk/printk.c. Thanks, Lukas