[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMMLpeRO3LJRHVW-815DMsTeNyB1HX12ck+o2i9uzEBtShYWng@mail.gmail.com>
Date: Tue, 2 May 2017 22:55:09 -0600
From: Alex Henrie <alexhenrie24@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>,
Mathias Nyman <mathias.nyman@...el.com>,
Joerg Roedel <jroedel@...e.de>
Cc: linux-usb@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: I'd like to donate a MacBook Pro
2017-05-01 3:03 GMT-06:00 Lukas Wunner <lukas@...ner.de>:
> On Mon, 1 May 2017 00:27:41 -0600, Alex Henrie wrote:
>> I am confident that this is a common problem because I have found
>> various other users complaining about it:
>>
>> https://bbs.archlinux.org/viewtopic.php?pid=1613363#p1613363
>> https://bbs.archlinux.org/viewtopic.php?pid=1451053#p1451053
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668105
>> https://bugzilla.kernel.org/show_bug.cgi?id=115741
>
> Briefly looking over those links I notice some people are reporting
> the same issue on macOS. This could indicate an EFI firmware bug
> or hardware issue. Have you tried updating the firmware? Has this
> issue always been present?
Everything worked fine when I first installed Linux last October. I
updated the firmware immediately before installing Linux. I think it
was a couple of months before the boot problems showed up.
2017-05-01 4:06 GMT-06:00 Greg KH <gregkh@...uxfoundation.org>:
> You are not saying what kernel version you are using here, newer ones
> have fixed issues like this. Have you tried 4.10? 4.11?
I am currently using 4.10. I tried 4.11 yesterday and the keyboard did
not work at all. The error messages changed to:
[ 0.453518] ACPI Error: Needed type [Reference], found [Integer] ffff88045bce
3798 (20170119/exresop-103)
[ 0.453525] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for
[OpcodeName unavailable] (20170119/dswexec-461)
[ 0.453530] ACPI Error: Method parse/execution failed [\_PR.CPU0._PDC] (Node
ffff88045e0ee320), AE_AML_OPERAND_TYPE (20170119/psparse-543)
starting version 232
A password is required to access the cryptroot volume:
Enter passphrase for /dev/sda4: [ 7.950202] xhci_hcd 0000:00:14.0:
Command completion event does not match command
[ 10.290329] usb 2-3: device not accepting address 2, error -62
[ 20.537740] xhci_hcd 0000:00:14:0: Command completion event does
not match command
[ 35.045403] xhci_hcd 0000:00:14.0: Error while assigning device slot ID
[ 35.045659] xhci_hcd 0000:00:14.0: Max number of devices this xHCI
host supports is 32.
[ 35.045934] usb usb2-port3: couldn't allocate usb_device
[ 47.419601] usb 1-3: hub failed to enable device, error -62
[ 59.793777] xhci_hcd 0000:00:14.0: Error while assigning device slot ID
[ 59.794032] xhci_hcd 0000:00:14.0: Max number of devices this xHCI
host supports is 32.
[ 59.794307] usb usb1-port3: couldn't allocate usb_device
[ 72.167966] xhci_hcd 0000:00:14.0: Error while assigning device slot ID
[ 72.168218] xhci_hcd 0000:00:14.0: Max number of devices this xHCI
host supports is 32.
[ 72.168493] usb usb1-port5: couldn't allocate usb_device
Today I ran a regression test to determine which commit made the
keyboard stop working entirely. The last commit that worked for me was
c09e22d5370739e16463c113525df51b5980b1d5. After that, there is a long
series of commits where the screen stays black, and after that, I
start getting errors like the one above.
Thanks for the information you've sent so far. Any ideas on how to fix
this new and serious problem with 4.11?
-Alex
Powered by blists - more mailing lists