This bug was fixed in the package linux - 4.10.0-26.30
---
linux (4.10.0-26.30) zesty; urgency=low
* linux: 4.10.0-26.30 -proposed tracker (LP: #1700528)
* CVE-2017-1000364
- Revert "UBUNTU: SAUCE: mm: Only expand stack if guard area is hit"
- Revert "mm: do not collapse
This bug was fixed in the package linux - 4.10.0-26.30
---
linux (4.10.0-26.30) zesty; urgency=low
* linux: 4.10.0-26.30 -proposed tracker (LP: #1700528)
* CVE-2017-1000364
- Revert "UBUNTU: SAUCE: mm: Only expand stack if guard area is hit"
- Revert "mm: do not collapse
This bug was fixed in the package linux - 4.8.0-58.63
---
linux (4.8.0-58.63) yakkety; urgency=low
* linux: 4.8.0-58.63 -proposed tracker (LP: #1700533)
* CVE-2017-1000364
- Revert "UBUNTU: SAUCE: mm: Only expand stack if guard area is hit"
- Revert "mm: do not collapse
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
Hope to see the new kernel soon. Thanks for the work Kai-Heng!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686592
Title:
APST quirk needed for Intel NVMe
To manage notifications about this bug
Thanks for the info, Onno.
So the firmware didn't fix the issue. The kernel fix in #21 will be in
newer kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686592
Title:
APST quirk needed for
One of the machines running 2.2.1 with stock firmware has crashed
overnight.
Machines with the kernel from #21 haven't had any issues since
installation (three weeks or so)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu Yakkety)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Zesty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686592
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a
Two machines on stock kernel with firmware 2.2.1, no issues so far.
Two different machines are running the kernel from #21 with 2.2.0, no
problems as well.
Should be able to tell you next week if we have encountered issues.
--
You received this bug notification because you are a member of
** Description changed:
+ [Impact]
+ Intel NVMe failed to work after some disk I/O.
+
+ [Test Case]
+ Use the system for a while. Any disk I/O may make Intel NVMe failed to
operate.
+
+ [Regression Potential]
+ None. It only applies to limited Intel NVMe devices.
+
Two users reports issue
Hmm, does 2.2.1 help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686592
Title:
APST quirk needed for Intel NVMe
To manage notifications about this bug go to:
Forgot to mention that the changelog is for version 2.2.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686592
Title:
APST quirk needed for Intel NVMe
To manage notifications about this bug go
We had the firmware 2.2.0 installed on the two machines, that did not
help.
Changelog seems to contain fixes that might help:
> This firmware versions contain fixes for the following issues:
> • Drive hangs intermittently after Format NVM command.
> • Format NVM command occasionally failing with
Hi, an Intel developer [1] said firmware update [2] can solve the issue.
After update the firmware, can you use kernel from Ubuntu's repo instead of
what I compiled?
[1] http://lists.infradead.org/pipermail/linux-nvme/2017-May/010560.html
[2] https://downloadcenter.intel.com/download/26491?v=t
@kaihengfeng I haven't seen an issue on both devices with the kernel
from #14. I just installed a third devices with the kernel from #21.
If you need any logging or device specs please let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
For intel nvme, please try this zesty kernel:
http://people.canonical.com/~khfeng/lp1686592-170525/
It added two more patches from Andy:
[1/2] nvme: Wait at least 6000ms before entering the deepest idle state
[2/2] nvme: Quirk APST on Intel 600P/P3100 devices
--
You received this bug
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5904] (rev 02)
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:5916]
(rev 02)
00:04.0 Signal processing controller [1180]: Intel Corporation Skylake
Processor Thermal Subsystem [8086:1903] (rev 02)
00:14.0 USB
@Onno
Do you still encounter this issue on the kernel in comment #14?
Other user reported the issue may still occur albeit with much lower rate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686592
For those of you with problematic Intel devices, could you post the
relevant line from 'lspci -nn'? It looks like there are a few known
firmware issues with some Intel SSDs and a fix is in the works.
Meanwhile, I want to quirk the correct set of devices.
(I'm hoping they're all 8086:f1a5)
--
As soon as the patch author (Andy Lutomirski) makes the change into
nvme/block/linus tree, I'll cherry pick the patches into Ubuntu's
kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686592
The kernel seems to resolve the issue, both machines haven't crashed
since I installed it.
Do you have any idea when this patch is included into the main repo?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
Within our company we have multiple Intel NUC with Intel NVMe drives
that regularly crash. Programs throw errors and hang and the filesystem
gets corrupt. When (re)booting it enters initramfs where a "fsck -y
/dev/nvme0n1p2" fixes the issues (for now).
As most issues happen after a period of
Hi guys, can you try the kernel in [1] and remove the nvme kernel
parameter? I slightly tested it on the Precision 5510 at my hand,
haven't notice any errors so far.
It should also work on Intel NVMe.
[1] http://people.canonical.com/~khfeng/apst-rste-z/
--
You received this bug notification
@kaihengfeng, I'm not sure what your test kernel is, but could you build
one with the two patches here:
https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/log/?h=nvme/power=1115e17962c597d8e6dd140d903a51a58d0ec2c0
Those delete the earlier quirk and replace the APST table computation
Can you try again with http://people.canonical.com/~khfeng/lp1686592-2/?
If the issue persists, please attach dmesg here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686592
Title:
APST quirk
I am unable to boot up the above kernel reliably on my laptop.Both times
i booted it, my system hung. I had to do a hard reset (force power
down).
I am not able to tell if the new kernel fixes my issue. When the system
hangs, keyboard input doesn't work, this happened immediately after
kernel
Anyone who's using Intel NVMe, please try kernel in
http://people.canonical.com/~khfeng/lp1686592/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686592
Title:
APST quirk needed for Intel NVMe
To
Sorry, to be more precise that my first comment, my crash not while
booting. Really system crashed in less than an hour using 4.8.0-49 or
4.10.0-20 kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With 4.10.0-20 kernel:
NVME Identify Controller:
vid : 0x144d
ssvid : 0x144d
sn : S29PNXAH302364
mn : PM951 NVMe SAMSUNG 512GB
fr : BXV77D0Q
rab : 2
ieee: 002538
cmic: 0
mdts: 5
cntlid : 1
ver : 0
rtd3r : 0
rtd3e : 0
oaes: 0
@adn770 can you try to boot the newer kernels with the boot option
nvme_core.default_ps_max_latency_us=11000
That should disable the last state.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686592
This http://paste.ubuntu.com/24467585/ is the output on the Skull Canyon
systems we have here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686592
Title:
APST quirk needed for Intel NVMe
To
@javigs Can you post the output from nvme id-ctrl?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686592
Title:
APST quirk needed for Intel NVMe
To manage notifications about this bug go to:
Booting with 4.8.0-49 or 4.10.0-20 crash my system: Dell 9550 with PM951
NVMe SAMSUNG 512GB
Now I'm working with 4.8.0-46 without crashes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686592
Title:
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Booting with the kernel option nvme_core.default_ps_max_latency_us=11000
makes a difference for me. i no longer see filesystem crashes with this
option on 4.10.x and 4.8.0-49 kernel. Prior to this kernel change,
filesytem crashed soon after finishing the boot process.
--
You received this bug
Output from nvme id-ctrl on a Dell 9360 with Intel 600p nvme drive.
NVME Identify Controller:
vid : 0x8086
ssvid : 0x8086
sn : BTPY63850F281P0H
mn : INTEL SSDPEKKW010T7
fr : PSF104C
rab : 6
ieee: 5cd2e4
cmic: 0
mdts: 5
cntlid : 1
ver
38 matches
Mail list logo
