From: Jens Gecius <jens@gecius.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.4 kernel freeze
Date: 27 May 2001 22:50:12 -0400 [thread overview]
Message-ID: <878zjiqja3.fsf@maniac.gecius.de> (raw)
In-Reply-To: <3B10ECF2.220E1DFB@bluewin.ch>
In-Reply-To: <3B10ECF2.220E1DFB@bluewin.ch> (Stephan Brauss's message of "Sun, 27 May 2001 14:02:58 +0200")
Stephan Brauss <sbrauss@bluewin.ch> writes:
> > Any other hints are welcome (other than the noapic, which didn't help).
> My system is always completely dead as soon as I start a larger (interrupt
> driven?) data transfer to/from any (? I tested with two different NICs and a Promise
> Ultra100) PCI card in slot 4 or 5. And it seems that it really only occurs
> in slots 4 and 5... To get rid of it, I switched to 2.2.19.
I couldn't. Problems getting devfsd patched in 2.2.19 :-( - and I'm
going on vacation in shortly...
Now after the last couple of "lost interrupts" I set a debian-stable
as my primary firewall/router box in front of my server - this way I
got rid of the second nic and freed both slot 4 and 5. Unfortunately,
after a couple hours running my box again lost irq :-(.
And there's no obvious huge transfer going on. The boxes were just
alone. Now I try again noapic (different setup). Hope that
works. Otherwise I'm kind of lost...
--
Tschoe, Get my gpg-public-key here
Jens http://gecius.de/gpg-key.txt
next prev parent reply other threads:[~2001-05-30 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-27 12:02 2.4.4 kernel freeze Stephan Brauss
2001-05-28 2:50 ` Jens Gecius [this message]
[not found] <Pine.LNX.4.10.10105231215280.11617-100000@coffee.psychology.mcmaster.ca>
2001-05-23 18:12 ` Stephan Brauss
2001-05-23 23:30 ` Jens Gecius
2001-05-24 23:21 ` Jens Gecius
-- strict thread matches above, loose matches on Subject: below --
2001-05-23 14:34 Stephan Brauss
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=878zjiqja3.fsf@maniac.gecius.de \
--to=jens@gecius.de \
--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