8000 rasdaemon: trace SIGBUS event for hardware error by winterddd · Pull Request #199 · mchehab/rasdaemon · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

rasdaemon: trace SIGBUS event for hardware error #199

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

winterddd
Copy link
@winterddd winterddd commented Mar 18, 2025

Kernel will send SIGBUS to program when read DE/UE, use rasdaemon to catch this SIGBUS and print it like follow:

<...>-105439 [063] 0.007348: signal_generate: 2025-03-18 14:12:05 +0800 signal: 7, errorno: 0, code: 4, comm: einj_mem_uc, pid: 105439, grp: 0, res: 0, msg: Hardware memory error consumed: action required

@winterddd winterddd force-pushed the signal branch 2 times, most recently from 2dbaa03 to 3da1f18 Compare March 26, 2025 02:14
Copy link
@axiqia axiqia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please see my comments inline.

@axiqia
Copy link
axiqia commented Mar 28, 2025

LGTM.

Reviewed-by: Shuai Xue xueshuai@linux.alibaba.com

@vt-alt
Copy link
vt-alt commented Apr 26, 2025

@winterddd Thanks for doing great work! I hope your pull requests are merged.

Kernel will send SIGBUS to program when read DE/UE, use rasdaemon to
catch this SIGBUS and print it like follow:
	<...>-71085 [056] d...     0.007781 signal_generate \
	2025-03-18 15:24:11 +0800 signal: Bus error, errorno: 0, code: 4, \
	comm: einj_mem_uc, pid: 71085, grp: 0, res: Deliverd, \
	msg: Hardware memory error consumed: action required

Signed-off-by: Ruidong Tian <tianruidong@linux.alibaba.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0