Jacob S wrote:
What is the chipset on eth1 and what driver are you using for it? (Not
saying that I have the answer, but you are more likely to get one if you
include that information.) You might also copy/paste the output of "cat
/proc/interrupts".
You may have a driver that a) is buggy b) doesn't fully support that
chipset or a faulty NIC. If you have done any troubleshooting to
eliminate any of those possibilities, that would also be helpful
information to include in your next e-mail.
# cat /proc/interrupts
CPU0 CPU1
0: 139404201 139651227 IO-APIC-edge timer
1: 31 21 IO-APIC-edge i8042
2: 0 0 XT-PIC cascade
5: 22026 40 IO-APIC-level eth1
10: 307860 62574 IO-APIC-level 3w-9xxx, eth0
12: 0 0 IO-APIC-edge i8042
15: 6 8 IO-APIC-edge ide1
NMI: 0 0
LOC: 279066285 279066255
ERR: 4
MIS: 0
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]