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, 08 Mar 2007 15:04:05 -0800
From:	Jay Vosburgh <fubar@...ibm.com>
To:	Chris Stromsoe <cbs@....ucla.edu>
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) 

Chris Stromsoe <cbs@....ucla.edu> wrote:

>It's active-backup.  Testing with the same setup and e100 works fine. I've
>done a few tests without the bonding module, using the dual-port
>separately.

	Somebody else a couple of weeks ago was having similar issues
running bonding with skge (in 802.3ad mode, in his case) that also
vanished with different hardware.  I don't have any skge hardware, so I
can't test it here.  His problem was a failure in 802.3ad negotiation,
not a system lockup, though.

	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).

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

	-J

---
	-Jay Vosburgh, IBM Linux Technology Center, fubar@...ibm.com
-
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