[lkml]   [2000]   [Dec]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: About Celeron processor memory barrier problem
> >         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
Please read the FAQ at

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