Linux IOMMU Development
 help / color / mirror / Atom feed
From: "jroedel@suse.de" <jroedel@suse.de>
To: "Merger, Edgar [AUTOSOL/MAS/AUGS]" <Edgar.Merger@emerson.com>
Cc: "iommu@lists.linux-foundation.org" <iommu@lists.linux-foundation.org>
Subject: Re: [EXTERNAL] Re: amdgpu error whenever IOMMU is enabled
Date: Wed, 4 Nov 2020 11:14:54 +0100	[thread overview]
Message-ID: <20201104101454.GR22179@suse.de> (raw)
In-Reply-To: <MWHPR10MB13109574BDA0F1D8219A225C89EF0@MWHPR10MB1310.namprd10.prod.outlook.com>

On Wed, Nov 04, 2020 at 09:21:35AM +0000, Merger, Edgar [AUTOSOL/MAS/AUGS] wrote:
> AMD-Vi: Completion-Wait loop timed out is at [65499.964105] but amdgpu-error is at [   52.772273], hence much earlier.

Yes, but it could be the same underlying reason.

> Have not tried to use an upstream kernel yet. Which one would you recommend?

For a first try, use 5.9.3. If it reproduces there, please try booting
with "pci=noats" on the kernel command line.

Please also send me the output of 'lspci -vvv' and 'lspci -t' of the
machine where this happens.

Regards,

	Joerg


> 
> As far as inconsistencies in the PCI-setup is concerned, the only thing that I know of right now is that we haven´t entered a PCI subsystem vendor and device ID yet. It is still "Advanced Micro Devices". We will change that soon to "General Electric" or "Emerson".
> 
> Best regards,
> Edgar
> 
> -----Original Message-----
> From: jroedel@suse.de <jroedel@suse.de> 
> Sent: Mittwoch, 4. November 2020 09:53
> To: Merger, Edgar [AUTOSOL/MAS/AUGS] <Edgar.Merger@emerson.com>
> Cc: iommu@lists.linux-foundation.org
> Subject: [EXTERNAL] Re: amdgpu error whenever IOMMU is enabled
> 
> Hi Edgar,
> 
> On Fri, Oct 30, 2020 at 02:26:23PM +0000, Merger, Edgar [AUTOSOL/MAS/AUGS] wrote:
> > With one board we have a boot-problem that is reproducible at every ~50 boot.
> > The system is accessible via ssh and works fine except for the 
> > Graphics. The graphics is off. We don´t see a screen. Please see 
> > attached “dmesg.log”. From [52.772273] onwards the kernel reports 
> > drm/amdgpu errors. It even tries to reset the GPU but that fails too. 
> > I tried to reset amdgpu also by command “sudo cat /sys/kernel/debug/dri/N/amdgpu_gpu_recover”. That did not help either.
> 
> Can you reproduce the problem with an upstream kernel too?
> 
> These messages in dmesg indicate some problem in the platform setup:
> 
> 	AMD-Vi: Completion-Wait loop timed out
> 
> Might there be some inconsistencies in the PCI setup between the bridges and the endpoints or something?
> 
> Regards,
> 
> 	Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2020-11-04 10:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30 14:26 amdgpu error whenever IOMMU is enabled Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-11-03  9:21 ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-11-04  8:53 ` jroedel
2020-11-04  9:21   ` [EXTERNAL] " Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-11-04 10:14     ` jroedel [this message]
2020-11-04 14:19       ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-11-04 14:35         ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-11-05 11:15           ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-11-05 11:58             ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-11-05 12:32               ` jroedel
2020-11-06  5:51                 ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-11-06 12:18                   ` jroedel
2020-11-06 13:03                     ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-11-06 14:06                       ` jroedel
2020-11-06 14:28                         ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-11-06 14:32                           ` jroedel
2020-11-09  5:33                             ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2020-11-23  6:41                               ` Merger, Edgar [AUTOSOL/MAS/AUGS]
2021-01-15  8:18                                 ` jroedel
2021-01-15 13:15                                   ` Merger, Edgar [AUTOSOL/MAS/AUGS]

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=20201104101454.GR22179@suse.de \
    --to=jroedel@suse.de \
    --cc=Edgar.Merger@emerson.com \
    --cc=iommu@lists.linux-foundation.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