Created attachment 204744 [details] Log output (rerun) eee attached files for log and kernel config
Created attachment 204745 [details] kernel config
scc.conf and src-env.conf will be attached if needed
Salient part: linking kernel ld: error: undefined symbol: t4_register_cpl_handler >>> referenced by t4_crypto.c >>> t4_crypto.o:(ccr_modevent) ld: error: undefined symbol: t4_register_cpl_handler >>> referenced by t4_crypto.c >>> t4_crypto.o:(ccr_modevent) ld: error: undefined symbol: M_CXGBE >>> referenced by t4_crypto.c >>> t4_crypto.o:(ccr_process) ld: error: undefined symbol: M_CXGBE >>> referenced by t4_crypto.c >>> t4_crypto.o:(ccr_process) ld: error: undefined symbol: M_CXGBE >>> referenced by t4_crypto.c >>> t4_crypto.o:(ccr_process) ld: error: undefined symbol: t4_wrq_tx_locked >>> referenced by t4_crypto.c >>> t4_crypto.o:(ccr_process) ld: error: undefined symbol: t4_wrq_tx_locked >>> referenced by t4_crypto.c >>> t4_crypto.o:(ccr_process) ld: error: undefined symbol: t4_wrq_tx_locked >>> referenced by t4_crypto.c >>> t4_crypto.o:(ccr_process) ld: error: undefined symbol: M_CXGBE >>> referenced by t4_crypto.c >>> t4_crypto.o:(ccr_process) ld: error: undefined symbol: t4_wrq_tx_locked >>> referenced by t4_crypto.c >>> t4_crypto.o:(ccr_process) ld: error: undefined symbol: t4_aes_getdeckey >>> referenced by t4_crypto.c >>> t4_crypto.o:(ccr_aes_setkey) ld: error: undefined symbol: M_CXGBE >>> referenced by t4_crypto.c >>> t4_crypto.o:(ccr_hash) ld: error: undefined symbol: t4_wrq_tx_locked >>> referenced by t4_crypto.c >>> t4_crypto.o:(ccr_hash) *** [kernel] Error code 1
Kernel config includes 'device ccr' but not 'device cxgbe', which is probably invalid.
I guess another solution would be to changes 'optional ccr' to 'optional ccr cxgbe' in conf/files t4_crypto.c line, but that just silently "succeeds" when ccr is set and cxgbe is not set, when failure seems more desirable. 3rd option would be to make all the 'optional cxgbe' files 'optional cxgbe | ccr', which looks a bit odd, but would make this config "work." Short term fix is to add 'device cxgbe' to your configuration if you want ccr.
ccr depends on cxgbe both at link time and at runtime (ccr0 devices are children of the t6nex devices created by 'device cxgbe'). I can add 'device cxgbe' in the synopsis of the manpage though. The manpage does mention the runtime dependency, but it currently only lists 'device ccr'.
A commit references this bug: Author: jhb Date: Mon Jun 3 15:41:55 UTC 2019 New revision: 348542 URL: https://svnweb.freebsd.org/changeset/base/348542 Log: Add 'device cxgbe' explicitly in the synopsis. ccr depends on symbols exported by the cxgbe driver as well as having a runtime dependency. While the runtime depenency was noted in the manpage already, the compile-time dependency wasn't as clear. PR: 238265 MFC after: 3 days Sponsored by: Chelsio Communications Changes: head/share/man/man4/ccr.4
A commit references this bug: Author: jhb Date: Thu Jun 6 20:03:23 UTC 2019 New revision: 348755 URL: https://svnweb.freebsd.org/changeset/base/348755 Log: MFC 348542: Add 'device cxgbe' explicitly in the synopsis. ccr depends on symbols exported by the cxgbe driver as well as having a runtime dependency. While the runtime depenency was noted in the manpage already, the compile-time dependency wasn't as clear. PR: 238265 Changes: _U stable/12/ stable/12/share/man/man4/ccr.4
A commit references this bug: Author: jhb Date: Thu Jun 6 20:03:55 UTC 2019 New revision: 348756 URL: https://svnweb.freebsd.org/changeset/base/348756 Log: MFC 348542: Add 'device cxgbe' explicitly in the synopsis. ccr depends on symbols exported by the cxgbe driver as well as having a runtime dependency. While the runtime depenency was noted in the manpage already, the compile-time dependency wasn't as clear. PR: 238265 Approved by: re (gjb) Changes: _U stable/11/ stable/11/share/man/man4/ccr.4