Re: About Celeron processor memory barrier problem

From: Matthias Schniedermeyer (ms@citd.de)
Date: Sat Dec 23 2000 - 18:36:48 EST

  • Next message: Cesar Eduardo Barros: "TCP keepalive seems to send to only one port"

    > > I found that when I compiled the 2.4 kernel with the option
    > > of Pentium III or Pentium 4 on a Celeron's PC, it could cause the
    > > system hang at very beginning boot stage, and I found the problem
    > > is cause by the fact that Intel Celeron doesn't have a real memory
    > > barrier,but when you choose the Pentium III option, the kernel
    > > assume the processor has a real memory barrier.
    > > Here is a patch to fix it:
    >
    > No.
    >
    > The fix is to not lie to the configurator.
    >
    > A Celeron isn't a PIII, and you shouldn't tell the configure that it is.
    >
    > The whole point of being able to choose the CPU to optimize for is that we
    > can optimize things at compile-time.

    This is what 2.2.17 thinks about my Celeron 600MHz

    processor : 0
    vendor_id : GenuineIntel
    cpu family : 6
    model : 8
    model name : Pentium III (Coppermine)
    stepping : 6
    cpu MHz : 601.374
    cache size : 128 KB
    fdiv_bug : no
    hlt_bug : no
    sep_bug : no
    f00f_bug : no
    coma_bug : no
    fpu : yes
    fpu_exception : yes
    cpuid level : 2
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov
    pat pse36 mmx fxsr xmm
    bogomips : 1199.31

    Bis denn 

    -- 
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.

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

    This archive was generated by hypermail 2b29 : Sat Dec 23 2000 - 19:07:44 EST