All of lore.kernel.org
 help / color / mirror / Atom feed
From: dAgeCKo <dagecko@free.fr>
To: "Borislav Petkov" <bp@alien8.de>,
	"H. Peter Anvin" <hpa@linux.intel.com>,
	linux-kernel@vger.kernel.org,
	"Alan Stern" <stern@rowland.harvard.edu>,
	linux-usb@vger.kernel.org, "Shane Huang" <Shane.Huang@amd.com>,
	"Jörg Rödel" <joro@8bytes.org>
Subject: Re: Fwd: Linux - AMD SB950 USB Regression
Date: Sat, 19 Jan 2013 15:47:53 +0100	[thread overview]
Message-ID: <50FAB219.5020108@free.fr> (raw)
In-Reply-To: <20130117213602.GA5998@pd.tnic>

Le 17/01/2013 22:36, Borislav Petkov a écrit :

>
> So, there seems to be some serious breakage with GART on SB9xx. I don't
> know whether this is the platform BIOS or the vendor BIOS causing it
> because the original bug reporter says he observes the issue on an MSI
> board and I'm experiencing this on my favourite bunch ASUS.
>
> So, if you use the GART as an IOMMU, i.e.:
>
> Jan 17 22:08:15 pd kernel: [    0.924063] PCI-DMA: using GART IOMMU.
> Jan 17 22:08:15 pd kernel: [    0.924120] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
>
> USB ports start choking like this:
>
> Jan 17 22:08:15 pd kernel: [    3.229909] usb 4-1: device descriptor read/64, error -32
> Jan 17 22:08:15 pd kernel: [    3.432786] usb 4-1: new high-speed USB device number 3 using ehci-pci
> Jan 17 22:08:15 pd kernel: [    3.534684] usb 4-1: device descriptor read/64, error -32
> Jan 17 22:08:15 pd kernel: [    3.737642] usb 4-1: device descriptor read/64, error -32

Yes, this is exactly what I faced.

>
> I'd go and venture a guess here since I don't have an idea that DMA
> somehow gets busted with the GART and thus the errors.
>
> Now, those boards normally have an IOMMU too so if you go and enable
>
> CONFIG_AMD_IOMMU=y
>
> the problem is gone (we're using the real IOMMU for DMA mapping, etc,
> etc). So dAgeCKo, that would be another thing you could do: try enabling
> the IOMMU in the BIOS and the above CONFIG option and the issue would be
> fixed too.

Here is below, exactly what the guy from MSI said me after I said him a 
BIOS upgrade did resolve my bug:

"The  reacts differently to Win/Linux, but it relies on updates by AMD. 
The new AGESA in the BIOS might had fixes for Linux."

After few researches, it seems that this "BIOS-level" software has 
effectively a special implementation wrapper for Linux (something I 
can't understand why actually). For more reference you can find little 
information here 
(http://www.coreboot.org/data/LinuxBIOS%20AMD%202006%20Final_10-02-2006.pdf).

I can't try the solution you are giving since I can't (and don't want to 
try to) downgrade my BIOS.

Another important thing you might be interested in is that not only my 
USB 2 weren't working. My mainboard ethernet wasn't working to (and was 
resolved with the BIOS upgrade too). The ethernet chip is:

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)

I don't know if that can be related to what you are saying.

>
> At least this fixes it on my box.
>
> To the question "how do we fix the GART issue?" I have no answer and
> would expect more informed opinions from someone else.

Actually I can't tell if I have any GART issues. The only thing I can 
say is that 3D looks to work nicely. However I think I never consumed 
more memory than my graphic card has.

>
> Thanks and HTH.
>

Thanks you too.

  reply	other threads:[~2013-01-19 14:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50C9FCD6.6050809@free.fr>
2013-01-04 10:22 ` Fwd: Linux - AMD SB950 USB Regression dAgeCKo
2013-01-11 15:59   ` dAgeCKo
2013-01-17 21:36     ` Borislav Petkov
2013-01-19 14:47       ` dAgeCKo [this message]
2013-01-19 16:35         ` Borislav Petkov

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=50FAB219.5020108@free.fr \
    --to=dagecko@free.fr \
    --cc=Shane.Huang@amd.com \
    --cc=bp@alien8.de \
    --cc=hpa@linux.intel.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.