Hello,
I've just seen a question that triggered another on my side. I
sometime get the same messages whenever there is a problem on the FDDI. But
twice already I got the following :
Jun 24 17:21:38 foobar vmunix: fta0: Ring beacon initiated
Jun 24 17:21:40 foobar vmunix: fta0: PC Trace initiated
Jun 24 17:22:00 foobar vmunix: fta0: Halted.
Jun 24 17:22:03 foobar vmunix: fta0: Halt Reason: PC Trace
Jun 24 17:22:03 foobar vmunix: fta0: Link Unavailable.
Jun 24 17:22:48 foobar vmunix: fta0: Link Available.
When the messages "PC Trace initiated", "Halted." et "Halt Reason: PC
Trace" appear, it is going, going, gone !!! We then need to reboot the server
in order to get the FDDI interface working again.
I've placed a call to DEC support which finally told me that the
interface behaviour was normal but it would be better to install the patch for
DU 3.2D called OSF360-350084 which would fix some other FDDI related problems.
Has anyone seen that kind of message in the kern.log file with the
following FDDI problem ?
Will summarize
Bye now...
...Louis
----------------------------------------------------------------------------
| Louis Bouchard
J'aimes que ca cesse quand c'est fini. Quand | Ingenieur Systeme
ca recommence, ca me scie. | bouchard_l_at_decusf.fr
R. Ducharme | Bouygues Telecom
| 39-26-66-73
----------------------------------------------------------------------------
Received on Wed Jun 26 1996 - 17:53:47 NZST