lkml.org 
[lkml]   [2002]   [Feb]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: 2.4.18-pre8-K2: Kernel panic: CPU context corrupt
    On Sat, 9 Feb 2002, Pavel Machek wrote:

    > > > Feb 7 23:45:31 steel kernel: CPU 0: Machine Check Exception: 0000000000000004
    > > > Feb 7 23:45:31 steel kernel: Bank 4: b200000000040151
    > > > Feb 7 23:45:31 steel kernel: Kernel panic: CPU context corrupt
    > > Machine checks are indicative of hardware fault.
    > > Overclocking, inadequate cooling and bad memory are the usual
    > > causes.
    > Maybe you should print something like
    > Machine Check Exception: .... (hardware problem!)
    > so that we get less reports like this?

    When I get around to finishing the diagnosis tool, I'll add
    something like "Feed to decodemca for more info".

    --
    | Dave Jones. http://www.codemonkey.org.uk
    | SuSE Labs

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:24    [W:2.216 / U:0.064 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site