We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
PCEngines firmware version
v4.19.0.1
APU variant
apu2e
OS and OS Version
Linux 5.15.32, 6.0.7, 6.1.4
Affected component(s), peripheral(s) or functionality
The errors are reported as "corrected"… but there are a lot of them!
Brief summary
Very frequently (several times a day, at least) I'm seeing the following being logged via syslog():
[ T1030] [Hardware Error]: Corrected error, no action required. [ T1030] [Hardware Error]: CPU:0 (16:30:1) MC0_STATUS[-|CE|-|AddrV|-|-|-]: 0x9400000000010015 [ T1030] [Hardware Error]: Error Addr: 0x00008ae14b79c000 [ T1030] [Hardware Error]: MC0 Error: L1 TLB multimatch. [ T1030] [Hardware Error]: cache level: L1, tx: DATA
How reproducible
This has happened across a range of Linux kernels from early 5.x through to at least Linux 6.1 - and I'll test with more recent kernels shortly.
How to reproduce
Steps to reproduce the behavior:
Expected behavior
No L1 TLB multimatch errors.
L1 TLB multimatch
Actual behavior
Consistent errors over time.
The text was updated successfully, but these errors were encountered:
ECC RAM detecting a memory error?
Sorry, something went wrong.
Potentially, but I assume the TLB multimatch is something like this:
TLB multimatch
https://www.mail-archive.com/[email protected]/msg1575932.html
… which looks to have been fixed years ago in the general case, but still happening here?
(Plus, I'm booting with nopti and still getting this)
nopti
No branches or pull requests
PCEngines firmware version
v4.19.0.1
APU variant
apu2e
OS and OS Version
Linux 5.15.32, 6.0.7, 6.1.4
Affected component(s), peripheral(s) or functionality
The errors are reported as "corrected"… but there are a lot of them!
Brief summary
Very frequently (several times a day, at least) I'm seeing the following being logged via syslog():
How reproducible
This has happened across a range of Linux kernels from early 5.x through to at least Linux 6.1 - and I'll test with more recent kernels shortly.
How to reproduce
Steps to reproduce the behavior:
Expected behavior
No
L1 TLB multimatch
errors.Actual behavior
Consistent errors over time.
The text was updated successfully, but these errors were encountered: