LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Jouni Malinen" <jkmalinen@gmail.com>
To: "Oliver Neukum" <oliver@neukum.org>
Cc: "Nicolas Bareil" <nico@chdir.org>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	"Joerg Roedel" <joerg.roedel@amd.com>,
	"Ingo Molnar" <mingo@elte.hu>,
	j@w1.fi
Subject: Re: USB problem on x86_64: nommu_map_single() issue?
Date: Tue, 28 Oct 2008 11:07:40 +0200	[thread overview]
Message-ID: <e785a1360810280207p1c162decs5a70b8915ea08476@mail.gmail.com> (raw)
In-Reply-To: <200810141300.29502.oliver@neukum.org>

On Tue, Oct 14, 2008 at 1:00 PM, Oliver Neukum <oliver@neukum.org> wrote:
> Am Dienstag, 14. Oktober 2008 12:45:00 schrieb Nicolas Bareil:
>> On Tue, Oct 14, 2008 at 11:48:47AM +0200, Oliver Neukum wrote:
>> > > On 2.6.27, I can't use any USB device (mass storage, mouse) anymore on my x86_64 system, the devices
>> > > are not detected: lsusb returns nothing except the hub.
>> >
>> > Is this a regression? Did it work on earlier kernels?
>>
>> Yes this is a regression: USB works in 2.6.26.x with (almost) the same configuration.
>
> This a an IOMMU problem, not really a USB problem. Can you bisect the problem?

It looks like I'm seeing something similar with the current
linux-2.6.git. However, in my case, 2.6.27 seemed to work and I
started seeing this only after the 2.6.27 release (though, git bisect
ended up in 2.6.27-rc3). In addition, I'm seeing way more issues than
just USB dying (both wired and wireless networking were hosed; r8169
was returning random memory or all zeroes in the payload of the
frames, etc.).

After a painful git bisect (two other bugs that prevented boot and
some build issues in the tested commits) the first bad commit turned
out to be cf169702ba6928cee9d4f4adf3e932b643b8db7a (see below; author
cc'ed). This is only adding a new PCI device id, so the commit itself
seems to just trigger the issue somewhere else.

I've verified that I can get rid of the nommu_map_single() messages by
reverting this patch (i.e., made kernel not find the northbridge) with
the current linux-2.6.git head. Obviously, that does not sound like a
proper fix here. Would anyone have any idea on what is the real issue
here or what could be done to find it?

I'm seeing this issue on a HP Pavilion dv5 laptop that has AMD Turion
X2 Ultra Dual-Core Mobile ZM-80. lspci shows the PCI id that was added
(1022:1303). mem=2G works around the problem. pci_swiotlb_init() did
not set swiotlb to 1, but hardcoding it to 1 there did not help
either.


$ git bisect bad
cf169702ba6928cee9d4f4adf3e932b643b8db7a is first bad commit
commit cf169702ba6928cee9d4f4adf3e932b643b8db7a
Author: Joerg Roedel <joerg.roedel@amd.com>
Date:   Tue Sep 2 13:13:40 2008 +0200

    x86, gart: add detection of AMD family 0x11 northbridges

    This patch adds the detection of the northbridges in the AMD family 0x11
    processors. It also fixes the magic numbers there while changing this code.

    Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>

:040000 040000 183c03461f96be8bbf96cb51bae9bb0fb93dae89
58638c91f03393225f3c48cb12476466f9c5e2be M	arch

----------------------------- arch/x86/kernel/k8.c -----------------------------
index 7377ccb..304d8ba 100644
@@ -16,8 +16,9 @@ EXPORT_SYMBOL(num_k8_northbridges);
 static u32 *flush_words;

 struct pci_device_id k8_nb_ids[] = {
-	{ PCI_DEVICE(PCI_VENDOR_ID_AMD, 0x1103) },
-	{ PCI_DEVICE(PCI_VENDOR_ID_AMD, 0x1203) },
+	{ PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_K8_NB_MISC) },
+	{ PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_10H_NB_MISC) },
+	{ PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_11H_NB_MISC) },
 	{}
 };
 EXPORT_SYMBOL(k8_nb_ids);


- Jouni

  parent reply	other threads:[~2008-10-28  9:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14  7:20 Nicolas Bareil
2008-10-14  9:48 ` Oliver Neukum
2008-10-14 10:45   ` Nicolas Bareil
2008-10-14 11:00     ` FUJITA Tomonori
2008-10-14 11:05       ` Nicolas Bareil
2008-10-14 11:14         ` FUJITA Tomonori
2008-10-14 17:11           ` Yinghai Lu
2008-10-14 11:00     ` Oliver Neukum
2008-10-14 13:43       ` Nicolas Bareil
2008-10-14 14:15         ` Nicolas Bareil
2008-10-28  9:07       ` Jouni Malinen [this message]
2008-10-28 15:13         ` [PATCH] x86, gart: fix gart detection for Fam11h CPUs Joerg Roedel
2008-10-28 16:00           ` Ingo Molnar
2008-10-28 16:52           ` Greg KH
2008-10-29  9:55             ` Joerg Roedel
2008-10-29 23:12               ` Greg KH

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=e785a1360810280207p1c162decs5a70b8915ea08476@mail.gmail.com \
    --to=jkmalinen@gmail.com \
    --cc=j@w1.fi \
    --cc=joerg.roedel@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nico@chdir.org \
    --cc=oliver@neukum.org \
    --subject='Re: USB problem on x86_64: nommu_map_single() issue?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).