[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure
Seems to be working for me now. -- 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/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure
Will do, this testing can be tricky since the issue appears randomly (can take minutes, hours, even a day for me). Can we review the patch for the issue somewhere as well? -- 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/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure
For the record, I'm using my SSD on on M2 slot on an Intel NUC (http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5i3ryk.html). @ddstreet, I tried to use your kernel but for whatever reason, it won't zork with my LVM based installation. -- 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/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure
Yes please re-open as this bug does not not seem to be fixed due to the last mentioned change. See: [56990.782669] nvme0n1: detected capacity change from 128035676160 to 0 [56990.782652] nvme :03:00.0: Removing after probe failure [56990.531978] nvme :03:00.0: Failed status: 0x, reset controller. I'm using Intel 600P Series M.2. -- 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/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584042] Re: Hyper-V NIC cannot pass IPv6 UDP packets by default until protocol offload is disabled
I can confirm this issue. I'm currently experiencing it with newly installed Ubuntu Server 16.04. I also can confirm that this issue was not present in 14.04. -- 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/1584042 Title: Hyper-V NIC cannot pass IPv6 UDP packets by default until protocol offload is disabled Status in linux package in Ubuntu: Confirmed Bug description: Hi, On a client server, I can't get a response from a name server in ipv6+udp. On the same server, it works fine in tcp. If I log on my name server, I can get a response from himself but, as a client, it can't get a response from another name server. here are the steps to reproduce : - Create a new server using Ubuntu server 16.04. Set it to use ipv4 and use your preferred name server. Select absolutely nothing as functionality. - check some nslookup and apt-get stuff to verify network is OK - add ipv6 to the interface and refer to an IPV6 nameserver. I have 3 and thats why I noticed the problem >> All 3 ipv6 nameservers are filling the 3 places in resolv.conf. - if you don't have 3 ipv6 nameservers, just add one and comment the line with the ipv4 name server. - verify your resolv.conf. Should only content ipv6 reference. - Now, you can't nslookup anymore... - add some tests : "dig @ipv4server google.com" works but "dig @ipv6server google.com" don't Here a more tests : Nameserver1 : Nameserver1.MyDomain : XXX.YYY.ZZZ.250 / ::::250 ClientStandAloneServer.MyDomain : XXX.YYY.ZZZ.209 / ::::209 With IPV4 # dig @XXX.YYY.ZZZ.226 www.google.fr /var/log/named/queries.log on Nameserver1: 20-May-2016 12:25:02.834 queries: info: client XXX.YYY.ZZZ.209#35116 (www.google.fr): query: www.google.fr IN A +E (XXX.YYY.ZZZ.226) Tcp Dump on Nameserver1: 12:25:02.834092 IP StandAloneServer.MyDomain.35116 > Nameserver1.MyDomain.domain: 62949+ [1au] A? www.google.fr. (42) 12:25:02.834395 IP Nameserver1.MyDomain.domain > StandAloneServer.MyDomain.35116: 62949 1/4/5 A 216.58.210.195 (204) Tcp Dump on Client 12:25:02.668200 IP StandAloneServer.MyDomain.35116 > Nameserver1.MyDomain.domain: 62949+ [1au] A? www.google.fr. (42) 12:25:02.669573 IP Nameserver1.MyDomain.domain > StandAloneServer.MyDomain.35116: 62949 1/4/5 A 216.58.210.195 (204) RESULT: ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @XXX.YYY.ZZZ.226 www.google.fr ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49591 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 5 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;www.google.fr. IN A ;; ANSWER SECTION: www.google.fr.300 IN A 216.58.210.195 ;; AUTHORITY SECTION: google.fr.171625 IN NS ns1.google.com. [TRUNCATED] WITH IPV6 # dig @::::226 www.google.fr NOTE : I only asked once, it created 3 queries with 5 secs d’intervalle environ /var/log/named/queries.log on Nameserver1: 20-May-2016 12:32:34.902 queries: info: client ::::209#35362 (www.google.fr): query: www.google.fr IN A +E (::::226) 20-May-2016 12:32:39.902 queries: info: client ::::209#35362 (www.google.fr): query: www.google.fr IN A +E (::::226) 20-May-2016 12:32:44.902 queries: info: client ::::209#35362 (www.google.fr): query: www.google.fr IN A +E (::::226) Tcp Dump on Nameserver1: 12:32:34.902598 IP6 StandAloneServer.MyDomain.35362 > Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42) 12:32:34.902994 IP6 Nameserver1.MyDomain.domain > StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204) … 12:32:39.902644 IP6 StandAloneServer.MyDomain.35362 > Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42) 12:32:39.902975 IP6 Nameserver1.MyDomain.domain > StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204) … 12:32:39.902644 IP6 StandAloneServer.MyDomain.35362 > Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42) 12:32:39.902975 IP6 Nameserver1.MyDomain.domain > StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204) Tcp Dump on Client12:32:34.725312 IP6 StandAloneServer.MyDomain.35362 > Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42) 12:32:34.726036 IP6 Nameserver1.MyDomain.domain > StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204) … 12:32:39.725199 IP6 StandAloneServer.MyDomain.35362 > Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42) 12:32:39.726045 IP6 Nameserver1.MyDomain.domain > StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204) …
