Arch Linux User Repository

Why is this package being built with

--enable-abrt-report

There is no abrt daemon for Arch, so this generates an "error" about 5 per minute. I've built it with this removed and we're down to a heartbeat every 3 seconds or so.

-----Burton

Stellar! ;-)

pancho,

Thanks for the heads-up. I added your workaround and will report the problem upstream.

Hi there.

It seems that we've been hit by a change¹ in GCC 10. See the topic² for more details. It also affects pam_ssh, so I've managed to easily workaround it² by adding:

CFLAGS="$CFLAGS -fcommon" ./configure ...

This just reverts GCC to the pre-10 behavior.

Hope that it helps.

¹: https://gcc.gnu.org/gcc-10/porting_to.html

²: https://bbs.archlinux.org/viewtopic.php?id=255727

³: https://aur.archlinux.org/cgit/aur.git/commit/?h=pam_ssh&id=cb4ed823ece6b3316a7b4103135dec8d1711473c

I get some of those disk errors, though not nearly as many. Also don't see any corresponding problems or errors outside of rasdaemon, so I'm not sure what to make of them. If they're causing people problems, I can disable the disk error feature in the PKGBUILD, but I think reporting this upstream is the best answer.

Those new "experimental features" don't seem to be working right for me here. On certain boots, I get hundreds of the following errors recorded in ras-mc-ctl --errors:

Disk errors
1 2019-09-30 12:19:31 +0200 error: dev=0:2080, sector=192357784, nr_sector=256, error='unknown block error', rwbs='RA', cmd='', 
...
504 2019-10-11 21:02:08 +0200 error: dev=0:2048, sector=12986960, nr_sector=8, error='unknown block error', rwbs='R', cmd='', 

This does not happen on every boot, it only happens every three days or so.

While those errors are getting recorded by rasdaemon, I can't find any strange messages in journalctl or dmesg. The log messages there look fine with no errors or warnings.

Because this was an orphaned package I took over and I didn't notice the change because I was using my own custom unit :). Fixed.

Why are you removing "-r" from ExecStart in rasdaemon.service? Without "-r" it doesn't record anything, journalctl -u rasdaemon output is nearly useless when MCE occurs:

сен 02 19:37:55 X299 rasdaemon[552]: overriding event (1081) ras:mc_event with new print handler
сен 02 19:37:55 X299 rasdaemon[552]: overriding event (1078) ras:aer_event with new print handler
сен 02 19:37:55 X299 rasdaemon[552]: overriding event (1079) ras:non_standard_event with new print handler
сен 02 19:37:55 X299 rasdaemon[552]: overriding event (1080) ras:arm_event with new print handler
сен 02 19:37:55 X299 rasdaemon[552]: overriding event (109) mce:mce_record with new print handler
сен 02 19:37:55 X299 rasdaemon[552]: overriding event (1082) ras:extlog_mem_event with new print handler

automake and autoconf are in base-devel.

automake and autoconf are needed to build this package.