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=-1.0 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED autolearn=unavailable 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 662B2C282C2 for ; Thu, 7 Feb 2019 08:26:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 34A462175B for ; Thu, 7 Feb 2019 08:26:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=benyossef-com.20150623.gappssmtp.com header.i=@benyossef-com.20150623.gappssmtp.com header.b="HdafhgbZ" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727021AbfBGIZx (ORCPT ); Thu, 7 Feb 2019 03:25:53 -0500 Received: from mail-ua1-f67.google.com ([209.85.222.67]:36009 "EHLO mail-ua1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726788AbfBGIZw (ORCPT ); Thu, 7 Feb 2019 03:25:52 -0500 Received: by mail-ua1-f67.google.com with SMTP id j3so3189004uap.3 for ; Thu, 07 Feb 2019 00:25:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=benyossef-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=KKJXec/17dqhQqZhGlHFxMNW2trdhcCphzGyRH7qzEQ=; b=HdafhgbZ4WM3HTG0itqg1wEnY6zUcnWBRCx9tmIVvN0J0jOUnn2G614UDXiChkw/QE xynvjMQznqsO5tM8sEqs+Aj7yE10EBHzGjiUcnlUQIL92oi3cB0iaNwNHROfLE9da4wF jKGou/tTwneqZYidegNJw3fm/4WKbzTSLnfhQNJ8VO5D7/1XSuSm7RTJc9UXWCPwSjSX Ov1hXA0Q+cUDEP+LvVrPt7aEg9RBnBoA3mlXCsuFloI0Lq3Jx7WQHqOLbXdiPioq+zF3 i0wzJMcgZRdv8wewSjYAxqJPmRW3WjyhhOYgdAg15DUsHu2LU4R/4pRUcYexZawEOR/D 6j/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=KKJXec/17dqhQqZhGlHFxMNW2trdhcCphzGyRH7qzEQ=; b=k5emgpsheA/TYjD2QgGTU4FWa+zj0qBc241f+k80VGeeLw/8M0pfdWjKYnHVciE3v6 PbRMhXqSye43UGJb6Bm0/QE7WT1+ONsKufhZ+qK69zGUowZAlqwRstQHD3uX8CLFSEFe Qt+MzP5jezER0ZuEQzFw1NegGAoFoI8Fj2vv/G8Mc/eplcm4qJlGSv3wt5V0ITmZA1Pp TySHIleeuCaEgzZ74ZNeYA6JQJaVq5+rCkfTgZzBspPwz9NgK6/vZf8Q/uRxyasxEBDQ 7L9bgxv6qonxNC+WuoNBbfOFEMCLzRUXFCCWRJApK5H/bJ2OyQyvVRfoPNsviGyMpDJr 5JHA== X-Gm-Message-State: AHQUAubseqL1Lp7NYYwB7dpHsinanPEAUZ4lzdxQV7Ko8BFOZCKx3tGk JEN3+m/VAjf/fo9PIC5sx3adNU1tp2gTRS6bHRJi7g== X-Google-Smtp-Source: AHgI3IZ7cKqXrgKQbYesx29ikvEuoy4tjKOx3fbi04mk0XRHjC7A7T4pxaXx6CEdF1teYeBisKMyr/Q400SVdtV6m68= X-Received: by 2002:ab0:2c08:: with SMTP id l8mr5688696uar.113.1549527951445; Thu, 07 Feb 2019 00:25:51 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Gilad Ben-Yossef Date: Thu, 7 Feb 2019 10:25:40 +0200 Message-ID: Subject: Re: Regression due to "PM-runtime: Switch autosuspend over to using hrtimers" To: Vincent Guittot Cc: "Rafael J. Wysocki" , Pavel Machek , Len Brown , "open list:THERMAL" , Linux Crypto Mailing List , Linux kernel mailing list , Ofir Drang Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Hi, Thank for the quick response. On Wed, Feb 6, 2019 at 6:59 PM Vincent Guittot wrote: > > Hi Gilad, > > On Wed, 6 Feb 2019 at 17:40, Gilad Ben-Yossef wrote= : > > > > Hi all, > > > > A regression was spotted in the ccree driver running on Arm 32 bit > > causing a kernel panic during the crypto API self test phase (panic > > messages included with this message) happening in the PM resume > > callback that was not happening before. > > > > I've bisected the change that caused this to commit 8234f6734c5d > > ("PM-runtime: Switch autosuspend over to using hrtimers"). > > > > I'm still trying to figure out what is going on inside the callback, > > but as it was not happening before, I thought I'd give you a shout out > > to make you aware of this. > > Are you using autosuspend mode for this device ? Yes. > Also this happen in a platform specific function cc_init_hash_sram(). > I can't see anything related to pm runtime and autosuspend in it. True. However, the function is called from the driver PM resume callback and before that commit it did not fail. My guess is that there is something related to the timing the callback is called, probably some race condition the change exposed. There is probably nothing for you do until I figure out what is failing in the internal function. I just wanted to give the heads up in case someone else runs into a similar issue with another driver. > Do you have more details about where this panic happen in the function ? I'm looking into this right now and will update. Thanks! Gilad --=20 Gilad Ben-Yossef Chief Coffee Drinker values of =CE=B2 will give rise to dom!