similar to: New kernel causes hardware error?

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

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

Hello, While working on a fix for the rare-but-possible problem of reentrant NMIs and MCEs, I have discovered that it is sadly possible to generate fake NMIs and MCEs which will run the relevant handlers on the relevant stacks, without invoking any of the other CPU logic for these special interrupts. A fake NMI can be generated by a processor in PIC mode as opposed to Virtual wire mode, with a

Dump mce log by ERST when mc panic We have implemented basic ERST logic before. Now linux3.0 as dom0 has included APEI logic. Hence it''s time to add mce apei interface and enable APEI ERST feature. With it, it can save mce log by ERST method when mc panic. Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com> diff -r ca2f58c2dfea xen/arch/x86/cpu/mcheck/mce.c ---

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:<.....>

Intercept guest reads of MSR_IA32_MCG_CAP and limit the number of memory banks reported to one. This prevents us from trying to read status of non-existent banks when migrated to a machine with fewer banks. Signed-off-by: Ben Guthro Signed-off-by: David Lively <dlively@virtualiron.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

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, every few hours I get the following message in /var/log/message: Jul 5 20:23:28 hXXX kernel: Machine check events logged Jul 5 20:53:28 hXXX kernel: Machine check events logged Jul 5 22:13:28 hXXX kernel: Machine check events logged Jul 5 23:53:28 hXXX kernel: Machine check events logged Jul 5 23:58:27 hXXX kernel: Machine check events logged Jul 6 01:38:27 hXXX kernel: Machine

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

CentOS 6.4, 2.6.32-358.11.1.el6.x86_64 (And no, I can't just upgrade - the users have to be sure that the computational results will be correct....) It's throwing ECC errors. Trying to start mcelogd, first it said nothing. Restart told me "Please load edac_mce_amd module." I did a modprobe edac_mce_amd, and lsmod tells me it's in. But now service mcelogd restart Stopping

On my new Haswell-based machines, I am occasionally seeing entries like the following in /var/log/messages: kernel: [Hardware Error]: Machine check events logged (I would not have even noticed them, except that they get flagged by logwatch.) These messages always occur alone, and don't seem to have a corresponding entry in any other log file in /var/log. How can I get more info about these

I am running the latest updated version of CentOS on a HP DL160 G6 server as a workstation with the Mate desktop, not Gnome. The only expansion card I have installed is a MSI Geforce GT710 graphics card driving two monitors. Unfortunately the computer locks up at random intervals: neither the mouse nor the keyboard work and I lose the SSH connection to the computer I have used to see if the

Dear list, I''m running Debian Lenny with xen build from source completely. After upgrading xen to 4 with 2.6.32.12 kernel any paravirtualized domU hangs and after some minutes it breaks with: Error: Device 0 (vif) could not be connected. Hotplug scripts not working. There isn''t any log entry regarding this error. When I switch back to 3.4.2 with 2.6.18 kernel anything boots

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?

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

On 11/16/2020 01:23 PM, Jonathan Billings wrote: > On Sun, Nov 15, 2020 at 07:49:09PM -0500, H wrote: >> I have been having some problems with hardware RAID 1 on the >> motherboard that I am running CentOS 7 on. After a BIOS upgrade of >> the system, I lost the RAID 1 setup and was no longer able to boot >> the system. > The Intel RST RAID (aka Intel Matrix RAID) is

Hello all I am running CentOS 5 on a small server and I am having very strange memory malfunctions. The computer runs perfectly with no problems whatsoever. From time to time, after a soft reboot, the computer emmits beeps corresponding to a memory fault. It never reboots again until I find and remove a now defective DIMM. That DIMM can never be used again because it is out of order. This just

David Hildenbrand <david at redhat.com> writes: > On 30.04.20 17:38, Eric W. Biederman wrote: >> David Hildenbrand <david at redhat.com> writes: >> >>> Some devices/drivers that add memory via add_memory() and friends (e.g., >>> dax/kmem, but also virtio-mem in the future) don't want to create entries >>> in /sys/firmware/memmap/ -

David Hildenbrand <david at redhat.com> writes: > On 30.04.20 17:38, Eric W. Biederman wrote: >> David Hildenbrand <david at redhat.com> writes: >> >>> Some devices/drivers that add memory via add_memory() and friends (e.g., >>> dax/kmem, but also virtio-mem in the future) don't want to create entries >>> in /sys/firmware/memmap/ -

Hi, I've done my fair share of CentOS 7 installations, but this is the first time I have this kind of weird problem. Here goes. In my office I have a battered Dell Optiplex 320 PC with two NICs that I'm using as a bare metal sandbox server for testing purposes. The CentOS 7 installer sees the connected network card as eth0. But after the first reboot, the interface comes up as eth1.