From: Russell King <rmk@arm.linux.org.uk>
To: dennis@etinc.com (Dennis)
Cc: R.E.Wolff@BitWizard.nl (Rogier Wolff), linux-kernel@vger.kernel.org
Subject: Re: 2.4. continues after Aieee...
Date: Thu, 16 Nov 2000 16:11:06 +0000 (GMT) [thread overview]
Message-ID: <200011161611.QAA02401@raistlin.arm.linux.org.uk> (raw)
In-Reply-To: <5.0.0.25.0.20001116103133.02162c80@mail.etinc.com> from "Dennis" at Nov 16, 2000 10:34:30 AM
Dennis writes:
> >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.
If you read on, you'll discover I did in fact say this.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King rmk@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/personal/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
-
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/
next prev parent reply other threads:[~2000-11-16 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 7:53 2.4. continues after Aieee 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
2000-11-16 16:11 ` Russell King [this message]
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=200011161611.QAA02401@raistlin.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=R.E.Wolff@BitWizard.nl \
--cc=dennis@etinc.com \
--cc=linux-kernel@vger.kernel.org \
/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