mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "John Treubig" <jtreubig@hotmail.com>
To: alan@lxorguk.ukuu.org.uk
Cc: raw@dslr.net, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: ATA Write Error and Time-out Notification in User Space
Date: Tue, 03 Jan 2006 13:27:28 -0600	[thread overview]
Message-ID: <BAY101-F32BC19A49EC86F6FED361BDF2C0@phx.gbl> (raw)
In-Reply-To: <1136314722.22598.36.camel@localhost.localdomain>

I receive this as great news, only I don't know where the -mm tree is 
located to see if I can get the patch or fix!  Can you give me a few 
pointers?!



From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: John Treubig <jtreubig@hotmail.com>
CC: raw@dslr.net, linux-ide@vger.kernel.org,linux-kernel@vger.kernel.org, 
linux-scsi@vger.kernel.org
Subject: Re: ATA Write Error and Time-out Notification in User Space
Date: Tue, 03 Jan 2006 18:58:42 +0000

On Maw, 2006-01-03 at 12:29 -0600, John Treubig wrote:
 > failure point.  I put a drive on the Secondary IDE bus hanging off the
 > motherboard Nvidia NForce 2 controller, began an access and pulled the 
plug.
 >   Sure enough the failures occured and were passed back to user level, 
but
 > the system did not hang.  I've repeated this a number of times.  I moved 
the
 > same drive to the Promise Controller and the hang occurs.  Thus it seems 
we
 > have proved the Promise sub-system is my problem.


Bingo. Yes I know why this is occuring now.

There is a known old bug with error handling in some cases on promise
chips. The core kernel code tries to clean up any remaining data after
an error (to handle chip prefetch/postwrite FIFOs) if DRQ_STAT is
asserted. Its a nice trick, saves on resets and slow recovery but isn't
compatible with some promise controllers.

The -mm tree has a partial but incomplete fix to this implemented, the
base kernel does not have this fixed.

Its been known for some time so perhaps the ide maintainers have patches
waiting for 2.6.16 now its opened ?

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2006-01-03 19:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03 18:29 John Treubig
2006-01-03 18:58 ` Alan Cox
2006-01-03 19:27   ` John Treubig [this message]
2006-01-03 21:48     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2006-01-05 20:27 John Treubig
2005-12-20 21:55 John Treubig
2005-12-20 22:50 ` Alan Cox
2005-12-21  0:31   ` Drew Winstel
2005-12-22  1:09     ` Alan Cox

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=BAY101-F32BC19A49EC86F6FED361BDF2C0@phx.gbl \
    --to=jtreubig@hotmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=raw@dslr.net \
    /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®