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=-0.9 required=3.0 tests=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 59FE1C433E0 for ; Wed, 20 May 2020 18:52:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 39637207D4 for ; Wed, 20 May 2020 18:52:32 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="iUGO1zFe" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726832AbgETSw3 (ORCPT ); Wed, 20 May 2020 14:52:29 -0400 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:35311 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726785AbgETSw2 (ORCPT ); Wed, 20 May 2020 14:52:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1590000748; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=zrw5y7kLFs3H7gZeyqDRl7rn5ygDIp8+n8h/0YJPWVI=; b=iUGO1zFeS5/a9FJUezmQCZIUsFPHacDGQtR3BQopDH3X4edWOEHRiLIf0M7JToLvGDbAVF ye4Mq8TD+Nus51Lj3aASW6QfEW1TqqN7EkspOUzJRrs0RnhtitYojQBUKRRmZVmONpcmTM UYcbYBhLW0VPQUfO32wpXBpUcfurrBQ= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-184-jksy1QilOYqlkFCsKtakrQ-1; Wed, 20 May 2020 14:52:26 -0400 X-MC-Unique: jksy1QilOYqlkFCsKtakrQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 05EB9835B40; Wed, 20 May 2020 18:52:25 +0000 (UTC) Received: from starship.redhat.com (unknown [10.35.207.28]) by smtp.corp.redhat.com (Postfix) with ESMTP id D9B5D4739A; Wed, 20 May 2020 18:52:22 +0000 (UTC) From: Maxim Levitsky To: linux-kernel@vger.kernel.org Cc: Andreas Noever , Michael Jamet , Mika Westerberg , Jiri Kosina , linux-usb@vger.kernel.org (open list:THUNDERBOLT DRIVER), Yehezkel Bernat , Maxim Levitsky Subject: [PATCH 0/1] RFC: Make thunderbolt NHI driver work with kexec [RESEND] Date: Wed, 20 May 2020 21:52:20 +0300 Message-Id: <20200520185221.122283-1-mlevitsk@redhat.com> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Sender: linux-usb-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org While trying to use kexec on my desktop,=0D which has Titan Ridge Thunderbolt add-on card,=0D I noticed that after a kexec, system hangs=0D for about a minute in the 'wating for udev devices=0D to settle' phase of the boot.=0D =0D I found out that if I unload the thunderbolt driver=0D prior to the kexec, then it works just fine.=0D =0D Looking at the code I see that the driver doeesn't=0D implement .shutdown method, so this on-liner patch=0D points it to the same method that is used on device removal.=0D =0D I don't know if this is the right solution,=0D but it does appear to work just fine with this patch.=0D =0D What do you think?=0D =0D Best regards,=0D Maxim Levitsky=0D =0D Maxim Levitsky (1):=0D thunderbolt: add trivial .shutdown=0D =0D drivers/thunderbolt/nhi.c | 1 +=0D 1 file changed, 1 insertion(+)=0D =0D -- =0D 2.25.4=0D =0D