linux-kernel - Re: Oops in acpi_gpiochip_add on MacBookPro with Linux v3.14-12042-g69cd9eba3886

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140411065624.GB19349@intel.com>
Date:	Fri, 11 Apr 2014 09:56:24 +0300
From:	Mika Westerberg <mika.westerberg@...ux.intel.com>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Josh Boyer <jwboyer@...oraproject.org>,
	Rafał Miłecki <zajec5@...il.com>,
	Alexandre Courbot <gnurou@...il.com>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Subject: Re: Oops in acpi_gpiochip_add on MacBookPro with Linux
 v3.14-12042-g69cd9eba3886

On Thu, Apr 10, 2014 at 08:47:23PM +0200, Linus Walleij wrote:
> On Thu, Apr 10, 2014 at 2:40 PM, Mika Westerberg
> <mika.westerberg@...ux.intel.com> wrote:
> > On Thu, Apr 10, 2014 at 08:22:12AM -0400, Josh Boyer wrote:
> >> On Thu, Apr 10, 2014 at 2:50 AM, Rafał Miłecki <zajec5@...il.com> wrote:
> >> > 2014-04-09 23:09 GMT+02:00 Josh Boyer <jwboyer@...oraproject.org>:
> >> >> With Linux v3.14-12042-g69cd9eba3886 I get an oops from the bcma
> >> >> module on the MacBookPro 10,2 I have here.  This works fine with Linux
> >> >> v3.14-7333-g59ecc26004e7.  There have been no changes between those
> >> >> 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 of 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 searching
> >> 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.
> 
> I've queued this for fixes!
> 
> Will send upstream ASAP.

Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/