> > As I think it could just disable profiling (at worst case) instead
> > of using panic().
> >
> It should!
The net profiler is a _debugging_ code for just a few network hackers,
not intended to be used by mere mortals, therefore it can expect weird
things about the hardware it runs on.
> Just comment out the code that disables the tsc capability for Cyrix
> chips. I think Linus stuffed it in bugs.h or in setup.c, just grep for
> "Cyrix" in these two files.
>
> The TSC in the Cyrix/IBM 6x86MX is _not_ broken, it works just like a
> Pentium TSC when Suspend-on-Halt is not enabled explicitly.
>
> This behaviour is independent of chip revision i.e. ALL Cyrix/IBM 6x86MX
> chip revisions (including the new MII) will stop the TSC when entering a
> Halt state IFF Suspend-on-Halt is enabled explicitly (it is normally
> disabled).
>
> Also, somebody posted an Oops on an AMD K5-90 machine a few days ago, in
> routine do_fast_gettimeoffset(). This is because Linus forgot to copy
> the relevant code that was originally in time.c on to setup.c; the said
> code takes care of a similar problem with some AMD K5 revisions. A new
> time.c will be available soon that solves this and other issues.
I'll look at the CPU identification, bug testing and TTSC issues soon, but
not just now as all my time is consumed by PCI and exams...
Have a nice fortnight
-- Martin `MJ' Mares <mj@ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth "A LISP programmer knows value of everything, but cost of nothing."- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu