1. Forum
  2. Usenet
  3. LINUX.DEBIAN.USER

  • Re: Hardware Error Messages

    From Dan Purgert@21:1/5 to Michael on Mon Jan 6 17:00:02 2025
    On Jan 06, 2025, Michael wrote:
    - I have a Debian Bullseye desktop PC. From time to time I receive
    several Hardware Error Messages which begin with a Hardware Error Message
    of the form :-

    Message from syslogd@piglit at Jan 5 02:49:03 ...
    kernel:[1064021.151590] [Hardware Error]: Corrected error, no action required.

    This just looks like a notification sent to TTY1 (or where-ever you've
    got an active session), with the intent that the operator look in syslog
    for more details.

    --
    |_|O|_|
    |_|_|O| Github: https://github.com/dpurgert
    |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmd7/CYACgkQbWVw5Uzn KGC/fRAAqTVIiwBtrd+he19Sw0sKT5M9vlbZ8ZOqmttfT1hwRnp5cgEw76AwoUDh xZ6FCSZ0Ycr3wWWV6N30KooxDk3NOWaopU0OAB+W3E3Y5VnIYZBKvrA12Cu69Hih jKMmo0Yw05WYrpDp/8L6Nk6H4afv3dT6WlQ2VdvXzF/qW2fibJC6pgAFVwero7T7 9v7cPIilXmVrmQJC4g0knpq7FLSl19cZurV3K3NOq1UKn7x4Nd/rypHhjm72cf6N /8Pg4V/9LAbi4vSBXsYweaFh/GbuVxf+/tiIpvIHphUZCvyZNvIOFbX/dv7GCr2/ sN5h0UdGIjGUYYwwKkC4vxGtVqy7lOsHzylobkM4rvA3CjAl+cGapfA5zwxJwUtD bes+4osGhbESKf67j6qysllR80YmWEgad0r9K3/Soax8lF66O4OjXwYvGxuWQFZa uiMMjv3bkZZHALA7LSwizcFe32JYH8Oz1bSdAL1j5cAMAE4xDGoLgO8ylhs2JdvW bXmBFhEme9irpGWWOzFDIXvOR5UcRrxyqCQK4sT/QCIjMCy7NtjjMO6OneyXxi2q wh5LO7fB1Uyr0WEpoc0TnbrOxZkBVJOK29+uct9zovCg9YC6e3zpkISH581cYcNx gJIuSQhwJ0KeLJfq209fEv1B87zU6Q7d523kidJ1CoDkRznpttU=
    =rd+n
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Us
  • From Michael =?utf-8?B?S2rDtnJsaW5n?=@21:1/5 to All on Tue Jan 7 09:30:01 2025
    On 6 Jan 2025 10:52 -0500, from dan@djph.net (Dan Purgert):
    Message from syslogd@piglit at Jan 5 02:49:03 ...
    kernel:[1064021.151590] [Hardware Error]: Corrected error, no action
    required.

    This just looks like a notification sent to TTY1 (or where-ever you've
    got an active session), with the intent that the operator look in syslog
    for more details.

    Yes, the actual system logs from the kernel should have more details.
    If you haven't rebooted since, you can try something like:

    $ sudo dmesg | grep -C 10 1064021

    The most plausible explanation absent any further details is likely a correctable CRC/ECC/FEC error somewhere. You can check component and
    cable seating, including power cabling.

    --
    Michael Kjörling
    🔗 https://michael.kjorling.se

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)