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: <50FEBE5D.7040905@xs4all.nl>
Date:	Tue, 22 Jan 2013 17:29:17 +0100
From:	Udo van den Heuvel <udovdh@...all.nl>
To:	Boris Ostrovsky <boris.ostrovsky@....com>
CC:	suravee.suthikulpanit@....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-22 17:12, Boris Ostrovsky wrote:
>> Seen once over here. Correlated with raid-check.
> 
> Then the answer from Gigabyte doesn't prove anything. You can also boot
> Linux without seeing this problem in most cases.

That was my situation until the first time it hit.

> Your BIOS does not have the required erratum workaround. We will provide
> a patch to close that hole but since the problem is not easily
> reproducible (and the erratum is also not easy to trigger) it may be
> difficult to say whether it really helped with your problem.

Can we think of certain loads/actions/etc that could help trigger the issue?
Then if reproducing is easier we can better say if stuff is actually
fixed after the workaround.

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/