netdev - Re: PROBLEM: A set of networking related oopses

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <2DAAA71E-5F03-41CA-B7E0-5BE4073D14F5@solitudo.net>
Date:	Sun, 9 Mar 2008 18:58:47 +0200
From:	Tuomas Jormola <tj@...itudo.net>
To:	Jarek Poplawski <jarkao2@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: PROBLEM: A set of networking related oopses


On 8 Mar 2008, at 19:57, Jarek Poplawski wrote:

> On Sat, Mar 08, 2008 at 06:13:55PM +0200, Tuomas Jormola wrote:
> ...
>> (18:08:32)(tj@...kti)(~)$ cat /proc/interrupts
>>           CPU0       CPU1
> ...
>> 18:     875645     873991   IO-APIC-fasteoi   uhci_hcd:usb1,
>> uhci_hcd:usb6, eth0
>> 19:          2          1   IO-APIC-fasteoi   uhci_hcd:usb5, ohci1394
>> 20:          0          0   IO-APIC-fasteoi   uhci_hcd:usb2
>> 21:          0          0   IO-APIC-fasteoi   uhci_hcd:usb4,
>> ehci_hcd:usb8
>> 22:          4          3   IO-APIC-fasteoi   heci
>> 217:     498561     498427   PCI-MSI-edge      eth1
>> 218:   88587922   88715380   PCI-MSI-edge      ahci
> ...
>> So I would be able to bind eth0 to CPU0 by running
>>
>> echo 1 > /proc/irq/18/smp_affinity
>>
>> right? http://www.cs.uwaterloo.ca/~brecht/servers/apic/SMP-affinity.txt
>> says that smp affinity only works for drivers that support IO-APIC.  
>> The
>> eth1 card is an old Intel card, and looks like it doesn't support  
>> this. I
>> guess I'll replace the card with a newer one.
>
> Should be right. If it's possibile, you can try if moving eth0 to
> another slot could give it it's own irq.

> I think it should work with both of your cards: eth1 uses newer type
> of interrupts - are you sure it's e100?
No, eth0 is the one driven by e100 driver. The card itself is probably  
ten years old. So it's old but it has always been a reliable work  
horse for me :) eth1 is embedded on the Intel motherboard. It's brand  
new and it's driven by e1000e driver. I'm not sure which interface's  
interrupts are giving these oopses. The machine was booted two days  
ago, and after that, still no oopses, though net traffic has been  
quite light. Should there be new oopses, I will replace the old card  
with a newer Intel gigabit card that I have laying around, and put it  
in a different PCI slot.

>
>
> You can also check if it really fixes the problem by booting with
> a kernel parameter: noirqbalance.
Ok, thanks for the info. I'll try that if changing the card doesn't  
help.

-- 
Tuomas Jormola <tj@...itudo.net>



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html