From mboxrd@z Thu Jan 1 00:00:00 1970 From: Frank Rowand Subject: Re: panic, bisect to commit 7f1d4e58dabb "spmi: pmic-arb: optimize table lookups" Date: Mon, 17 Jul 2017 22:44:47 -0700 Message-ID: <596DA04F.7020300@gmail.com> References: <596D839C.2030907@gmail.com> <55a449e0-68ae-988a-070c-f73dd5aabb78@codeaurora.org> <596D9765.5060807@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: Received: from mail-pf0-f193.google.com ([209.85.192.193]:34902 "EHLO mail-pf0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751026AbdGRFo7 (ORCPT ); Tue, 18 Jul 2017 01:44:59 -0400 In-Reply-To: <596D9765.5060807@gmail.com> Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Rajendra Nayak , Kiran Gunda , Abhijeet Dharmapurikar Cc: Greg Kroah-Hartman , Christophe JAILLET , "linux-kernel@vger.kernel.org" , Timur Tabi , linux-arm-msm , adharmap@quicinc.com, aghayal@qti.qualcomm.com On 07/17/17 22:06, Frank Rowand wrote: > On 07/17/17 20:56, Rajendra Nayak wrote: >> >> On 07/18/2017 09:12 AM, Frank Rowand wrote: >>> Hi Abhijeet, >>> >>> My qcom-apq8074-dragonboard panics on boot on v4.13-rc1. >>> >>> I bisected the problem to commit 7f1d4e58dabb, "spmi: pmic-arb: >>> optimize table lookups". >> >> there's a fix on its way upstream, >> https://patchwork.kernel.org/patch/9810723/ >> > > Thank you for the pointer to the patch. After adding the patch, my > board still does not boot, but now has several different stack > dumps from various drivers. I do not know if the new errors are > related to this patch or something entirely different. I'll dig > into it tomorrow. There is one more test I should have done before sending my previous email. I added the patch that is planned to fix the problem I reported on top of: 76b069b1cb20 spmi: spmi-pmic-arb: enable the SPMI interrupt as a wakeup source which is the last patch in the series that included the patch that I reported a problem with. My board boots fine at that point, so I am fairly confident that my further boot issues have yet another cause, and that the fix on its way upstream should fix the specific problem that I reported. -Frank