All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Biro <rossb@google.com>
To: John Bradford <john@bradfords.org.uk>
Cc: "D.A.M. Revok" <marvin@synapse.net>, 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:19:52 -0800	[thread overview]
Message-ID: <3E00BC48.3040506@google.com> (raw)
In-Reply-To: 200212152337.gBFNbZp9002196@darkstar.example.net


The promise chips often respond to starnge situations by locking up the 
PCI bus.  In particular they assert the wait signal and do not release 
it.  This locks the system up had the next time the CPU tries to access 
the PCI bus.  The machine is dead in your case and needs to be reset.

I've sent a PCI bus trace of this happening to Promise and have not yet 
heard anything back yet.

    Ross

John Bradford wrote:

>>man, the Magic SysReq key didn't work ( at all ):
>>it were DEAD
>>The drive-light stayed on for 10+ hours, nothing happening ( that I could 
>>figure out ) the whole time.  It /stayed/ dead.
>>
>>/dev/hde is part of a RAID-5 in my system ( because I no longer trust 
>>anything else ), and this only happens on drives connected onto the 
>>Promise controller.
>>
>>Oh, yeah, I forgot to include this:
>>trying to touch/activate/read the S.M.A.R.T. in any drive on the Promise 
>>kills it, too.  Can't activate the reliability-system without killing 
>>the kernel? /that's/ ironic, eh?
>>
>>
>>As for having another terminal connected to my home machine...
>>1. if the kernel's dead, then how's that gonna work, and
>>    
>>
>
>Maybe just the console was not responding.
>
>If I start X with /dev/null as the core pointer, the console locks
>completely, but I can still log in on a serial terminal.
>
>I have seen machines which will mostly stop responding when you issue
>a sleep command to a disk, E.G.
>
>hdparm -Y /dev/hda
>
>you can't terminate the process with control-C, for example, but if
>you are logged in on another virtual terminal, or have another
>terminal window open in X, you can reset the interface, and the
>machine will respond again.
>
>  
>
>>2. why have 2 terminals on one machine when I'm a hermit?
>>    
>>
>
>Why not?  I read and write a lot of E-Mail on a serial terminal right
>next to my main console, and what about debugging SVGALIB applications?
>
>  
>
>>I /do/ thank you for the interface-reset tip, though, I hope I never need 
>>that info  : )
>>    
>>
>
>It can be useful for recovering from a spun-down disk that won't spin
>up again :-)
>
>John
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>  
>




  reply	other threads:[~2002-12-18 18:12 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 [this message]
2002-12-18 18:17 ` Ross Biro
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=3E00BC48.3040506@google.com \
    --to=rossb@google.com \
    --cc=john@bradfords.org.uk \
    --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.