[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bad CRC (Cyclic Redundancy Check)




I get that too, but I am running 2.8 (patched), with two (2) de
interfaces, and my machine freezes hard, I can ping it, and it still
functions as a gateway, but no logins, no mail, nothing else.... takes a
power cycle to unlock it. last show a crash and a reboot, but no
savecore.

This has happened when using NFS or AppleTalk/EtherTalk (netatalk) to do
file transfers. It has always done nfs, but in 2.8 I started using
netatalk. They are not related in the sense that loading netatalk caused
the NFS problem, because I have seen the NFS freeze before I loaded
netatalk. In each and every case there has been bab crc errors...

My SWAG is that it is in the de driver itself, and not in the stack,
possibly in the detection of framing errors due to collisions. I have
not tested on a switched hub, which would aleviate any collisions, I
only have a passive hub currently. Might be time to upgrade to a
switch....

I currently don't have the b/w to try to debug it further, i.e., using
the kernel debugger.... plus it is my mailserver, webserver,
gateway/firewall, and file server (nfs/atalk)...

I can provide my dmesg if necessary. Below is the appropriate lines from
it:

de0 at pci0 dev 10 function 0 "DEC DECchip 21140 (FasterNet)" rev 0x22:
irq 10
de0: 21140A [10-100Mb/s] pass 2.2 address 00:80:c8:47:47:7b
de1 at pci0 dev 11 function 0 "DEC DECchip 21140 (FasterNet)" rev 0x22:
irq 11
de1: 21140A [10-100Mb/s] pass 2.2 address 00:80:c8:47:58:e7

The cards are d-link dfe-500s...

Cheers,

Bruce...

Elneorojo wrote:
> 
> OS Version: 2.6 patched
> NIC's:  Cheap de* 10/100's  (standard DEC 21143)
> 
> Well i came home today to find that i had received a "bad crc" error on
> the internal NIC on my LAN.  While receiving a bad crc does not happen
> that often I was curious to know if this was due to the hardware not
> being able to compute the frame in ? or if this can be duplicated.
> Simply put, I was wondering why the NIC (or the TCP/IP stack) was not
> able to recover from computing the CRC value and continue normal
> operation.  Any thoughts?

-- 
"Those who would sacrifice Liberty for temporary safety deserve neither 
Liberty nor safety."
    - Benjamin Franklin

(echo Mhbqnrnes Stbjr |tr a-y b-z)