linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Rajendra Nayak <rnayak@codeaurora.org>,
	Kiran Gunda <kgunda@codeaurora.org>,
	Abhijeet Dharmapurikar <adharmap@codeaurora.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Timur Tabi <timur@codeaurora.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	adharmap@quicinc.com, aghayal@qti.qualcomm.com
Subject: Re: panic, bisect to commit 7f1d4e58dabb "spmi: pmic-arb: optimize table lookups"
Date: Mon, 17 Jul 2017 22:06:45 -0700	[thread overview]
Message-ID: <596D9765.5060807@gmail.com> (raw)
In-Reply-To: <55a449e0-68ae-988a-070c-f73dd5aabb78@codeaurora.org>

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.

-Frank

  reply	other threads:[~2017-07-18  5:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18  3:42 panic, bisect to commit 7f1d4e58dabb "spmi: pmic-arb: optimize table lookups" Frank Rowand
2017-07-18  3:56 ` Rajendra Nayak
2017-07-18  5:06   ` Frank Rowand [this message]
2017-07-18  5:44     ` Frank Rowand
2017-07-18 23:41       ` Frank Rowand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=596D9765.5060807@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=adharmap@codeaurora.org \
    --cc=adharmap@quicinc.com \
    --cc=aghayal@qti.qualcomm.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=gregkh@linuxfoundation.org \
    --cc=kgunda@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rnayak@codeaurora.org \
    --cc=timur@codeaurora.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).