mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Ross Biro <rossb@google.com>
Cc: alan@lxorguk.ukuu.org.uk, andre@linux-ide.org,
	marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: PATCH: [2.4.21-pre3] Fix for Promise PIO Lockup
Date: Wed, 15 Jan 2003 15:21:13 +0100	[thread overview]
Message-ID: <15909.28249.617353.381378@harpo.it.uu.se> (raw)
In-Reply-To: <3E2368CF.6050608@google.com>

Ross Biro writes:
 > Newer kernels will lock up when a drive command (SMART, hdparm -I, etc.) 
 > is issued to a drive connected to a Promise 20265 or 20267 controller 
 > while the controller is in DMA mode.  The problem appears to be that 
 > tune_chipset incorrectly clears the high PIO bit thinking that it is a 
 > "PIO force on" bit.  The documentation I have access to does not seem to 
 > mention a PIO force bit.  Not changing that bit seems to fix the problem 
 > with drive commands on a promise controller.
 > 
 > The documentation I have also says the values for the TB and TC 
 > variables should be the same for all UDMA modes and they are not. 
 >  However the driver seems to work anyway, so I left them the way they are.
 > 
 > To reproduce this problem make sure your drive is set to a DMA mode, eg 
 > hdparm -X 67 and then issue a drive command, e.g. hdparm -I.

I have tried to reproduce this problem according to your description
above, but neither my 20269 (with "new" driver) nor my 20267 (with
"old" driver) hangs. I checked with kernels 2.5.58 and 2.4.21-pre3.

Maybe something else is needed for the hang to occur?

/Mikael

      reply	other threads:[~2003-01-15 14:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14  1:33 Ross Biro
2003-01-15 14:21 ` Mikael Pettersson [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=15909.28249.617353.381378@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=rossb@google.com \
    /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®