1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: MRF kernel module, failed to map BARS |
From: | Lucas Russo via Tech-talk <tech-talk at aps.anl.gov> |
To: | GAGET Alexis <alexis.gaget at cea.fr> |
Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Tue, 23 Mar 2021 15:22:42 -0300 |
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" |
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 0Consequence, 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
01 69 08 95 17