Arch Linux User Repository

It's not part of base-devel which is what the guide on building in chroot uses. I can't find info on if base should also be installed.

pciutils is required by base, so I usually wouldn't add it, but I guess old systems might still be using the base group. Should be updated shortly.

Missing pciutils in dependencies.

checking for libpci... no
configure: error: Package requirements (libpci) were not met:

Package 'libpci' not found

Ok, this finally updated to 0.8.4. The update includes a patch to handle the deprecation of /sys/kernel/debug/tracing.

Here is a patch for version 0.8.4.

diff --git a/PKGBUILD b/PKGBUILD
index e75ee5f..d354d1a 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,7 +1,7 @@
 # Maintainer: Ashley Bone <ashley DOT bone AT pm DOT me>
 # Orginally Packaged By: Mantas Mikulėnas <grawity@gmail.com>
 pkgname=rasdaemon
-pkgver=0.8.3
+pkgver=0.8.4
 pkgrel=1
 pkgdesc="Logging daemon for Platform Reliability, Availability and Serviceability (RAS), replacing mcelog"
 arch=(i686 x86_64)
@@ -17,18 +17,25 @@ depends=(
   perl-dbd-sqlite
 )

-source=("https://www.infradead.org/~mchehab/rasdaemon/rasdaemon-${pkgver}.tar.bz2"
-        buffer-overflow.patch)
-sha256sums=('44ca3b02951e45411ea75a9fa5314ff4efb424ab029f196807632b905645c37b'
-            '87f4e9584fdebcb80060fbfea720733b80ffd98aebdef099c62dad778e3916d1')
+source=("https://github.com/mchehab/rasdaemon/archive/refs/tags/v${pkgver}.tar.gz"
+        # Fix usage of deprecated /sys/kernel/debug/tracing
+        "https://github.com/mchehab/rasdaemon/pull/231.patch"
+        # Allow for built-in EDAC modules in status check
+        "https://github.com/mchehab/rasdaemon/pull/233.patch")
+sha256sums=('7e12459f9477036491ac2b1e4c07cc3e8efea6dcd30525a263ab1f83910b773a'
+            '3c107fc0d81f1713a7aabd24885adbed25fc936c51638b67467e8753bc1cf289'
+            'edf164ae180a7764da92b10d56fd83e2df9f471e70f0725dbb4fe1eaaedbc0ec')

 prepare() {
   cd "${srcdir}/${pkgname}-${pkgver}"
-  patch -p1 < "${srcdir}/buffer-overflow.patch"
+  for file in '231.patch' '233.patch'; do
+    patch -F5 -lp1 -f <"${srcdir}/${file}"
+  done
 }

 build() {
   cd "$srcdir/$pkgname-$pkgver"
+  autoreconf -vfi
   ./configure \
     --prefix=/usr           \
     --sbindir=/usr/bin      \

buffer-overflow.patch is not required anymore, because it was upstreamed. Also, I included 2 PRs that allow the tool to actually work on current Arch systems.

• src mirror is down, switched to github with the source/sha256 below
• build is missing a call to autoreconf

source=("https://github.com/mchehab/rasdaemon/archive/refs/tags/v0.8.3.tar.gz"
        buffer-overflow.patch)
sha256sums=('207bf6822e05377da9fea07b2b4ded4dbe8b8a44889febac0010450ac00030ec'
            '87f4e9584fdebcb80060fbfea720733b80ffd98aebdef099c62dad778e3916d1')

prepare() {
  cd "${srcdir}/${pkgname}-${pkgver}"
  patch -p1 < "${srcdir}/buffer-overflow.patch"
}

build() {
  cd "$srcdir/$pkgname-$pkgver"
  autoreconf -vfi
  ./configure \
    --prefix=/usr           \
    --sbindir=/usr/bin      \
    --sysconfdir=/etc       \
    --with-sysconfdefdir=/etc/sysconfig \
    --localstatedir=/var    \
    --enable-sqlite3        \
    --enable-aer            \
    --enable-non-standard   \
    --enable-arm            \
    --enable-mce            \
    --enable-extlog         \
    --enable-devlink        \
    --enable-hisi-ns-decode \
    --enable-memory-ce-pfa  \
    --enable-memory-row-ce-pfa \
    --enable-cpu-fault-isolation \
    ;
  make
}

I'm working on updating to 0.8.3, but I'm getting a buffer overflow on startup. I'll take another look at it later this week.

Somehow the checksum for the tarball has changed and is now 3cb5bbb2091cd278a394674259256bb7ff8f1eba8f2462c67e5172dccda0bebe (just run updpkgsums).

I have removed --enable-diskerror as it does seem to still be experimental.

I just run sudo ras-mc-ctl --errors to see if there is something new, and under Disk errors I have 25363 lines which look like this:

1 2023-XX-XX XX:XX:XX +XXXX error: dev=0:2048, sector=0, nr_sector=0, error='unknown block error', rwbs='WS', cmd='', 
2 2023-XX-XX XX:XX:XX +XXXX error: dev=0:2064, sector=5943568, nr_sector=240, error='unknown block error', rwbs='W', cmd='', 
..
25363 2024-XX-XX XX:XX:XX +XXXX error: dev=0:2048, sector=973342720, nr_sector=0, error='unknown block error', rwbs='WS', cmd='', 

Searching around, I found other people wondering/complaining what this is and someone said that the disk error feature in rasdaemon is experimental and that --enable-diskerror in the PKGBUILD file should be removed for the time being.