Return to PROB_REP CVS log

Up to [Power 6/32 Unix Tahoe 4.2BSD] / cci / d / ether

Annotation of cci/d/ether/PROB_REP, revision 1.1.1.1

1.1       root        1: 
                      2: 
                      3: 
                      4: 
                      5: COMPUTER CONSOLES INC.                         INTER-OFFICE MEMO
                      6: -----------------------------------------------------------------
                      7: 
                      8:                                                Jan 7th, 1985
                      9: 
                     10: 
                     11: TO:      Naresh Desai
                     12: 
                     13: FR:      Pham, Phuc M.
                     14: 
                     15: SUBJECT:  Report of Ethernet Controller Diagnostic Problems.
                     16: 
                     17: 
                     18:        Following are the problems of the ethernet controller
                     19: functionality that I found while trying to develop a diagnostic
                     20: program for it.
                     21: 
                     22: 
                     23:        1. In loop 2 mode, the rbc of the receiver buffer are
                     24:           not updated to reflect the length of the buffered
                     25:           message, but instead, the crs (the first word of the
                     26:           receive buffer) always contains a value of 0xB000.
                     27:           This causes the error-checking mechanism to generate
                     28:           the following errors even though the message is corr-
                     29:           ectly received.
                     30: 
                     31:                - CRC error
                     32:                - Underrun error (because rbc = 0)
                     33:                - Oddbit error
                     34: 
                     35:        2. In loop 3 mode, the crs word of the receive buffer
                     36:           always contains a value of 0xA000 which, again,
                     37:           causes the error checking mechanism to generate CRC
                     38:           and underrun errors for every message transmitted.
                     39:           Moreover, as seen in the attached sample run, no mess-
                     40:           age has shown up in the receive buffers. 
                     41: 

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.