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

Bug#973765: marked as done (linux-image-5.9.0-1-amd64: Apple NVMe SSD controller fails to start)

Your message dated Thu, 25 Nov 2021 23:31:25 +0100
with message-id <YaAOvRYkhzfaHqEZ@eldamar.lan>
and subject line Re: Bug#973765: linux-image-5.9.0-1-amd64: Apple NVMe SSD controller fails to start
has caused the Debian Bug report #973765,
regarding linux-image-5.9.0-1-amd64: Apple NVMe SSD controller fails to start
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
973765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973765
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-5.9.0-1-amd64
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: rgrove@rsu20.org

Dear Maintainer,

Updating to any Linux kernel after 5.7.0-2-amd64 makes the NVMe SSD on Apple MacBookAir7,1 fail to start. 
dmesg spits out:
[   64.565416] nvme nvme0: controller is down; will reset: CSTS=0x3, PCI_STATUS=0x10
[   64.645531] nvme nvme0: detected Apple NVMe controller, set queue depth=2 to work around controller resets
[   80.149335] nvme nvme0: Device not ready; aborting reset, CSTS=0x3
[   80.149373] nvme nvme0: Removing after probe failure status: -19
[   80.173515] blk_update_request: I/O error, dev nvme0n1, sector 2056 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[   80.173611] blk_update_request: I/O error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
[   80.173623] blk_update_request: I/O error, dev nvme0n1, sector 208768 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[   80.173638] Buffer I/O error on dev nvme0n1p1, logical block 1, async page read
[   80.173873] Buffer I/O error on dev nvme0n1p2, logical block 25584, async page read


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-5.9.0-1-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.137
ii  kmod                                    27+20200310-2
ii  linux-base                              4.6

Versions of packages linux-image-5.9.0-1-amd64 recommends:
ii  apparmor             2.13.4-3
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-5.9.0-1-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  grub-efi-amd64          2.04-8
pn  linux-doc-5.9           <none>

--- End Message ---
--- Begin Message --- 
Hi,

On Wed, Nov 04, 2020 at 01:45:41PM -0500, Harold R. Grove wrote:
> Package: linux-image-5.9.0-1-amd64
> Severity: critical
> Justification: breaks the whole system
> X-Debbugs-Cc: rgrove@rsu20.org
> 
> Dear Maintainer,
> 
> Updating to any Linux kernel after 5.7.0-2-amd64 makes the NVMe SSD on Apple MacBookAir7,1 fail to start. 
> dmesg spits out:
> [   64.565416] nvme nvme0: controller is down; will reset: CSTS=0x3, PCI_STATUS=0x10
> [   64.645531] nvme nvme0: detected Apple NVMe controller, set queue depth=2 to work around controller resets
> [   80.149335] nvme nvme0: Device not ready; aborting reset, CSTS=0x3
> [   80.149373] nvme nvme0: Removing after probe failure status: -19
> [   80.173515] blk_update_request: I/O error, dev nvme0n1, sector 2056 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
> [   80.173611] blk_update_request: I/O error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
> [   80.173623] blk_update_request: I/O error, dev nvme0n1, sector 208768 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
> [   80.173638] Buffer I/O error on dev nvme0n1p1, logical block 1, async page read
> [   80.173873] Buffer I/O error on dev nvme0n1p2, logical block 25584, async page read

Does the above workaround helps?

In case the above workaround does not help, and you are able to
reproduce the issue with a recent kernel, please do reopen the bug.

Regards,
Salvatore

--- End Message ---
Reply to: