Subject: Re: Problems bringing 2.0C up on Challenge S system
To: None <>
From: Havard Eidnes <>
List: port-sgimips
Date: 05/12/2004 09:40:56

a brief update:

I cross-built 2.0E (as an "update" build) and installed that on
the Challenge S.  Things are better than they were.  However, I
note a couple of odd things:

Using the per-default "su -> su -m" alias in csh causes csh to
segfault.  This used earlier to trigger the panic / cache error.

Also, csh spews while processing .login when root logs in on the
console, complaining about "Badly placed ()'s."  Doing "set
verbose" and sourcing .login appears to indicate that just before
that complaint csh gets a segfault.

I could log in via ssh to the system (after setting up an account
for myself and starting sshd), but exiting and trying that again
appears to cause a "silent reset"; the second ssh login appears
to hang, and 10-30 seconds later the machine simply reboots with
no error message and no drop back to DDB.

So, while things are better than they were, something is still
not quite right.


- H=E5vard