linux-kernel - Re: [BUG] OOPS 2.6.24.2 raid5 write with ioatdma

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] [day] [month] [year] [list]

Message-ID: <3cce60f30802151143gc98e3a2l29aa49f8f829e2f6@mail.gmail.com>
Date:	Fri, 15 Feb 2008 11:43:09 -0800
From:	"Shannon Nelson" <shannon.lee.nelson@...il.com>
To:	"Laurent CORBES" <laurent.corbes@...rtjog.com>
Cc:	linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org,
	"Nelson, Shannon" <shannon.nelson@...el.com>
Subject: Re: [BUG] OOPS 2.6.24.2 raid5 write with ioatdma

On Fri, Feb 15, 2008 at 8:19 AM, Laurent CORBES
<laurent.corbes@...rtjog.com> wrote:
> Hi all,
>
>  I got a raid5 oops when trying to write on a raid 5 array, with ioatdma loaded
>  and without DCA activated in bios:
>
[...]

Dan's quick patch is likely the right answer.

>
>  When I enable DCA in system bios I cannot boot, the ioatdma subsystem failed to
>  initialize, it stalled at:
>  ioatdma: ioat_dma_test_callback(00008086)

I don't see this example in the dmesg, but I'm not sure why you think
this is the case.  If DCA is enabled, you should not see any further
messages from ioatdma after the ioat_self_test_callback().

sln
-- 
==============================================
Mr. Shannon Nelson Parents can't afford to be squeamish.
--
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/