Re: [plug] Kernel Error

[fooler]

this error is generated by a lan card network driver specifically on the transmission part (TX)... possible causes are:   1. bad nic 2. cable problem 3. duplex mismatch   fooler. ----- Original Message ----- From: Rikki T. Vizcarra To: PLUG Sent: Tuesday, August 27, 2002 4:49 PM Subject: [plug] Kernel Error Hello fellow pluggers...   Have anyone of you experienced this problem?? I've been trying to locate where the error is coming from but it's been a week and I can't seem to find it. Aug 27 15:42:57 server3 kernel:   Flags; bus-master 1, dirty 57590(6) current 57590(6)Aug 27 15:42:57 server3 kernel:   Transmit list 00000000 vs. cf4e7380.Aug 27 15:42:57 server3 kernel:   0: @cf4e7200  length 800000d5 status 000100d5Aug 27 15:42:57 server3 kernel:   1: @cf4e7240  length 800005ea status 000105eaAug 27 15:42:57 server3 kernel:   2: @cf4e7280  length 800005ea status 000105eaAug 27 15:42:57 server3 kernel:   3: @cf4e72c0  length 800004ce status 000104ceAug 27 15:42:57 server3 kernel:   4: @cf4e7300  length 800005ea status 000105eaAug 27 15:42:57 server3 kernel:   5: @cf4e7340  length 800005ea status 800105eaAug 27 15:42:57 server3 kernel:   6: @cf4e7380  length 800005ea status 000105eaAug 27 15:42:57 server3 kernel:   7: @cf4e73c0  length 80000036 status 00010036Aug 27 15:42:57 server3 kernel:   8: @cf4e7400  length 800005ea status 000105eaAug 27 15:42:57 server3 kernel:   9: @cf4e7440  length 800002a2 status 000102a2Aug 27 15:42:57 server3 kernel:   10: @cf4e7480  length 800005ea status 000105eaAug 27 15:42:57 server3 kernel:   11: @cf4e74c0  length 800005ea status 000105eaAug 27 15:42:57 server3 kernel:   12: @cf4e7500  length 800005ea status 000105eaAug 27 15:42:57 server3 kernel:   13: @cf4e7540  length 800005ea status 000105eaAug 27 15:42:57 server3 kernel:   14: @cf4e7580  length 8000059f status 0001059fAug 27 15:42:57 server3 kernel:   15: @cf4e75c0  length 80000036 status 00010036 Can this error be generated by one of my LAN cards installed in the server?  I'm using multiple LAN cards with all of my servers but only one keeps on generating the error. One of my theories which up to now I can't trace is that one of the connected workstations or hub on one of the LAN cards has collisions and the errors are somehow being catched by the system. Can I be right at this?   I've been checking the system and tracking my network and it seems that most of the errors are generated during office hours. Is my suspicion correct?? Could it be one of the LAN cards? Can it be a workstation, switch or hub connected to one of the LAN cards is where the error is coming from??   If anyone can help I would gladly appreciate it.  Thanks in advance...   --- Rikki T. Vizcarra Systems Administrator Publicis-AMA, Inc. Tel No: +63 2 9115353 E-mail: [EMAIL PROTECTED]