Package Details: rasdaemon 0.8.3-1

Git Clone URL: https://aur.archlinux.org/rasdaemon.git (read-only, click to copy)
Package Base: rasdaemon
Description: Logging daemon for Platform Reliability, Availability and Serviceability (RAS), replacing mcelog
Upstream URL: https://github.com/mchehab/rasdaemon
Licenses: GPL-2.0-or-later
Submitter: grawity
Maintainer: eta-carinae
Last Packager: eta-carinae
Votes: 43
Popularity: 0.124978
First Submitted: 2017-05-04 06:49 (UTC)
Last Updated: 2025-06-18 16:20 (UTC)

Latest Comments

1 2 3 4 Next › Last »

eta-carinae commented on 2025-04-29 16:07 (UTC)

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.

SunRed commented on 2024-11-23 13:04 (UTC)

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

eta-carinae commented on 2024-07-06 18:36 (UTC)

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

dbrtbgdstbgdz commented on 2024-07-02 10:17 (UTC)

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.

eta-carinae commented on 2023-01-09 15:28 (UTC)

@hamelg,

The new release 0.6.8-2 applies the patch you mentioned. Thanks for finding that. It fixed a startup crash I've been having for a while on one system where rasdaemon detected the wrong number of CPU cores. From what I can tell it mostly affects AMD systems.

hamelg commented on 2023-01-07 15:02 (UTC)

Here, rasdaemon crashes at startup since the linux kernel v6.0.8. This patch fixes the issue :

https://github.com/mchehab/rasdaemon/issues/77

eta-carinae commented on 2022-11-10 15:00 (UTC)

I don't know if this is causing your problems, but there's an issue with rasdaemon and the linux kernel starting with 6.0.5. It apparently is patched for the upcoming 6.0.8 kernel release.

eta-carinae commented on 2022-11-07 21:11 (UTC)

I haven't seen any of the problems people have been reporting, so it's probably best to report them upstream if you haven't already.

The PKGBUILD does enable a couple of features listed as experimental on the github page (PCIe AER and MCE events). It might be worth building a version without those features and testing that.

avb commented on 2022-11-06 03:12 (UTC)

@xamino, @axzxc1236: I'm also seeing weird interference. In my case, I lost both wifi and bluetooth (same card - Intel ax200) at first, and then after upgrading to 6.0.7 kernel pacman was unable to download files. Uninstalling rasdaemon fixed both of these issues.

xamino commented on 2022-11-03 09:59 (UTC) (edited on 2022-11-03 09:59 (UTC) by xamino)

I can confirm on a pure Arch machine – spent a day fighting to get back to a graphical interface. Looking at the logs there may have been a kernel exception, so this might be tied to the newest Linux kernel. GDM refused to start up, couldn't switch to TTY, shutdown also didn't really work, etc. I stopped it and everything started working again.

1 2 3 4 Next › Last »