Bug#918140: Confirming linux-image-4.17.0-3-amd64 works

2019-01-04 Thread Tyler Schwend
Just confirming that linux-image-4.17.0-3-amd64 is working fine. Almost 24
hours of uptime whereas I couldn't get 2 hours on
linux-image-4.19.0-1-amd64.

I am using the same kernel options on both kernels, so I'm not sure if 4.17
works without disabling APSTE or not.


Bug#918140: linux-image-4.19.0-1-amd64: Samsung PM951 SSD in Dell XPS 15 9550 goes read-only

2019-01-03 Thread Tyler Schwend
Package: src:linux
Version: 4.19.12-1
Severity: critical
Tags: upstream
Justification: breaks the whole system

Dear Maintainer,

Submitting a bug report wherein after a kernel upgrade my laptop's SSD will,
during use or idle, go into read-only mode after minutes or hours of uptime. It
seems this is related to NVME/APSTE features (which I don't understand). Below
are some similar reports for other models:

https://groups.google.com/forum/#!searchin/linux.debian.bugs.dist/apst$20samsung|sort:date/linux.debian.bugs.dist/1AAKPI7rfQA/450TYup-
AQAJ

https://bbs.archlinux.org/viewtopic.php?id=232692

https://askubuntu.com/questions/905710/ext4-fs-error-after-
ubuntu-17-04-upgrade/906105#906105

I had been running an older kernel (because I previously noticed this and
associated it with a kernel upgrade) but over time forgot why I was using an
old kernel. Some docker work required me to update my kernel again, the problem
returned, and I was reminded of why I kept running the old kernel.

I believe that linux-image-4.17.0-3-amd64 works fine for me (possibly now that
I have disabled APSTE) but linux-image-4.19.0-1-amd64 does not. I don't know
what version of kernel I was running previously, but I will boot back to
4.17.03 and use that for a time, and then update the bug report.


   * What led up to the situation?
- Upgrading from an older 4.x kernel. I think 4.17 is fine, but will have to
run for a while to be sure.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
- No fixes found except for running older kernel.
- Disabling APSTE with nvme_core.default_ps_max_latency_us=0 provides no
relief, though it is reported as disabled by NVME tool.
- There are no firmware updates available for this drive.



-- Package-specific info:
** Version:
Linux version 4.19.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 
8.2.0 (Debian 8.2.0-13)) #1 SMP Debian 4.19.12-1 (2018-12-22)

** Command line:
BOOT_IMAGE=/vmlinuz-4.19.0-1-amd64 root=/dev/mapper/func--platform--vg-root ro 
quiet nvme_core.default_ps_max_latency_us=0

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
[3.661043] Bluetooth: L2CAP socket layer initialized
[3.661055] Bluetooth: SCO socket layer initialized
[3.666339] usbcore: registered new interface driver btusb
[3.690698] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[3.690699] Bluetooth: BNEP filters: protocol multicast
[3.690702] Bluetooth: BNEP socket layer initialized
[3.713324] input: HDA Intel PCH Headphone Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input20
[3.713365] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input21
[3.713400] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input22
[3.713450] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input23
[3.713507] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input24
[3.715654] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input25
[3.736832] input: Logitech Unifying Device. Wireless PID:2011 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:046D:C52B.0008/0003:046D:2011.000A/input/input26
[3.737036] input: Logitech Unifying Device. Wireless PID:2011 Consumer 
Control as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:046D:C52B.0008/0003:046D:2011.000A/input/input27
[3.737096] input: Logitech Unifying Device. Wireless PID:2011 System 
Control as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:046D:C52B.0008/0003:046D:2011.000A/input/input28
[3.737154] hid-generic 0003:046D:2011.000A: input,hidraw7: USB HID v1.11 
Keyboard [Logitech Unifying Device. Wireless PID:2011] on usb-:00:14.0-2.3:4
[3.738701] input: Logitech Unifying Device. Wireless PID:4055 Mouse as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:046D:C52B.0008/0003:046D:4055.000B/input/input32
[3.738766] hid-generic 0003:046D:4055.000B: input,hidraw8: USB HID v1.11 
Mouse [Logitech Unifying Device. Wireless PID:4055] on usb-:00:14.0-2.3:1
[3.752683] input: Logitech K520 as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:046D:C52B.0008/0003:046D:2011.000C/input/input36
[3.781508] Bluetooth: hci0: BCM: chip id 102
[3.782508] Bluetooth: hci0: BCM: features 0x2f
[3.798526] Bluetooth: hci0: func-platform
[3.799513] Bluetooth: hci0: BCM (001.001.005) build 0422
[3.801782] bluetooth hci0: firmware: direct-loading firmware 
brcm/BCM-0a5c-6410.hcd
[3.847890] logitech-hidpp-device 0003:046D:2011.000C: input,hidraw9: USB 
HID v1.11 Keyboard [Logitech K520] on usb-:00:14.0-2.3:2
[3.854718] input: Logitech K520 as