From: Borislav Petkov <bp@alien8.de>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: "Jörg Rödel" <joro@8bytes.org>,
linux-kernel@vger.kernel.org,
"Boris Ostrovsky" <boris.ostrovsky@amd.com>,
"Jacob Shin" <jacob.shin@amd.com>
Subject: Re: 3.6.11 AMD-Vi: Completion-Wait loop timed out
Date: Sun, 20 Jan 2013 13:24:21 +0100 [thread overview]
Message-ID: <20130120122421.GD16519@pd.tnic> (raw)
In-Reply-To: <50FBDC3F.1090509@xs4all.nl>
On Sun, Jan 20, 2013 at 12:59:59PM +0100, Udo van den Heuvel wrote:
> On 2013-01-20 12:50, Borislav Petkov wrote:
> >> Right, Udo, you can try Gigabyte first.
> >
> > Btw, you're running the latest BIOS from them, I assume?
>
> Nope. But I am beyond their first released BIOS, I am running one of
> their beta BIOSes. I am two beta updates behind current with F3g.
> They list as description for BIOS F3k:
>
> 1. Beta BIOS
> 2. Modify option of APU and memory voltage
> 3. Modify option of CPU PWM switch rate
> 4. Modify memory compatibility
> 5. Modify ET6 compatibility
Yeah, fixes lists are not always exhaustive, especially with BIOS. You
could try the latest if you can downgrade it easily if something breaks
with F3k.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-01-20 12:24 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 10:33 3.6.11 AMD-Vi: Completion-Wait loop timed out Udo van den Heuvel
2013-01-20 10:36 ` Borislav Petkov
2013-01-20 10:40 ` Udo van den Heuvel
2013-01-20 11:19 ` Jörg Rödel
2013-01-20 11:25 ` Udo van den Heuvel
2013-01-20 11:40 ` Jörg Rödel
2013-01-20 11:48 ` Borislav Petkov
2013-01-20 11:50 ` Borislav Petkov
2013-01-20 11:59 ` Udo van den Heuvel
2013-01-20 12:24 ` Borislav Petkov [this message]
2013-01-20 11:52 ` Udo van den Heuvel
2013-01-20 11:57 ` Jörg Rödel
2013-01-21 13:09 ` Borislav Petkov
2013-01-21 14:10 ` Udo van den Heuvel
2013-01-21 14:55 ` Borislav Petkov
2013-01-21 15:10 ` Jörg Rödel
2013-01-21 15:32 ` Borislav Petkov
2013-01-21 15:34 ` Udo van den Heuvel
2013-04-21 1:03 ` Jake
2013-04-21 21:47 ` Borislav Petkov
2013-01-21 14:37 ` Boris Ostrovsky
2013-01-21 14:44 ` Udo van den Heuvel
2013-01-21 14:47 ` Jörg Rödel
2013-01-21 16:04 ` Jacob Shin
2013-01-21 22:35 ` Suravee Suthikulpanit
2013-01-22 3:22 ` Udo van den Heuvel
2013-01-22 14:13 ` Udo van den Heuvel
2013-01-22 14:36 ` Boris Ostrovsky
2013-01-22 15:16 ` Jörg Rödel
2013-01-22 15:27 ` Udo van den Heuvel
2013-01-22 16:12 ` Boris Ostrovsky
2013-01-22 16:29 ` Udo van den Heuvel
2013-01-22 23:29 ` Suravee Suthikulanit
2013-01-23 14:19 ` Udo van den Heuvel
2013-01-23 15:00 ` Suravee Suthikulpanit
2013-01-23 14:23 ` Udo van den Heuvel
2013-01-23 15:01 ` Suravee Suthikulpanit
2013-01-31 15:42 ` Udo van den Heuvel
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=20130120122421.GD16519@pd.tnic \
--to=bp@alien8.de \
--cc=boris.ostrovsky@amd.com \
--cc=jacob.shin@amd.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=udovdh@xs4all.nl \
/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.