I've had phenomenally bad luck using consvar to change NIC settings
on a running system. Is this common? I am not sure if it's only ES40s,
or also other systems. This particular machine is running T64 v5.1A,
but I've also done it on systems running 4.0F. I know, the obvious thing
is to *STOP TRYING TO CHANGE CONSOLE VARIABLES ON A RUNNING SYSTEM*, but
the man page makes it look so easy and reasonable!!! Anyone else had
these kinds of crashes, know the explanation, or know of any fixes for them?
I was doing:
consvar -s ewc0_mode FastFD
where ewc0 was an unused interface.
The error is appended here:
======================= Binary Error Log event =======================
EVM event name: sys.unix.binlog.op.panic._savecore.True
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted by kernel components as part of the system panic
process.
Action: Contact your service provider.
======================================================================
Formatted Message:
System panic: panic (cpu 2): tb_shoot ack timeout
Event Data Items:
Event Name : sys.unix.binlog.op.panic._savecore.True
Priority : 700
PID : 438
PPID : 1
Event Id : 99
Timestamp : 18-Oct-2002 08:53:35
Host Name : myhostname
User Name : root
Format : System panic: $message
Reference : cat:evmexp.cat:300
Variable Items:
subid_class (INT32) = 302
message (STRING) = "panic (cpu 2): tb_shoot ack timeout"
binlog_event (OPAQUE) = [OPAQUE VALUE: 240 bytes]
_savecore (BOOLEAN) = True
============================ Translation =============================
binlogshow: DECevent handshake protocol error
======================================================================
TIA...
Judith Reed
Received on Fri Oct 18 2002 - 13:04:08 NZDT