From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mika Westerberg Subject: Re: Oops in acpi_gpiochip_add on MacBookPro with Linux v3.14-12042-g69cd9eba3886 Date: Fri, 11 Apr 2014 09:56:24 +0300 Message-ID: <20140411065624.GB19349@intel.com> References: <20140410124045.GX19349@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Linus Walleij Cc: Josh Boyer , =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= , Alexandre Courbot , "linux-gpio@vger.kernel.org" , "Linux-Kernel@Vger. Kernel. Org" , "linux-wireless@vger.kernel.org" List-Id: linux-gpio@vger.kernel.org On Thu, Apr 10, 2014 at 08:47:23PM +0200, Linus Walleij wrote: > On Thu, Apr 10, 2014 at 2:40 PM, Mika Westerberg > wrote: > > On Thu, Apr 10, 2014 at 08:22:12AM -0400, Josh Boyer wrote: > >> On Thu, Apr 10, 2014 at 2:50 AM, Rafa=C5=82 Mi=C5=82ecki wrote: > >> > 2014-04-09 23:09 GMT+02:00 Josh Boyer : > >> >> With Linux v3.14-12042-g69cd9eba3886 I get an oops from the bcm= a > >> >> module on the MacBookPro 10,2 I have here. This works fine wit= h Linux > >> >> v3.14-7333-g59ecc26004e7. There have been no changes between t= hose > >> >> two versions to bcma itself, but the GPIO merge did go in that = window. > >> >> I can attempt to do a bisect tomorrow, but looking over some o= f the > >> >> GPIO commits it seems pretty relevant to the ACPI GPIO changes.= I'm > >> >> hoping someone here has an idea on what the issue might be and = has > >> >> some possible things for me to test for fixes. > >> > > >> > Bug report: https://lkml.org/lkml/2014/3/24/262 > >> > Patch: https://lkml.org/lkml/2014/3/24/293 > >> > Tested by Sabrina: https://lkml.org/lkml/2014/3/24/304 > >> > (all links are for the same thread). > >> > > >> > Now you simply have to find above patch in some git tree :) Not = sure > >> > if it's already in Linus's one. > >> > >> Ah, wonderful. I now wish I would have found those in my searchin= g > >> before doing the bisect. Oh well. For what it's worth, my bisect > >> landed on the same commit. > >> > >> The fix isn't in Linus' tree or linux-next. I'm guessing Mika is > >> either still on vacation, or hasn't sent out the formal fix yet. > > > > No, not on vacation anymore (unfortunately). I did send the formal = patch > > already: > > > > https://lkml.org/lkml/2014/3/31/135 > > > > but it isn't merged to Linus' GPIO tree yet. >=20 > I've queued this for fixes! >=20 > Will send upstream ASAP. Thanks!