Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 293630 Details for
Bug 390601
[RHEL5] EDAC k8 MC0: extended error code: GART error
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
[patch]
test patch
k8_edac-only_report_gart_errors_on_option.patch (text/plain), 2.06 KB, created by
Aristeu Rozanski
on 2008-01-31 19:25:47 UTC
(
hide
)
Description:
test patch
Filename:
MIME Type:
Creator:
Aristeu Rozanski
Created:
2008-01-31 19:25:47 UTC
Size:
2.06 KB
patch
obsolete
>--- > drivers/edac/k8_edac.c | 26 ++++++++++++++++++++++---- > 1 file changed, 22 insertions(+), 4 deletions(-) > >--- tree.orig/drivers/edac/k8_edac.c 2008-01-07 16:03:37.000000000 -0500 >+++ tree/drivers/edac/k8_edac.c 2008-01-07 16:39:59.000000000 -0500 >@@ -555,6 +555,9 @@ static void do_rdmsr(int cpu, u32 reg, u > *edx = cmd.data[1]; > } > >+static int report_gart_errors; >+module_param(report_gart_errors, int, 0644); >+ > /* > * FIXME - This is a large chunk of memory to suck up just to decode the > * syndrome. It would be nice to discover a pattern in the syndromes that >@@ -1719,8 +1722,22 @@ static int k8_process_error_info(struct > regs->nbeal, regs->nbsh, regs->nbsl); > > if ((err_code & 0xfff0UL) == 0x0010UL) { >- debugf1("GART TLB error\n"); >+ /* >+ * GART errors are intended to help graphics driver >+ * developers to detect bad GART PTEs. It is recommended by >+ * AMD to disable GART error reporting by default[1] (currently >+ * being disabled in mce_cpu_quirks()) and according to the >+ * comment in mce_cpu_quirks(), such GART errors can be >+ * incorrectly triggered. We may see these errors anyway and >+ * unless requested by the user, they won't be reported. >+ * >+ * [1] section 13.10.1 on BIOS and Kernel Developers Guide for >+ * AMD NPT family 0Fh processors >+ */ >+ if (report_gart_errors == 0) >+ return 1; > gart_tlb_error = 1; >+ debugf1("GART TLB error\n"); > decode_gart_tlb_error(mci, info); > } else if ((err_code & 0xff00UL) == 0x0100UL) { > debugf1("Cache error\n"); >@@ -1743,10 +1760,11 @@ static int k8_process_error_info(struct > "Error on hypertransport link: %s\n", > htlink_msgs[(info->error_info.nbsh >> 4) & 0x07UL]); > >- /* GART errors are benign as per AMD, do not panic on them */ >- if (!gart_tlb_error && (regs->nbsh & BIT(29))) { >+ if (regs->nbsh & BIT(29)) { > k8_mc_printk(mci, KERN_CRIT, "uncorrected error\n"); >- edac_mc_handle_ue_no_info(mci, "UE bit is set\n"); >+ /* don't panic in a GART TLB error */ >+ if (!gart_tlb_error) >+ edac_mc_handle_ue_no_info(mci, "UE bit is set\n"); > } > > if (regs->nbsh & BIT(25)) {
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 390601
: 293630