From owner-freebsd-net@FreeBSD.ORG Fri Feb 28 01:21:40 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D1C9C48F for ; Fri, 28 Feb 2014 01:21:40 +0000 (UTC) Received: from mail-lb0-x244.google.com (mail-lb0-x244.google.com [IPv6:2a00:1450:4010:c04::244]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4611B1BC6 for ; Fri, 28 Feb 2014 01:21:40 +0000 (UTC) Received: by mail-lb0-f196.google.com with SMTP id 10so793081lbg.7 for ; Thu, 27 Feb 2014 17:21:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Yr/aM/YYV431gwi/K4AnE9LfYl7VKwAJMSH5ofsgmtk=; b=egN4wtkh1i5SSImNEFxhmFO/NKZIuFmln0PYA5yUQaCeROeRPTN5N7in3HTFhbrjVS bTbXfOYAnWmgTcla279F3oNLbWS/Dvo3xIuZHF/8NozeQ6M7rEViwaPZZo5/K/Rq2GKi uqft602byPYSDB/0lwCe0JPjSMfeA3v+EWutxd8x9MHuRhcPixsBaDyFkaUONDH6FXIH JByV948zkjPQCsXkT+5p8RupOlzAyiHcn/SUcH18CztqaNv5OSaHXUB8bqqlwSnURnu5 ZfO1Byh9BWiDLM9guQwhj60BIlBqO4hIJPX2PDcWKMBATjdJtM0DvWAd+m+FyCK6vlgS gF7A== MIME-Version: 1.0 X-Received: by 10.112.43.70 with SMTP id u6mr8359334lbl.30.1393550498197; Thu, 27 Feb 2014 17:21:38 -0800 (PST) Received: by 10.114.4.82 with HTTP; Thu, 27 Feb 2014 17:21:37 -0800 (PST) Date: Thu, 27 Feb 2014 17:21:37 -0800 Message-ID: Subject: Panic when downing interface From: olivier To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Feb 2014 01:21:40 -0000 Hi all, The following kernel panic often happens for me after downing an Infiniband interface (i.e. calling ifconfig ib0 down). It happens both under 9-STABLE and 10-STABLE. The stack trace doesn't look Infiniband-specific so I'm not sending to the Infiniband mailing list for now. Details for 9-STABLE are as follows: panic: sbdrop cpuid = 25 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a/frame 0xffffffbff8b97480 kdb_backtrace() at kdb_backtrace+0x37/frame 0xffffffbff8b97540 panic() at panic+0x1ce/frame 0xffffffbff8b97640 sbdrop_internal() at sbdrop_internal+0x323/frame 0xffffffbff8b97680 sbflush_internal() at sbflush_internal+0x3b/frame 0xffffffbff8b976a0 sbflush() at sbflush+0x3b/frame 0xffffffbff8b976c0 tcp_disconnect() at tcp_disconnect+0x46/frame 0xffffffbff8b976f0 tcp_usr_disconnect() at tcp_usr_disconnect+0x10f/frame 0xffffffbff8b97710 soclose() at soclose+0x53/frame 0xffffffbff8b97740 _fdrop() at _fdrop+0x23/frame 0xffffffbff8b97760 closef() at closef+0x4c/frame 0xffffffbff8b97810 fdfree() at fdfree+0x23c/frame 0xffffffbff8b978d0 exit1() at exit1+0x330/frame 0xffffffbff8b97940 sys_sys_exit() at sys_sys_exit+0xe/frame 0xffffffbff8b97950 amd64_syscall() at amd64_syscall+0x5ea/frame 0xffffffbff8b97a70 Xfast_syscall() at Xfast_syscall+0xf7/frame 0xffffffbff8b97a70 (kgdb) list *(sbdrop_internal+0x323) 0xffffffff8099b823 is at /usr/src/sys/kern/uipc_sockbuf.c:855. 850 851 next = (m = sb->sb_mb) ? m->m_nextpkt : 0; 852 while (len > 0) { 853 if (m == 0) { 854 if (next == 0) 855 panic("sbdrop"); 856 m = next; 857 next = m->m_nextpkt; 858 continue; 859 } FreeBSD 9.2 r255606 compiled with options OFED # Infiniband protocol device mlx4ib # ConnectX Infiniband support device mlxen # ConnectX Ethernet support device mthca # Infinihost cards device ipoib # IP over IB devices Mellanox ConnectX HCA Ethernet driver v1.5.2 (July 2010) Mellanox ConnectX InfiniBand driver v1.0-ofed1.5.2 (August 4, 2010) output of ifconfig ib0: ib0: flags=8043 metric 0 mtu 2044 options=8009b lladdr 0.0.0.48.fe.80.0.0.0.0.0.0.0.2.c9.3.0.4f.ae.f1 inet 192.168.192.2 netmask 0xffffff00 broadcast 192.168.192.255 inet6 fe80::225:90ff:fe59:b78%ib0 prefixlen 64 scopeid 0xb nd6 options=29 Happy to provide more detail if that helps anyone look into this problem. Thanks Olivier