Discuss

discuss@lists.centos.org

34753 discussions

How to enable EDAC kernel module for checking ECC memory?
by Lists 02 Jul '14

02 Jul '14

In order to support ZFS, we upgraded a backups server with a new, ECC motherboard. We're running CentOS 6 with ZFS on Linux, recently patched. Now, I want to enable EDAC so we can check for memory errors (and maybe PCI errors as well) but so far, repeatedly pounding on the Google hasn't yielded exactly what I need to do to enable EDAC. One howto was covering PCI and edac, but "modprobe edac_mc" didn't work. Here's some information below, How do I get edac up and running? Many howtos cover how to use edac-ctl and edac-util, but none seem to cover how to determine what module to load into the kernel. [root@hume ~]# modprobe edac_mc FATAL: Module edac_mc not found. [root@hume ~]# lsmod | grep edac [root@hume ~]# cat /proc/version Linux version 2.6.32-431.11.2.el6.x86_64 (mockbuild(a)c6b8.bsys.dev.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-4) (GCC) ) #1 SMP Tue Mar 25 19:59:55 UTC 2014 [root@hume ~]# modprobe edac_mce FATAL: Module edac_mce not found. [root@hume ~]# edac-ctl --mainboard edac-ctl: mainboard: Supermicro X9SCL/X9SCM [root@hume ~]# edac-ctl --status edac-ctl: drivers not loaded. [root@hume ~]# lsmod Module Size Used by ext3 240013 1 jbd 80858 1 ext3 nfsd 309196 13 lockd 73662 1 nfsd nfs_acl 2647 1 nfsd auth_rpcgss 44949 1 nfsd sunrpc 262864 20 nfsd,lockd,nfs_acl,auth_rpcgss exportfs 4236 1 nfsd bnx2fc 90539 0 fcoe 23298 0 libfcoe 56791 2 bnx2fc,fcoe 8021q 25349 0 garp 7152 1 8021q stp 2218 1 garp libfc 108670 3 bnx2fc,fcoe,libfcoe llc 5546 2 garp,stp scsi_transport_fc 55299 3 bnx2fc,fcoe,libfc scsi_tgt 12077 1 scsi_transport_fc ipt_REJECT 2351 2 nf_conntrack_ipv4 9506 15 nf_defrag_ipv4 1483 1 nf_conntrack_ipv4 iptable_filter 2793 1 ip_tables 17831 1 iptable_filter ip6t_REJECT 4628 2 nf_conntrack_ipv6 8337 2 nf_defrag_ipv6 11156 1 nf_conntrack_ipv6 xt_state 1492 17 nf_conntrack 79758 3 nf_conntrack_ipv4,nf_conntrack_ipv6,xt_state ip6table_filter 2889 1 ip6_tables 18732 1 ip6table_filter iTCO_wdt 7115 0 iTCO_vendor_support 3056 1 iTCO_wdt zfs 1152935 53 zcommon 44698 1 zfs znvpair 80460 2 zfs,zcommon zavl 6925 1 zfs zunicode 323159 1 zfs spl 260832 5 zfs,zcommon,znvpair,zavl,zunicode zlib_deflate 21629 1 spl i2c_i801 11359 0 i2c_core 31084 1 i2c_i801 ses 6475 0 enclosure 8438 1 ses sg 29350 0 lpc_ich 12803 0 mfd_core 1895 1 lpc_ich shpchp 32778 0 ext4 374902 3 jbd2 93427 1 ext4 mbcache 8193 2 ext3,ext4 raid1 32045 2 usb_storage 49068 5 sd_mod 39069 27 crc_t10dif 1541 1 sd_mod ata_generic 3837 0 pata_acpi 3701 0 pata_jmicron 2813 2 video 20674 0 output 2409 1 video e1000e 267701 0 ptp 9614 1 e1000e pps_core 11458 1 ptp ahci 42247 8 xhci_hcd 148886 0 dm_mirror 14384 0 dm_region_hash 12085 1 dm_mirror dm_log 9930 2 dm_mirror,dm_region_hash dm_mod 84209 2 dm_mirror,dm_log be2iscsi 99578 0 bnx2i 48096 0 cnic 57079 2 bnx2fc,bnx2i uio 10462 1 cnic ipv6 317829 56 ip6t_REJECT,nf_conntrack_ipv6,nf_defrag_ipv6,cnic cxgb4i 28361 0 cxgb4 104882 1 cxgb4i cxgb3i 24491 0 libcxgbi 52202 2 cxgb4i,cxgb3i cxgb3 152922 1 cxgb3i mdio 4769 1 cxgb3 libiscsi_tcp 17020 3 cxgb4i,cxgb3i,libcxgbi qla4xxx 257114 0 iscsi_boot_sysfs 9458 2 be2iscsi,qla4xxx libiscsi 49836 7 be2iscsi,bnx2i,cxgb4i,cxgb3i,libcxgbi,libiscsi_tcp,qla4xxx scsi_transport_iscsi 84241 5 be2iscsi,bnx2i,libcxgbi,qla4xxx,libiscsi [root@hume ~]# rpm -qi edac-utils Name : edac-utils Relocations: (not relocatable) Version : 0.9 Vendor: CentOS Release : 14.el6 Build Date: Wed 20 Jul 2011 11:13:34 AM UTC Install Date: Wed 25 Jun 2014 09:27:40 PM UTC Build Host: c6b6.bsys.dev.centos.org Group : System Environment/Base Source RPM: edac-utils-0.9-14.el6.src.rpm Size : 78637 License: GPLv2+ Signature : RSA/SHA1, Mon 26 Sep 2011 04:17:58 AM UTC, Key ID 0946fca2c105b9de Packager : CentOS BuildSystem <http://bugs.centos.org> URL : http://sourceforge.net/projects/edac-utils/ Summary : Userspace helper for kernel EDAC drivers Description : EDAC is the current set of drivers in the Linux kernel that handle detection of ECC errors from memory controllers for most chipsets on i386 and x86_64 architectures. This userspace component consists of an init script which makes sure EDAC drivers and DIMM labels are loaded at system startup, as well as a library and utility for reporting current error counts from the EDAC sysfs files.

6 9

Re: [CentOS] Now booting - Re: Still won't boot - Re: remote yum update aborted with session closing - won't boot
by Robert Moskowitz 02 Jul '14

02 Jul '14

On 07/02/2014 10:50 AM, Reindl Harald wrote: > > Am 02.07.2014 16:41, schrieb Robert Moskowitz: >> So I made sure that all the packages were reinstalled. I did it step by >> step and did 'yum install' on: >> >> kernel-headers >> glibc-devel >> irqbalance >> mod_perl >> perl-Test-Simple >> redhat-lsb >> >> I then did a reboot and ran down to my NOC in the basement to watch the >> reboot. I did catch a message on the console about rebuilding initrd, >> but I don't see a matching message in /var/log/messages > /var/log/dracut.log Wed Jul 2 10:26:26 EDT 2014 Info: Wrote /boot/initramfs-2.6.32-431.20.3.el6.i686.img Wed Jul 2 10:26:26 EDT 2014 Info: -rw-------. 1 root root 16314559 Jul 2 10:26 /boot/initramfs-2.6.32-431.20.3.el6.i686.img

1 0

Re: [CentOS] Still won't boot - Re: remote yum update aborted with session closing - won't boot
by Robert Moskowitz 02 Jul '14

02 Jul '14

On 07/02/2014 10:33 AM, Reindl Harald wrote: > > Am 02.07.2014 16:31, schrieb Reindl Harald: >> >> Am 02.07.2014 16:27, schrieb Reindl Harald: >>> Am 02.07.2014 16:20, schrieb Robert Moskowitz: >>>> On 07/02/2014 09:35 AM, Reindl Harald wrote: >>>>> Am 02.07.2014 15:19, schrieb Robert Moskowitz: >>>>>> On 07/02/2014 08:41 AM, Reindl Harald wrote: >>>>>>> Am 02.07.2014 14:32, schrieb Robert Moskowitz: >>>>>>>> On 07/01/2014 06:25 PM, Frank Cox wrote: >>>>>>>>> On Tue, 01 Jul 2014 18:19:32 -0400 >>>>>>>>> Robert Moskowitz wrote: >>>>>>>>> >>>>>>>>>> How do I trouble shoot this? I am assuming that I only got a partially >>>>>>>>>> completed update. >>>>>>>>> Try yum-complete-transaction and see what happens. >>>>>>>> Well it looks like all the updates 'took' /etc/redhat-release now >>>>>>>> reports ver 6.5. >>>>>>>> >>>>>>>> But still getting a kernel panic and boot failing. I can fall back to >>>>>>>> the prior kernel and it will boot. So I tried to copy the lines off the >>>>>>>> monitor, as nothing is getting logged: >>>>>>>> >>>>>>>> IOMMU: failed to mpa dmn 0 >>>>>>>> kernel panic - not syncing: VFS: Unable to mount root fs on >>>>>>>> unknown_block (0,0) >>>>>>>> Pid:1, comm swapper Tainted: G -------------} 2.6.32-431.20.3.el6.i686 #1 >>>>>>>> >>>>>>>> then a a number of dump lines. >>>>>>>> >>>>>>>> The kernel that is working (only other one listed in menu) is: >>>>>>>> 2.6.32-279.22.1.el6.i686 >>>>>>> why don' t you just remove any package from the new kernel >>>>>>> which don't work anyways and after that "yum upgrade" again? >>>>>> But how do I determine what package from the new kernel >>>>> i said: and after that "yum upgrade" again man if you remove that >>>>> broken packages a "yum upgrade" pulls them simply as if they where >>>>> never be installed and the rpmscripts will generate a new initrd >>>> OK. So... >>>> >>>> # yum erase kernel* >>>> >>>> Transaction Summary >>>> =========================================================================================================== >>>> Remove 17 Package(s) >>>> >>>> So I am making notes about what is being removed so I can insure that it >>>> gets reinstalled with the upgrade >>> no you remove only the broken kernel and not a blind "+" >>> >>> rpm -qa | grep kernel >>> uname -r >>> >>> yum supports to be specific >>> example: "yum remove kernel-2.6.32-431.20.3.el6.x86_64" >>> >>> the kernel package itself is the one shipping drivers >>> and trigger rebuild of the initrd >>> >>> look that the dependencies is pulling - most likely "kernel-firmware" >>> >>>> Well the upgrade is NOT reinstalling all that was erased >>>> So looks like I will have to do all the others step by step >>> because you asking, then doing and then asking how to proceeed instead >>> consider "hmm remove LSB and GLIBC parts is not a godd idea" >> rpm -e --nodpes \ >> kernel-2.6.32-431.20.3.el6.i686 \ >> kernel-headers-2.6.32-431.20.3.el6.i686 \ >> kernel-firmware-2.6.32-431.20.3.el6.i686 >> >> yum upgrade > boah damned - "rpm -e --nodeps" instead "--nodpes" > > that removes only the named packages *but* be sure the version > is really the non-bootable and in that case the broken > dependencis don't matter, "yum upgrade" will pull the new > kernel again with all it's deps > > that way you avoid to remove the dependency chain, however > you already removed it instead wait for a response after > asking questions > As typical, you are right, Harald. I have a conference call in 15min where one of the discussions will be putting up my Teredo testbed, and this system is what is handy for the Teredo (Miredo) server. So I rushed more than I should have. But I did piece it all together. Now I can pull the rpmforge Miredo code and get that up. Too bad that it is not in EPEL 6; the Miredo maintainer has not commented on why it is not there.

