From owner-freebsd-xen@freebsd.org Tue Oct 15 08:27:02 2019 Return-Path: Delivered-To: freebsd-xen@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 795C11577B2 for ; Tue, 15 Oct 2019 08:27:02 +0000 (UTC) (envelope-from royger@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46spSQ2gTPz3NLF; Tue, 15 Oct 2019 08:27:02 +0000 (UTC) (envelope-from royger@freebsd.org) Received: from localhost (unknown [212.230.157.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: royger) by smtp.freebsd.org (Postfix) with ESMTPSA id D15C610EFB; Tue, 15 Oct 2019 08:27:01 +0000 (UTC) (envelope-from royger@freebsd.org) Date: Tue, 15 Oct 2019 10:26:55 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Brian Buhrow Cc: freebsd-xen@freebsd.org Subject: Re: i/o is very slow on FreeBSD dom0 with Xen-4.12 and Freebsd-12 Message-ID: <20191015082655.GB14005@Air-de-Roger> References: <201910142145.x9ELj4c8008732@lothlorien.nfbcal.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201910142145.x9ELj4c8008732@lothlorien.nfbcal.org> User-Agent: Mutt/1.12.2 (2019-09-21) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Oct 2019 08:27:02 -0000 On Mon, Oct 14, 2019 at 02:45:04PM -0700, Brian Buhrow wrote: > hello. Using: ioapic_ack=old causes the dom0 to crash. Below are the > logs. Does the crash happen every time you boot with ioapic_ack=old? [...] > dev = gpt/gptroot, block = 1, fs = / > panic: ffs_blkfree_cg: freeing free block > cpuid = 2 > time = 1571088217 > KDB: stack backtrace: > #0 0xffffffff80be78d7 at kdb_backtrace+0x67 > #1 0xffffffff80b9b4b3 at vpanic+0x1a3 > #2 0xffffffff80b9b303 at panic+0x43 > #3 0xffffffff80e87345 at ffs_blkrelease_finish+0x6e5 > #4 0xffffffff80e8433d at ffs_blkfree+0xad > #5 0xffffffff80eb10af at softdep_get_depcounts+0x48bf > #6 0xffffffff80eb0fe5 at softdep_get_depcounts+0x47f5 > #7 0xffffffff80ea195a at softdep_update_inodeblock+0x178a > #8 0xffffffff80eab94a at softdep_request_cleanup+0xa8a > #9 0xffffffff80e95272 at softdep_flushworklist+0x1a2 > #10 0xffffffff80e991df at softdep_unmount+0x4af > #11 0xffffffff80b5be83 at fork_exit+0x83 > #12 0xffffffff8105061e at fork_trampoline+0xe > Uptime: 1m59s > Automatic reboot in 15 seconds - press a key on the console to abort This looks like a file system error, likely some corruption caused by previous reboots? Ie: I'm not sure this is caused by Xen or rather by underlying errors in the filesystem. At least there are no hardware errors on the log AFAICT. Thanks, Roger.