All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Biro <rossb@google.com>
To: "D.A.M. Revok" <marvin@synapse.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19, don't "hdparm -I /dev/hde" if hde is on a Asus A7V133 Promise ctrlr, or...
Date: Wed, 18 Dec 2002 10:17:36 -0800	[thread overview]
Message-ID: <3E00BBC0.6020807@google.com> (raw)
In-Reply-To: 200212151549.37661.marvin@synapse.net


There is a bug in the Promise driver that clears an important PIO bit 
when switching into DMA mode.  When you do an hdparm -I, it issues a 
drive command that attempts to transfer data in PIO mode, but since the 
PIO mode timing registers are hosed, the machine locks up.  It's easy to 
reproduce and applies to all drive commands that return data including 
SMART commands.

The bit in particular is bit 4 of PCI config register 0x61+4*channel 
number (PB bit 4 in Promise terms.)  I've got a very unclean fix that I 
will attempt to clean up once I can put a few more important issues to bed.

For the time being, you can try to do a work around by putting the drive 
into PIO mode with hdparm -X 12  before issuing any drive commands.

    Ross

D.A.M. Revok wrote:

>( that's a capital-aye in the hdparm line )
>
>not even the Magic SysReq key will work.
>
>also, don't
>
>"cd /proc/ide/hde ; cat identify"
>
>... same thing
>drive-light comes on, but have to use the power-switch to get the machine 
>back, ( lost stuff again, fuck )
>
>
>proc says it's pdc202xx
>
>Promise Ultra series driver Ver 1.20.0.7 2002-05-23
>Adapter: Ultra100 on M/B
>
>  
>




  parent reply	other threads:[~2002-12-18 18:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-15 20:49 2.4.19, don't "hdparm -I /dev/hde" if hde is on a Asus A7V133 Promise ctrlr, or D.A.M. Revok
2002-12-15 21:39 ` John Bradford
2002-12-15 22:25   ` D.A.M. Revok
2002-12-15 23:37     ` John Bradford
2002-12-18 18:19       ` Ross Biro
2002-12-18 18:17 ` Ross Biro [this message]
2002-12-18 21:10   ` Andre Hedrick
2002-12-18 21:19     ` Ross Biro
     [not found] <233C89823A37714D95B1A891DE3BCE5202AB1B35@xch-a.win.zambeel.com>
2002-12-18 10:38 ` D.A.M. Revok
2002-12-18 10:44   ` Andre Hedrick
2002-12-18 21:35     ` D.A.M. Revok
2002-12-18 22:01       ` Andre Hedrick
2002-12-18 22:38       ` Alan Cox
2002-12-18 21:58         ` Andre Hedrick
2002-12-18 22:03         ` D.A.M. Revok
2002-12-19  1:11           ` Alan Cox
2002-12-19 14:40         ` Denis Vlasenko
2002-12-19 10:19           ` Andre Hedrick
2002-12-19 11:14             ` Tomas Szepe
2002-12-19 11:45               ` Andre Hedrick
2002-12-19 12:03                 ` Tomas Szepe
2002-12-19 12:41                   ` Andre Hedrick
2003-01-16 18:54               ` Ookhoi
2002-12-19 15:14             ` Denis Vlasenko
2002-12-19 10:33               ` Andre Hedrick
2002-12-19 18:12           ` Ross Biro
2002-12-19  6:47       ` Ross Vandegrift
     [not found]       ` <Pine.LNX.4.10.10212181359350.8350-100000@master.linux-ide. org>
2002-12-19 13:26         ` Stephen Satchell
     [not found] <200212182204.gBIM48uD000332@darkstar.example.net>
2002-12-18 22:18 ` D.A.M. Revok
2002-12-19  2:02   ` Mike Dresser
  -- strict thread matches above, loose matches on Subject: below --
2002-12-21 23:22 Jason Radford
2003-01-17 16:47 ` Paul Jakma

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=3E00BBC0.6020807@google.com \
    --to=rossb@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marvin@synapse.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 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.