summary: system hangs

From: B. Boersch-Pulm <acp30_at_mail1.rrz.Uni-Koeln.DE>
Date: Thu, 03 Sep 1998 17:28:39 +0200

Hallo,

thanks to all who answered my questions.

the system is up. There were two errors which occur indepently from one
other.

The system hang up depended on a simple nfs mount for a home directory of
one of my users. This one, already mounted at start time from amd, causes
the amd to make a core dump and to die with the error message : process
2010 exited with signal 11 in his log-file. I deleted the nfs mount from
the fstab, (it was just a try because I didn't know what else I should do
to repair the system), and the system came up with no problems. I mounted
this directory later on manually without any problems !

I don't know why it is this way, but it works.

The second (Hardware)problem ist still present, but in the moment ist
seems to have no consequences :

I wrote :

there is the following message in my startup-file :

 cam_logger: CAM_ERROR packet
 cam_logger: bus 1
 isp_probe

this occurs for isp0 isp1

and beside that there is the message :

NVRAM parameters invalid, using driver_Fast10 defaults
isp1: Firmware revision 2.10 (loaded _by console)

This message appears since the first start of the machine.
The technician from digital tried to solve it with a newer version of
the firmware : 2.10 but the message is still there.

Dr. Thomas P. Blinn wrote :

The message:

        NVRAM parameters invalid, using driver Fast10 defaults

is because the console firmware hasn't set the ISP SCSI controller into
the
state the operating system software expects. There is a command in the
SRM
console, if I remember right it's "isp1020_edit" that has a "-sd" (again,
if memory serves me correctly) option to set the NVRAM to the default
values.

If it's not set correctly, you might get problems.

The cam_logger message is telling you that when the SCSI subsystem code
was
trying to probe bus 1 (presumably isp1 at pci1000 slot 2, that is, the
second SCSI port on your dual port controller), it got back an error reply
(CAM_ERROR packet) instead of a valid reply. This suggests the controller
is not working correctly. It could be a hardware error or bad firmware or
firmware not configured correctly (NVRAM parameters invalid).


Is there someone who knows what to do, to set the right parameters, or
which number of the firmware probably will solve the problem ?


thanks to all, for of all, I'm happy to have a running system again.


Birgitt Boersch-Pulm
Received on Thu Sep 03 1998 - 15:29:37 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:38 NZDT