I got two answers on my questions. One from Casper Dik <casper@Holland.Sun.COM>
(I can't count the number of times I've seen his name next to solutions to
questions on this list) and one from Kalpesh Dharia <kdharia@fh.us.bosch.com>.
Thanks for all you help guys.
The answer to the first question was that I had not installed the package
SUNWdtcor from the Solaris 2.5 installation disk. I installed the package
using pkgadd -d <device> SUNWdtcor and the messages stopped immediately.
As for the second question, the concensus is that it is a SCSI problem.
Kalpesh suggested checking to make sure all the devices are of the same type.
--Original question--
Greetings O Wise People of the Sun Manager's List,
I am getting two different seemingly unrelated error messages on my system and
need your help in solving the problem.
Question #1:
I was recently looking through some of the log files on my system noticed that
most of the statements in /var/adm/messages looked like the following:
Feb 15 07:02:23 sausm inetd[141]: /usr/dt/bin/rpc.ttdbserverd: Child Status
Changed
Feb 15 07:09:03 sausm last message repeated 2243 times
Feb 15 07:09:03 sausm inetd[141]: /usr/dt/bin/rpc.ttdbserverd: Child Status
Changed
Feb 15 07:15:43 sausm last message repeated 2262 times
Most of the messages file is filled with these. I haven't noticed any
significant degradation in performance, but the problem still vexes me. I can
never catch the program running and I`m still not clear what it does.
Question #2:
I recently upgraded the motherboard on my SPARCstation 2 to an Improv-5 in
order to get the performance of SS 5 without having to buy a whole new system.
Anyway, on bootup, I get the following messages:
WARNING: /iommu@0,10000000/sbus@0,10001000/espdma@4,8400000/esp@4,8800000
(esp0):
Connected command timeout for Target 1.0
WARNING: /iommu@0,10000000/sbus@0,10001000/espdma@4,8400000/esp@4,8800000
(esp0):
Target 1.0 reducing sync. transfer rate
At other times I have gotten some of the following errors:
WARNING: /iommu@0,10000000/sbus@0,10001000/espdma@4,8400000/esp@4,8800000/sd@6,
0 (sd6):
SCSI transport failed: reason 'timeout': retrying command
WARNING: /iommu@0,10000000/sbus@0,10001000/espdma@4,8400000/esp@4,8800000/sd@2,
0 (sd2):
SCSI transport failed: reason 'reset': retrying command
WARNING: /iommu@0,10000000/sbus@0,10001000/espdma@4,8400000/esp@4,8800000/sd@3,
0 (sd3):
SCSI transport failed: reason 'reset': retrying command
WARNING: /iommu@0,10000000/sbus@0,10001000/espdma@4,8400000/esp@4,8800000
(esp0):
SCSI bus MESSAGE OUT phase parity error
WARNING: /iommu@0,10000000/sbus@0,10001000/espdma@4,8400000/esp@4,8800000
(esp0):
failed reselection (no valid cmd)
WARNING: /iommu@0,10000000/sbus@0,10001000/espdma@4,8400000/esp@4,8800000
(esp0):
Connected command timeout for Target 6.0
WARNING: /iommu@0,10000000/sbus@0,10001000/espdma@4,8400000/esp@4,8800000
(esp0):
Target 6.0 reverting to async. mode
I never got these errors before I upgraded the motherboard. Is this something
strictly related to the upgrade or am I having other problems that only cropped
up after the upgrade? After I installed the new board, the system would not
boot from the old OS (Solaris 2.4) because the OS was for the old archtecture.
I had been planning on upgrading to 2.5 anyway, so I just did a new install.
So instead of just upgrading the two separately, I basically did them at the
same time. Could this have any effect on the error messages? The biggest
question concerning this is "How do I fix it?"
Once again, my system is a SS2, motherboard upgraded to a SS5 with an Improv-5
motherboard. 64MB memory, SBus expansion box, 2nd SCSI controller. Running
Solaris 2.5.
Any help on either of these will be greatly appreciated.
Much thanks in advance.
Peter Richards
Westinghouse Savannah River Co.
Aiken, SC
peter.richards@srs.gov
richards@beta.lanl.gov
--End Original--
--Excerpts from Casper Dik's response:
>Question #1:
You haven't installed pkg SUNWdtcor so the link
/usr/dt/bin/rpc.ttdbserverd=/usr/openwin/bin/rpc.ttdbserverd s none SUNWdtcor
is missing. The "Child Status changed" message is bogus (bug 1189416).
>Question #2:
Perhaps the SS5 SCSI is pickier? These looks like cabling/termination
problems.
Casper
--End Casper Dik's response--
--Excerpts from Kalpesh Dharia's response:
Hi Peter,
Your second problem is probably due to a mismatch of SCSI types. Check to see
if all the devices on your SCSI bus, and the corresponding controller are of
the same type i.e all are regular 50-pin standard SCSI-2, fast wide SCSI, or
whatever. I know this is not an answer to your problem, but hoped it might
provide you with a pointer.
-Kalpesh
--End Kalpesh Dharia's response
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:54 CDT