From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: "G. Richard Bellamy" <rbellamy-1/AleqyZJC8ybS5Ee8rs3A@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:14.0 address=0x000000fdf9103300 flags=0x0600]
Date: Fri, 16 Oct 2015 11:02:54 +0200 [thread overview]
Message-ID: <20151016090254.GU27420@8bytes.org> (raw)
In-Reply-To: <CADw2B2N3VZdXVWTtotomZ2pZ3xb8ZEot=TR7j1gUq7-FM_R41w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, Oct 15, 2015 at 11:28:03PM -0700, G. Richard Bellamy wrote:
> Applied the patch, and no longer receiving the kernel error messages. Haven't
> tried to do anything with my VMs yet, but thought you'd want to know sooner
> than later.
Okay, thanks. It is possible that the issue only happens when you start
a VM, so it would be great if you could test this too.
Thanks,
Joerg
next prev parent reply other threads:[~2015-10-16 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 0:19 AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:14.0 address=0x000000fdf9103300 flags=0x0600] G. Richard Bellamy
[not found] ` <CADw2B2Mzo2DbMMiyTVjBGVc4-f6Koa6sWQjoLmfX7NZ3B4+saA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-11 19:37 ` G. Richard Bellamy
2015-10-14 9:06 ` Joerg Roedel
[not found] ` <20151014090649.GI27420-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-10-14 16:05 ` G. Richard Bellamy
[not found] ` <CADw2B2MzAMhNX5x9kZ5MN0mAh24ttDu=23EGVLy2aq6Paik4tQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-14 16:33 ` Joerg Roedel
[not found] ` <20151014163338.GR27420-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-10-14 23:47 ` G. Richard Bellamy
[not found] ` <CADw2B2MnBKOMvXOFNKo0-awM5oA7aYnEz0JgCqqOToVYYuzjZQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-16 6:28 ` G. Richard Bellamy
[not found] ` <CADw2B2N3VZdXVWTtotomZ2pZ3xb8ZEot=TR7j1gUq7-FM_R41w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-16 9:02 ` Joerg Roedel [this message]
[not found] ` <20151016090254.GU27420-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-10-16 22:02 ` G. Richard Bellamy
[not found] ` <CADw2B2PR7C1Uz+ewRM+686dZg7dPFRZ5szbfNqhSCFp-AG3zpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-16 22:02 ` G. Richard Bellamy
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=20151016090254.GU27420@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=rbellamy-1/AleqyZJC8ybS5Ee8rs3A@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox