Re: XHCI is slow during boot (bios/efi) and leaves many dmesg messages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Olliver Schinagl <oliver@xxxxxxxxxxx> writes:
> Hey all,
>
> On 11-04-16 07:12, Felipe Balbi wrote:
>> Hi,
>>
>> Janna Martl <janna.martl109@xxxxxxxxx> writes:
>>> On 2016-04-04 9:06:28, Olliver Schinagl wrote:
>>>> Hi list,
>>>>
>>>> I have a Apple Inc. MacBookPro11,1 (with the most recent 'bios': BIOS
>>>> MBP111.88Z.0138.B16.1509081438 09/08/2015).
>>>> At the beginning, USB worked normally. After a while (and after newer kernel
>>>> versions released by debian?) things started to act strangely. For one, the
>> you need to try with latest kernel from Linus. Please download v4.6-rc3
>> from kernel.org, compile and try with that.
> I've tried with kernels from 3.16 to v4.6-rc2 updating every few weeks. 
> Anything special I should watch out for in rc3 that changed since rc2?

nothing special. Just to confirm, can you check that disabling LPM
solves the problem ?

diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
index f0640b7a1c42..9c3ead114ad5 100644
--- a/drivers/usb/host/xhci-pci.c
+++ b/drivers/usb/host/xhci-pci.c
@@ -127,8 +127,8 @@ static void xhci_pci_quirks(struct device *dev, struct xhci_hcd *xhci)
 		xhci->quirks |= XHCI_TRUST_TX_LENGTH;
 
 	if (pdev->vendor == PCI_VENDOR_ID_INTEL) {
-		xhci->quirks |= XHCI_LPM_SUPPORT;
-		xhci->quirks |= XHCI_INTEL_HOST;
+		/* xhci->quirks |= XHCI_LPM_SUPPORT; */
+		/* xhci->quirks |= XHCI_INTEL_HOST; */
 		xhci->quirks |= XHCI_AVOID_BEI;
 	}
 	if (pdev->vendor == PCI_VENDOR_ID_INTEL &&

>>>> bios/efi boot takes a very long time (probably due to the same reason I describe
>>>> later) just to get to the bootloader/grub. Likley resetting and probing for USB
>>>> ports/mass storage. When grub finally pops up, I can use the (internal USB based
>>>> keyboard) normally to select a grub entry etc.
>>>> Booting the kernel then works reasonably fine, until it loads the xhci module.
>>>> It spews some messages in dmesg (taking some 15 seconds) and only then, the
>>>> keyboard starts to work again.
>> which messages ? We need these dmesg messages
> As mentioned by Janna, they are at the bugzilla issue number 115741 [0] 
> (unless you prefer them zipped otherwise they sometimes don't fit).

no, it's okay.

-- 
balbi

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux