[lkml]   [2012]   [Feb]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: RAS trace event proto
    On Wed, Feb 22, 2012 at 11:43:24AM +0100, Borislav Petkov wrote:
    > This will keep the bloat level to a minimum, keep the TPs apart and
    > hopefully make all of us happy :).

    Btw, here's how the rough MCE TP trace_mce_record() looks like: [001] .N.. 1049.818840: mce_record: [Hardware Error]: CPU:0 MC4_STATUS[Over|UE|-|PCC|AddrV|UECC]: 0xf604a00006080a41
    [Hardware Error]: MC4_ADDR: 0xbabedeaddeadbeef
    [Hardware Error]: Northbridge Error (node 0): DRAM ECC error detected
    (CPU: 0, MCGc/s: 0/0, MC4: f604a00006080a41, ADDR/MISC: babedeaddeadbeef/dead57ac1ba0babe, RIP: 00:<0000000000000000>, TSC: 0, PROCESSOR: 0:0, TIME: 0, SOCKET: 0, APIC: 0)

    Basically, the userspace daemon will consume the error string (after
    it's been massaged into looking prettier and smaller :-)) (1st arg)
    and dump it to some logs, and use some of the MCE fields to do error
    collection and thresholding/ratelimiting/whatever.

    While at it, I'm also looking very critically at the fields SOCKET,
    APIC, TSC (we have walltime) for I'd like to drop them. Also, MC4 should
    be MC4_STATUS btw.

    To be continued...


    Advanced Micro Devices GmbH
    Einsteinring 24, 85609 Dornach
    GM: Alberto Bozzo
    Reg: Dornach, Landkreis Muenchen
    HRB Nr. 43632 WEEE Registernr: 129 19551

     \ /
      Last update: 2012-02-22 17:03    [W:0.031 / U:0.044 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site