Date: Wed, 16 Oct 2019 10:36:46 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= <royger@freebsd.org> To: Brian Buhrow <buhrow@nfbcal.org> Cc: freebsd-xen@freebsd.org Subject: Re: i/o is very slow on FreeBSD dom0 with Xen-4.12 and Freebsd-12 Message-ID: <20191016083646.GC14005@Air-de-Roger> In-Reply-To: <201910151556.x9FFuNUA011130@lothlorien.nfbcal.org> References: <20191015082655.GB14005@Air-de-Roger> <201910151556.x9FFuNUA011130@lothlorien.nfbcal.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 15, 2019 at 08:56:22AM -0700, Brian Buhrow wrote: > 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? Hm, it's not so much that the autodetection is wrong, AFAIK there's some hardware issue with specific models that make the new ack method not work properly. This is limited to very specific (and older) models. Note that you might still see interrupt timeouts with the old ack method. I will try to figure out if there's any hardware errata that could be related to this issue, and try to find a box to reproduce (this might not be feasible since I'm not sure I have anything similar to your hardware available). Roger.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191016083646.GC14005>