1 0

Re: [CentOS] Still won't boot - Re: remote yum update aborted with session closing - won't boot
by Robert Moskowitz 02 Jul '14

02 Jul '14

On 07/02/2014 09:35 AM, Reindl Harald wrote: > > Am 02.07.2014 15:19, schrieb Robert Moskowitz: >> On 07/02/2014 08:41 AM, Reindl Harald wrote: >>> Am 02.07.2014 14:32, schrieb Robert Moskowitz: >>>> On 07/01/2014 06:25 PM, Frank Cox wrote: >>>>> On Tue, 01 Jul 2014 18:19:32 -0400 >>>>> Robert Moskowitz wrote: >>>>> >>>>>> How do I trouble shoot this? I am assuming that I only got a partially >>>>>> completed update. >>>>> Try yum-complete-transaction and see what happens. >>>> Well it looks like all the updates 'took' /etc/redhat-release now >>>> reports ver 6.5. >>>> >>>> But still getting a kernel panic and boot failing. I can fall back to >>>> the prior kernel and it will boot. So I tried to copy the lines off the >>>> monitor, as nothing is getting logged: >>>> >>>> IOMMU: failed to mpa dmn 0 >>>> kernel panic - not syncing: VFS: Unable to mount root fs on >>>> unknown_block (0,0) >>>> Pid:1, comm swapper Tainted: G -------------} 2.6.32-431.20.3.el6.i686 #1 >>>> >>>> then a a number of dump lines. >>>> >>>> The kernel that is working (only other one listed in menu) is: >>>> 2.6.32-279.22.1.el6.i686 >>> why don' t you just remove any package from the new kernel >>> which don't work anyways and after that "yum upgrade" again? >> But how do I determine what package from the new kernel > i said: and after that "yum upgrade" again man if you remove that > broken packages a "yum upgrade" pulls them simply as if they where > never be installed and the rpmscripts will generate a new initrd OK. So... # yum erase kernel* ... Removing: kernel i686 2.6.32-431.20.3.el6 installed 89 M kernel-firmware noarch 2.6.32-431.20.3.el6 installed 21 M kernel-headers i686 2.6.32-431.20.3.el6 installed 2.5 M Removing for dependencies: glibc-devel i686 2.12-1.132.el6_5.2 installed 953 k glibc-headers i686 2.12-1.132.el6_5.2 installed 2.1 M irqbalance i686 2:1.0.4-9.el6_5 installed 64 k mod_perl i686 2.0.4-11.el6_5 installed 6.0 M perl-ExtUtils-MakeMaker i686 6.55-136.el6 installed 608 k perl-ExtUtils-ParseXS i686 1:2.2003.0-136.el6 installed 61 k perl-Test-Harness i686 3.17-136.el6 installed 399 k perl-Test-Simple i686 0.92-136.el6 installed 184 k perl-devel i686 4:5.10.1-136.el6 installed 1.8 M redhat-lsb i686 4.0-7.el6.centos installed 0.0 redhat-lsb-compat i686 4.0-7.el6.centos installed 0.0 redhat-lsb-core i686 4.0-7.el6.centos installed 22 k redhat-lsb-graphics i686 4.0-7.el6.centos installed 0.0 redhat-lsb-printing i686 4.0-7.el6.centos installed 0.0 Transaction Summary =========================================================================================================== Remove 17 Package(s) So I am making notes about what is being removed so I can insure that it gets reinstalled with the upgrade. thanks for the help.

