public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul G. Allen" <pgallen@randomlogic.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: S2464 (K7 Thunder) hangs -- some lessons learned
Date: Sun, 12 Aug 2001 18:41:00 -0700	[thread overview]
Message-ID: <3B77302C.96C79272@randomlogic.com> (raw)
In-Reply-To: <20010812212430.A9300@thyrsus.com>

(Small note. The K7 Thunder is S2462, unless there is another, possibly
newer, version released?)

"Eric S. Raymond" wrote:
> 

[SNIP]
> 
> OK, so the lessons here are:
> 
> 1. The S2464 needs to be configured with "Use PCI Interrupt Entries In MP
>    Table" for sanity to prevail, and

I have been running my K7 in this mode since purchase. Could this be why
I see no SB Live!/ EMU10K problems (though I am running 2.4.7 kernels
now)?

> 
> 2. When you see a box hang that's clearly related to a daughtercard, *run*
>    (do not walk) to your local /proc directory, cat /proc/pci and check out
>    the IRQ assignments.

Problem is, when it does hang, I can't get there as the system is
completely locked, including ssh and telnet.

PGA

-- 
Paul G. Allen
UNIX Admin II/Network Security
Akamai Technologies, Inc.
www.akamai.com

  reply	other threads:[~2001-08-13  1:46 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13  1:24 S2464 (K7 Thunder) hangs -- some lessons learned Eric S. Raymond
2001-08-13  1:41 ` Paul G. Allen [this message]
2001-08-13  5:12   ` Christopher Abbey
2001-08-13 12:34 ` Alan Cox
2001-08-13 15:18   ` Eric S. Raymond
2001-08-13 15:46     ` Alan Cox
2001-08-13 15:52       ` Eric S. Raymond
2001-08-13 16:00         ` Alan Cox
2001-08-13 18:56           ` Is there something that can be done against this ??? Mircea Ciocan
2001-08-13 19:19             ` Jakob Østergaard
2001-08-13 19:19             ` Ulrich Drepper
2001-08-13 19:20               ` Mircea Ciocan
2001-08-13 19:41                 ` Aaron Lehmann
2001-08-13 19:53                 ` Chris Meadors
2001-08-13 20:09                 ` Admin Mailing Lists
2001-08-13 22:01                 ` Rik van Riel
2001-08-14  8:12                 ` Helge Hafting
2001-08-13 19:24             ` Peter T. Breuer
2001-08-13 19:34               ` Eli Carter
2001-08-13 19:32             ` Ben Collins
2001-08-13 19:48             ` Ronald Jeninga
2001-08-13 20:02             ` Richard B. Johnson
2001-08-14  8:02             ` Henning P. Schmiedehausen
2001-08-14  8:16             ` joseph.bueno
2001-08-14 10:00               ` David Schwartz
2001-08-14 12:42                 ` Helge Hafting
2001-08-14 17:10                   ` David Schwartz
2001-08-14 13:16                 ` joseph.bueno
     [not found]                   ` <9lb8vp$10q$1@ns1.clouddancer.com>
2001-08-14 16:34                     ` Colonel
2001-08-15  9:08                   ` Helge Hafting
2001-08-14 17:47                 ` Scott Wood
2001-08-14 21:27           ` S2464 (K7 Thunder) hangs -- some lessons learned Eric S. Raymond
2001-08-14 22:13             ` Alan Cox
2001-08-14  1:45       ` Paul G. Allen
     [not found] <Pine.LNX.4.10.10108140151000.10879-100000@coffee.psychology.mcmaster.ca>
2001-08-14  2:05 ` Paul G. Allen
  -- strict thread matches above, loose matches on Subject: below --
2001-08-14 11:55 Ryan C. Bonham

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=3B77302C.96C79272@randomlogic.com \
    --to=pgallen@randomlogic.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