Re: 4.17.x kernels cause "nvme0: controller is down" on MacBook Air

2018-10-17 Thread Lonni J Friedman
SMART identifies the drive as "APPLE SSD AP0256H", which is likely some rebranded thing from who knows where. Unfortunately, I already tried the solution that you linked to, and it made no difference. On Sat, Oct 13, 2018 at 2:00 PM Jonathan Dieter wrote: > > I don't have an NVME drive, but I cam

Re: 4.17.x kernels cause "nvme0: controller is down" on MacBook Air

2018-10-13 Thread Jonathan Dieter
I don't have an NVME drive, but I came across this the other day: https://community.wd.com/t/linux-support-for-wd-black-nvme-2018/225446/8 I have no idea what brand your NVME drive is, but perhaps this will help. Jonathan On Sat, 2018-10-13 at 12:54 -0700, Lonni J Friedman wrote: > And this pro

Re: 4.17.x kernels cause "nvme0: controller is down" on MacBook Air

2018-10-13 Thread Lonni J Friedman
And this problem exists on a fresh install of Fedora28 too. The original shipping 4.16 kernel works fine, every kernel starting with 4.17.x fails. Is literally no one else running into this?? On Sun, Jul 15, 2018 at 3:06 PM Lonni J Friedman wrote: > > Ever since Fedora(27) released a 4.17.x kern

4.17.x kernels cause "nvme0: controller is down" on MacBook Air

2018-07-15 Thread Lonni J Friedman
Ever since Fedora(27) released a 4.17.x kernel, my MacBook Air (7,1) is no longer able to boot at all. It hangs when trying to use the NVMe disk controller: nvme nvme0: controller is down; will reset: CSTS=0x3, PCI_STATUS=0x810 and the entire boot process eventually times out completely. If I r