netdev - Re: skge- "soft lockup on CPU#0" with mtu=9000 (2.6.20.1 + web100 patch)

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]

Date:	Thu, 8 Mar 2007 15:13:16 -0800 (PST)
From:	Chris Stromsoe <cbs@....ucla.edu>
To:	Jay Vosburgh <fubar@...ibm.com>
cc:	Stephen Hemminger <shemminger@...ux-foundation.org>,
	netdev@...r.kernel.org
Subject: Re: skge- "soft lockup on CPU#0" with mtu=9000 (2.6.20.1 + web100
 patch) 

On Thu, 8 Mar 2007, Jay Vosburgh wrote:

> 	If you're running active-backup and not using the ARP monitor 
> (arp_interval), then I'm not aware of any possible locking problems in 
> bonding for the kernel version you reference (2.6.20.1).

I'm not using arp_interval.

On Thu, 8 Mar 2007, Jay Vosburgh wrote:
> Chris Stromsoe <cbs@....ucla.edu> wrote:
>
>> 1) ip link set mtu 9000 eth2  <-- eth2 is no longer responsive
>>    ip link set mtu 1500 eth2  <-- eth2 remains unresponsive
>>
>> 2) ifup eth2
>>    ifdown eth2
>>
>>    perl -pi -e 's/eth2/eth3/' /etc/network/interfaces
>>
>>    ifup eth3   <--  locks up here
>
> 	This would seem to suggest a problem with skge itself, although 
> there might be some other interaction with bonding that causes the 
> problems for that case.

In both of the above mentioned cases, I was not using bonding.  That was 
with the skge driver only.


-Chris
-
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