From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Greear Subject: Re: IPv6 FIB related crash with MACVLANs in 3.9.11+ kernel. Date: Sat, 08 Feb 2014 08:43:32 -0800 Message-ID: <52F65EB4.1050306@candelatech.com> References: <52EFFE20.5080500@candelatech.com> <20140203220323.GB17999@order.stressinduktion.org> <52F012FF.9030105@candelatech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit To: netdev Return-path: Received: from mail.candelatech.com ([208.74.158.172]:41798 "EHLO ns3.lanforge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751532AbaBHQnd (ORCPT ); Sat, 8 Feb 2014 11:43:33 -0500 Received: from [192.168.100.236] (firewall.candelatech.com [70.89.124.249]) (authenticated bits=0) by ns3.lanforge.com (8.14.2/8.14.2) with ESMTP id s18GhWoP011501 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 8 Feb 2014 08:43:32 -0800 In-Reply-To: <52F012FF.9030105@candelatech.com> Sender: netdev-owner@vger.kernel.org List-ID: On 02/03/2014 02:06 PM, Ben Greear wrote: > On 02/03/2014 02:03 PM, Hannes Frederic Sowa wrote: >> Hi Ben, >> >> On Mon, Feb 03, 2014 at 12:37:52PM -0800, Ben Greear wrote: >>> The kernel has some additional patches, but not much to IPv6. >>> >>> The bug is that when we have lots of mac-vlans on some ixgbe ports >>> (500 per interface in this case), and boot up the system with the ports unplugged, >>> we get this crash almost every time. Boot-up is going to do normal bootup >>> stuff plus create and configure the 1000 mac-vlans, dump their routing >>> tables, etc. >>> >>> We are using one routing table per network device, and some >>> ip rules. >>> >>> If we plug in the ixgbe ports, we do not ever see a crash. >>> >>> We have not yet tried reproducing it on other drivers, but I suspect >>> the issue is not related to ixgbe. >>> >>> Any ideas on this one? >> >> Could you bring the machine to a panic again with enabling RT6_DEBUG at the >> top of ip6_fib.c and send a dump of the trace? > > Yes, but it will be a bit until we can create a duplicate machine. > We ended up delivering the machine with a note to make sure the > interfaces were plugged in (we found the bug hours before shipping > the system, of course). According to my system test guy, it took a lot longer to reproduce the problem with the debug enabled kernel, but I do not see any extra debug messages on the serial console logging or in /var/log/messages Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com