linux-kernel - Re: Nova-T, cx88-dvb & "cx88_wakeup: 2 buffers handled (should be 1)"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 11 Jul 2007 10:55:25 +0200
From:	Gerd Hoffmann <kraxel@...hat.com>
To:	Hanno Zulla <abos@...no.de>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Nova-T, cx88-dvb & "cx88_wakeup: 2 buffers handled (should be
 1)"

> Using a Nova-T dvb card, I get the following in /var/log/messages...
> 
> 22:09:54 kernel: cx88_wakeup: 2 buffers handled (should be 1)

> ...every few seconds while watching TV with xine or other dvb-apps. The
> event results in a visible interruption of the video stream.

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.

The message is in no way critical, the driver should cope just fine with
the situation, and as usually some more buffers are queued for dma it
also doesn't imply dvb stream data got lost.  It seems in your case some
data actually got lost though, otherwise the effect wouldn't be visible.

Background:  The card raises an interrupt for each filled buffer, so in
theory each time the irq handler runs it should handle a single buffer.
 If it is more than one it means the irq handler wasn't called in time
or wasn't called at all for some reason.

Could be someone in the kernel blocked interrupts for a insane long
time, so the hardware managed to fill the one more buffer before the irq
handler was actually called.  Could be IRQ handling in the cx88 driver
is screwed.  Could be a scheduling issue (Is this a core2 duo?  If so
check the longish discussion on about that here in lkml, subject "long
freezes on thinkpad t60").

> The problem appears to be shared irq resources [3]. However, my
> mainboard doesn't allow to choose specific irqs for pci slots and
> anyway, shared irqs shouldn't break this dvb card, in the first place.

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?

cheers,
  Gerd
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/