Machine check events loggedExt2-fs error which crops up monthly or sometimes weeklyApparent IRQ conflict driving me nuts under CentOSProblem with NFS server lockd timing out on Debian linuxLinux networking crash: best steps to find out the cause?Debian Squeeze and exim4: cannot send mailXen connect to dom0 with vnc?Determining Cause of System RebootBusy Debian server (Xen guest) seems to go to sleep (energy saving mode)How to get notified of mdadm RAID problems?spontaneous reboot, machine check events, AMD ryzen

Can a wire having a 610-670 THz (frequency of blue light) AC frequency supply, generate blue light?

Do firearms count as ranged weapons?

Draw a checker pattern with a black X in the center

Question about exercise 11.5 in TeXbook

Could I be denied entry into Ireland due to medical and police situations during a previous UK visit?

How feasible is the Delta-Glider?

How to extract lower and upper bound in numeric format from a confidence interval string?

I think I may have violated academic integrity last year - what should I do?

Were pen cap holes designed to prevent death by suffocation if swallowed?

How to properly maintain eye contact with people that have distinct facial features?

Leading and Suffering Numbers

Different PCB color ( is it different material? )

Where did the “Vikings wear helmets with horn” stereotype come from and why?

What does the behaviour of water on the skin of an aircraft in flight tell us?

Is it ok to put a subplot to a story that is never meant to contribute to the development of the main plot?

Can the Help action be used to give advantage to a specific ally's attack (rather than just the next ally who attacks the target)?

How to prevent bad sectors?

What's the connection between "kicking a pigeon" and "how a bill becomes a law"?

Is this story about US tax office reasonable?

Uses of T extends U?

Why are huge challot displayed on the wedding couple / Bar Mitzvah's table?

Is it possible to change original filename of an exe?

Is there any use case for the bottom type as a function parameter type?

What problems does SciDraw still solve?



Machine check events logged


Ext2-fs error which crops up monthly or sometimes weeklyApparent IRQ conflict driving me nuts under CentOSProblem with NFS server lockd timing out on Debian linuxLinux networking crash: best steps to find out the cause?Debian Squeeze and exim4: cannot send mailXen connect to dom0 with vnc?Determining Cause of System RebootBusy Debian server (Xen guest) seems to go to sleep (energy saving mode)How to get notified of mdadm RAID problems?spontaneous reboot, machine check events, AMD ryzen






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








2















In /var/log/messages, this error occurred:



Sep 19 13:18:15 wdc kernel: [2772302.630416] Machine check events logged


Shortly there after, the entire server became unresponsive. This is in the log of the Dom0 for a Xen Server (running the latest version on Debian Squeeze).



Can anyone shed some light on what this error means? Should I be ordering new hardware?



Edit: Also, it seems to imply it logged something, where can I find that?










