similar to: odd mcelogd problem

During booting of Centos6 I see an error message that goes something like: Starting mcelog daemon [FAILED] AMD Processor family 15: Please load edac_mce_amd module. CPU is unsupported The only helpful information I have found is in the "preview" of https://access.redhat.com/knowledge/solutions/158503. I don't have a RedHat account, so

Ok, we've got a new machine that's throwing ECC errors. I've gotten new memory overnighted to me from the manufacturer, and replaced it, oops, not that end of the bank, as their support told me, this end of the bank, as the mobo manual I found online shows (Supermicro). Still throwing errors. Ok, try to get more info.... Last week, I moved /var/log/mcelog to /var/log/mcelog.1, and

I have recently upgraded to 2.6.18-194.3.1.el5 and within several days the machine crashed with the following error (repeating in mcelog): MCE 0 HARDWARE ERROR. This is *NOT* a software problem! Please contact your hardware vendor CPU 2 BANK 8 MISC 41 MCG status: MCi status: Error overflow Uncorrected error MCi_MISC register valid Processor context corrupt MCA: MEMORY CONTROLLER AC_CHANNEL0_ERR

Hi all, After an electric breaking, my server (Centos 5.2 x86_64 with all updates) can not boot. The error message on screen is: ----------------------------------------------------------------------------------------------------------- Memory for crash kernel (0x0 to 0x0) notwithin permissible range <0> HARDWARE ERROR CPU 1: Machine Check Exception: 7 Bank 4: .... RIP 10:<.....>

Hi Konrad, Sometime ago i reported this one at boot up: [ 3009.778974] mcelog:16842 map pfn expected mapping type write-back for [mem 0x0009f000-0x000a0fff], got uncached-minus [ 3009.788570] ------------[ cut here ]------------ [ 3009.798175] WARNING: at arch/x86/mm/pat.c:774 untrack_pfn+0xa1/0xb0() [ 3009.807966] Hardware name: MS-7640 [ 3009.817677] Modules linked in: [ 3009.827524] Pid:

Hello community. We are running, Centos 4.8 on SuperMicro SYS-6026T-3RF with 2xIntel Xeon E5630 and 8xKingston KVR1333D3D4R9S/4G For some time we have lots of MCE in mcelog and we cant find out the reason. "Ordinary" mce message looks like: CPU 51 BANK 8 TSC 8511e3ca77dc MISC 274d587f00006141 ADDR 807044840 STATUS cc0055000001009f MCGSTATUS 0 decode with mcelog --ascii --cpu p4(cause

Is there something odd going on? The question about the errors in mcelog just showed up *again*, and it's the original that I answered this morning. The question about something - was it the md? - original seems as though it's shown up more than twice today, with the same timestamp, I think. Is anyone else seeing this, or is it my host's mailserver? mark

Hello, Today, I got the below error server Console, Cpu 1:machine check exception Tcs c7f3d370acf17a ADDR 112d6c00040288 MISC c453176c00040200 This is not a softeware problem Run through mcelog ascii to decode and contact your hW vendor Kernel panic not syncing :machine check Can anybody please provide the meaning of this. How can I pull the logs from server ? Still not able to

The ARM platform has no concept of PVMMU and therefor no HYPERVISOR_update_va_mapping et al. Allow this code to be compiled out when not required. In some similar situations (e.g. P2M) we have defined dummy functions to avoid this, however I think we can/should draw the line at dummying out actual hypercalls. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> --- arch/x86/xen/Kconfig

On 05/02/17 21:49, H wrote: > On 05/02/2017 08:01 AM, mark wrote: >> On 05/02/17 06:56, Steven Tardy wrote: >>> >>>> On May 1, 2017, at 8:49 PM, H <agents at meddatainc.com> wrote: >>>> >>>> the computer locks up at random intervals >>> >>> Anything in /var/log/mcelog? >>> Is the "edac" module running?

On 05/02/17 06:56, Steven Tardy wrote: > >> On May 1, 2017, at 8:49 PM, H <agents at meddatainc.com> wrote: >> >> the computer locks up at random intervals > > Anything in /var/log/mcelog? > Is the "edac" module running? > Does that model support bundle include any Intel MCA files? systemctl start ipmi ipmitool sel list mark

Hi, today I updated the glibc packages on some CentOS machines. After the Update I checked which services/processes I have to restart "yum -C ps" or "needs-restarting" At the most machines I get no information about necessary restarts, but at two machines a long listing : 1 : /sbin/init 386 : /sbin/udevd-d 659 : /sbin/udevd-d 999 : /usr/sbin/vmtoolsd 1103 : auditd 1128 :

-------------- next part -------------- An embedded message was scrubbed... From: Deon Rodden <drodden@webunited.net> Subject: Re: [Asterisk-Users] Strange Quality problems with Asterisk, Gentoo, Redhat and Kernels - /dev/dsp Date: Thu, 30 Sep 2004 09:05:39 -0400 Size: 5509 Url: http://lists.digium.com/pipermail/asterisk-users/attachments/20040930/289c69cc/dsp.eml

Hi Folks, I see that currently Xen doesn''t export the machine check exceptions to dom0. Is there any plans to export this information to Dom0 (so that it can be read by utilities like mcelog) or is there already some ongoing work on this? Thanks, Sanjay -- ---------------------- PhD Candidate, Georgia Tech http://www.cc.gatech.edu/~ksanjay/

hi, i upgraded my testsystem running on a Dell Optiplex 780 fine for the last five years from Debian 8 to Debian 9. It also crashes on boot, after complaining abount an errer for the mcelog (-16) mounting the root partition (/dev/md0) loading parport driver (?) afterwards my monitor is out of frequency was not able to run further tests right now. best regards Thomas --------------

Prowling around in the system logs this morning I discover the following entries: May 27 09:48:27 vhost01 mcelog: Cannot open logfile /var/log/mcelog: Permission denied May 27 09:48:27 vhost01 mcelog: failed to prefill DIMM database from DMI data May 27 09:48:27 vhost01 mcelog: Cannot bind to client unix socket `/var/run/mcel og-client': Permission denied and later: vhost01 setroubleshoot:

Stephen John Smoogen wrote: > On Wed, 22 May 2019 at 09:30, mark <m.roth at 5-cent.us> wrote: > >> Ok, we used to get this occasionally on cluster nodes, and we just got >> it on a fileserver (very bad). The system is discovered to be >> unresponsive: >> it doesn't ping, and plugging a console in, you can see that it's not >> dead, but there

Unprivileged user can crash kernel by using DRM_IOCTL_NOUVEAU_CHANNEL_ALLOC ioctl. This was reported by trinity[1] fuzzer. [ 71.073906] nouveau 0000:01:00.0: crashme[1329]: channel failed to initialise, -17 [ 71.081730] BUG: kernel NULL pointer dereference, address: 00000000000000a0 [ 71.088928] #PF: supervisor read access in kernel mode [ 71.094059] #PF: error_code(0x0000) - not-present

Hello Everyone, I recently installed CentOS 5.5 x86_64 on a brand new ProLiant DL380 G7. I have identical OS software running reock-solid on two other DL380 ProLiant servers, but they are G6 models, not G7. On the G7, the installation went perfectly and the machine ran great for about 2 weeks, when it just seemed to "stop". The system stopped responding on the network, and there was

been playing with my host machine and thought some might want to see what I have on and the full list of chkconfig I have installed desktop and x windows system to bring up a desktop when I want one with startx. I turned 'off' quite a bit and yum removed quite a bit. These set of programs still allow full use as a host so far, including the startx desktop. Always afraid to remove or