From: Roger Heflin <rheflin@atipa.com>
To: "Fortier,Vincent [Montreal]" <Vincent.Fortier1@EC.GC.CA>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>, linux-ide@vger.kernel.org
Subject: Re: Issues with sata_nv and 2 disks under 2.6.16 and 2.6.17-rc2
Date: Wed, 26 Apr 2006 09:42:26 -0500 [thread overview]
Message-ID: <444F86D2.7030000@atipa.com> (raw)
In-Reply-To: <8E8F647D7835334B985D069AE964A4F7011B2606@ECQCMTLMAIL1.quebec.int.ec.gc.ca>
Fortier,Vincent [Montreal] wrote:
> I think I might be having the "same type of bug" or something related using sata_via?
> Bug opened at bugzilla: http://bugzilla.kernel.org/show_bug.cgi?id=6317
>
> This started appearing with 2.6.16. It often does it using only one SATA HD. It does not do it at every boot but often starts doing it after a little while (a few hours...) and finally hanging my PC.
>
> - vin
>
>
I can duplicate my problem everything, and I can make it stop a will.
doing "dd if=/dev/sda of=/dev/null bs=64k &"
and then
"dd if=/dev/sdb of=/dev/null bs=64k &"
will cause the problem within a couple of seconds.
Doing "kill %1 %2" (assuming the dd's are %1 and %2) will
stop the machine from hanging on disk io within 30-60 seconds.
Once it hangs it does not appear to do any disk io until the
offending processes are killed.
Roger
next prev parent reply other threads:[~2006-04-26 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 14:28 Issues with sata_nv and 2 disks under 2.6.16 and 2.6.17-rc2 Fortier,Vincent [Montreal]
2006-04-26 14:42 ` Roger Heflin [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-26 14:46 Fortier,Vincent [Montreal]
2006-04-26 14:52 ` Roger Heflin
2006-04-25 17:02 Roger Heflin
2006-04-26 13:16 ` Roger Heflin
2006-04-26 13:24 ` Emmanuel Fleury
2006-04-26 14:05 ` Roger Heflin
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=444F86D2.7030000@atipa.com \
--to=rheflin@atipa.com \
--cc=Vincent.Fortier1@EC.GC.CA \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).