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: <Pine.LNX.4.64.0703121504590.25767@potato.cts.ucla.edu>
Date:	Mon, 12 Mar 2007 15:09:07 -0700 (PDT)
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, Chris Stromsoe wrote:
> 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.

The above tests both work fine with the 2.6.20.1 sk98lin driver loaded as 
"modprobe sk98lin RlmtMode=DualNet".

I can change the MTU, add and remove eth2/eth3 from the bond, and up and 
down the interface.  It also works fine with different hardware (e100, 
e1000, tg3, bnx2).  Running both interfaces alone without the bonding 
driver also works (I can up and down the interfaces with no side-affects).




-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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