[Bug 2088250] Re: [Lenovo Ubuntu 20.04.6&22.04.5 bug] After injecting a memory MCE error, no error logs were obtained from rasdaemon

[Tai Ho]

** Changed in: rasdaemon (Ubuntu)
       Status: New => In Progress

** Changed in: rasdaemon (Ubuntu)
     Assignee: (unassigned) => Tai Ho (tai271828)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2088250

Title:
  [Lenovo Ubuntu 20.04.6&22.04.5 bug] After injecting a memory MCE
  error, no error logs were obtained from rasdaemon

Status in rasdaemon package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  * This update fixes LP: #2088250, where critical hardware error logs
  are not correctly recorded in the database.

  * This fix has already been implemented and validated in Debian
  (version 0.8.1-3) and has been successfully running in Debian
  Bookworm-backports for several months.

  * This SRU synchronizes Ubuntu Jammy with the stable Debian backport
  baseline

  
  [ Test Plan ]

  * Basic verification includes confirming the presence of binaries and
  the systemd unit files, as well as verifying the daemon's ability to
  initialize the event database:

  for path in "/usr/lib/systemd/system/ras-mc-ctl.service" \
  "/usr/lib/systemd/system/rasdaemon.service" \
  "/usr/sbin/ras-mc-ctl" \
  "/usr/sbin/rasdaemon" \
  "/var/lib/rasdaemon"
  do
  ls -d $path
  done

  # Check event database persistence
  ls /var/lib/rasdaemon/ras-mc_event.db

  # Test summary reporting tool
  /usr/sbin/ras-mc-ctl --summary

  # Verify service health and log registration
  systemctl status rasdaemon
  journalctl -b | grep EDAC

  
  * Note on Error Injection Testing: If you wish to perform active error injection testing, ensure the kernel has been built with EDAC debugfs support (CONFIG_EDAC_DEBUG) and is running on hardware that supports these triggers.

  
  [ Where problems could occur ]

  * Standalone Nature: rasdaemon is an optional, standalone monitoring
  application. It is not part of the critical boot path or core kernel
  functions. If the daemon were to fail or crash, it would not impact
  system stability, network connectivity, or the ability to boot.

  * Large Delta: While the version jump from 0.6.7 to 0.8.1 is
  significant, this specific version has undergone testing in the Debian
  ecosystem. As the current Debian Maintainer for rasdaemon, I am
  overseeing this transition to ensure that the Ubuntu package benefits
  from the same stability and feature set as the current Debian Backport
  (https://packages.debian.org/bookworm-backports/rasdaemon).

  
  [ Other Info ]

  A traditional debdiff is not provided due to the extensive delta
  between the legacy Jammy version and the current Debian Backport.
  Alternatively, we can check the reference build from my PPA:
  https://launchpad.net/~tai271828/+archive/ubuntu/rasdaemon-deb-dev/




  =========== Original Bug Description Below =================



  
  Release: 20.04.6 and 22.04.5

  rasdaemon version : 0.6.5(20.04.6)    0.6.7(22.04.5)

  Describe:
      After injecting a memory MCE error, no error logs were obtained from rasdaemon
  ---------------------------------------
  # root at test:/tmp# ras-mc-ctl --errors
  No Memory errors.

  No PCIe AER errors.

  No Extlog errors.

  No MCE errors.
  --------------------------------------

  After upgrading rasdaemon to 0.8.1-3 on 22.04.5, MCE errors will be recorded by rasdaemon.Due to the complexity of handling dependencies, we have not yet attempted 0.8.1-3 on 20.4.6.
  Also, I found a similar bug https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/2058328.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/2088250/+subscriptions