All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Zytaruk, Kelly" <Kelly.Zytaruk@amd.com>
Cc: "Xen-devel@lists.xen.org" <Xen-devel@lists.xen.org>
Subject: Re: Failed to access register with invalid access size alignment
Date: Fri, 4 Apr 2014 09:59:40 -0400	[thread overview]
Message-ID: <20140404135940.GB19478@phenom.dumpdata.com> (raw)
In-Reply-To: <B756807489D6244883AC0B799A6EEC15F44219@storexdag02.amd.com>

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

  parent reply	other threads:[~2014-04-04 13:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 19:28 Failed to access register with invalid access size alignment Zytaruk, Kelly
2014-04-03  8:40 ` Jan Beulich
2014-04-03 13:29   ` Zytaruk, Kelly
2014-04-09 15:32     ` Zytaruk, Kelly
2014-04-09 15:39       ` Jan Beulich
2014-04-10 14:06         ` Zytaruk, Kelly
2014-04-10 14:14           ` Andrew Cooper
2014-04-10 15:18             ` Zytaruk, Kelly
2014-09-23 15:16   ` Zytaruk, Kelly
2014-04-04 13:59 ` Konrad Rzeszutek Wilk [this message]
2014-04-04 14:33   ` Zytaruk, Kelly
2014-04-04 16:51     ` Konrad Rzeszutek Wilk
2014-04-21  6:16 ` Nick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140404135940.GB19478@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Kelly.Zytaruk@amd.com \
    --cc=Xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.