From owner-freebsd-xen@freebsd.org  Tue Oct 15 15:56:28 2019
Return-Path: <owner-freebsd-xen@freebsd.org>
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 BA3BE14BD59
 for <freebsd-xen@mailman.nyi.freebsd.org>;
 Tue, 15 Oct 2019 15:56:28 +0000 (UTC)
 (envelope-from buhrow@lothlorien.nfbcal.org)
Received: from lothlorien.nfbcal.org (ns.NFBCAL.ORG [157.22.230.125])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "nfbcal.org", Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 46t0R03hLTz4Q5y;
 Tue, 15 Oct 2019 15:56:28 +0000 (UTC)
 (envelope-from buhrow@lothlorien.nfbcal.org)
Received: from lothlorien.nfbcal.org (localhost [127.0.0.1])
 by lothlorien.nfbcal.org (8.15.2/8.14.1-NFBNETBSD) with ESMTPS id
 x9FFuNaZ010075
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Tue, 15 Oct 2019 08:56:23 -0700 (PDT)
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.97.3 at lothlorien.nfbcal.org
Received: (from buhrow@localhost)
 by lothlorien.nfbcal.org (8.15.2/8.12.11) id x9FFuNUA011130;
 Tue, 15 Oct 2019 08:56:23 -0700 (PDT)
Message-Id: <201910151556.x9FFuNUA011130@lothlorien.nfbcal.org>
From: Brian Buhrow <buhrow@nfbcal.org>
Date: Tue, 15 Oct 2019 08:56:22 -0700
In-Reply-To: <20191015082655.GB14005@Air-de-Roger>
X-Mailer: Mail User's Shell (7.2.6 beta(4.pl1)+dynamic 20000103)
To: Roger Pau =?iso-8859-1?Q?Monn=E9?= <royger@freebsd.org>
Subject: Re: i/o is very slow on FreeBSD dom0 with Xen-4.12 and Freebsd-12
Cc: freebsd-xen@freebsd.org, buhrow@nfbcal.org
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (lothlorien.nfbcal.org [127.0.0.1]); Tue, 15 Oct 2019 08:56:24 -0700 (PDT)
X-Rspamd-Queue-Id: 46t0R03hLTz4Q5y
X-Spamd-Bar: -----
Authentication-Results: mx1.freebsd.org;
	none
X-Spamd-Result: default: False [-6.00 / 15.00];
 NEURAL_HAM_MEDIUM(-1.00)[-0.996,0];
 NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]
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
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Oct 2019 15:56:28 -0000

	hello Roger.  Sorry, my bad.  I didn't even look at the cause of the
panic.   Rebooting the system caused it to come up clean after another pass
with fsck.  With the ioapic_ack=old argument, the system comes up right
away and is quite responsive.
	Can you explain how to select which argument to use on the command
line if the autoselection code doesn't work?

	Thank you for your help!

-Brian

On Oct 15, 10:26am, Roger Pau =?iso-8859-1?Q?Monn=E9?= wrote:
} Subject: Re: i/o is very slow on FreeBSD dom0 with Xen-4.12 and Freebsd-12
} 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: