Hi Alls, Thanks for your suggestion. I'll try it out later.
"James P. Roberts" wrote: > > > Hi! I'm using Redhat 7.3 with default kernel version 2.4.7-10 & two > > build in network card which brand is SMC. Below is the output when i > > type ifconfig -a > > > > > > eth0 Link encap:Ethernet HWaddr 00:30:AB:01:F4:41 > > inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.xxx > > Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:715431 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:2713190 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:5759 txqueuelen:100 > > RX bytes:239039791 (227.9 Mb) TX bytes:205402003 (195.8 Mb) > > Interrupt:5 Base address:0xd000 > > > > eth1 Link encap:Ethernet HWaddr 00:50:BF:94:BD:D1 > > inet addr:192.168.10.1 Bcast:192.168.10.255 > > Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:569985 errors:70 dropped:0 overruns:0 frame:74 > > TX packets:0 errors:161464 dropped:0 overruns:0 > carrier:319669 > > collisions:0 txqueuelen:100 > > RX bytes:55468243 (52.8 Mb) TX bytes:0 (0.0 b) > > Interrupt:5 Base address:0xa000 > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:118 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:118 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:7766 (7.5 Kb) TX bytes:7766 (7.5 Kb) > > > > What my question is why my eth1 get an errors :70 & TX bytes:0 ? > > The biggest problem looks like the 161464 TX errors on eth1. > Noticeably, it fails on every TX attempt. I've never seen "carrier" > packets, either. > > I could be wrong, but I think the problem is that both cards are using > the same interrupt (IRQ 5). (If they are PCI-type cards, that may not > be a problem, iff the motherboard/BIOS can handle PCI IRQ sharing). You > may have to mess with your BIOS settings (use caution!!!!); and/or, > depending on the type of cards, set the IRQ on the cards themselves > (either switches or software - refer to manufacturer's manuals). > > If that's not it, I'd try swapping the two cards and see if the problem > follows the card... If so, replace the bad card. > > And if THAT's not it, check the cabling... perhaps you have a bad/loose > TX wire/connection. > > Actually, you might want to check these things in the reverse order > listed. Easy things first, right? > > Best wishes, > Jim Roberts > > _______________________________________________ > Seawolf-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/seawolf-list -- Thanks & Regards, Jason Lim _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
