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]
Date:	Fri, 28 Dec 2007 18:12:39 -0800
From:	"Shannon Nelson" <shannon.lee.nelson@...il.com>
To:	"Gustavo Guillermo Pérez" <gustavo@...punauta.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Corrupted Hard Drive after activating intel I/oat dma

On Dec 27, 2007 5:49 PM, Gustavo Guillermo Pérez <gustavo@...punauta.com> wrote:
> By mistake we activate intel I/oat dma support on a laptop with a centrino duo
> to try to get better performance on IO.
>
> The wd1200bevs Western Digital Scorpio 120GB HD fails with bad sectors and
> power down (randomly) after booting linux with this option enabled, and
> rebooting with old options does not help, I'm just reporting it, cause we can
> think on a power failure too, but the only change was that, and linux start
> up take too long and HD activity was so hard. I know the option was not
> supported, but I want to know if cause that we can have a fried hd :(.

I highly doubt that ioatdma could break a harddrive, as it is only
used by the networking stack.  Besides, the driver will only be useful
on a server type motherboard using a chipset that supports ioatdma.
This is not the case with a Centrino-based machine.

By the way, you might try checking the Maintainer's file to find out
who supports that module and copy them directly.  If they're at work
this week they might have a more official answer.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