1 2

remote yum update aborted with session closing - won't boot
by Robert Moskowitz 02 Jul '14

02 Jul '14

I was upgrading a system remotely from Centos 6.3 to 6.5 via VNC. Now the system will not boot. Or at least without bringing up the console and switching to the older kernel. The last messages I see in /var/log/messages are: Jul 1 14:53:51 rigel yum[3220]: Updated: scl-utils-20120927-8.el6.i686 Jul 1 14:53:53 rigel gnome-keyring-daemon[2710]: dbus failure unregistering from session: Connection is closed Jul 1 14:53:53 rigel gnome-keyring-daemon[2710]: dbus failure unregistering from session: Connection is closed Jul 1 14:53:54 rigel gnome-keyring-daemon[2822]: dbus failure unregistering from session: Connection is closed Jul 1 14:53:54 rigel gnome-keyring-daemon[2822]: dbus failure unregistering from session: Connection is closed yum update reports 'No Packages marked for Update'. How do I trouble shoot this? I am assuming that I only got a partially completed update.

5 12

Re: [CentOS] Still won't boot - Re: remote yum update aborted with session closing - won't boot
by Robert Moskowitz 02 Jul '14

02 Jul '14

On 07/02/2014 09:35 AM, Reindl Harald wrote: > > Am 02.07.2014 15:19, schrieb Robert Moskowitz: >> On 07/02/2014 08:41 AM, Reindl Harald wrote: >>> Am 02.07.2014 14:32, schrieb Robert Moskowitz: >>>> On 07/01/2014 06:25 PM, Frank Cox wrote: >>>>> On Tue, 01 Jul 2014 18:19:32 -0400 >>>>> Robert Moskowitz wrote: >>>>> >>>>>> How do I trouble shoot this? I am assuming that I only got a partially >>>>>> completed update. >>>>> Try yum-complete-transaction and see what happens. >>>> Well it looks like all the updates 'took' /etc/redhat-release now >>>> reports ver 6.5. >>>> >>>> But still getting a kernel panic and boot failing. I can fall back to >>>> the prior kernel and it will boot. So I tried to copy the lines off the >>>> monitor, as nothing is getting logged: >>>> >>>> IOMMU: failed to mpa dmn 0 >>>> kernel panic - not syncing: VFS: Unable to mount root fs on >>>> unknown_block (0,0) >>>> Pid:1, comm swapper Tainted: G -------------} 2.6.32-431.20.3.el6.i686 #1 >>>> >>>> then a a number of dump lines. >>>> >>>> The kernel that is working (only other one listed in menu) is: >>>> 2.6.32-279.22.1.el6.i686 >>> why don' t you just remove any package from the new kernel >>> which don't work anyways and after that "yum upgrade" again? >> Always can count on you for good insight, Harald. > that's why i am not allowed to post on this list :-) Why does this not supprise me? > >> But how do I determine what package from the new kernel is not working to erase and reinstall? If I erase it, will >> yum upgrade really fix it? Do I erase the new kernel then install it again? > frankly you asking what i have said and even quote it For you it is clear what 'broken means'. I have the same problem talking secure identities inside my company. It is clear to me, but others just miss the important points. And you get frustrated going back to 'basic principles' and teaching them again.... So thanks for putting up with me, who rarely has to dig into these parts of systems. > >> But how do I determine what package from the new kernel > no idea what is unclear in "remove any package from the new kernel" > which maybe kernel, kernel-headers, kernel-devel..... Ah, perhaps my dyslexia, but I was wondering what drivers or other things I might have to contend with. If it is 'just' kernel* I can deal with that. > >> Do I erase the new kernel then install it again > i said: and after that "yum upgrade" again > > man if you remove that broken packages a "yum upgrade" pulls them simply as if > they where never be installed and the rpmscripts will generate a new initrd > Again, a bit of 'magic' here that 'yum upgrade' knows what should be present and sees to it that these packages get installed. Again, thinking that more than kernel* would need to be removed, then how would it get reinstalled? So off I go try again. The box had been off for a year; it was a DNSSEC tester (I need to replace my router(s), I think to get DNSSEC working right, and that project is on hold). So it was quite back-leveled. If I end up needing to do a reinstall because I stumbled, so be it as a learning lesson.

