From owner-freebsd-net@FreeBSD.ORG Wed Aug 29 17:30:50 2012 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8888C106566B for ; Wed, 29 Aug 2012 17:30:50 +0000 (UTC) (envelope-from vijju.singh@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 208AE8FC16 for ; Wed, 29 Aug 2012 17:30:49 +0000 (UTC) Received: by eaak11 with SMTP id k11so283296eaa.13 for ; Wed, 29 Aug 2012 10:30:48 -0700 (PDT) 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=ayaeLBWyyaPgi0rPMFkAFYykC/pQCllOjuknPPQd1oY=; b=yqD10ds8x1XSXCarYH+nUulOVKrNoKET2pZHV0e3t4GanyqY7TJ7ZlUxAfXkCBWWlh B9UAepYZZRj0E/IQxjOm5Ob5FV7sGc1pkrWle6IQMva2uAksB2wpT3tnUnaV5zuAB5pH FLDSntgCOjho7fl848gkFIMt8NRNl6RLtB3k655E1rTDVx+ExlCdxaZe5ZbLmJPgUGe0 ArpyNK6zM5OoJC4CVbkJNGA+5Clue39apwEQoKnI7Lk+xbxeJb6vc+IqfnCOlRbgR3PN p/0XYeJ4ldn3lFVcZFcCWFPzZyFWkrIhpte776YU7ByWQfY6WCqJYdXmk8jvlVTdGaeR AMOQ== MIME-Version: 1.0 Received: by 10.14.203.73 with SMTP id e49mr2955475eeo.27.1346261448850; Wed, 29 Aug 2012 10:30:48 -0700 (PDT) Received: by 10.14.219.134 with HTTP; Wed, 29 Aug 2012 10:30:48 -0700 (PDT) Date: Wed, 29 Aug 2012 10:30:48 -0700 Message-ID: From: Vijay Singh To: net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: witness warning in arp processing X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Aug 2012 17:30:50 -0000 All, I am seeing this warning on my 8.2 based system. taskqueue_drain with the following non-sleepable locks held: exclusive rw lle (lle) r = 0 (0xffffff0014dc9110) locked @ sys/netinet/in.c:1760 KDB: stack backtrace: kdb_backtrace() at kdb_backtrace+0x3e _witness_debugger() at _witness_debugger+0x24 witness_warn() at witness_warn+0x402 taskqueue_drain() at taskqueue_drain+0x36 cancel_delayed_work() at cancel_delayed_work+0x56 set_timeout() at set_timeout+0x18 netevent_callback() at netevent_callback+0x29 _handle_arp_update_event() at _handle_arp_update_event+0x31 in_arpinput() at in_arpinput+0xe92 arpintr() at arpintr+0x255 netisr_dispatch_src() at netisr_dispatch_src+0x14a netisr_dispatch() at netisr_dispatch+0x20 ether_demux() at ether_demux+0x281 ether_input_internal() at ether_input_internal+0x60c ether_nh_input() at ether_nh_input+0x1d netisr_dispatch_src() at netisr_dispatch_src+0x14a netisr_dispatch() at netisr_dispatch+0x20 ether_input() at ether_input+0xef lem_rxeof() at lem_rxeof+0x6ee lem_handle_rxtx() at lem_handle_rxtx+0x4f taskqueue_run_locked() at taskqueue_run_locked+0x145 taskqueue_thread_loop() at taskqueue_thread_loop+0x73 fork_exit() at fork_exit+0x180 fork_trampoline() at fork_trampoline+0xe Is this a known issue? Has it been fixed? -vijay