linux-kernel - Re: USB problem on x86_64: nommu_map

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081014110539.GA2997@sd-5945.dedibox.fr>
Date:	Tue, 14 Oct 2008 13:05:39 +0200
From:	Nicolas Bareil <nico@...ir.org>
To:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Cc:	nico@...ir.org, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org
Subject: Re: USB problem on x86_64: nommu_map_single() issue?

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

The full kern.log is available here: http://chdir.org/~nbareil/kern.log-2.6.26-1

Thanks!

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/