* NVME module won't load ("nvme: disagrees about version of symbol nvme_uninit_ctrl")
@ 2020-08-25 1:39 Chris Worley
2020-08-25 5:10 ` Leon Romanovsky
2020-08-25 13:24 ` Christoph Hellwig
0 siblings, 2 replies; 3+ messages in thread
From: Chris Worley @ 2020-08-25 1:39 UTC (permalink / raw)
To: OFED mailing list
Running MLNX_OFED_LINUX-5.0-2.1.8.0-rhel8.2-x86_6 on ConnectX-3 cards,
attempting to run NVME-over-fabrics.
OFED installed with: "./mlnxofedinstall --add-kernel-support
--with-nvmf --force"
The OFED install did indicate it couldn't load the firmware (although
these are Mellanox cards) and said: "Note: In order to load the new
nvme-rdma and nvmet-rdma modules, the nvme module must be reloaded."
... but the nvme driver doesn't even load.
Where did I go wrong?
Thanks,
Chris
[ 1862.838855] nvme: disagrees about version of symbol nvme_uninit_ctrl
[ 1862.838856] nvme: Unknown symbol nvme_uninit_ctrl (err -22)
[ 1862.838872] nvme: disagrees about version of symbol nvme_complete_rq
[ 1862.838873] nvme: Unknown symbol nvme_complete_rq (err -22)
[ 1862.838886] nvme: disagrees about version of symbol nvme_reset_ctrl_sync
[ 1862.838887] nvme: Unknown symbol nvme_reset_ctrl_sync (err -22)
[ 1862.838900] nvme: disagrees about version of symbol nvme_wait_freeze_timeout
[ 1862.838901] nvme: Unknown symbol nvme_wait_freeze_timeout (err -22)
[ 1862.838932] nvme: disagrees about version of symbol nvme_start_queues
[ 1862.838933] nvme: Unknown symbol nvme_start_queues (err -22)
[ 1862.838944] nvme: disagrees about version of symbol nvme_alloc_request
[ 1862.838944] nvme: Unknown symbol nvme_alloc_request (err -22)
[ 1862.838983] nvme: disagrees about version of symbol nvme_setup_cmd
[ 1862.838984] nvme: Unknown symbol nvme_setup_cmd (err -22)
[ 1862.838996] nvme: disagrees about version of symbol nvme_start_freeze
[ 1862.838997] nvme: Unknown symbol nvme_start_freeze (err -22)
[ 1862.839009] nvme: disagrees about version of symbol nvme_start_ctrl
[ 1862.839010] nvme: Unknown symbol nvme_start_ctrl (err -22)
[ 1862.839028] nvme: disagrees about version of symbol nvme_submit_sync_cmd
[ 1862.839029] nvme: Unknown symbol nvme_submit_sync_cmd (err -22)
[ 1862.839066] nvme: disagrees about version of symbol nvme_disable_ctrl
[ 1862.839067] nvme: Unknown symbol nvme_disable_ctrl (err -22)
[ 1862.839097] nvme: disagrees about version of symbol nvme_wait_freeze
[ 1862.839097] nvme: Unknown symbol nvme_wait_freeze (err -22)
[ 1862.839108] nvme: disagrees about version of symbol nvme_cancel_request
[ 1862.839108] nvme: Unknown symbol nvme_cancel_request (err -22)
[ 1862.839121] nvme: disagrees about version of symbol nvme_cleanup_cmd
[ 1862.839121] nvme: Unknown symbol nvme_cleanup_cmd (err -22)
[ 1862.839132] nvme: disagrees about version of symbol nvme_sync_queues
[ 1862.839132] nvme: Unknown symbol nvme_sync_queues (err -22)
[ 1862.839167] nvme: disagrees about version of symbol nvme_change_ctrl_state
[ 1862.839168] nvme: Unknown symbol nvme_change_ctrl_state (err -22)
[ 1862.839182] nvme: disagrees about version of symbol nvme_init_ctrl
[ 1862.839182] nvme: Unknown symbol nvme_init_ctrl (err -22)
[ 1862.839200] nvme: Unknown symbol disk_to_nvme_ns (err 0)
[ 1862.839221] nvme: disagrees about version of symbol nvme_remove_namespaces
[ 1862.839221] nvme: Unknown symbol nvme_remove_namespaces (err -22)
[ 1862.839231] nvme: disagrees about version of symbol nvme_init_identify
[ 1862.839232] nvme: Unknown symbol nvme_init_identify (err -22)
[ 1862.839261] nvme: disagrees about version of symbol nvme_enable_ctrl
[ 1862.839262] nvme: Unknown symbol nvme_enable_ctrl (err -22)
[ 1862.839291] nvme: disagrees about version of symbol nvme_kill_queues
[ 1862.839291] nvme: Unknown symbol nvme_kill_queues (err -22)
[ 1862.839303] nvme: disagrees about version of symbol nvme_complete_async_event
[ 1862.839303] nvme: Unknown symbol nvme_complete_async_event (err -22)
[ 1862.839315] nvme: disagrees about version of symbol nvme_stop_queues
[ 1862.839316] nvme: Unknown symbol nvme_stop_queues (err -22)
[ 1862.839327] nvme: disagrees about version of symbol nvme_set_queue_count
[ 1862.839327] nvme: Unknown symbol nvme_set_queue_count (err -22)
[ 1862.839339] nvme: disagrees about version of symbol nvme_shutdown_ctrl
[ 1862.839339] nvme: Unknown symbol nvme_shutdown_ctrl (err -22)
[ 1862.839352] nvme: disagrees about version of symbol nvme_unfreeze
[ 1862.839353] nvme: Unknown symbol nvme_unfreeze (err -22)
[ 1862.839363] nvme: disagrees about version of symbol nvme_stop_ctrl
[ 1862.839364] nvme: Unknown symbol nvme_stop_ctrl (err -22)
[ 1862.839387] nvme: disagrees about version of symbol nvme_reset_ctrl
[ 1862.839387] nvme: Unknown symbol nvme_reset_ctrl (err -22)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: NVME module won't load ("nvme: disagrees about version of symbol nvme_uninit_ctrl")
2020-08-25 1:39 NVME module won't load ("nvme: disagrees about version of symbol nvme_uninit_ctrl") Chris Worley
@ 2020-08-25 5:10 ` Leon Romanovsky
2020-08-25 13:24 ` Christoph Hellwig
1 sibling, 0 replies; 3+ messages in thread
From: Leon Romanovsky @ 2020-08-25 5:10 UTC (permalink / raw)
To: Chris Worley; +Cc: OFED mailing list
On Mon, Aug 24, 2020 at 03:39:29PM -1000, Chris Worley wrote:
> Running MLNX_OFED_LINUX-5.0-2.1.8.0-rhel8.2-x86_6 on ConnectX-3 cards,
> attempting to run NVME-over-fabrics.
>
> OFED installed with: "./mlnxofedinstall --add-kernel-support
> --with-nvmf --force"
>
> The OFED install did indicate it couldn't load the firmware (although
> these are Mellanox cards) and said: "Note: In order to load the new
> nvme-rdma and nvmet-rdma modules, the nvme module must be reloaded."
> ... but the nvme driver doesn't even load.
>
> Where did I go wrong?
You posted to the wrong mailing list.
Please approach Mellanox support channel for MOFED related questions.
Thanks
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: NVME module won't load ("nvme: disagrees about version of symbol nvme_uninit_ctrl")
2020-08-25 1:39 NVME module won't load ("nvme: disagrees about version of symbol nvme_uninit_ctrl") Chris Worley
2020-08-25 5:10 ` Leon Romanovsky
@ 2020-08-25 13:24 ` Christoph Hellwig
1 sibling, 0 replies; 3+ messages in thread
From: Christoph Hellwig @ 2020-08-25 13:24 UTC (permalink / raw)
To: Chris Worley; +Cc: OFED mailing list
On Mon, Aug 24, 2020 at 03:39:29PM -1000, Chris Worley wrote:
> Running MLNX_OFED_LINUX-5.0-2.1.8.0-rhel8.2-x86_6 on ConnectX-3 cards,
> attempting to run NVME-over-fabrics.
>
> OFED installed with: "./mlnxofedinstall --add-kernel-support
> --with-nvmf --force"
>
> The OFED install did indicate it couldn't load the firmware (although
> these are Mellanox cards) and said: "Note: In order to load the new
> nvme-rdma and nvmet-rdma modules, the nvme module must be reloaded."
> ... but the nvme driver doesn't even load.
That's what you get for using a completely broken out of tree version
of the RDMA code. Don't do that.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-08-25 13:24 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-08-25 1:39 NVME module won't load ("nvme: disagrees about version of symbol nvme_uninit_ctrl") Chris Worley
2020-08-25 5:10 ` Leon Romanovsky
2020-08-25 13:24 ` Christoph Hellwig
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.