From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Wolfram Schlich <lists@schlich.org>
Cc: Linux-Kernel mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Hardlocks with 2.4.21-pre5, pdc202xx_new (PDC20269) and shared IRQs
Date: 20 Mar 2003 01:42:20 +0000 [thread overview]
Message-ID: <1048124539.647.18.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20030319221608.ALLYOURBASEAREBELONGTOUS.A29767@bla.fasel.org>
On Wed, 2003-03-19 at 22:16, Wolfram Schlich wrote:
> When one of the Promise controllers is sharing the same IRQ with one of
> the NICs (don't matter which, I tried all) and data is copied *to* the
> machine over the network, the system deadlocks. When data is copied
> *from* the system over the network, it works all ok. Unfortunately the
> system BIOS doesn't give me any possibility of setting the IRQ
> channels by hand, so all I can do is put the cards into other slots.
>
Thats very useful information. There certain have been (and it seems
still are) some cases with shared IRQ that are not quite handled right.
The 2.4.21pre5/pre5-ac work has partly been about fixing it. Deadlocks
suprise me however, since the problems I've seen have been I/O
errors.
However there is another known problem that does cause deadlocks with
the AMD76x, especially if the onboard IDE is used. Shove a PS/2 mouse
in the box, reboot and retest - if you dont already have one
next prev parent reply other threads:[~2003-03-20 0:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 22:16 Wolfram Schlich
2003-03-20 1:42 ` Alan Cox [this message]
2003-03-20 7:22 ` Wolfram Schlich
2003-03-20 8:51 ` Stephan von Krawczynski
2003-03-20 12:08 ` Wolfram Schlich
2003-03-20 10:23 ` Chris Newland
2003-03-20 12:06 ` Wolfram Schlich
2003-03-20 14:57 ` Alan Cox
2003-03-20 14:35 ` Wolfram Schlich
2003-03-25 18:32 ` Jan Kasprzak
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=1048124539.647.18.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@schlich.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
all inboxes | Powered by JetHome®