From owner-freebsd-current@freebsd.org Fri Jul 24 02:43:55 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1CDC99A8DA6 for ; Fri, 24 Jul 2015 02:43:55 +0000 (UTC) (envelope-from dieterich.joh@gmail.com) Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D376A151B for ; Fri, 24 Jul 2015 02:43:54 +0000 (UTC) (envelope-from dieterich.joh@gmail.com) Received: by obnw1 with SMTP id w1so8440606obn.3 for ; Thu, 23 Jul 2015 19:43:54 -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=MwfaHjEeMDAxakOhHU7NOq3ZeeNDPjFLGDQn1rY6mfg=; b=jKbn3lkHJ6zNxRYhCInBwydvzEnWn9NLLhDzUGmrYUg79+OPEge/cpXQgCkmKWugRT 23mteb0RbSyhLltyglxHAc0Rlz9ki4xxHHbfPjeW2xmT/KPttq1bCigljgnucH5S/GFo 3Vtt7gfTG0F32WY1Nbe0JglzEjuIuMIGeR33WpLGskAbmCnOO3CIHv2CsQRmiVyttvJY Hn5H5cDEWo2RNet7F+JKnAYl450JJt61Ax6ns2j16TmDrLJQZpccAHpLX0OKrBcAHIFT s2MFJB12lujNGhGgPV04la4h68YcmQjaz5as5ax/3PJvTVM8Wfu2HpqFV9QDvmKXFFnT +P8Q== MIME-Version: 1.0 X-Received: by 10.182.200.131 with SMTP id js3mr13246684obc.58.1437705834016; Thu, 23 Jul 2015 19:43:54 -0700 (PDT) Received: by 10.202.177.11 with HTTP; Thu, 23 Jul 2015 19:43:53 -0700 (PDT) Date: Thu, 23 Jul 2015 22:43:53 -0400 Message-ID: Subject: reproducible kernel panic on CURRENT, I/O related From: Johannes Dieterich To: freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 02:43:55 -0000 Dear all, since approximately three weeks I am seeing kernel panics on CURRENT that are in so far reproducible as that they typically occur when I run svn up on the ports tree. Hence, it seems I/O related to me. Sorry that I only now got around to reporting it! The system is a CURRENT amd64 running ZFS on root w/ GELI. It has the aesni kernel module loaded. The world and kernel are on SVN r285764. The kernel stack backtrace looks as follows (transcript): db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe03d0394830 vpanic() at vpanic+0x189/frame 0xffffe03d03948b0 panic() at panic+0x43/frame 0xfffffe03d0394910 trash_ctor() at trash_ctor+0x48/frame 0xfffffe03d0394920 uma_zalloc_arg() at uma_zalloc_arg+0x573/frame 0xfffffe03d0394990 g_clone_bio() at g_clone_bio+0x1d/frame 0xfffffe03d03949b0 g_part_start() at g_part_start+0x8e/frame 0xfffffe03d0394a30 g_io_schedule_down() at g_io_schedule_down+0xe6/frame 0xfffffe03d0394a60 g_down_procbody() at g_down_procbody+0x7d/frame 0xfffffee03d0394a70 fork_exit() at fork_exit+0x84/frame 0xfffffe03d0394ab0 fork_trampoline at fork_trampoline+0xe/frame 0xfffffe03d0394ab0 --- trap 0, rip = 0, rsp =0xfffffe03d0394b90, rbp = 0--- KDB: enter: panic [ thread pid 13 tid 100017 ] Stopped at kdb_enter+0x3e: movq $0,kdb_why Due to above setup, I cannot provide a core file, sorry. Please let me know if there is any data you want me to obtain for debugging. As I said above, it is fairly simple for me to hit the panic. Best Johannes