From: Stephan Brauss <sbrauss@bluewin.ch>
To: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.4 kernel freeze
Date: Wed, 23 May 2001 20:12:15 +0200 [thread overview]
Message-ID: <3B0BFD7F.B32695C8@bluewin.ch> (raw)
In-Reply-To: <Pine.LNX.4.10.10105231215280.11617-100000@coffee.psychology.mcmaster.ca>
Hello,
> what do you mean by freeze? in theory, the fact that the irq
I cannot ping the machine anymore, no Ooops, no kernel messages, the
attached screen is freezed (which implies that no more interrupts
are handled, right?)
> for those slots is shared with arbitrary onboard peripherals
> shouldn't matter, since PCI devices can all share irq's.
Yes... And it is not the problem, as I make use of interrupt
sharing on the first three slots.
> I guess it would be valuable to compare the boot messages
>From 2.2.19 and 2.4.4?
> under these conditions, since a real freeze implies that the
> kernel is adjusting irq routing incorrectly...
Yes, one could think. But I checked that interrupt handling basically
works for slots 4+5 with "cat /proc/interrupts". As soon as
I start a larger ftp data transfer over an ethernet adapter in
one of these slots the problem occurs.
next parent reply other threads:[~2001-05-23 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10105231215280.11617-100000@coffee.psychology.mcmaster.ca>
2001-05-23 18:12 ` Stephan Brauss [this message]
2001-05-23 23:30 ` 2.4.4 kernel freeze Jens Gecius
2001-05-24 23:21 ` Jens Gecius
2001-05-27 12:02 Stephan Brauss
2001-05-28 2:50 ` 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=3B0BFD7F.B32695C8@bluewin.ch \
--to=sbrauss@bluewin.ch \
--cc=hahn@coffee.psychology.mcmaster.ca \
--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