You are not logged in.
Pages: 1
I tried blacklisting the module and adding in the grub command to blacklist.
Is there another way or something else to get this not to load as it makes my boot time take another 60 seconds while it times out.
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=4f97b57c-00fb-4f6f-a80f-e62047d007c8 rw module_blacklist=nvme
[ 0.175230] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=4f97b57c-00fb-4f6f-a80f-e62047d007c8 rw module_blacklist=nvme
[ 0.979422] nvme nvme0: pci function 0000:02:00.0
[ 61.297289] nvme nvme0: I/O 8 QID 0 timeout, disable controller
[ 61.404325] nvme nvme0: Identify Controller failed (-4)
[ 61.404353] nvme nvme0: Removing after probe failure status: -5
Offline
That was my first try as I forgot to include that as well. When that didn't work, I moved on to grub to try to catch it earlier.
[root@gemini modprobe.d]# cat blacklist.conf
blacklist nvme
[root@gemini modprobe.d]# mkinitcpio -v | grep nvme
[root@gemini modprobe.d]#
[root@gemini modprobe.d]# mkinitcpio -M | grep nvme
[root@gemini modprobe.d]#
I also tried the false method as well:
cat /etc/modprobe.d/blacklist.conf
install nvme /bin/false
Last edited by Animosity022 (2019-04-22 12:49:20)
Offline
nvme is not built as a module so can not be blacklisted.
Offline
I don't know why you want to blacklist it, but you can try your own kernel and set the kernel config stuff to n under the NVME support.
#
# NVME Support
#
CONFIG_NVME_CORE=y
CONFIG_BLK_DEV_NVME=y
CONFIG_NVME_MULTIPATH=y
CONFIG_NVME_FABRICS=m
CONFIG_NVME_RDMA=m
CONFIG_NVME_FC=m
CONFIG_NVME_TCP=m
CONFIG_NVME_TARGET=m
CONFIG_NVME_TARGET_LOOP=m
CONFIG_NVME_TARGET_RDMA=m
CONFIG_NVME_TARGET_FC=m
CONFIG_NVME_TARGET_FCLOOP=m
CONFIG_NVME_TARGET_TCP=m
Offline
If there is another way to disable as I don’t use it and it adds a 60 second lock up to my boot process, please let me know.
There are no options in the bios to turn off that specifically without turning off all the onboard Sata.
Offline
The 60 second timeout matches the default for admin_timeout so I would suggest nvme.admin_timeout=0
If that fails vfio-pci.ids=VID:PID to assign the device to the vfio-pci instead of the nvme.
Offline
Ok. I’ll give that a try. Is that timeout a module option or sysctl.conf change?
Last edited by Animosity022 (2019-04-22 15:36:45)
Offline
module option
Edit:
https://github.com/torvalds/linux/blob/ … core.c#L40
Last edited by loqs (2019-04-22 15:40:34)
Offline
So if it isn't compiled as a module and not loaded that way, it doesn't seem to take into account of those changes.
I tried making it 0 and 5 for a test and rebooted and it still takes 60 seconds to timeout:
cat /etc/modprobe.d/nvme.conf
nvme.admin_timeout=5
I'm going take a look at turning it off via the custom kernel.
Offline
cat /etc/modprobe.d/nvme.conf nvme.admin_timeout=5
Module options are not applied in the same way as sysctl variables.
Try this instead:
# /etc/modprobe.d/nvme.conf
options nvme admin-timeout=5
Offline
No dice even with that:
[ 0.964620] nvme nvme0: pci function 0000:02:00.0
[ 61.299497] nvme nvme0: I/O 28 QID 0 timeout, disable controller
[ 61.406517] nvme nvme0: Identify Controller failed (-4)
[ 61.406543] nvme nvme0: Removing after probe failure status: -5
[root@gemini ~]# cat /etc/modprobe.d/nvme.conf
options nvme admin-timeout=5
Offline
Sorry, yes, it's not a module so modprobe.d won't work. That was silly of me.
Is there an NVMe option in sysctl?
Offline
I checked via this:
[root@gemini ~]# sysctl -a | grep -i nvme
[root@gemini ~]#
so I don't see any. I am just about done making a kernel and I turned it off that way but that's a long way around the issue.
Offline
I just ended up with a very simple approach of using grub and blacklisting the call to initialize it since it is a driver and not a module as that makes things very easy.
GRUB_CMDLINE_LINUX_DEFAULT="initcall_blacklist=nvme_init"
and the boot
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=4f97b57c-00fb-4f6f-a80f-e62047d007c8 rw initcall_blacklist=nvme_init
[ 0.175118] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=4f97b57c-00fb-4f6f-a80f-e62047d007c8 rw initcall_blacklist=nvme_init
[ 0.175137] blacklisting initcall nvme_init
[ 0.962603] initcall nvme_init blacklisted
Last edited by Animosity022 (2019-04-22 18:09:02)
Offline
Pages: 1