From: "Eric S. Raymond" <esr@thyrsus.com>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: S2464 (K7 Thunder) hangs -- some lessons learned
Date: Sun, 12 Aug 2001 21:24:30 -0400 [thread overview]
Message-ID: <20010812212430.A9300@thyrsus.com> (raw)
Alas, the 2.4.8+ emu10k1 driver does not completely banish the K7 Thunder
lockups problem. It makes them a lot rarer, though, and enabled us to get to
the next level of diagnosis.
More from the article in progress:
<para>But as it turned out, the story didn't end there. The 2.4.8+ driver
doesn't completely banish the hangs; early in the morning of the third day,
while I was asleep, Gary tripped over a way to re-induce them by logging
into the machine via <command>ssh</command> while an X build is running. I
didn't yet know this when I next read my mail and saw a report from Jeffrey
Ingber of the linux-kernel list that he had continued to see emu10k1
lockups after installing 2.4.8 -- but that they were banished by the ALSA
drivers.</para>
<para>Further testing proved, in fact, that the presence of the SB Live!
in the machine can make it vulnerable to lockups triggered by network
activity even when the emul10k1 support is not configured in at all! This
takes the operating system out of the picture and suggests a hardware-
or BIOS-level problem. Our suspicions were immediately directed to PCI
IRQ sharing, a well-known source of lossage.</para>
<para>Upon investigation (via <filename>/proc/pci</filename>), we
discovered that the IRQ assignments looked distinctly dubious. IRQs
shared between on-board devices didn't bother us; we presumed the board
designers had been smart enough to avoid conflicts. But IRQs shared
between on-board and daughtercard devices looked like they might be
part of the problem.</para>
<para>Unlike some other PCI BIOSes, the S2464's doesn't give you the
capability to wire IRQs to specific card slots. While looking for this,
however, we found a BIOS setting that seemed relevant -- "Use PCI Interrupt
Entries In MP Table". When we switched it to `Yes', rebooted, and looked at
<filename>/proc/pci</filename>, the IRQ assignments looked a lot saner --
and when we tested, the <command>ssh</command> hang was gone!</para>
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
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.
I'm not certain we've nailed the entire problem yet -- we still need to test
with the emu10k1 sound driver linked in. But it's looking pretty good.
BTW, somebody mailed me an explanation of that BIOS setting ("Use PCI
Interrupt Entries In MP Table") but I managed to lose it. Whoever you
are, could you remail? I want to include some sort of explanation in
the article.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
The people cannot delegate to government the power to do anything
which would be unlawful for them to do themselves.
-- John Locke, "A Treatise Concerning Civil Government"
next reply other threads:[~2001-08-13 1:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 1:24 Eric S. Raymond [this message]
2001-08-13 1:41 ` S2464 (K7 Thunder) hangs -- some lessons learned Paul G. Allen
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=20010812212430.A9300@thyrsus.com \
--to=esr@thyrsus.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