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=-9.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SIGNED_OFF_BY,SPF_PASS autolearn=ham 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 7AF05C43219 for ; Fri, 3 May 2019 07:08:01 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 2E5CD2075C for ; Fri, 3 May 2019 07:08:01 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2E5CD2075C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 44wNWM3CCQzDqWF for ; Fri, 3 May 2019 17:07:59 +1000 (AEST) Received: from ozlabs.org (bilbo.ozlabs.org [203.11.71.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 44wNK74HqxzDqPW for ; Fri, 3 May 2019 16:59:07 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Received: by ozlabs.org (Postfix) id 44wNK71wzrz9sNf; Fri, 3 May 2019 16:59:07 +1000 (AEST) Received: by ozlabs.org (Postfix, from userid 1034) id 44wNK66JHGz9sDn; Fri, 3 May 2019 16:59:06 +1000 (AEST) X-powerpc-patch-notification: thanks X-powerpc-patch-commit: de269129a48a2d590ba1d20c719e19d86e3ddb3f X-Patchwork-Hint: ignore In-Reply-To: <155172853902.20037.16712960724031791025.stgit@jupiter> To: Mahesh J Salgaonkar , linuxppc-dev From: Michael Ellerman Subject: Re: [PATCH] powerpc/hmi: Fix kernel hang when TB is in error state. Message-Id: <44wNK66JHGz9sDn@ozlabs.org> Date: Fri, 3 May 2019 16:59:06 +1000 (AEST) X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Stewart Smith Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Mon, 2019-03-04 at 19:42:19 UTC, Mahesh J Salgaonkar wrote: > From: Mahesh Salgaonkar > > On TOD/TB errors timebase register stops/freezes until HMI error recovery > gets TOD/TB back into running state. On successful recovery, TB starts > running again and udelay() that relies on TB value continues to function > properly. But in case when HMI fails to recover from TOD/TB errors, the > TB register stay freezed. With TB not running the __delay() function > keeps looping and never return. If __delay() is called while in panic > path then system hangs and never reboots after panic. > > Signed-off-by: Mahesh Salgaonkar Applied to powerpc next, thanks. https://git.kernel.org/powerpc/c/de269129a48a2d590ba1d20c719e19d8 cheers