Peter Stuge schrieb:
The first column is the interrupt number, 11. The second is the interrupt count since Linux start. 354 interrupts. Third is the mode that the interrupt controller is running in. AMD, is XT-PIC-XT correct for the LX platform? Fourth is the list of drivers/interfaces that are sharing this interrupt.
Since it's shared between eth0 and USB we can't see reliably if you are getting interrupts from the NIC.
Start with disabling USB until this is solved. Then look at the interrupt count before and after trying to communicate with the system. When running iperf the number should increase fairly steadily.
Again, it's important to disable USB (unloading the driver is enough) so that you can be sure of the interrupt source.
I have unloaded the usb stuff. I have cated the interrupts before and after iperf...:
---------------------------------- # cat /proc/interrupts CPU0 0: 1268114 XT-PIC-XT timer 2: 0 XT-PIC-XT cascade 4: 934 XT-PIC-XT serial 11: 4330 XT-PIC-XT eth0 14: 907 XT-PIC-XT ide0 NMI: 0 LOC: 0 ERR: 6 MIS: 0
# iperf -s ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 85.3 KByte (default) ------------------------------------------------------------ [ 6] local 192.168.2.58 port 5001 connected with 192.168.2.2 port 32948 [ 6] 0.0-11.6 sec 1.66 MBytes 1.20 Mbits/sec
meshnode:~# cat /proc/interrupts CPU0 0: 1322253 XT-PIC-XT timer 2: 0 XT-PIC-XT cascade 4: 937 XT-PIC-XT serial 11: 6418 XT-PIC-XT eth0 14: 907 XT-PIC-XT ide0 NMI: 0 LOC: 0 ERR: 6 MIS: 0
----------------------------------