share|improve this question






























    2















    In /var/log/messages, this error occurred:



    Sep 19 13:18:15 wdc kernel: [2772302.630416] Machine check events logged


    Shortly there after, the entire server became unresponsive. This is in the log of the Dom0 for a Xen Server (running the latest version on Debian Squeeze).



    Can anyone shed some light on what this error means? Should I be ordering new hardware?



    Edit: Also, it seems to imply it logged something, where can I find that?










    share|improve this question


























      2












      2








      2








      In /var/log/messages, this error occurred:



      Sep 19 13:18:15 wdc kernel: [2772302.630416] Machine check events logged


      Shortly there after, the entire server became unresponsive. This is in the log of the Dom0 for a Xen Server (running the latest version on Debian Squeeze).



      Can anyone shed some light on what this error means? Should I be ordering new hardware?



      Edit: Also, it seems to imply it logged something, where can I find that?










      share|improve this question
















      In /var/log/messages, this error occurred:



      Sep 19 13:18:15 wdc kernel: [2772302.630416] Machine check events logged


      Shortly there after, the entire server became unresponsive. This is in the log of the Dom0 for a Xen Server (running the latest version on Debian Squeeze).



      Can anyone shed some light on what this error means? Should I be ordering new hardware?



      Edit: Also, it seems to imply it logged something, where can I find that?







      linux debian xen






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Sep 20 '12 at 2:55









      quanta

      43.6k15114196




      43.6k15114196










      asked Sep 19 '12 at 19:43









      GoldenNewbyGoldenNewby

      75212




      75212




















          3 Answers
          3






          active

          oldest

          votes


















          7














          For more information check logfile (this log file might be there or might not be, it depends how it is configured in /etc/mcelog/mcelog.conf) where should be detail description of the problem found.



          /var/log/mcelog


          or just run command



          mcelog




          Mcelog is decoding kernel machine check log on x86 machines. From man mcelog:



          X86 CPUs report errors detected by the CPU as machine check events (MCEs). These
          can be data corruption detected in the CPU caches, in main memory by an integrated
          memory controller, data transfer errors on the front side bus or CPU interconnect or
          other internal errors. Possible causes can be cosmic radiation, instable power
          supplies, cooling problems, broken hardware, or bad luck.
          Most errors can be corrected by the CPU by internal error correction mechanisms.
          Uncorrected errors cause machine check exceptions which may panic the machine.
          When a corrected error happens the x86 kernel writes a record describing the MCE into
          a internal ring buffer available through the /dev/mcelog device mcelog retrieves
          errors from /dev/mcelog, decodes them into a human readable format and prints them on
          the standard output or optionally into the system log.




          You can find more information about mcelog and its configuration/errors/triggers on the project webpage Mcelog project webpage






          share|improve this answer
































            1














            mcelog was removed in Debian 10+ (Buster) and Ubuntu 18.04+



            The functionality has been replaced by rasdaemon.






            share|improve this answer























            • Question asked in 6 years back

              – serverAdmin123
              May 15 at 8:39







            • 1





              And search results live forever ;-) Good to shortcut technical mazes.

              – Firefishy
              May 15 at 8:42


















            0














            The log entries were written by mcelog. Its logfile can be found in /var/log/mcelog, or depending on the system, additionally in syslog or the systemd journal.



            X86 CPUs have the ability to detect and sometimes correct hardware errors (memory, IO, and CPU hardware errors). mcelog retrieves these errors from /dev/mcelog, where the Linux kernel writes then.



            As your system crashed, correction of the hardware likely failed. If the system keeps running, auto-correction seems to be working.



            For more background about the implications of seeing such messages, refer to “mce: [Hardware Error]: Machine check events logged” appears in syslog. What should I do?






            share|improve this answer























              Your Answer








              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "2"
              ;
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function()
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled)
              StackExchange.using("snippets", function()
              createEditor();
              );

              else
              createEditor();

              );

              function createEditor()
              StackExchange.prepareEditor(
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader:
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              ,
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );













              draft saved

              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f430005%2fmachine-check-events-logged%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              3 Answers
              3






              active

              oldest

              votes








              3 Answers
              3






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              7














              For more information check logfile (this log file might be there or might not be, it depends how it is configured in /etc/mcelog/mcelog.conf) where should be detail description of the problem found.



              /var/log/mcelog


              or just run command



              mcelog




              Mcelog is decoding kernel machine check log on x86 machines. From man mcelog:



              X86 CPUs report errors detected by the CPU as machine check events (MCEs). These
              can be data corruption detected in the CPU caches, in main memory by an integrated
              memory controller, data transfer errors on the front side bus or CPU interconnect or
              other internal errors. Possible causes can be cosmic radiation, instable power
              supplies, cooling problems, broken hardware, or bad luck.
              Most errors can be corrected by the CPU by internal error correction mechanisms.
              Uncorrected errors cause machine check exceptions which may panic the machine.
              When a corrected error happens the x86 kernel writes a record describing the MCE into
              a internal ring buffer available through the /dev/mcelog device mcelog retrieves
              errors from /dev/mcelog, decodes them into a human readable format and prints them on
              the standard output or optionally into the system log.




              You can find more information about mcelog and its configuration/errors/triggers on the project webpage Mcelog project webpage






              share|improve this answer





























                7














                For more information check logfile (this log file might be there or might not be, it depends how it is configured in /etc/mcelog/mcelog.conf) where should be detail description of the problem found.



                /var/log/mcelog


                or just run command



                mcelog




                Mcelog is decoding kernel machine check log on x86 machines. From man mcelog:



                X86 CPUs report errors detected by the CPU as machine check events (MCEs). These
                can be data corruption detected in the CPU caches, in main memory by an integrated
                memory controller, data transfer errors on the front side bus or CPU interconnect or
                other internal errors. Possible causes can be cosmic radiation, instable power
                supplies, cooling problems, broken hardware, or bad luck.
                Most errors can be corrected by the CPU by internal error correction mechanisms.
                Uncorrected errors cause machine check exceptions which may panic the machine.
                When a corrected error happens the x86 kernel writes a record describing the MCE into
                a internal ring buffer available through the /dev/mcelog device mcelog retrieves
                errors from /dev/mcelog, decodes them into a human readable format and prints them on
                the standard output or optionally into the system log.




                You can find more information about mcelog and its configuration/errors/triggers on the project webpage Mcelog project webpage






                share|improve this answer



























                  7












                  7








                  7







                  For more information check logfile (this log file might be there or might not be, it depends how it is configured in /etc/mcelog/mcelog.conf) where should be detail description of the problem found.



                  /var/log/mcelog


                  or just run command



                  mcelog




                  Mcelog is decoding kernel machine check log on x86 machines. From man mcelog:



                  X86 CPUs report errors detected by the CPU as machine check events (MCEs). These
                  can be data corruption detected in the CPU caches, in main memory by an integrated
                  memory controller, data transfer errors on the front side bus or CPU interconnect or
                  other internal errors. Possible causes can be cosmic radiation, instable power
                  supplies, cooling problems, broken hardware, or bad luck.
                  Most errors can be corrected by the CPU by internal error correction mechanisms.
                  Uncorrected errors cause machine check exceptions which may panic the machine.
                  When a corrected error happens the x86 kernel writes a record describing the MCE into
                  a internal ring buffer available through the /dev/mcelog device mcelog retrieves
                  errors from /dev/mcelog, decodes them into a human readable format and prints them on
                  the standard output or optionally into the system log.




                  You can find more information about mcelog and its configuration/errors/triggers on the project webpage Mcelog project webpage






                  share|improve this answer















                  For more information check logfile (this log file might be there or might not be, it depends how it is configured in /etc/mcelog/mcelog.conf) where should be detail description of the problem found.



                  /var/log/mcelog


                  or just run command



                  mcelog




                  Mcelog is decoding kernel machine check log on x86 machines. From man mcelog:



                  X86 CPUs report errors detected by the CPU as machine check events (MCEs). These
                  can be data corruption detected in the CPU caches, in main memory by an integrated
                  memory controller, data transfer errors on the front side bus or CPU interconnect or
                  other internal errors. Possible causes can be cosmic radiation, instable power
                  supplies, cooling problems, broken hardware, or bad luck.
                  Most errors can be corrected by the CPU by internal error correction mechanisms.
                  Uncorrected errors cause machine check exceptions which may panic the machine.
                  When a corrected error happens the x86 kernel writes a record describing the MCE into
                  a internal ring buffer available through the /dev/mcelog device mcelog retrieves
                  errors from /dev/mcelog, decodes them into a human readable format and prints them on
                  the standard output or optionally into the system log.




                  You can find more information about mcelog and its configuration/errors/triggers on the project webpage Mcelog project webpage







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Sep 19 '12 at 20:12

























                  answered Sep 19 '12 at 20:05









                  panaroikpanaroik

                  762412




                  762412























                      1














                      mcelog was removed in Debian 10+ (Buster) and Ubuntu 18.04+



                      The functionality has been replaced by rasdaemon.






                      share|improve this answer























                      • Question asked in 6 years back

                        – serverAdmin123
                        May 15 at 8:39







                      • 1





                        And search results live forever ;-) Good to shortcut technical mazes.

                        – Firefishy
                        May 15 at 8:42















                      1














                      mcelog was removed in Debian 10+ (Buster) and Ubuntu 18.04+



                      The functionality has been replaced by rasdaemon.






                      share|improve this answer























                      • Question asked in 6 years back

                        – serverAdmin123
                        May 15 at 8:39







                      • 1





                        And search results live forever ;-) Good to shortcut technical mazes.

                        – Firefishy
                        May 15 at 8:42













                      1












                      1








                      1







                      mcelog was removed in Debian 10+ (Buster) and Ubuntu 18.04+



                      The functionality has been replaced by rasdaemon.






                      share|improve this answer













                      mcelog was removed in Debian 10+ (Buster) and Ubuntu 18.04+



                      The functionality has been replaced by rasdaemon.







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered May 15 at 8:36









                      FirefishyFirefishy

                      362




                      362












                      • Question asked in 6 years back

                        – serverAdmin123
                        May 15 at 8:39







                      • 1





                        And search results live forever ;-) Good to shortcut technical mazes.

                        – Firefishy
                        May 15 at 8:42

















                      • Question asked in 6 years back

                        – serverAdmin123
                        May 15 at 8:39







                      • 1





                        And search results live forever ;-) Good to shortcut technical mazes.

                        – Firefishy
                        May 15 at 8:42
















                      Question asked in 6 years back

                      – serverAdmin123
                      May 15 at 8:39






                      Question asked in 6 years back

                      – serverAdmin123
                      May 15 at 8:39





                      1




                      1





                      And search results live forever ;-) Good to shortcut technical mazes.

                      – Firefishy
                      May 15 at 8:42





                      And search results live forever ;-) Good to shortcut technical mazes.

                      – Firefishy
                      May 15 at 8:42











                      0














                      The log entries were written by mcelog. Its logfile can be found in /var/log/mcelog, or depending on the system, additionally in syslog or the systemd journal.



                      X86 CPUs have the ability to detect and sometimes correct hardware errors (memory, IO, and CPU hardware errors). mcelog retrieves these errors from /dev/mcelog, where the Linux kernel writes then.



                      As your system crashed, correction of the hardware likely failed. If the system keeps running, auto-correction seems to be working.



                      For more background about the implications of seeing such messages, refer to “mce: [Hardware Error]: Machine check events logged” appears in syslog. What should I do?






                      share|improve this answer



























                        0














                        The log entries were written by mcelog. Its logfile can be found in /var/log/mcelog, or depending on the system, additionally in syslog or the systemd journal.



                        X86 CPUs have the ability to detect and sometimes correct hardware errors (memory, IO, and CPU hardware errors). mcelog retrieves these errors from /dev/mcelog, where the Linux kernel writes then.



                        As your system crashed, correction of the hardware likely failed. If the system keeps running, auto-correction seems to be working.



                        For more background about the implications of seeing such messages, refer to “mce: [Hardware Error]: Machine check events logged” appears in syslog. What should I do?






                        share|improve this answer

























                          0












                          0








                          0







                          The log entries were written by mcelog. Its logfile can be found in /var/log/mcelog, or depending on the system, additionally in syslog or the systemd journal.



                          X86 CPUs have the ability to detect and sometimes correct hardware errors (memory, IO, and CPU hardware errors). mcelog retrieves these errors from /dev/mcelog, where the Linux kernel writes then.



                          As your system crashed, correction of the hardware likely failed. If the system keeps running, auto-correction seems to be working.



                          For more background about the implications of seeing such messages, refer to “mce: [Hardware Error]: Machine check events logged” appears in syslog. What should I do?






                          share|improve this answer













                          The log entries were written by mcelog. Its logfile can be found in /var/log/mcelog, or depending on the system, additionally in syslog or the systemd journal.



                          X86 CPUs have the ability to detect and sometimes correct hardware errors (memory, IO, and CPU hardware errors). mcelog retrieves these errors from /dev/mcelog, where the Linux kernel writes then.



                          As your system crashed, correction of the hardware likely failed. If the system keeps running, auto-correction seems to be working.



                          For more background about the implications of seeing such messages, refer to “mce: [Hardware Error]: Machine check events logged” appears in syslog. What should I do?







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Aug 14 '17 at 11:05









                          Philipp ClaßenPhilipp Claßen

                          221416




                          221416



























                              draft saved

                              draft discarded
















































                              Thanks for contributing an answer to Server Fault!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid


                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.

                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f430005%2fmachine-check-events-logged%23new-answer', 'question_page');

                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              Club Baloncesto Breogán Índice Historia | Pavillón | Nome | O Breogán na cultura popular | Xogadores | Adestradores | Presidentes | Palmarés | Historial | Líderes | Notas | Véxase tamén | Menú de navegacióncbbreogan.galCadroGuía oficial da ACB 2009-10, páxina 201Guía oficial ACB 1992, páxina 183. Editorial DB.É de 6.500 espectadores sentados axeitándose á última normativa"Estudiantes Junior, entre as mellores canteiras"o orixinalHemeroteca El Mundo Deportivo, 16 setembro de 1970, páxina 12Historia do BreogánAlfredo Pérez, o último canoneiroHistoria C.B. BreogánHemeroteca de El Mundo DeportivoJimmy Wright, norteamericano do Breogán deixará Lugo por ameazas de morteResultados de Breogán en 1986-87Resultados de Breogán en 1990-91Ficha de Velimir Perasović en acb.comResultados de Breogán en 1994-95Breogán arrasa al Barça. "El Mundo Deportivo", 27 de setembro de 1999, páxina 58CB Breogán - FC BarcelonaA FEB invita a participar nunha nova Liga EuropeaCharlie Bell na prensa estatalMáximos anotadores 2005Tempada 2005-06 : Tódolos Xogadores da Xornada""Non quero pensar nunha man negra, mais pregúntome que está a pasar""o orixinalRaúl López, orgulloso dos xogadores, presume da boa saúde económica do BreogánJulio González confirma que cesa como presidente del BreogánHomenaxe a Lisardo GómezA tempada do rexurdimento celesteEntrevista a Lisardo GómezEl COB dinamita el Pazo para forzar el quinto (69-73)Cafés Candelas, patrocinador del CB Breogán"Suso Lázare, novo presidente do Breogán"o orixinalCafés Candelas Breogán firma el mayor triunfo de la historiaEl Breogán realizará 17 homenajes por su cincuenta aniversario"O Breogán honra ao seu fundador e primeiro presidente"o orixinalMiguel Giao recibiu a homenaxe do PazoHomenaxe aos primeiros gladiadores celestesO home que nos amosa como ver o Breo co corazónTita Franco será homenaxeada polos #50anosdeBreoJulio Vila recibirá unha homenaxe in memoriam polos #50anosdeBreo"O Breogán homenaxeará aos seus aboados máis veteráns"Pechada ovación a «Capi» Sanmartín e Ricardo «Corazón de González»Homenaxe por décadas de informaciónPaco García volve ao Pazo con motivo do 50 aniversario"Resultados y clasificaciones""O Cafés Candelas Breogán, campión da Copa Princesa""O Cafés Candelas Breogán, equipo ACB"C.B. Breogán"Proxecto social"o orixinal"Centros asociados"o orixinalFicha en imdb.comMario Camus trata la recuperación del amor en 'La vieja música', su última película"Páxina web oficial""Club Baloncesto Breogán""C. B. Breogán S.A.D."eehttp://www.fegaba.com

                              Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

                              Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020