From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: libata total system lockup fix
Date: Fri, 19 Aug 2005 00:01:34 -0400 [thread overview]
Message-ID: <4305599E.4000303@rtr.ca> (raw)
In-Reply-To: <430555F6.4090709@gmail.com>
One idea would be to inject more faults into disk (ATA)
as opposed to the Optical (ATAPI) drives, and see if doing
so in combination with the existing ATAPI poll/fails will
trigger things more quickly.
This can be done by using Passthru to issue invalid commands
to a drive, which the drive will reject with "Drive Status Errors".
I just tried it now on a whim, using "hdparm -Z /dev/sda",
and my system never recovered until I used ctrl-alt-sysreq-b.
Now mind you, "hdparm -Z" sends a Seagate vendor-unique opcode
(to my Fujitsu hard drive), and perhaps that maps to something
the Fujitsu recognized or choked on.. But one could edit
hdparm to send a NOP or something instead.
Cheers
next prev parent reply other threads:[~2005-08-19 4:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 13:47 libata total system lockup fix Mark Lord
2005-07-25 14:51 ` Jeff Garzik
2005-07-25 15:53 ` Mark Lord
2005-08-05 3:52 ` Tejun Heo
2005-08-05 4:01 ` Tejun Heo
2005-08-11 20:13 ` Jeff Garzik
2005-08-12 0:49 ` Tejun Heo
2005-08-12 2:22 ` Mark Lord
2005-08-12 2:38 ` Tejun Heo
2005-08-12 2:41 ` Tejun Heo
2005-08-09 15:16 ` Mark Lord
2005-08-09 23:54 ` Tejun Heo
2005-08-10 14:16 ` Mark Lord
2005-08-10 21:24 ` Jeff Garzik
2005-08-19 0:46 ` Mark Lord
2005-08-19 3:21 ` Tejun Heo
2005-08-19 3:36 ` Mark Lord
2005-08-19 3:45 ` Tejun Heo
2005-08-19 4:01 ` Mark Lord [this message]
2005-08-19 9:37 ` Erik Slagter
2005-08-19 9:35 ` Erik Slagter
2005-08-19 13:07 ` Mark Lord
2005-08-19 13:32 ` Bartlomiej Zolnierkiewicz
2005-08-19 13:37 ` Bartlomiej Zolnierkiewicz
2005-09-03 22:58 ` Mark Lord
2005-09-03 23:06 ` Jeff Garzik
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=4305599E.4000303@rtr.ca \
--to=liml@rtr.ca \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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).