All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: ojab // <ojab-uv7J75MkRmE@public.gmane.org>
Cc: Tom Lendacky <thomas.lendacky-5C7GfCeVMHo@public.gmane.org>,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Boot hangs with "AMD-Vi Command Buffer Timeout"
Date: Thu, 26 Apr 2018 17:22:33 +0200	[thread overview]
Message-ID: <20180426152233.GP15462@8bytes.org> (raw)
In-Reply-To: <CAKzrAgQN-qML3-kheKxwAH3aUwny5UNp1vcDKAEEuh0S+4hyTg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

I've added some AMD people to Cc. Suravee, Tom, any ideas here? One of
the screen-shots behind the link below show IOTLB_INV_TIMEOUT errors, so
it is likely ATS related. Maybe you guys can reproduce it on your side?


Thanks,

	Joerg


On Thu, Apr 26, 2018 at 10:28:47AM +0000, ojab // wrote:
> I've made a bugzilla issue [1] about it, but I'm not sure if anyone
> reading bugzilla reports, so duplicating here.
> I have raven ridge APU (2400g) + ASUS A320M-K motherboard and boot
> (4.16.4 & 4.17-rc2) hangs printing many `[    0.001000] AMD-Vi Command
> Buffer Timeout` messages. With IOMMU disabled (either via EFI/BIOS or
> using amd_iommu=off) it boots fine.
> 
> What info is needed to debug/fix it?
> 
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=199513
> 
> //wbr ojab

  parent reply	other threads:[~2018-04-26 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 10:28 Boot hangs with "AMD-Vi Command Buffer Timeout" ojab //
     [not found] ` <CAKzrAgQN-qML3-kheKxwAH3aUwny5UNp1vcDKAEEuh0S+4hyTg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-04-26 15:22   ` Joerg Roedel [this message]
     [not found]     ` <20180426152233.GP15462-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2018-04-26 16:25       ` Gary R Hook
     [not found]         ` <fd019529-d65e-8739-d6d1-4c5d5606dac0-5C7GfCeVMHo@public.gmane.org>
2018-04-26 16:51           ` ojab //
     [not found]             ` <CAKzrAgSxxWjaH4U=aEsEkxBoZ+V5unGkADRcB=Zfm2BTQtS4ag-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-04-26 16:57               ` ojab //

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=20180426152233.GP15462@8bytes.org \
    --to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=ojab-uv7J75MkRmE@public.gmane.org \
    --cc=thomas.lendacky-5C7GfCeVMHo@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 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.