mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dennis <dennis@etinc.com>
To: Russell King <rmk@arm.linux.org.uk>,
	R.E.Wolff@BitWizard.nl (Rogier Wolff)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4. continues after Aieee...
Date: Thu, 16 Nov 2000 10:34:30 -0500	[thread overview]
Message-ID: <5.0.0.25.0.20001116103133.02162c80@mail.etinc.com> (raw)
In-Reply-To: <200011161120.eAGBKUm08641@flint.arm.linux.org.uk>
In-Reply-To: <200011151630.RAA04141@cave.bitwizard.nl>


>
>Not every case causes a panic either.  This week, I had an instance of
>an i686 box lock solid with a DFE-530TX net card.  Rebooting/power
>cycling it didn't recover it (despite it working for the past month
>without any problems).  It only started working again after I moved
>it into a different PCI slot.
>
>I've seen a couple of instances now on totally different hardware where
>it is possible to lock a PCI bus solid by improper connections on some
>of the PCI bus lines, so a faulty PCI socket seem to be the most likely
>cause.


theres nothing that software can do with a pci bus lockup. You need a 
hardware watchdog to reboot the system for this type of failure.

PCI has a very tight spec, and running a card (say on an extender) or with 
another card that has too many loads can cause a bus failure. If you have 
more than 4 cards on the bus you are out of spec, for example.

But that doesnt change the panic issue. if you have hardware problems you 
cant expect any OS to help you, you need new  hardware.

Dennis


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-11-16 16:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-15  7:53 Rogier Wolff
2000-11-15 16:15 ` Dennis
2000-11-15 16:30   ` Rogier Wolff
2000-11-16 11:20     ` Russell King
2000-11-16 15:34     ` Dennis [this message]
2000-11-16 16:11       ` Russell King
2000-11-16  4:51   ` David Feuer

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=5.0.0.25.0.20001116103133.02162c80@mail.etinc.com \
    --to=dennis@etinc.com \
    --cc=R.E.Wolff@BitWizard.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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®