mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Hanno Zulla <abos@hanno.de>
Cc: Gerd Hoffmann <kraxel@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Slow IRQ handling? (was: Nova-T, cx88-dvb & "cx88_wakeup: 2 buffers handled (should be 1)")
Date: Thu, 19 Jul 2007 17:13:45 -0300	[thread overview]
Message-ID: <1184876025.4049.275.camel@gaivota> (raw)
In-Reply-To: <4694BF03.5070508@hanno.de>

Hi Hanno,

Em Qua, 2007-07-11 às 13:29 +0200, Hanno Zulla escreveu:
> Hi,
> 
> [ please cc me. Thanks. ]
> 
> > I've added the printk some years ago.  I stopped maintaining v4l/dvb
> > bits two years ago, so it's a bit a shot into the dark because I have no
> > idea what has changed recently in the driver.
> 
> Indeed, it appears that this driver has no maintainer right now. (Or the
> maintainer is on holidays.
It is the second :) I was in vacations.

> > Could also be the irq handler for the other device sharing the same irq
> > being very slow.  Any pattern here that it is linked to some specific
> > device sharing the irq?
> 
> No idea, I did not see any pattern here. Also, the problem on my system
> appears with every PCI slot I tried.
> 
> What do you suggest? How can I debug this issue so that you kernel guys
> can look into it?

Debugging this type of trouble is not always easy, since it is
system-specific, and probably not directly related to cx88 driver, since
cx88 drivers work fine on several configurations. 

So, we need more details about your configuration. You may try also to
use the latest vanilla linux kernel (2.6.22.1). Maybe this might be an
issue already handled.

You can do a "cat /proc/interrupts". This will help to identify the
shared interrupts and if the processors are balancing the IRQ handling. 

There are some tutorials that may help seeking for a bug:
Documentation/BUG-HUNTING

Also, the file /REPORTING-BUGS, at the main tree contains some
orientations on what kind of information can be retrieved for you to
report a bug.

This can also help you to force the handling of an IRQ to an specific
CPU:
Documentation/IRQ-affinity.txt                                                                          

-- 
Cheers,
Mauro


      reply	other threads:[~2007-07-19 20:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 17:34 Nova-T, cx88-dvb & "cx88_wakeup: 2 buffers handled (should be 1)" Hanno Zulla
2007-07-11  8:55 ` Gerd Hoffmann
2007-07-11 11:29   ` Slow IRQ handling? (was: Nova-T, cx88-dvb & "cx88_wakeup: 2 buffers handled (should be 1)") Hanno Zulla
2007-07-19 20:13     ` Mauro Carvalho Chehab [this message]

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=1184876025.4049.275.camel@gaivota \
    --to=mchehab@infradead.org \
    --cc=abos@hanno.de \
    --cc=kraxel@redhat.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

all inboxes | Powered by JetHome®