public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: Jacob Shin <jacob.shin@amd.com>
Cc: "Borislav Petkov" <bp@alien8.de>, "Jörg Rödel" <joro@8bytes.org>,
	"Udo van den Heuvel" <udovdh@xs4all.nl>,
	linux-kernel@vger.kernel.org,
	"Boris Ostrovsky" <boris.ostrovsky@amd.com>
Subject: Re: 3.6.11  AMD-Vi: Completion-Wait loop timed out
Date: Mon, 21 Jan 2013 16:35:12 -0600	[thread overview]
Message-ID: <1358807712.2812.2.camel@Greyghost-ubuntu> (raw)
In-Reply-To: <20130121160450.GA24792@jshin-Toonie>

Udo, 

I am trying to debug the issue but need to check one thing on your
system.  Would you please try the following and check the output value
on your system?

# setpci -s 00:00.02 F0.w=90
# setpci -s 00:00.02 F4.w


Thank you,

Suravee


On Mon, 2013-01-21 at 10:04 -0600, Jacob Shin wrote:
> On Sun, Jan 20, 2013 at 12:48:28PM +0100, Borislav Petkov wrote:
> > On Sun, Jan 20, 2013 at 12:40:11PM +0100, Jörg Rödel wrote:
> > > Yes, the BIOS vendor can fix this issue. They need to disable NB clock
> > > gating for the IOMMU.
> > 
> > Right, Udo, you can try Gigabyte first.
> > 
> > Btw, can't we add a quirk to disable NB clock gating? Maybe Boris and
> > Jacob could help. CCed.
> 
> Hi, yes we will try and reproduce the NB clock gating issue on our
> end and submit a patch ASAP.
> 
> And Boris P., I think your IOAPIC not in IVRS issue we've also seen
> something similar recently (on Xen), so we'll atempt to tackle that
> one too afterwards.
> 
> -Jacob
> 
> > 
> > Guys, the error description is at
> > http://marc.info/?l=linux-kernel&m=135867802432660
> > 
> > Thanks.
> > 
> > -- 
> > Regards/Gruss,
> >     Boris.
> > 
> > Sent from a fat crate under my desk. Formatting is fine.
> > --
> > 




  reply	other threads:[~2013-01-21 22:36 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
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 [this message]
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=1358807712.2812.2.camel@Greyghost-ubuntu \
    --to=suravee.suthikulpanit@amd.com \
    --cc=boris.ostrovsky@amd.com \
    --cc=bp@alien8.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox