mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Carl Thompson <cet@carlthompson.net>
Cc: vda <vda@port.imtp.ilyichevsk.odessa.ua>, linux-kernel@vger.kernel.org
Subject: Re: hard lock using combination of devices
Date: Tue, 17 Feb 2004 09:39:29 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0402170927330.912@chaos> (raw)
In-Reply-To: <20040217061400.z9r4gss0gsockws4@carlthompson.net>


Linux interrupt code does shared interrupts fine.
There may be a bad driver so you need to find which
one it is and contact its author. There are still
entirely too many drivers that loop in the ISR, ...
so-called "interrupt mitigation"... If you are
using one such creation, find the loop terminating
variable and squash it to where it will not loop.
Magically, everything will start to work and share
wonderfully.

There is a big difference between maximizing the through-put
of a device and getting all devices to play nicely together.
Often device-driver writers think only of their hardware and
don't bother to think about the consequences of keeping
the CPU practically forever. For instance, a network card
will probably always have new packets available on an active
network. If you loop to get them all, you loop forever.

On Tue, 17 Feb 2004, Carl Thompson wrote:

> Quoting vda <vda@port.imtp.ilyichevsk.odessa.ua>:
>
> > On Tuesday 17 February 2004 09:14, Carl Thompson wrote:
> >> Quoting vda <vda@port.imtp.ilyichevsk.odessa.ua>:
> >> > ...
> >> >
> >> > Your box share IRQs in a big way :)
> >>
> >> Your point?
> >
> > While shared interrupts can in theory work right,
> > lots of hardware and/or drivers do not handle
> > that.
>
> First, the two devices in question are not on the same interrupt.  Second, it
> is very difficult in this day in age to build a system without interrupt
> sharing.  While I agree that it's better to have as few devices sharing as
> possible, there are simply too many devices in modern systems and too few
> interrupts.  Interrupt sharing needs to work on modern hardware and needs to
> work in Linux.  This notebook is pretty typical in its interrupt distribution
> and I'm not certain that this is a problem.  In fact, while many devices on
> this system use IRQ 11 the only one active at the time was the audio
> controller.  And while IRQ 10 is shared between the CardBus adapters and the
> video card the problems still occur if I don't run X and video interrupts
> shouldn't be generated in console mode, right?
>
> > I think you should try to reconfigure your
> > system so that devices do not share same IRQ
> > and see whether that 'fix' the problem.
>
> There are no options in my notebook's BIOS to reconfigure interrupts or
> disable
> devices.
>
> > BTW, can you show your /proc/interrupts ?
>
> Attached.
>
> > --
> > vda
>
> Carl Thompson
>

Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2004-02-17 14:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17  5:41 Carl Thompson
2004-02-17  6:54 ` vda
2004-02-17  7:14   ` Carl Thompson
2004-02-17  9:49     ` vda
2004-02-17 14:14       ` Carl Thompson
2004-02-17 14:39         ` Richard B. Johnson [this message]
2004-02-17 20:30           ` Carl Thompson
2004-02-17 22:33         ` Pavel Machek
2004-02-18  0:32           ` Carl Thompson
2004-02-18 22:13             ` Vlasenko Denis
2004-02-18 23:20               ` Carl Thompson
2004-02-19 21:04                 ` Vlasenko Denis

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=Pine.LNX.4.53.0402170927330.912@chaos \
    --to=root@chaos.analogic.com \
    --cc=cet@carlthompson.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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®