Date: Thu, 4 Dec 2014 09:46:47 +0100 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= <roger.pau@citrix.com> To: "David P. Discher" <dpd@dpdtech.com> Cc: freebsd-xen@freebsd.org Subject: Re: Attempting to Get Xen FreeBSD Dom0 working Message-ID: <54801F77.5050700@citrix.com> In-Reply-To: <7C356027-01D8-4800-B211-282566BC9871@dpdtech.com> References: <481F7D02-BFE9-4E35-A475-5A8A05A801CE@dpdtech.com> <547DFCC0.6030003@citrix.com> <DCB954B5-0E45-4DE6-AAC4-C5ACF7FD90A7@dpdtech.com> <547F1476.8080305@citrix.com> <29437DB9-7DC8-47A8-8FC4-2BFDE736B5BC@dpdtech.com> <547F59B4.1010105@citrix.com> <2DDCAA68-3B11-4E3C-AE61-EAD8CEEF1E2D@dpdtech.com> <547F6AC1.9060709@citrix.com> <BBBFE7EC-BB42-4514-9A68-437ECAB8E640@dpdtech.com> <7C356027-01D8-4800-B211-282566BC9871@dpdtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, El 04/12/14 a les 3.27, David P. Discher ha escrit: > So, the “working” part … the hypervisor up, and Dom0 running, is correct. > > However, after ~5 minutes, the AHCI buses timeout. This seems to be constantly > reproducible via Dom0. FreeBSD on the this bare metal does’t have this issue. If you boot Xen with iommu=debug, do you see any messages on the Xen console? My test boxes also use AHCI, but the chipset is not exactly the same (mine is ICH8, yours is ICH10). Do you do anything specific to trigger the timeout, or just leaving Dom0 in an idle state also triggers this? Could you switch to the Xen console and post the output of the "i" debug key when this happens? Also, you can try to play with the AHCI driver sysctls, to see if some of them have any effect. I would recommend trying to disable MSI interrupts (hint.ahci.X.msi=0) and power control (hint.ahcich.X.pm_level=0). Roger.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54801F77.5050700>