From: Derek Gatherer (d.gatherer@vir.gla.ac.uk)
Date: Wed Mar 03 2004 - 03:27:25 EST
Thanks also to Bryan LaVelle for extra feedback following the first summary.
The faulty CPU was replaced by a new one, but the problem remained.
The solution was in /etc/sysconfigtab under generic, where lockmode was set
at 1. Erasing this line and rebooting 'released' the cpu_enable_mask
parameter (which was stuck at 0x1, and greyed-out in dxkerneltuner), and it
reset itself automatically on reboot to 0x3. Apparently lockmode set
itself, probably on Friday, when the bad CPU was trying to run. However,
when the bad CPU was replaced with a good one, lockmode did not
automatically release itself (and is probably not supposed to (?), but
requires manual reset).
psrinfo -v now gives:
Status of processor 0 as of: 03/02/04 16:35:12
Processor has been on-line since 03/02/2004 16:20:56
The alpha EV6 (21264) processor operates at 500 MHz,
has a cache size of 4194304 bytes,
and has an alpha internal floating point processor.
Status of processor 1 as of: 03/02/04 16:35:12
Processor has been on-line since 03/02/2004 16:20:56
The alpha EV6 (21264) processor operates at 500 MHz,
has a cache size of 4194304 bytes,
and has an alpha internal floating point processor.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:52 EDT