linux-kernel - Re: [Bug #13001] PCI-DMA: Out of IOMMU space

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: <db2b43030904280218v61fded68rc585ce9c58ba1cce@mail.gmail.com>
Date:	Tue, 28 Apr 2009 14:18:57 +0500
From:	Данила Жукоцкий 
	<optimusgd@...il.com>
To:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Cc:	rjw@...k.pl, linux-kernel@...r.kernel.org,
	kernel-testers@...r.kernel.org, grundler@...gle.com
Subject: Re: [Bug #13001] PCI-DMA: Out of IOMMU space

No, it is regression. I can reproduce that without allowdac and any
other unnecessary boot options. In later discussion Grant Grundler ask
me apply patch that show 32 bit dma devices in my system. Results I
attached to bugreport. Looks like only one 32 bit dma device in my
system is ata controller, sata-nv. I can stable reproduce IOMMU out of
space when I write data to sata drive.

2009/4/28 FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>:
> On Sun, 26 Apr 2009 11:46:28 +0200 (CEST)
> "Rafael J. Wysocki" <rjw@...k.pl> wrote:
>
>> This message has been generated automatically as a part of a report
>> of regressions introduced between 2.6.28 and 2.6.29.
>>
>> The following bug entry is on the current list of known regressions
>> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
>> be listed and let me know (either way).
>>
>>
>> Bug-Entry     : http://bugzilla.kernel.org/show_bug.cgi?id=13001
>> Subject               : PCI-DMA: Out of IOMMU space
>> Submitter     :  <optimusgd@...il.com>
>> Date          : 2009-04-03 09:30 (24 days old)
>
> Probably, this is not a regression.
>
> He doesn't hit this problem with 2.6.29 when he uses the kernel boot
> option that he used with 2.6.28. I have no idea how not using
> 'allowdac' can solve the problem though.
>



-- 
С уважением Данила Жукоцкий, системный администратор ЗАО "Роснефтегазмаш"
--
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/