| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
Hi all,
we have a customer with a DE500-XA in a 4100 running UNIX 3.2f.
This is running fine at 100Mbit/s in half duplex. The only question I
have is an entry in the errorlog at startup time for tu1 which gives a
status of "no link".
e.g
tu1: DECchip 21140-AA; Revision: 1.2
tu1 at pci0 slot 8
tu1: DEC Fast Ethernet Interface,
_hardware address: 00-00-F8-02-38-29
tu1: console mode: selecting 100BaseTX
_(UTP) port: full duplex: no link
Any one care to enlighten me as to why this may be
happening. The full startup errorlog entry follows:
thanks for the help
Chris Poppins
SPT CSC
********************UNIX uerf startup message***********************
EVENT CLASS OPERATIONAL EVENT
EVENT TYPE 300 SYSTEM STARTUP
SEQUENCE NUMBER 0.
OPERATING SYSTEM DEC OSF/1
OCCURED/LOGGED ON Thu Feb 13 18:30:42 1997
OCCURED ON SYSTEM wcau015
SYSTEM ID x00050009 CPU TYPE: DEC 2100
SYSTEM ID x0000000C
MESSAGE PCXAL keyboard, language English
_(American)
Alpha boot: available memory from
_0Xbe4000 to 0xfffe000
Digital UNIX V3.2G (Rev. 62); Fri
_20 12:53:26 EST 1996
physical memory = 256.00 megabytes.
available memory = 244.10 megabytes.
using 975 buffers containing 7.61
_megabytes of memory
Master cpu at slot 0.
Firmware revision: 4.5
PALcode: OSF version 1.21
ibus0 at nexus
AlphaServer 2100 5/300
cpu 0 EV-5 4mb b-cache
cpu 1 EV-5 4mb b-cache
gpc0 at ibus0
pci0 at ibus0 slot 0
tu0: DECchip 21040-AA: Revision: 2.3
tu0 at pci0 slot 0
tu0: DEC TULIP Ethernet
_hardware address: 08-00-2B-E4-BB-69
tu0: console mode: selecting 10BaseT
_(UTP) port: half duplex
psiop0 at pci0 slot 1
Loading SIOP: script 1001d00, reg
_81222000, dats 100dc10
scsi0 at psiop0 slot 0
rz0 at scsi0 bus 0 target 0 lun 0 (DEC
_ RZ29B (c) DEC0014)
rz1 at scsi0 bus 0 target 1 lun 0 (DEC
_ RZ29B (C) DEC0014)
tz4 at scsi0 bus 0 target 4 lun 0 (DEC
_ TZ877 (C) DEC9B3C)
rz5 at scsi0 bus 0 target 5 lun 0 (DEC
_ RRD43 (C) DEC 1084)
eisa0 at pci0
ace0 at eisa0
ace1 at eisa0
lp0 at eisa0
fdi0 at eisa0
fd0 at fdi0 unit 0
vga0 at eisa0
1024x768 (QVision)
fta0 DEC CRE DEFEA FDDI Module.
_Hardware Revision 2
fta0 at eisa0
fta0: DMA Available
fta0: DEC CRE DEFEA (PDQ) FDDI
_Interface, Hardware address:
_08-00-2B-B1-1C-EE
fta0: Firmware rev: 2.3
aha0 at eisa0 slot 4
scsi1 at aha0
tz10 at scsi1 bus 1 target 2 lun 0
_(DEC TLX07 (C)DEC 4BQE)
tz12 at scsi1 bus 1 target 4 lun 0
_(SONY SDT-5000 3.26)
Initializing xcr1. Please wait.
Initializing xcr1. Please wait.
Initializing xcr1. Please wait.
Initializing xcr1. Please wait.
Initializing xcr1. Please wait.
xcr0 at eisa0
re0 at xcr0 unit 0 (unit status =
_ONLINE, raid level = 0)
re1 at xcr0 unit 1 (unit status =
_ONLINE, raid level = 0)
Initializing xcr1. Please wait.
Initializing xcr1. Please wait.
Initializing xcr1. Please wait.
Initializing xcr1. Please wait.
Initializing xcr1. Please wait.
xcr1 at eisa0
re8 at xcr1 unit 8 (unit status =
_ONLINE, raid level = 0)
re9 at xcr1 unit 9 (unit status =
_ONLINE, raid level = 0)
pza0 at pci0 slot 6
pza0 firmware version: DEC P01 A10
_
scsi2 at pza0 slot 0
rz16 at scsi2 bus 2 target 0 lun 0
_(EMC SYMMETRIX 5062)
rz17 at scsi2 bus 2 target 1 lun 0
_(EMC SYMMETRIX 5062)
rz16 at scsi2 bus 2 target 0 lun 3
_(EMC SYMMETIRX 5062)
rz16 at scsi2 bus 2 target 0 lun 4
_(EMC SYMMETIRX 5062)
rz16 at scsi2 bus 2 target 0 lun 1
_(EMC SYMMETIRX 5062)
rz16 at scsi2 bus 2 target 0 lun 2
_(EMC SYMMETIRX 5062)
rz16 at scsi2 bus 2 target 0 lun 5
_(EMC SYMMETIRX 5062)
rz16 at scsi2 bus target lun 6
_(EMC SYMMETIRX 5062)
rz16 at scsi2 bus 2 target 0 lun 7
_(EMC SYMMETIRX 5062)
rz17 at scsi2 bus 2 target 1 lun 1
_(EMC SYMMETIRX 5062)
pza1 at pci0 slot 7
pza1 firmware version: DEC P01 A10
_
scsi3 at pza1 slot 0
rz28 at scsi3 bus 3 target 4 lun 0
_(EMC SYMMETRIX 5062)
rz29 at scsi3 bus 3 target 5 lun 0
_(EMC SYMMETRIX 5062)
rz28 at scsi3 bus 3 target 4 lun 3
_(EMC SYMMETRIX 5062)
rz28 at scsi3 bus 3 target 4 lun 1
_(EMC SYMMETRIX 5062)
rz28 at scsi3 bus 3 target 4 lun 2
_(EMC SYMMETRIX 5062)
rz28 at scsi3 bus 3 target 4 lun 4
_(EMC SYMMETRIX 5062)
rz28 at scsi3 bus 3 target 4 lun 5
_(EMC SYMMETRIX 5062)
rz28 at scsi3 bus 3 target 4 lun 6
_(EMC SYMMETRIX 5062)
rz28 at scsi3 bus 3 target 4 lun 7
_(EMC SYMMETRIX 5062)
tu1: DECchip 21140-AA; Revision: 1.2
tu1 at pci0 slot 8
tu1: DEC Fast Ethernet Interface,
_hardware address: 00-00-F8-02-38-29
tu1: console mode: selecting 100BaseTX
_(UTP) port: full duplex: no link
lvm0: configured.
lvm1: configured.
dli: configured
SuperLAT. Copyrigth 1993 Meridian
_Technology Corp. All rights
_reserved.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 9260.1 | de500-xa "no link" at startup | NETRIX::"[email protected]" | Bob Spear | Tue Mar 25 1997 14:16 | 9 |
Chris, Looking at the if_tu.c driver, the first check is for a "good link" or "100 forced at the console". Since you have forced 100 at the console, you must wait 2.4 seconds for link-test to complete. After link-test is complete, it tests again and if link_ok =1, you break out and start setting up transmit ring and command registers. There would be no message to the console unless you failed to establish link_ok after the link-test completes. The bottom line is, yours is an expected messaged based on forcing 100BaseT at the console. [Posted by WWW Notes gateway] | |||||
| 9260.2 | SMURF::GILLUM | Kirt Gillum | Wed Mar 26 1997 10:33 | 6 | |
Besides, the driver doesn't really care about the link signal. I
regret having that printf in the driver.
Link signal is not required for the device to use the Ethernet.
| |||||