1 0

Re: [CentOS] Still won't boot - Re: remote yum update aborted with session closing - won't boot
by Robert Moskowitz 02 Jul '14

02 Jul '14

On 07/02/2014 08:41 AM, Reindl Harald wrote: > > Am 02.07.2014 14:32, schrieb Robert Moskowitz: >> On 07/01/2014 06:25 PM, Frank Cox wrote: >>> On Tue, 01 Jul 2014 18:19:32 -0400 >>> Robert Moskowitz wrote: >>> >>>> How do I trouble shoot this? I am assuming that I only got a partially >>>> completed update. >>> Try yum-complete-transaction and see what happens. >> Well it looks like all the updates 'took' /etc/redhat-release now >> reports ver 6.5. >> >> But still getting a kernel panic and boot failing. I can fall back to >> the prior kernel and it will boot. So I tried to copy the lines off the >> monitor, as nothing is getting logged: >> >> IOMMU: failed to mpa dmn 0 >> kernel panic - not syncing: VFS: Unable to mount root fs on >> unknown_block (0,0) >> Pid:1, comm swapper Tainted: G -------------} 2.6.32-431.20.3.el6.i686 #1 >> >> then a a number of dump lines. >> >> The kernel that is working (only other one listed in menu) is: >> 2.6.32-279.22.1.el6.i686 > why don' t you just remove any package from the new kernel > which don't work anyways and after that "yum upgrade" again? Always can count on you for good insight, Harald. But how do I determine what package from the new kernel is not working to erase and reinstall? If I erase it, will yum upgrade really fix it? Do I erase the new kernel then install it again? > > your update was interrupted so the RPM scripts never finished a > nd so no initrd created or the interrupt was in the middle of > create the initrd which is now broken > > that's nothing which can be fixed with just continue the transaction >

