Thanks for following up - we can close this bug, I no longer have this
issue. I have attached info just for the record. I upgraded my system
BIOS and the problems went away.
$ sudo nvme id-ctrl /dev/nvme0
[sudo] password for ian:
NVME Identify Controller:
vid : 0x144d
ssvid : 0x144d
Hello Yingfag - can I check please - was it a 1TB Samsung SSD? Which
model of SSD (950? 960? 970? something else?). When you changed the SSD
- did you keep the same model? What was your final solution? Regards,
Ian.
--
You received this bug notification because you are a member of Kernel
Oops - I can mark this issue as "New" but not "Complete" (which in turn
was me mis-reading the instruction from the bot in #4). Sorry for the
noise.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Sorry - I've hit a hiccup. `apport` wants me to file extra information (as
uploaded above, twice) but upon running at the command line it notes:
`
It appears you are currently running a mainline kernel. It would be better to
report this bug upstream at http://bugzilla.kernel.org/ so that the
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1805816/+attachment/5217334/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Description changed:
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
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1805816/+attachment/5217298/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1805816/+attachment/5217299/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816/+attachment/5217297/+files/lspci-vnvn.log
** Tags added: apport-collected tara
** Description changed:
This is a fresh posted connected to a very similar now-solved bug ("APST
quirk needed
Public bug reported:
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
I have posted my 1TB (PM951) issue as a new bug here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1678184
Title:
APST
Hi Kai-Heng, thanks!
Overnight I've used `nvme_core.default_ps_max_latency_us=0` in GRUB with
no read-only crashes (everything has been smooth). I left the machine
awake all night, I've since suspended & awoken it twice, all seems to be
ok.
As expected all APSTE is disabled:
`
$ sudo nvme
To follow-up. Earlier today I fresh-booted and didn't use the APST
disable command - my machine crashed out with read-only errors after
minutes.
I then updated grub to use `nvme_core.default_ps_max_latency_us=250` as
suggested - it was stable for 6 hours, through 2 suspends. A little
while ago it
I'd like to follow-up on this bug - it affects me using kernel 4.19.0 on
a Dell XPS 9550 with a 1TB Samsung drive. Details below. Do I need to
open a new bug as I've got a 1TB drive and this bug report was opened
for a 512GB drive?
$ uname -a
Linux ian-XPS-15-9550 4.19.0-041900-generic
Further note - when I made comment #4 I was using the NVIDIA driver
331.113 and kernel 3.13.0-24. I've just updated from Mint 17.1 to Mint
17.2 (with a new nvidia driver and kernel), I'll try suspend hibernate
over the coming days and report back.
--
You received this bug notification because
Further notes - the A19 bios was from approx June 2013, there is an A21
bios released in 2014 but the few fixes don't seem relevant.
I would *very much* like to have a way of getting some sort of kernel
log dump after a failure on the next boot, so I can even diagnose if it
is failing the same
** This bug is no longer a duplicate of bug 1275621
[Hewlett-Packard HP Pavilion dv6 Notebook PC] suspend/resume failure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1297049
Title:
Note I removed the duplicate link (to #1275621) as the other link
doesn't mention NVIDIA and it isn't a Dell machine, I suspect that the
NVIDIA chipset is the problem.
For the 4 years I've owned my E6420 I've failed to get reliable
suspend/hibernate behaviour, I always turn the laptop off when I
18 matches
Mail list logo
