LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
To: nico@chdir.org
Cc: yhlu.kernel@gmail.com, mingo@elte.hu,
	fujita.tomonori@lab.ntt.co.jp, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: Re: USB problem on x86_64: nommu_map_single() issue?
Date: Tue, 14 Oct 2008 20:14:44 +0900	[thread overview]
Message-ID: <20081014201447I.fujita.tomonori@lab.ntt.co.jp> (raw)
In-Reply-To: <20081014110539.GA2997@sd-5945.dedibox.fr>

On Tue, 14 Oct 2008 13:05:39 +0200
Nicolas Bareil <nico@chdir.org> wrote:

> On Tue, Oct 14, 2008 at 08:00:09PM +0900, FUJITA Tomonori wrote:
> > > > 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.
> > 
> > With old kernels, you can find something like the following line in
> > the boot log?
> > 
> > PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
> 
> Indeed, I have this line:
> 
> Oct 14 12:46:29 brew kernel: [    0.004000] Calgary: detecting Calgary via BIOS EBDA area
> Oct 14 12:46:29 brew kernel: [    0.004000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
> Oct 14 12:46:29 brew kernel: [    0.004000] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
> Oct 14 12:46:29 brew kernel: [    0.004000] Placing software IO TLB between 0x4000000 - 0x8000000
> Oct 14 12:46:29 brew kernel: [    0.004000] Memory: 4055544k/4980736k available (2225k kernel code, 138092k reserved, 1079k data, 392k init)
> Oct 14 12:46:29 brew kernel: [    0.004000] CPA: page pool initialized 1 of 1 pages preallocated

Probably, the changes to the initial memory setup code breaks the
following code:

void __init pci_swiotlb_init(void)
{
	/* don't initialize swiotlb if iommu=off (no_iommu=1) */
	if (!iommu_detected && !no_iommu && max_pfn > MAX_DMA32_PFN)
	       swiotlb = 1;


SWIOTLB should be used for your box but somehow pci-nommu is used.


> The whole kern.log and my config are available here :
> http://chdir.org/~nbareil/kern.log

The following part in the 2.6.27 boot log looks suspicious:

Oct 13 15:43:48 brew kernel: last_pfn = 0x130000 max_arch_pfn = 0x3ffffffff
Oct 13 15:43:48 brew kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 13 15:43:48 brew kernel: last_pfn = 0xcffc2 max_arch_pfn = 0x3ffffffff


CC'ed Yinghai and Ingo, who might have clues.

  reply	other threads:[~2008-10-14 11:15 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 [this message]
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
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=20081014201447I.fujita.tomonori@lab.ntt.co.jp \
    --to=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nico@chdir.org \
    --cc=yhlu.kernel@gmail.com \
    --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).