From: Jake <client.alive@gmx.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 3.6.11 AMD-Vi: Completion-Wait loop timed out
Date: Sun, 21 Apr 2013 01:03:16 +0000 (UTC) [thread overview]
Message-ID: <loom.20130421T025332-280@post.gmane.org> (raw)
In-Reply-To: 20130121130942.GB4445@pd.tnic
Borislav Petkov <bp <at> alien8.de> writes:
>
> On Sun, Jan 20, 2013 at 12:57:55PM +0100, Jörg Rödel wrote:
> > BorisO is no longer with AMD afaik.
>
> Why am I not surprised...
>
> > I wrote an email to Sherry and Suravee and asked them to either send
> > me hardware to write the fix on my own or to send a fix for the issue.
> > Let's see what happens...
>
> Btw, while we're at it, here's some more h0rkage from my PD box:
>
> [ 0.220022] [Firmware Bug]: AMD-Vi: IOAPIC[9] not in IVRS table
> [ 0.220078] [Firmware Bug]: AMD-Vi: IOAPIC[10] not in IVRS table
> [ 0.220132] [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS
table
> [ 0.220187] AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
>
hello,
I've never posted to this type of message board before so I hope I'm not out
of order. I found my way here while trying to solve a shutdown problem in a
new linux install (Arch). I've noticed for some time that I have the same
lines as above in my dmesg as well as:
ACPI BIOS Bug: Warning: Optional FADT field Pm2CintrolBlock has no address
or length: 0x0000000000000000/0x1 (20121018/tbfadt-589)
I have no idea whether this is related to my shutdown problem or not and
what I was hoping is if someone would advise me how to find help for my
problem. I have tried all the normal routes for my distro (forum and irc)
repeatedly, and googled my weeping eyes out - but to no avail.
Any advice would be greatly appreciated.
Thanks
Jake
next prev parent reply other threads:[~2013-04-21 1:10 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
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 [this message]
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=loom.20130421T025332-280@post.gmane.org \
--to=client.alive@gmx.com \
--cc=linux-kernel@vger.kernel.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