This bug was fixed in the package linux - 4.11.0-13.19
---
linux (4.11.0-13.19) artful; urgency=low
* CVE-2017-7533
- dentry name snapshots
linux (4.11.0-12.18) artful; urgency=low
* linux: 4.11.0-12.18 -proposed tracker (LP: #1707635)
- no change rebuild to pick up the
This bug was fixed in the package linux - 4.10.0-30.34
---
linux (4.10.0-30.34) zesty; urgency=low
* CVE-2017-7533
- dentry name snapshots
linux (4.10.0-29.33) zesty; urgency=low
* linux: 4.10.0-29.33 -proposed tracker (LP: #1704961)
* Opal and POWER9 DD2 (LP: #1702159)
Hi @Nils,
Could you please test the Zesty kernel that's currently in proposed
(4.10.0-29.33)?
Thank you.
--
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/1699004
Title:
APST gets enabled
@Nils,
You need to remove 4.12.0-041200rc5-generic, or other mainline/testing kernel
you installed.
After that, boot with kernel 4.10.0-29, verify if this bug still happen to your
system.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I really don't understand what's going on here and what I'm expected to
do.
After enabling -proposed, my system boots with kernel
4.12.0-041200rc5-generic
and APST is enabled again (and my system crashed after about 10 Minutes with
exactly the same behaviour as before). Should that kernel conta
Just realized you were replying previous comment...
--
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/1699004
Title:
APST gets enabled against explicit kernel option
Status in linux packag
@Nils,
Wha you need to do is to enable -proposed repository, and verify that
the Linux kernel in -proposed actually fixes the problem.
--
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/169900
I'm sorry, for taking so long to respond.
I do not have any logs, since they cannot be written to my hard drive in
the event of failure. (The SSD is my only hard drive and it can no
longer be accessed.)
But the error messages are something like:
EXT4-fs error (device nvme0n1p2): ext4_find_entry:
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 'verificati
** Changed in: linux (Ubuntu Yakkety)
Status: New => Fix Committed
--
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/1699004
Title:
APST gets enabled against explicit kernel option
** Changed in: linux (Ubuntu Zesty)
Status: New => Fix Committed
--
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/1699004
Title:
APST gets enabled against explicit kernel option
St
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a m
** Description changed:
+ [Impact]
+ The NVMe driver doesn't set APSTE on APST quirked devices at initialization.
If the BIOS or NVMe enables APST before driver loading, APST will never be
disabled, it also ignores explicit kernel option as result.
+ So the faulty NVMe may not work as intended.
Nils,
Andy means what exactly error message when booting with kernel like
4.10.0-22. Bad means "APST is enabled all the time" bad.
--
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/1699004
T
I'm not sure what exactly you're asking. The kernel above that does not
boot? The boot seems to fail before the drive is mounted, so I have no
logfiles whatsoever. The only thing I have is a photo of the last
messages on screen.
Or are you talking about something else?
--
You received this bug n
Nils, what the actual failure mode on a bad kernel? Do you have dmesg
output?
--
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/1699004
Title:
APST gets enabled against explicit kernel opt
Patch sent:
https://lists.infradead.org/pipermail/linux-nvme/2017-June/011382.html
--
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/1699004
Title:
APST gets enabled against explicit kernel
Looks like your system enables APST by default. So we can't assume APST
is disabled by default - APST needs to be set on all circumstances.
--
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/16
In that case it's enabled again:
$ dmesg | grep -i nvme
[0.00] Command line:
BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash
nvme_core.default_ps_max_latency_us=0 nvme_core.dyndbg=+p vt.handoff=7
[0.00] Kernel
Can you do one more testing? If now you boot with Ubuntu's 4.10 kernel
with default_ps_max_latency_us=0, is APST enabled or disabled?
--
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/1699004
Your system somehow saves APST config across reboots. The current code
logic will skip configuring APST if the device is in quirk table - so
the new APST value will never get set despite
default_ps_max_latency_us=0.
I'll send a patch for this issue. Also, thanks for your testing =)
--
You receiv
With the new kernel the system boots up.
I get the following:
$ dmesg | grep -i nvme
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.0-rc6+
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash
nvme_core.dyndbg=+p vt.handoff=7
[0.00] Kernel command line: BOOT_IMAGE=/b
Built a new kernel for testing:
http://people.canonical.com/~khfeng/lp1699004/linux-image-4.12.0-rc6+_4.12.0-rc6+-6_amd64.deb
Also, you can remove "nvme_core.default_ps_max_latency_us=0" - the model
you use is already in the quirk table. Keep "nvme_core.dyndbg=+p" in the
meantime.
Attach `dmesg |
I have not upgraded the BIOS or the firmware, no.
This is really weird.
I tried the new kernel, however my system does not boot up with it.
It also does not show me an error that i can interpret, and the boot messages
do not seem to be logged anywhere. I'm assuming that the system has problems
w
Please try http://people.canonical.com/~khfeng/lp1699004/linux-
image-4.12.0-rc6+_4.12.0-rc6+-3_amd64.deb
--
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/1699004
Title:
APST gets enabled
So APST is not enabled in NVMe driver. I have no idea who does it,
probably BIOS or NVMe firmware?
Did you upgrade them before the issue reappear?
Anyway, we probably need to explicitly disable APST in the NVMe driver.
--
You received this bug notification because you are a member of Kernel
Pac
Now I get the following:
$ dmesg | grep -i apst
[2.232133] nvme nvme0: apsta = 0, no APST
[2.448134] nvme :04:00.0: NVME_QUIRK_NO_APST
[2.448135] nvme :04:00.0: disabling APST.
[2.448137] nvme nvme0: apsta = 0, no APST
It seems like those messages are telling me that apst
Please try this one:
http://people.canonical.com/~khfeng/lp1699004/
I added several messages to debug what code path it took.
Grep apst again:
$ dmesg | grep -i apst
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
Sorry, you are indeed correct, apparently I forgot to update-grub.
Nevertheless, I get the same results
$ dmesg | grep -i apst
$ dmesg | grep -i nvme
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.0-041200rc5-generic
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash
nvm
"nvme_core.default_ps_max_latency_us=0" is still in the kernel
parameter.
--
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/1699004
Title:
APST gets enabled against explicit kernel option
$ dmesg | grep -i apst
still does not return anything
$ dmesg | grep -i nvme
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.0-041200rc5-generic
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash
nvme_core.default_ps_max_latency_us=0 nvme_core.dyndbg=+p vt.handoff=7
[
I don't know (yet) how kernel parses its cmdline parameters - can you
remove "nvme_core.default_ps_max_latency_us=0" but keep
"nvme_core.dyndbg=+p", then do the grep again?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
It is indeed very odd.
dmesg | grep dyndbg
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.0-041200rc5-generic
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash
nvme_core.default_ps_max_latency_us=0 nvme_core.dyndbg=+p vt.handoff=7
[0.00] Kernel command line:
BOO
That's weird. 4.12-rc5 should have APST message if dynamic debug is
enabled.
--
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/1699004
Title:
APST gets enabled against explicit kernel optio
$ dmesg | grep -i apst
does not return anything.
--
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/1699004
Title:
APST gets enabled against explicit kernel option
Status in linux package
It means the quirk doesn't work:
commit be56945c4edd5a3da15f8254b68d1ddb1588d0c4
Author: Andy Lutomirski
Date: Thu Apr 20 13:37:56 2017 -0700
nvme: Quirk APST off on "THNSF5256GPUK TOSHIBA"
Can you do
$ dmesg | grep -i apst
instead?
--
You received this bug notification because you are
I installed the kernel you linked to and set the kernel parameter.
On first boot the system immediately crashed with I/O errors upon login.
After reboot I could run the commands:
$ dmesg | grep -i nvme
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.0-041200rc5-generic
root=UUID=365f1a
Can you install latest mainline kernel [1], add "nvme_core.dyndbg=+p" to
your kernel parameter, and do
$ dmesg | grep -i nvme
$ sudo nvme get-feature -f 0x0c -H /dev/nvme0
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc5/linux-
headers-4.12.0-041200rc5-generic_4.12.0-041200rc5.20170611
I get
$ cat /sys/module/nvme_core/parameters/default_ps_max_latency_us
0
which kind of surprises me.
$ sudo find /sys -name '*latency*' | grep nvme0 | xargs cat
does not return anything.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Please attach the value of `sudo find /sys -name '*latency*' | grep
nvme0 | xargs cat` as well.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
What's the value of `cat
/sys/module/nvme_core/parameters/default_ps_max_latency_us`?
--
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/1699004
Title:
APST gets enabled against explicit ker
41 matches
Mail list logo
