EDAC sbridge: couldn't find mci handler

Issues related to applications and software problems
Post Reply
alpha754293
Posts: 69
Joined: 2019/07/29 16:15:14

EDAC sbridge: couldn't find mci handler

Post by alpha754293 » 2019/09/05 20:15:58

Here is my system specs:

Asus P9X79-E WS
Intel Core i7-4930K
8x Crucial 8 GB Ballstix DDR3-1600 Non-ECC, unbuffered RAM
EVGA GTX Titan
Intel 535s Series 240 GB SATA 6 Gbps SSD (on SATA 6 Gbps from Intel X79 chipset)
4x Samsung 860 Evo 1 TB SATA 6 Gbps SSD (on RAID0 on Marvell 9230 RAID controller)
2x HGST 6TB 7200 rpm HDD SATA 6 Gbps (on SATA 3 Gbps, RAID0 from Intel X79 chipset)

I am running a fresh install of CentOS 7.6.1810.

Here is the error message that I am getting from journalctl -xb:

Code: Select all

Sep 05 14:39:57 aes0 kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Sep 05 14:39:57 aes0 kernel: EDAC sbridge: Couldn't find mci handler
Sep 05 14:39:57 aes0 kernel: EDAC sbridge: Failed to register device with error -19.
I've already disabled SElinux, and installed the nVidia driver.

The El-Repo kmod-nvidia driver failed to install due to a dependency issue and I didn't want to force the install.

Nouveau has also already been blacklisted.

I ran memtest and it successfully completed 5 passes, so there is nothing coming up from that.

If anybody can help me figure out why I am getting this error, that would be greatly appreciated.

(I ran the steps above after trying to google the issue for quite some time and implemented those solutions in an attempt to try and fix this and the error message is still occurring, so I am at a bit of a loss as to why this is still happening.)

Thank you.

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: EDAC sbridge: couldn't find mci handler

Post by TrevorH » 2019/09/05 20:21:03

I've already disabled SElinux, and installed the nVidia driver.
Please don't disable selinux.
The El-Repo kmod-nvidia driver failed to install due to a dependency issue and I didn't want to force the install.
We recommend using the ELRepo packages for a good reason :they work. All you needed to do was to also yum install yum-plugin-elrepo and it would have sorted this problem out for you. Or enable the CR repo and get advanced access to 7.7. The problem is that the current kmod-nvidia from ELRepo depends on the 7.7 kernel which is not GA for CentOS as yet (but is in CR).
Sep 05 14:39:57 aes0 kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
The EDAC driver is for machines with ECC RAM and you don't have any so it will nto load or do anything.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

alpha754293
Posts: 69
Joined: 2019/07/29 16:15:14

Re: EDAC sbridge: couldn't find mci handler

Post by alpha754293 » 2019/09/06 00:28:19

TrevorH wrote:
2019/09/05 20:21:03
I've already disabled SElinux, and installed the nVidia driver.
Please don't disable selinux.
The El-Repo kmod-nvidia driver failed to install due to a dependency issue and I didn't want to force the install.
We recommend using the ELRepo packages for a good reason :they work. All you needed to do was to also yum install yum-plugin-elrepo and it would have sorted this problem out for you. Or enable the CR repo and get advanced access to 7.7. The problem is that the current kmod-nvidia from ELRepo depends on the 7.7 kernel which is not GA for CentOS as yet (but is in CR).
Sep 05 14:39:57 aes0 kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
The EDAC driver is for machines with ECC RAM and you don't have any so it will nto load or do anything.
@TrevorH

Thank you.

Yeah, I just followed the instructions that was on the el repo page (copy-and-paste).

Can I blacklist the EDAC driver then since I don't haven't ECC RAM?

It's causing the system to go into emergency maintenance mode (where I would either enter the root password or press control+D to bypass) and I would prefer if either there is a way for me to set the system so that it will automatically bypass it with each reboot or that I disable/blacklist the EDAC driver.

Thank you.

alpha754293
Posts: 69
Joined: 2019/07/29 16:15:14

Re: EDAC sbridge: couldn't find mci handler

Post by alpha754293 » 2019/09/06 01:27:18

Code: Select all

# lsmod | grep edac
and

Code: Select all

# lspci | grep edac
Both returned nothing.

So I blacklisted all of the *edac* modules I can find that were installed on my system by editing /etc/modprobe.d/blacklist.conf, and then using dracut to update the boot image and that seem to have taken care of that specific error message.

The other thing that apparently was causing my system to go into emergency mode was one of the HGST 6 TB drives had bad sectors on it, so that was stopping the system.

I tried disabling SMART to bypass that (because it wasn't really that important to me), but that didn't work, so I've just removed the drive from /etc/fstab and physically unplugged them until I can get replacement drives in so that the system would stop going into emergency mode.

Thanks.

alpha754293
Posts: 69
Joined: 2019/07/29 16:15:14

Re: EDAC sbridge: couldn't find mci handler

Post by alpha754293 » 2019/09/06 01:48:44

Turns out that it was the hard drive failure that was sending the system into emergency mode, and not because of the EDAC.

Thank you.

Post Reply