Ik krijg de onderstaande melding en wil aan de hand van de diagnostics
van lnc een oplossing vinden voor dit probleem, echter ik weet niet hoe dat moet. Iemand een idee??
Melding v
/kernel: lnc0: Heartbeat error -- SQE test failed
/kernel: lnc0: Loss of carrier during transmit -- Net error?
man lnc v
van lnc een oplossing vinden voor dit probleem, echter ik weet niet hoe dat moet. Iemand een idee??
Melding v
/kernel: lnc0: Heartbeat error -- SQE test failed
/kernel: lnc0: Loss of carrier during transmit -- Net error?
man lnc v
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
| DESCRIPTION
The lnc driver provides support for the AMD family of Lance/PCnet Ether-
net NICs including the Am7990 and Am79C960. The Ethernet cards supported
by the lnc interface are:
Novell NE2100
Novell NE32-VL
Isolan BICC
Digital DEPCA
Hewlett Packard Vectra 486/66XM
Hewlett Packard Vectra XU
Diamond HomeFree
DIAGNOSTICS
lnc%d: Framing error A framing error occurred. This means a CRC error
also occurred. This caused the driver to drop the packet that contained
the framing error.
lnc%d: Receive CRC error The received Ethernet frame failed the CRC
checksum. This caused the driver to drop the packet that failed the
checksum.
lnc%d: Packet dropped, no mbufs The driver ran out of mbuf's. This may
suggest a resource problem.
lnc%d: Couldn't allocate memory for NIC This is a fatal error. The
driver will not attach to the card under this circumstance.
lnc%d: Memory allocated above 16Mb limit ISA and ESIA cards require
bounce buffers for DMA transfers above 16mb. The Am7990 and Am79C960
only have 24 address lines and so can only access the lower 16Mb of phys-
ical memory. The lnc driver assumes the memory it allocates is within
the lower 16Mb range. This is not a very valid assumption but there's
nothing that can be done about it yet. For shared memory NICs this isn't
relevant.
lnc%d: Device timeout -- Resetting The device has stopped responding to
the network, or there is a problem with the network connection (cable).
Make sure the network connection in use is the same one the card is con-
figured for.
lnc%d: Transmit late collision -- Net error?
lnc%d: Loss of carrier during transmit -- Net error?
lnc%d: Transmit of packet failed after 16 attempts -- TDR = %d
lnc%d: Heartbeat error -- SQE test failed
lnc%d: Babble error - more than 1519 bytes transmitted
lnc%d: Missed packet -- no receive buffer
lnc%d: Memory error -- Resetting
lnc%d: Couldn't get mbuf for transmit packet -- Resetting
lnc%d: Receive buffer error
lnc%d: Receive overflow error
lnc%d: Receive interrupt with buffer still owned by controller --
Resetting
lnc%d: Receive interrupt but not start of packet -- Resetting
lnc%d: Start of packet found before end of previous in receive ring --
Resetting
lnc%d: End of received packet not found -- Resetting
lnc%d: Transmit interrupt with buffer still owned by controller --
Resetting
lnc%d: Transmit interrupt but not start of packet -- Resetting
lnc%d: Start of packet found before end of previous in transmit ring --
Resetting
lnc%d: End of transmitted packet not found -- Resetting
lnc%d: Transmit buffer error -- Resetting
lnc%d: Transmit underflow error -- Resetting
BUGS
This driver has the potential of being the most verbose of any of the
Ethernet device drivers.
SEE ALSO
arp(4), netintro(4), ng_ether(4), ifconfig(8)
HISTORY
The lnc device driver first appeared in FreeBSD 2.2.
AUTHORS
The lnc device driver was written by Paul Richards. Support for the AMD
PCHome phone-line based network added by Robert Watson. This manual page
was written by David E. O'Brien. |