[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tru64-unix-managers
Subject:    SUMMARY:  Can't rebuild kernel after CLC update
From:       "Bennett, Laura L. \(CIT\)" <lbennett () exchange ! nih ! gov>
Date:       1999-04-30 14:17:21
[Download RAW message or body]

Quick summary of orginal problem:  after installing product CLCM313 and
rebuilding the kernel, we experienced a panic, and we were no longer able to do
kernel builds.  We also experienced some inetd problems requiring removal of a
Tooltalk patch.

Thanks for the responses:
alan@nabeth.cxo.dec.com  noted that he's been lead to believe that some patches
may change a file that is also part of the CLC installation, and therefore the
CLC installation may place an older copy of a file out there, overlaying a
patched version. 

Robert.Otterson@compaq.com and Saar Picker[saarp@uclink4.berkeley.edu] both
suggested booting the Generic Kernel and and trying to rebuild from there.
Otterson also noted that he has had files that "build" the kernel get corrupt
and replacing them (from a LIKE system) allowed him to get futher.

In the end here's what happened:
We booted with the generic kernel, and were still unable to do a kernel build
(still makelint problems).
We restored an old configuration directory (usr/sys/NAME) and were able to build
a kernel using this directory.  We also successfully installed the CLCMC313
(rebuilding the kernel ourselves rather than through their script), and
installed the ToolTalk patch, all without problems.

So it appears that something in the configuration directory was corrupted
(though we never were able to determine from diffs where the corruption was).

Thanks for the help,
Lolly Bennett


== Original question  ===============
Our environment is an 8400,  firmware level Rev: 5.3-11,  operating system
Tru64-unix 4.0d, and patch kit 3 (the December version DUV40DAS00003-19981208>
OSF425). 

Has anyone seen this:  we were performing an upgrade of CAM Medium Changer
Driver from V3.1A to V3.1C (CLCMC311 to CLCMC313).  We went to single user,
deleted the 3.1A version, installed the 3.1C version, and let the CLC
installation script back up the kernel and rebuild the new kernel.  Before
rebooting with the new kernel, the "robot" CLC command was issued and the
machine panicked  (which was to be expected under the old kernel - the reason we
were upgrading the CLC).  

The system was reset and began rebooting with the new upgraded kernel, but got
hung during boot.    We booted with the old kernel and attempted to rebuild a
new kernel (to pick up the new CLC code again).   Could not perform a kernel
rebuild - recieved errors about problems with makelint  (noted later that
makelint contained many null characters -  \000 ).   Renamed and came back up
with orginal/old kernel.   

As an aside, we had also installed Tooltalk patch SSRT0566U, which updates
rpc.ttdbserverd and restarts inetd.  Though this patch had installed on our
other systems successfully, in this instance it flooded the system, spawning
processes, so we backed it out.

We wonder if the panic could have caused all of the problems that followed: 1)
new kernel hung in boot, 2) inability to perform a kernel rebuild, and 3)
Tooltalk patch spawning processes.   If so, we would try the same procedures
again, minus the "panic".  If the panic doesn't sound like the culprit, has
anyone else experienced an inability to do kernel rebuilds, or problems with the
Tooltalk patch, in a similar environment? 

--------------------------------------------------------------------------
Lolly Bennett           
National Institutes of Health
Center for Information Technology
email:   lolly@nih.gov

[prev in list] [next in list] [prev in thread] [next in thread]