From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Failed to access register with invalid access size alignment Date: Fri, 4 Apr 2014 09:59:40 -0400 Message-ID: <20140404135940.GB19478@phenom.dumpdata.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Zytaruk, Kelly" Cc: "Xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Wed, Apr 02, 2014 at 07:28:44PM +0000, Zytaruk, Kelly wrote: > I have seen the subject-line error message in a few posts but I haven't yet seen a resolution for it yet. Has anyone resolved this problem? > > The full error line from the log file is; > [00:05.0] xen_pt_pci_config_access_check: Error: Failed to access register with invalid access size alignment. (addr: 0x0e, len: 4) > You could instrument QEMU to pause the guest immediately when this happens. Then you can use xen_hvmtrace to figure the EIP and get an idea of where things are. > Address 0x0e in PCIe config space is 2 byte aligned and can't be accessed as a 4 byte read. > > I am passing an AMD graphics adapter into a guest as a secondary adapter. I can connect with VNC and the PCI passthrough is successful as I can see the [00:05.0] device in Win7 device Manager but the device is "banged out" with the error "Windows has stopped this device because it has reported problems. (Code 43)". > > The error occurs with both QEMU-upstream and QEMU-traditional. > My configuration is Xen 4.5-unstable on Linux 3.13.4. > > Thanks, > Kelly > > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel