From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linas Vepstas <linas@austin.ibm.com>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Stuart_Hayes@dell.com, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] ide dma_timer_expiry, then hard lockup
Date: Thu, 21 Jun 2007 21:58:37 +0400 [thread overview]
Message-ID: <467ABC4D.5010004@ru.mvista.com> (raw)
In-Reply-To: <20070620180123.642316ae@the-village.bc.nu>
Hello.
Alan Cox wrote:
>>Google seems to show that there is no publically available
>>firmware updates for Maxtor disks.
> There are for some but only if you irritate the tech support people.
>>hours at high cpu usage.... There were maybe a a dozen DriveReady
>>SeekComplete Timeout errors clustered a few minutes apart.
> That suggests the drive is having problems occassionally and that the DMA
> path code then blows up when they occur.
>>Is there a way of viewing the contents of he command queue on
>>the hard drive, to see if the command actually made it across?
> queue ? You are overestimating IDE ;)
He's not -- there is queued commands support since ATA[PI]-5. I'm not sure
why but Linux decided not to support it.
MBR, Sergei
next prev parent reply other threads:[~2007-06-21 17:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 17:57 [BUG] ide dma_timer_expiry, then hard lockup Linas Vepstas
2007-06-18 18:11 ` Stuart_Hayes
2007-06-18 18:11 ` Stuart_Hayes
2007-06-19 14:07 ` Sergei Shtylyov
2007-06-19 15:05 ` Linas Vepstas
2007-06-19 16:10 ` Sergei Shtylyov
2007-06-19 16:48 ` Linas Vepstas
2007-06-19 18:43 ` Bartlomiej Zolnierkiewicz
2007-06-19 20:07 ` Sergei Shtylyov
2007-06-20 16:28 ` Linas Vepstas
2007-06-20 17:01 ` Alan Cox
2007-06-20 17:01 ` Alan Cox
2007-06-21 17:58 ` Sergei Shtylyov [this message]
2007-06-21 21:41 ` Alan Cox
2007-06-21 19:47 ` Linas Vepstas
2007-06-21 22:04 ` Alan Cox
2007-06-21 22:04 ` Alan Cox
2007-06-18 20:27 ` Alan Cox
2007-06-18 20:27 ` Alan Cox
2007-06-18 20:46 ` Linas Vepstas
2007-06-18 21:04 ` Alan Cox
2007-06-18 21:04 ` Alan Cox
2007-06-18 21:22 ` Linas Vepstas
2007-06-19 14:56 ` bug in libata [was " Linas Vepstas
2007-06-19 14:10 ` Sergei Shtylyov
2007-06-19 14:19 ` Alan Cox
2007-06-19 14:24 ` Sergei Shtylyov
2007-06-19 15:38 ` Mark Lord
2007-06-19 15:51 ` Sergei Shtylyov
2007-06-19 16:17 ` Alan Cox
2007-06-19 16:32 ` Sergei Shtylyov
2007-06-22 15:39 ` Sergei Shtylyov
2007-06-29 18:52 ` Sergei Shtylyov
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=467ABC4D.5010004@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=Stuart_Hayes@dell.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=linas@austin.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.