From: "Shannon Nelson" <shannon.lee.nelson@gmail.com>
To: "Gustavo Guillermo Pérez" <gustavo@compunauta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Corrupted Hard Drive after activating intel I/oat dma
Date: Fri, 28 Dec 2007 18:12:39 -0800 [thread overview]
Message-ID: <3cce60f30712281812v5f7ce335l35d698553449187a@mail.gmail.com> (raw)
In-Reply-To: <200712271949.02116.gustavo@compunauta.com>
On Dec 27, 2007 5:49 PM, Gustavo Guillermo Pérez <gustavo@compunauta.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.
prev parent reply other threads:[~2007-12-29 2:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 1:49 Gustavo Guillermo Pérez
2007-12-28 3:03 ` Marek Kierdelewicz
2007-12-28 22:51 ` Shourya Sarcar
2007-12-29 2:10 ` Valdis.Kletnieks
2008-01-07 17:57 ` Gustavo Guillermo Pérez
2007-12-29 2:12 ` Shannon Nelson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3cce60f30712281812v5f7ce335l35d698553449187a@mail.gmail.com \
--to=shannon.lee.nelson@gmail.com \
--cc=gustavo@compunauta.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®