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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 10 Apr 2014 08:22:12 -0400
From:	Josh Boyer <jwboyer@...oraproject.org>
To:	Rafał Miłecki <zajec5@...il.com>
Cc:	Linus Walleij <linus.walleij@...aro.org>,
	Alexandre Courbot <gnurou@...il.com>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>,
	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 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.

josh
--
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/