linux-kernel - Re: USB transfer_buffer allocations on 64bit systems

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: <20100414222550.GB25962@sequoia.sous-sol.org>
Date:	Wed, 14 Apr 2010 15:25:50 -0700
From:	Chris Wright <chrisw@...s-sol.org>
To:	Pedro Ribeiro <pedrib@...il.com>
Cc:	David Woodhouse <dwmw2@...radead.org>,
	Alan Stern <stern@...land.harvard.edu>,
	Daniel Mack <daniel@...aq.de>,
	USB list <linux-usb@...r.kernel.org>,
	Andi Kleen <andi@...stfloor.org>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Greg KH <gregkh@...e.de>, iommu@...ts.linux-foundation.org,
	Chris Wright <chrisw@...s-sol.org>
Subject: Re: USB transfer_buffer allocations on 64bit systems

* Pedro Ribeiro (pedrib@...il.com) wrote:
> Turns out CONFIG_DMAR was disabled because of PREEMPT_RT. I disabled
> the later and enabled _DMAR. It took a long time to boot, something
> wrong with the usb ports. You can see it in the appended dmesg from
> time 11s to 100s.
> 
> Then after it booted, I could barely move my USB mouse and lots of
> errors appeared on dmesg. I tried to connect the DVB card but it
> wouldn't even initialize.

[  316.360045] DMAR:[DMA Write] Request device [00:02.0] fault addr 23c00000 
[  316.360046] DMAR:[fault reason 05] PTE Write access is not set

That's your video device.  Do you have CONFIG_DMAR_BROKEN_GFX_WA=y?

> Enabling it with iommu=pt seemed to make no difference.

It should (it should at least eliminate the video device problem).
--
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/