1 0

gdb question
by Les Mikesell 01 Jul '14

01 Jul '14

If you are trying to debug a core dump from a different machine, how do you tell gdb where to look for the debug info files to match the shared libs that you have in a non-standard location? It finds the shared libs themselves with a 'set solib-absolute-path' directive, but it doesn't look for the corresponding (relative) usr/lib/debug/... file that you get if you extract the debuginfo rpm in the same place. And if I set debug-file-directory to the top of the tree, it wants to also add the solib-absolute-path to that. Is there some way to make it realize that the top of the tree is the same for both? -- Les Mikesell lesmikesell(a)gmail.com

1 0

Miredo for Centos
by Robert Moskowitz 01 Jul '14

01 Jul '14

Is the Miredo server available for Centos? A quick check of 'yum install miredo*" came up empty. I have miredo for Fedora 20, but I want the server to be Centos... thank you.

5 15

CentOS-announce Digest, Vol 113, Issue 1
by centos-announce-request＠centos.org 01 Jul '14

01 Jul '14

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CEBA-2014:0806 CentOS 6 gnupg2 FASTTRACK Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 30 Jun 2014 12:21:04 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:0806 CentOS 6 gnupg2 FASTTRACK Update To: centos-announce(a)centos.org Message-ID: <20140630122104.GA43196(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:0806 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0806.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: cc899e37a6629404af5e11bc04e9e2b37c822a849d665e37d455b0f82f8dec2f gnupg2-2.0.14-8.el6.i686.rpm 3440468c520bcc8164c90cda156a02fab9ea9203a43897a6d8862c9141253cd6 gnupg2-smime-2.0.14-8.el6.i686.rpm x86_64: 78113fea0eda249fd9c7666228dc73c1dd4af842929c72b692e21646ed0cd9e3 gnupg2-2.0.14-8.el6.x86_64.rpm ee0bb8c5066bfb55269f8318ba40db62650ff03562ab43310ad7f008b3af78d7 gnupg2-smime-2.0.14-8.el6.x86_64.rpm Source: 0022c55626b4cfd32c5616a3509ab2704a336897cd7b01c25a7ba7de9a2fa750 gnupg2-2.0.14-8.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 113, Issue 1 ***********************************************

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss