Comment 12 for bug 1626894

Revision history for this message
Stefan Lindblad (fairglow) wrote : Re: [Bug 1626894] Re: nvme drive probe failure

The second one (30d6592-reverted) worked for me, but not the first one.

Thanks,
/Stefan

On Fri, Sep 23, 2016 at 7:41 PM Joseph Salisbury <
<email address hidden>> wrote:

> The second test kernel is available at:
> http://kernel.ubuntu.com/~jsalisbury/lp1626894/30d6592-reverted/
>
> Can you see if either of these kernels resolve this bug?
>
>
> ** Tags added: kernel-da-key xenial
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1627040).
> 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:
> In Progress
> 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] 0000000000000286 00000000b6c91251 ffff880fe6e8bce0
> ffffffff813f1f83
> [ 1.005800] ffff880fe02150f0 ffffc90006a7c000 ffff880fe6e8bd00
> ffffffff8106bdff
> [ 1.006117] ffff880fe02150f0 ffff880fe0215258 ffff880fe6e8bd10
> ffffffff8106be3c
> [ 1.006433] Call Trace:
> [ 1.006509] [<ffffffff813f1f83>] dump_stack+0x63/0x90
> [ 1.006589] [<ffffffff8106bdff>] iounmap.part.1+0x7f/0x90
> [ 1.006668] [<ffffffff8106be3c>] iounmap+0x2c/0x30
> [ 1.006770] [<ffffffffc007a64a>] nvme_dev_unmap.isra.35+0x1a/0x30
> [nvme]
> [ 1.007048] [<ffffffffc007b75e>] nvme_remove+0xce/0xe0 [nvme]
> [ 1.007140] [<ffffffff81443409>] pci_device_remove+0x39/0xc0
> [ 1.007220] [<ffffffff815549f1>] __device_release_driver+0xa1/0x150
> [ 1.007301] [<ffffffff81554ac3>] device_release_driver+0x23/0x30
> [ 1.007382] [<ffffffff8143be7a>] pci_stop_bus_device+0x8a/0xa0
> [ 1.007462] [<ffffffff8143bfca>]
> pci_stop_and_remove_bus_device_locked+0x1a/0x30
> [ 1.007559] [<ffffffffc007a09c>]
> nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme]
> [ 1.007642] [<ffffffff8109a3e5>] process_one_work+0x165/0x480
> [ 1.007722] [<ffffffff8109a74b>] worker_thread+0x4b/0x4c0
> [ 1.007801] [<ffffffff8109a700>] ? process_one_work+0x480/0x480
> [ 1.007881] [<ffffffff810a0928>] kthread+0xd8/0xf0
> [ 1.007959] [<ffffffff810a0850>] ? kthread_create_on_node+0x1e0/0x1e0
> [ 1.008041] [<ffffffff81831a8f>] ret_from_fork+0x3f/0x70
> [ 1.008120] [<ffffffff810a0850>] ? kthread_create_on_node+0x1e0/0x1e0
> [ 1.008222] Trying to free nonexistent resource
> <00000000f7100000-00000000f7103fff>
> [ 1.008276] genirq: Flags mismatch irq 0. 00000080 (nvme1q0) vs.
> 00015a00 (timer)
> [ 1.008281] Trying to free nonexistent resource
> <000000000000d000-000000000000d0ff>
> [ 1.008282] nvme 0000:02:00.0: Removing after probe failure
> [ 1.008645] Trying to free nonexistent resource
> <000000000000e000-000000000000e0ff>
> [ 1.027213] iounmap: bad address ffffc90006ae0000
> [ 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
>