From owner-freebsd-arm@freebsd.org Mon Sep 17 16:13:14 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05CD810A169C for ; Mon, 17 Sep 2018 16:13:14 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5148082907 for ; Mon, 17 Sep 2018 16:13:13 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w8HGD4iw076503 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 17 Sep 2018 09:13:05 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w8HGD4hr076502; Mon, 17 Sep 2018 09:13:04 -0700 (PDT) (envelope-from fbsd) Date: Mon, 17 Sep 2018 09:13:04 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Camcontrol reprobe da0 causes kernel panic Message-ID: <20180917161304.GA76451@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Sep 2018 16:13:14 -0000 Trying to run, in single-user on a pi3 at FreeBSD 12.0-ALPHA6 r338691 arm64 # camcontrol reprobe da0 instigated panic: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /usr/src/sys/cam/scsi/scsi_da.c:2123 cpuid = 0 time = 1537199321 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x28 pc = 0xffff00000069b2ec lr = 0xffff0000000d952c sp = 0xffff0000517c8410 fp = 0xffff0000517c8620 db_trace_self_wrapper() at vpanic+0x1a8 pc = 0xffff0000000d952c lr = 0xffff000000388a18 sp = 0xffff0000517c8630 fp = 0xffff0000517c86e0 vpanic() at panic+0x44 pc = 0xffff000000388a18 lr = 0xffff0000003887c4 sp = 0xffff0000517c86f0 fp = 0xffff0000517c8770 panic() at __mtx_lock_sleep+0x3f8 pc = 0xffff0000003887c4 lr = 0xffff000000369924 sp = 0xffff0000517c8780 fp = 0xffff0000517c87f0 __mtx_lock_sleep() at __mtx_lock_flags+0xe0 pc = 0xffff000000369924 lr = 0xffff000000369440 sp = 0xffff0000517c8800 fp = 0xffff0000517c8840 __mtx_lock_flags() at daasync+0x64 pc = 0xffff000000369440 lr = 0xffff0000000364e8 sp = 0xffff0000517c8850 fp = 0xffff0000517c88a0 daasync() at xpt_async_process_dev+0x204 pc = 0xffff0000000364e8 lr = 0xffff00000001f5cc sp = 0xffff0000517c88b0 fp = 0xffff0000517c8900 xpt_async_process_dev() at xptdevicetraverse+0x9c pc = 0xffff00000001f5cc lr = 0xffff00000001e5b4 sp = 0xffff0000517c8910 fp = 0xffff0000517c8950 xptdevicetraverse() at xpttargettraverse+0x78 pc = 0xffff00000001e5b4 lr = 0xffff00000001e320 sp = 0xffff0000517c8960 fp = 0xffff0000517c89a0 xpttargettraverse() at xpt_async_process+0x130 pc = 0xffff00000001e320 lr = 0xffff00000001b2ec sp = 0xffff0000517c89b0 fp = 0xffff0000517c8ac0 xpt_async_process() at xpt_done_process+0x358 pc = 0xffff00000001b2ec lr = 0xffff00000001bcb8 sp = 0xffff0000517c8ad0 fp = 0xffff0000517c8af0 xpt_done_process() at xpt_done_td+0x104 pc = 0xffff00000001bcb8 lr = 0xffff00000001dac0 sp = 0xffff0000517c8b00 fp = 0xffff0000517c8b50 xpt_done_td() at fork_exit+0x7c pc = 0xffff00000001dac0 lr = 0xffff00000034b0d4 sp = 0xffff0000517c8b60 fp = 0xffff0000517c8b90 fork_exit() at fork_trampoline+0x10 pc = 0xffff00000034b0d4 lr = 0xffff0000006b572c sp = 0xffff0000517c8ba0 fp = 0x0000000000000000 KDB: enter: panic [ thread pid 7 tid 100033 ] Stopped at 0 db> The circumstance was a desire to enlarge a partition, da0p7, mounted on /usr/ports, which turned out to be too small. The man page for growfs suggests using for my predicament camcontrol reprobe da0 gpart recover da0 gpart resize -i 7 da0 growfs /dev/da0p7 There's nothing irreplaceable on the system, I just wanted to see if www/chromium will build and run. The root filesystem is on mmcsd0. Thanks for reading, and any workarounds. bob prohaska