You're very welcome Guo! I'll mark this as resolved, in case you have questions,
feel free to comment here.
Cheers,
Guilherme
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Fix Released
--
You received this
hi Guilherme,
Get it! Thank you very much for your support.
Guo Yaowen
--
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/1792660
Title:
nvme name floated after boot with 4.15.0 kernel
Hi Guo, the Ubuntu kernels schedule can be checked here:
https://wiki.ubuntu.com/Kernel/Support .
Ubuntu kernel team chooses a kernel version for a specific release, and
once that release is available, there's a support schedule. Some
versions have long-term support, so they're called LTS.
In
hi Guilherme,
I couldn't find a normal Linux-image package in 4.17 and 4.17-rac4, just a
package with unsigned. Could you please tell me if this package is available.
linux-headers-4.17.0-041700_4.17.0-041700.201806041953_all.deb
I've just tested a mainline kernel version 4.17.0, and nvme names didn't
float when using the kernel parameter "nvme_core.multipath=0", which
reinforces that the fix patch is present in 4.17, so Guo: I guess your
4.17 version is really based on 4.17-rc1.
Let me know if there's anything else to
Hi Guo, thanks for your tests!
So, to confirm:
a) With Ubuntu kernel 4.15.0-34, using the kernel parameter
"nvme_core.multipath=0", you _don't_ see the issue;
b) With kernel 4.17.0-041700rc1-generic, even using the parameter
"nvme_core.multipath=0", you *can reproduce* the issue.
Right?
I've
hi Guilherme,
I upgraded to version 34 of the Ubuntu kernel with the "apt-get upgrade"
command, and the problem was solved. So I think the kernel version of
the kernel.ubuntu.com site doesn't fit into the patch, so can we say
that it's Ubuntu's own behavior?
Thanks,
Guo Yaowen
--
You received
hi Guilherme,
I have tested kernel 4.17.0,but the issuse is same.The 4.17.0 testing results
are as below:
uname -r
4.17.0-041700rc1-generic
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc1-generic
root=UUID=3e875566-3c1b-4bda-a869-6eb59ff1624a ro nvme_core.multipath=0
ls -l
Hi Mao, I see...the partner is not using a regular Ubuntu build.
This patch was introduced upstream in kernel 4.17, so it's not present in a
regular 4.15 or 4.16. It is present in our Ubuntu kernel though, because it was
backported and added, but I can't guarantee it's present in the custom
hi Guilherme,
The partner have tested both for 4.16.0 and 4.15.1 ( I guess it is newer than
4.15.0-34), it was reported that the issues is same. The 4.15.1 testing results
are as below:
zlmao@zlmao-T460s:~/tmp$ cat test_result.txt
uname -r
4.15.1-041501-generic
cat /proc/cmdline
Hi Zhanglei, thanks for the test and screenshot.
I can't say for sure, but based on the screenshot, seems they are still
running 4.15.0-29 - I'm seeing the BOOT_IMAGE entry in the
/proc/cmdline. Specifically, this doesn't mean much (one can boot like a
4.4 kernel and add a BOOT_IMAGE of a 4.15,
@Guiherme
Firstly, thank you much to provide those inforamtion. I asked customer
to check on 4.15.0-34 with kernel parameter of "nvme_core.multipath=0",
it was reported the same ( nvme device name would be changed every
reboot).
** Attachment added: "nvme name mismatch screen shoot"
Hi Zhanglei, I've faced this issue some time ago - in fact, it's not
a bug, but some annoyance caused by the multipath introduction in the
nvme driver.
It started recently, after [0] - the introduction of NVMe multipath
brought a change in the way namespaces' "identity" is calculated. Basically,
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
The log which collect via
apport-cli --save=/tmp/apport-log linux
** Attachment added: "apport-cli log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792660/+attachment/5191267/+files/apport-log
--
You received this bug notification because you are a member of Kernel
Packages,
If the bug still exists in the mainline kernel, we can perform a kernel
bisect to identify the commit that introduced this regression.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)
--
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/1792660
Title:
nvme name floated after boot with 4.15.0 kernel
Status in
18 matches
Mail list logo
