linux-kernel - Re: [Bug #14375] Intel(R) I/OAT DMA Engine init failed

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 for Android: free password hash cracker in your pocket

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

Message-ID: <a4423d670910261457o2e1ccb7t768199dfd9985270@mail.gmail.com>
Date:	Tue, 27 Oct 2009 01:57:04 +0400
From:	Alexander Beregalov <a.beregalov@...il.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Dan Williams <dan.j.williams@...el.com>
Subject: Re: [Bug #14375] Intel(R) I/OAT DMA Engine init failed

2009/10/26 Rafael J. Wysocki <rjw@...k.pl>:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.31.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=14375
> Subject         : Intel(R) I/OAT DMA Engine init failed
> Submitter       : Alexander Beregalov <a.beregalov@...il.com>
> Date            : 2009-10-02 9:46 (25 days old)
> References      : http://marc.info/?l=linux-kernel&m=125447680016160&w=4
> Handled-By      : Dan Williams <dan.j.williams@...el.com>
> Patch           : http://patchwork.kernel.org/patch/51808/

When I patch reiserfs the bug goes to libata, it means ioatdma works
and libata does not. It looks like inaccurate work with memory
somewhere, but I do not know how to find it.
I cannot reproduce it since 2.6.32-rc3 and I do not see any bugs since then.
--
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/