Re: MRF kernel module, failed to map BARS

[Lucas Russo via Tech-talk <tech-talk at aps.anl.gov>]

Hi Alexis,

I have a similar setup (NAT R2 and R9 crates, with NAT COMEX CPUs), CentOS 7 (but with newer kernel: 4.4.128-1.el7.elrepo.x86_64) and I think I remember having similar issues.

I think, If I remember correctly, that the following kernel boot parameters helped with this issue:

GRUB_CMDLINE_LINUX="crashkernel=128M rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet pciehp.pciehp_force=1 pciehp.pciehp_debug=1 pcie_ports=native pci=realloc,noaer"

Particularly the pci/pcie options helped with the hot-plugging support.

Maybe this will help,

Cheers,

Lucas

On Tue, Mar 23, 2021 at 12:35 PM GAGET Alexis via Tech-talk <tech-talk at aps.anl.gov> wrote:

Dear All,

Here at saclay we are using MRF timing system with MTCA.4 in R2 NAT crate.

I’m using the COMex-E3 and a MCH-PHYS80. The IOC using the mrfioc2 driver is running on the Comex and the mrf kernel module is loaded on it. I have forked from ESS version of mrfioc2, and the kernel module I built seems the same.

My kernel version is : 3.10.0-1160.15.2.el7.x86_64 on a CenTOS Linux 7.9.2009

It works globally very well, but I have a reproducible issue:

When I reboot the whole R2 crate and when I load the MRF kernel module I have the following message :

 [  347.344081] mrf: module verification failed: signature and/or required key missing - tainting kernel
[  347.345504] mrf-pci 0000:04:00.0: Attaching MRF device w/o PLX bridge (00007011)
[  347.345581] mrf-pci 0000:04:00.0: can't ioremap BAR 0: [??? 0x00000000 flags 0x0]
[  347.345646] mrf-pci 0000:04:00.0: Failed to map BARS! 0 0
[  347.345918] mrf-pci 0000:06:00.0: Attaching MRF device w/o PLX bridge (00007011)
[  347.345989] mrf-pci 0000:06:00.0: can't ioremap BAR 0: [??? 0x00000000 flags 0x0]
[  347.346053] mrf-pci 0000:06:00.0: Failed to map BARS! 0 0

Consequence, my Comex can’t find some of my EVR or EVM (some are found..).

To make it work I just have to reboot the Comex and after that it’s working. Meaning after a shutdown I have to reboot it twice…

Does anyone have this kind of trouble ? Knows how to solve it ? or even understand this message ?

Thanks for your consideration

Alexis GAGET

CEA Saclay - DRF/Irfu/DIS/LDISC

Bâtiment 472 – pièce 105

alexis.gaget at cea.fr

01 69 08 95 17