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>] [day] [month] [year] [list]
Message-ID: <479de488-dc78-c58f-d31c-140aa7fc1c72@bananateam.nl>
Date:   Thu, 6 Dec 2018 17:42:17 +0100
From:   Ferry van Steen <ferry@...anateam.nl>
To:     linux-kernel@...r.kernel.org
Subject: No screen on Mac 18,1 / A1418 since kernel 4.17.x

Hi,

we have received a Mac 18,1 (A1418), from a customer, on which we are 
unable to get any screen since seemingly 4.17.x (tested with 4.17.16).

4.16.16 works fine. Tried several 4.17, 4.18 and 4.19 releases (latest 
4.19.4), none of these show any output on the screen after the bootloader.

We've tested mostly with Fedora 27/28/29 kernels, but also with Ubuntu 
18.04 LTS (which uses 4.15.x and works fine and so does Fedora's 4.16.16 
(fc28)).

Bit at a loss on how to proceed with this. First off, I'm not a 
driver-/kernel developer. I can compile kernels and capture debug output 
etc. No clue on how to capture the debug output on this machine however. 
The machine has USB, but 'lspci -vv' doesn't show any debug capabilities 
on the USB ports, if it did we would probably be able to acquire a 
NET20DC for debugging, but I doubt it's possible if the capability isn't 
listed (never done debugging via USB/NET20DC). There's no serial port 
(not on the outside at least). We boot a somewhat modified version of 
Fedora (most of the modification being that it runs entirely from RAM, 
the initrd is the actual filesystem, no difference trying to boot it 
from a USB stick / filesystem on a disk or NFS / stock Fedora with 
kernels 4.17.x or higher).

Sending stuff to netconsole doesn't seem possible either. One of the 
first things it's supposed to do, if the kernels comes up, is acquiring 
DHCP. No DHCP request can be captured with these kernels from the NIC, 
kernel seems to get stuck way before then thus. We also have a script in 
place that if a FAT32 formatted USB stick is inserted with in the root a 
file with a certain name, it should dump the logs to the stick. This 
doesn't happen either, which we presume is another indicator that the 
kernel locks up / panics.

As stated I'm not a developer. Applying patches, building kernels, 
running them and probably debugging some stuff with perhaps (slight?) 
hints are things I probably can do (quite sure on the first 3, done 
those before many times :)). If there's anybody willing to help with 
this, please let me know.

Not sure how long we can borrow this hardware btw. Probably a couple of 
weeks, but will be required to send it back to the customer eventually.

As I have no clue on how to proceed due to the lack of screen / ability 
to capture anything, I've gathered, from Ubuntu 18.04 live USB:

lspci -vv
dmidecode
lsusb -vv
dmesg
journalctl

Whom can be downloaded from https://freaky.bananateam.nl/mac-a1418.txz

Thanks in advance and kind regards,

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