2002-06-28 08:30:04

by Cosmin Matei (lkml)

[permalink] [raw]
Subject: IRQ sharing problem - 2.4.18 kernel


Hi,
I have a TYAN Tiger 200T M/B with 2xIntel PIII CPUs at 1GHz and 1,3GB RAM.
I'm using RadHat up to date and 2.4.18 vanilla kernel. On heavy load on
ethernet interfaces (eth1,2,3,4) and scsi controller which are on the same
IRQ (11) my server stops responding.

Thease are the erros given by kernel:
Jun 27 21:56:27 lapd eth3: Promiscuous mode enabled.
Jun 27 21:56:27 lapd NETDEV WATCHDOG: eth4: transmit timed out
Jun 27 21:56:27 lapd eth4: Tx queue start entry 4 dirty entry 0.
Jun 27 21:56:27 lapd eth4: Tx descriptor 0 is 00002000. (queue head)
Jun 27 21:56:27 lapd eth4: Tx descriptor 1 is 00002000.
Jun 27 21:56:27 lapd eth4: Tx descriptor 2 is 00002000.
Jun 27 21:56:27 lapd eth4: Tx descriptor 3 is 00002000.
Jun 27 21:56:27 lapd eth4: Setting half-duplex based on auto-negotiated partner ability 0000.
Jun 27 21:56:27 lapd eth4: Promiscuous mode enabled.
Jun 27 21:56:39 lapd NETDEV WATCHDOG: eth3: transmit timed out
Jun 27 21:56:39 lapd eth3: Tx queue start entry 4 dirty entry 0.
Jun 27 21:56:39 lapd eth3: Tx descriptor 0 is 00002000. (queue head)
Jun 27 21:56:39 lapd eth3: Tx descriptor 1 is 00002000.
Jun 27 21:56:39 lapd eth3: Tx descriptor 2 is 00002000.
Jun 27 21:56:39 lapd eth3: Tx descriptor 3 is 00002000.
Jun 27 21:56:39 lapd eth3: Setting 100mbps full-duplex based on auto-negotiated partner ability 45e1

How can I put the eths on different IRQs?
This is the IRQ router MAP table:
PCI->APIC IRQ transform: (B0,I6,P0) -> 5
PCI->APIC IRQ transform: (B0,I7,P3) -> 5
PCI->APIC IRQ transform: (B0,I7,P3) -> 5
PCI->APIC IRQ transform: (B0,I13,P0) -> 11
PCI->APIC IRQ transform: (B0,I14,P0) -> 11
PCI->APIC IRQ transform: (B0,I15,P0) -> 11
PCI->APIC IRQ transform: (B0,I16,P0) -> 11
PCI->APIC IRQ transform: (B0,I17,P0) -> 5
PCI->APIC IRQ transform: (B0,I18,P0) -> 11
PCI->APIC IRQ transform: (B0,I19,P0) -> 10

# cat /proc/interrupts
CPU0 CPU1
0: 51399 64321 IO-APIC-edge timer
1: 1981 2474 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
3: 1 0 IO-APIC-edge serial
5: 444 551 IO-APIC-level eth0
9: 0 1 IO-APIC-edge acpi
11: 8984 9458 IO-APIC-level ncr53c8xx, eth1, eth2, eth3, eth4
Here is my problem ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
12: 7375 9158 IO-APIC-edge PS/2 Mouse
14: 10644 8483 IO-APIC-edge ide0
15: 10 13 IO-APIC-edge ide1
NMI: 0 0
LOC: 115618 115638
ERR: 3
MIS: 2

I tried to change the IRQs with pirq and ether at the boot time but it
dosen't work.

Thanx,
Cosmin
--
NetAdm at "Alexandru Papiu Ilarian" Highschool Dej
e-mail: <[email protected]> LRU: #192084
phone: +40-264.211.421 int 25 +40-723.514.225
It's nice to be important
But is more important to be nice
---

---
Pentru dezabonare, trimiteti mail la
[email protected] cu subiectul 'unsubscribe rlug'.
REGULI, arhive si alte informatii: http://www.lug.ro/mlist/






2002-06-28 13:28:54

by Lech Szychowski

[permalink] [raw]
Subject: Re: IRQ sharing problem - 2.4.18 kernel

> Hi,
> I have a TYAN Tiger 200T M/B with 2xIntel PIII CPUs at 1GHz and 1,3GB RAM.
> I'm using RadHat up to date and 2.4.18 vanilla kernel. On heavy load on
> ethernet interfaces (eth1,2,3,4) and scsi controller which are on the same
> IRQ (11) my server stops responding.
[...]
> 11: 8984 9458 IO-APIC-level ncr53c8xx, eth1, eth2, eth3, eth4
> Here is my problem ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Is this a Tulip NIC? If so, have you tried using the de4x5 driver
rather than the tulip one?

--
Leszek.

-- [email protected] 2:480/33.7 -- REAL programmers use INTEGERS --
-- speaking just for myself...

2002-06-28 13:35:24

by Cosmin Matei (lkml)

[permalink] [raw]
Subject: Re: IRQ sharing problem - 2.4.18 kernel


> Is this a Tulip NIC? If so, have you tried using the de4x5 driver
> rather than the tulip one?

No. I have 2 Intel NICs and 3 RTL 8139 NICs ... the problems is not from
the driver.

Best Regards,
Cosmin

2002-06-29 08:34:26

by Cosmin Matei (lkml)

[permalink] [raw]
Subject: Re: IRQ sharing problem - 2.4.18 kernel


Hi!

> > No. I have 2 Intel NICs and 3 RTL 8139 NICs ... the problems is not from
> > the driver.
> Hmm. Not sure about that. I had same problems with my RTL 8139. Build a new
> kernel with CONFIG_8139TOO_PIO set. That's what solved it with my machine.


It dosen't works. If you have some experience in usage of pirq option
please tell me how to use tha option.

Thanx a lot for the answers,
Cosmin