linux-kernel - Re: 3.6.11 AMD-Vi: Completion-Wait loop timed out

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <50FFF15E.7010403@xs4all.nl>
Date:	Wed, 23 Jan 2013 15:19:10 +0100
From:	Udo van den Heuvel <udovdh@...all.nl>
To:	Suravee Suthikulanit <suravee.suthikulpanit@....com>
CC:	Boris Ostrovsky <boris.ostrovsky@....com>,
	Jacob Shin <jacob.shin@....com>,
	Borislav Petkov <bp@...en8.de>,
	Jörg Rödel <joro@...tes.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 3.6.11  AMD-Vi: Completion-Wait loop timed out

On 2013-01-23 00:29, Suravee Suthikulanit wrote:
> I sent out a patch
> (http://marc.info/?l=linux-kernel&m=135889686523524&w=2) which should
> implement
> the workaround for AMD processor family15h model 10-1Fh erratum 746 in
> the IOMMU driver.
> In your case, the output from "setpci -s 00:00.02 F4.w" is "0050" which
> tells me that BIOS doesn't
> implement the work around. After patching, you should see the following
> message in "dmesg".
> 
> "AMD-Vi: Applying erratum 746 for IOMMU at 0000:00:00.2"

Thanks!
I'll check for that after these messages.

> The following patch slightly modify
> the code to always issue "COMPLETION_WAIT" after every command.  This
> should help increasing the chance of reproducing
> the issue.

Should I test with these two patches together?
Or should I apply the first one first and then see what the second can help?


Kind regards,
Udo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/