| 2018-11-29 11:12:28 |
Ian Ozsvald |
bug |
|
|
added bug |
| 2018-11-29 11:14:25 |
Ian Ozsvald |
attachment added |
|
lspci-vnvn.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816/+attachment/5217297/+files/lspci-vnvn.log |
|
| 2018-11-29 11:18:14 |
Ian Ozsvald |
tags |
|
apport-collected tara |
|
| 2018-11-29 11:18:15 |
Ian Ozsvald |
description |
This is a fresh posted connected to a very similar now-solved bug ("APST quirk needed for Samsung 512GB NVMe drive"): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
My NVMe is the less-common 1TB version. It exhibits similar (possibly identical) behaviour but has not yet been quirked.
I've followed up as Comment #101 but maybe I need to open this as a new issue? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/comments/101
Specifically - using Kernel 4.19.0 on Mint 19.0 the default APST settings caused read-only errors within minutes-1 hour, this is fatal. Disabling APST solves the problem, I have this disabled in GRUB now. Reducing the APST settings but not disabling them does not stop the problem.
An example of the read-only result (copied from #101) that occurs if APST is left in its default state:
Oct 31 11:33:04 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
Oct 31 11:33:04 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
Oct 31 11:33:05 ian-XPS-15-9550 kernel: EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
I had tried `nvme_core.default_ps_max_latency_us=250` but the read-only bug persists, it just takes longer to occur. Disabling APST with `nvme_core.default_ps_max_latency_us=0` has solved the issue.
I've been using my laptop successfully (no read-only errors) for over a week having disabled APST including many suspend/awaken cycles. Prior to this every boot would crash and burn with read-only errors within an hour or so.
This is the drive and kernel (copied from #101):
$ sudo nvme list
Node SN Model Namespace Usage Format FW Rev
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1 S2FZNYAG801690 PM951 NVMe SAMSUNG 1024GB 1 314.10 GB / 1.02 TB 512 B + 0 B BXV76D0Q
$ uname -a
Linux ian-XPS-15-9550 4.19.0-041900-generic #201810221809 SMP Mon Oct 22 22:11:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -rd
Description: Linux Mint 19 Tara
Release: 19
I am of course happy to upload more info - let me know what's needed?
Could this be added as a quirk to the kernel please? |
This is a fresh posted connected to a very similar now-solved bug ("APST quirk needed for Samsung 512GB NVMe drive"): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
My NVMe is the less-common 1TB version. It exhibits similar (possibly identical) behaviour but has not yet been quirked.
I've followed up as Comment #101 but maybe I need to open this as a new issue? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/comments/101
Specifically - using Kernel 4.19.0 on Mint 19.0 the default APST settings caused read-only errors within minutes-1 hour, this is fatal. Disabling APST solves the problem, I have this disabled in GRUB now. Reducing the APST settings but not disabling them does not stop the problem.
An example of the read-only result (copied from #101) that occurs if APST is left in its default state:
Oct 31 11:33:04 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
Oct 31 11:33:04 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
Oct 31 11:33:05 ian-XPS-15-9550 kernel: EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
I had tried `nvme_core.default_ps_max_latency_us=250` but the read-only bug persists, it just takes longer to occur. Disabling APST with `nvme_core.default_ps_max_latency_us=0` has solved the issue.
I've been using my laptop successfully (no read-only errors) for over a week having disabled APST including many suspend/awaken cycles. Prior to this every boot would crash and burn with read-only errors within an hour or so.
This is the drive and kernel (copied from #101):
$ sudo nvme list
Node SN Model Namespace Usage Format FW Rev
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1 S2FZNYAG801690 PM951 NVMe SAMSUNG 1024GB 1 314.10 GB / 1.02 TB 512 B + 0 B BXV76D0Q
$ uname -a
Linux ian-XPS-15-9550 4.19.0-041900-generic #201810221809 SMP Mon Oct 22 22:11:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -rd
Description: Linux Mint 19 Tara
Release: 19
I am of course happy to upload more info - let me know what's needed?
Could this be added as a quirk to the kernel please?
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
InstallationDate: Installed on 2018-10-27 (32 days ago)
InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
Package: linux (not installed)
Tags: tara
Uname: Linux 4.19.0-041900-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True |
|
| 2018-11-29 11:18:17 |
Ian Ozsvald |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1805816/+attachment/5217298/+files/ProcCpuinfoMinimal.txt |
|
| 2018-11-29 11:18:18 |
Ian Ozsvald |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1805816/+attachment/5217299/+files/ProcEnviron.txt |
|
| 2018-11-29 11:30:07 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2018-11-29 12:17:34 |
Ian Ozsvald |
description |
This is a fresh posted connected to a very similar now-solved bug ("APST quirk needed for Samsung 512GB NVMe drive"): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
My NVMe is the less-common 1TB version. It exhibits similar (possibly identical) behaviour but has not yet been quirked.
I've followed up as Comment #101 but maybe I need to open this as a new issue? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/comments/101
Specifically - using Kernel 4.19.0 on Mint 19.0 the default APST settings caused read-only errors within minutes-1 hour, this is fatal. Disabling APST solves the problem, I have this disabled in GRUB now. Reducing the APST settings but not disabling them does not stop the problem.
An example of the read-only result (copied from #101) that occurs if APST is left in its default state:
Oct 31 11:33:04 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
Oct 31 11:33:04 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
Oct 31 11:33:05 ian-XPS-15-9550 kernel: EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
I had tried `nvme_core.default_ps_max_latency_us=250` but the read-only bug persists, it just takes longer to occur. Disabling APST with `nvme_core.default_ps_max_latency_us=0` has solved the issue.
I've been using my laptop successfully (no read-only errors) for over a week having disabled APST including many suspend/awaken cycles. Prior to this every boot would crash and burn with read-only errors within an hour or so.
This is the drive and kernel (copied from #101):
$ sudo nvme list
Node SN Model Namespace Usage Format FW Rev
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1 S2FZNYAG801690 PM951 NVMe SAMSUNG 1024GB 1 314.10 GB / 1.02 TB 512 B + 0 B BXV76D0Q
$ uname -a
Linux ian-XPS-15-9550 4.19.0-041900-generic #201810221809 SMP Mon Oct 22 22:11:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -rd
Description: Linux Mint 19 Tara
Release: 19
I am of course happy to upload more info - let me know what's needed?
Could this be added as a quirk to the kernel please?
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
InstallationDate: Installed on 2018-10-27 (32 days ago)
InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
Package: linux (not installed)
Tags: tara
Uname: Linux 4.19.0-041900-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True |
This is a fresh posted connected to a very similar now-solved bug ("APST quirk needed for Samsung 512GB NVMe drive"): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
My NVMe is the less-common 1TB version. It exhibits similar (possibly identical) behaviour but has not yet been quirked.
I've followed up as Comment #101 but maybe I need to open this as a new issue? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/comments/101
Specifically - using Kernel 4.19.0 on Mint 19.0 the default APST settings caused read-only errors within minutes-1 hour, this is fatal. Disabling APST solves the problem, I have this disabled in GRUB now. Reducing the APST settings but not disabling them does not stop the problem.
An example of the read-only result (copied from #101) that occurs if APST is left in its default state:
Oct 31 11:33:04 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
Oct 31 11:33:04 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
Oct 31 11:33:05 ian-XPS-15-9550 kernel: EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
Oct 31 15:09:44 ian-XPS-15-9550 kernel: EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null)
I had tried `nvme_core.default_ps_max_latency_us=250` but the read-only bug persists, it just takes longer to occur. Disabling APST with `nvme_core.default_ps_max_latency_us=0` has solved the issue.
I've been using my laptop successfully (no read-only errors) for over a week having disabled APST including many suspend/awaken cycles. Prior to this every boot would crash and burn with read-only errors within an hour or so.
This is the drive and kernel (copied from #101):
$ sudo nvme list
Node SN Model Namespace Usage Format FW Rev
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1 S2FZNYAG801690 PM951 NVMe SAMSUNG 1024GB 1 314.10 GB / 1.02 TB 512 B + 0 B BXV76D0Q
$ uname -a
Linux ian-XPS-15-9550 4.19.0-041900-generic #201810221809 SMP Mon Oct 22 22:11:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -rd
Description: Linux Mint 19 Tara
Release: 19
I am of course happy to upload more info - let me know what's needed?
Could this be added as a quirk to the kernel please?
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
InstallationDate: Installed on 2018-10-27 (32 days ago)
InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
Package: linux (not installed)
Tags: tara
Uname: Linux 4.19.0-041900-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
InstallationDate: Installed on 2018-10-27 (32 days ago)
InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
Package: linux (not installed)
Tags: tara
Uname: Linux 4.19.0-041900-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True |
|
| 2018-11-29 12:17:34 |
Ian Ozsvald |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1805816/+attachment/5217333/+files/ProcCpuinfoMinimal.txt |
|
| 2018-11-29 12:17:36 |
Ian Ozsvald |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1805816/+attachment/5217334/+files/ProcEnviron.txt |
|
| 2018-11-29 12:26:45 |
Jan Vlug |
bug |
|
|
added subscriber Jan Vlug |
| 2018-11-29 12:39:20 |
Ian Ozsvald |
bug watch added |
|
https://bugzilla.kernel.org/show_bug.cgi?id=201811 |
|
| 2018-11-29 12:40:15 |
Ian Ozsvald |
linux (Ubuntu): status |
Incomplete |
New |
|
| 2018-11-29 13:00:10 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2019-02-27 21:26:41 |
Dan Streetman |
bug |
|
|
added subscriber Dan Streetman |
| 2019-04-08 15:22:10 |
Dan Streetman |
removed subscriber Dan Streetman |
|
|
|
| 2019-05-28 10:27:41 |
Kai-Heng Feng |
linux (Ubuntu): status |
Incomplete |
Won't Fix |
|
| 2019-09-12 14:34:45 |
Marcelo |
bug |
|
|
added subscriber Marcelo |
| 2023-04-18 12:12:09 |
Junior Lawrence Kibirige |
attachment added |
|
IMG_5075.jpeg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816/+attachment/5664964/+files/IMG_5075.jpeg |
|
