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]
Date:   Thu, 11 May 2017 14:21:14 -0600
From:   Alex Henrie <alexhenrie24@...il.com>
To:     Mathias Nyman <mathias.nyman@...ux.intel.com>
Cc:     Joerg Roedel <jroedel@...e.de>,
        Greg KH <gregkh@...uxfoundation.org>,
        Mathias Nyman <mathias.nyman@...el.com>,
        linux-usb@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: I'd like to donate a MacBook Pro

2017-05-11 5:16 GMT-06:00 Mathias Nyman <mathias.nyman@...ux.intel.com>:
> Looks like there are a few people suffering from macbook xhci related issues
>
> From the bugs linked it looks like there are both some UEFI issues and a
> non-responsive
> usb device at boot. at least one USB device does not respond to a address
> device command,
> and driver times out and aborts the command after 5 second.
>
> I don't think I can do anything about the UEFI or the first 5 second command
> timeout
> from the xhci driver, but after that some improvement could be done.
>
> This timeout code path in the xhci driver is not exercised that often.
> Some minor races were fixed in 4.11 in this area, and better tracing added,
> but unfortunately
> I just discovered there is also has a regression in 4.11
>
> If you can help me debug this by compiling some new kernels and taking logs
> and traces on
> your MacBook we could get this forward.
>
> I set up a branch for this issue, it has the race-fixes, tracing and
> regression fixes:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git xhci-macbook
>
> Remember to check out the xhci-macbook branch.
>
> Can you compile and run that kernel on yout MacBook, and take logs?
>
> Traces can be enabled by adding "trace_event=xhci-hcd" to you kernel command
> line,
> then send me the output of both dmesg and /sys/kernel/debug/tracing/trace
> after the issue is seen.

Thanks for the detailed instructions. Your xhci-macbook branch works
just as well as Linux 4.10: The system boots up with a working
keyboard after a 2-minute delay. Unfortunately, I was not able to save
any logs because I couldn't figure out which kernel option would let
me access the encrypted hard drive. After putting in my password, I
got the error "crypt: unknown target type".

-Alex

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