[linux-dvb] Nova-s VDSB Problem : Disabling IRQ #18

To: <linux-dvb@linuxtv.org>
Subject: [linux-dvb] Nova-s VDSB Problem : Disabling IRQ #18
From: "christian jacobsen" <Christian.Jacobsen@stageholding.de>
Date: Mon, 11 Oct 2004 11:40:32 +0200
Content-class: urn:content-classes:message
Content-transfer-encoding: 8bit
Content-type: text/plain; charset="US-ASCII"
List-help: <mailto:ecartis@linuxtv.org?subject=help>
List-id: linux-dvb <linux-dvb.mail>
List-owner: <mailto:listmaster@convergence.de>
List-post: <mailto:linux-dvb@linuxtv.org>
List-software: Ecartis version 1.0.0
List-subscribe: <mailto:ecartis@linuxtv.org?subject=subscribe%20linux-dvb>
List-unsubscribe: <mailto:ecartis@linuxtv.org?subject=unsubscribe%20linux-dvb>
Sender: linux-dvb-bounce@linuxtv.org
Thread-index: AcSvdlmKsxRlGoTWRV+EbnAJCdNo0w==
Thread-topic: Nova-s VDSB Problem : Disabling IRQ #18

Hallo,

While trying to move to dvb-kernel I have installed SuSE 9.1 and had the
well Known VDSB (Video Data Stream Broken). With my current parallel
installed SuSE 8.0 system (kernel 2.4) I don't have that.

Looking at www.vdrportal.de a lot of people have this error :(

I think that I have found something here though, maybe it/I can help
finding this bug.
Please tell me what I can do to help ?

I have installed an Kernel 2.6.9-rc3-mm3 (kernel.org) and now I get this
error on the console :

Message from syslogd@vdr at Sat Oct  9 01:50:43 2004 ...
vdr kernel: Disabling IRQ #18

The Nova-s is on IRQ 18 (see below) ! 

After that I get the VDSB error, what could be the reason for this ?

With the standard 2.6.5-7.108 kernel from suse and and 2.6.9rc2 I don't
see this error, but still get the VDSB.

I am using ACPI and APIC with 2.6.9-rc3-mm3 with the Suse kernel only
ACPI.

My System :
1 DVB-s Rev 1.6
1 Nova-s
Tyan Dual Mainboard with 1 CPU P3 933
512MB RAM

This is how I can reproduce it. 

1. Load DVB Driver from kernel 2.6.9-rc3-mm3 
2. start VDR 1.3.12
3. start a recording.
4. stop the recording again (or let it recod til it is finished)
5. Wait a couple of hours
6. Error : vdr kernel: Disabling IRQ #18
7. When I now try to recod something I get a VDSB - even after reloading
the driver !


Here some more Infos (I used Streamdev before at that day, but it does
not matter)

Syslog :
Oct  9 01:42:50 vdr vdr[14711]: Streamdev: Closing connection to
XXX.XXX.XXX.XXX:2585
Oct  9 01:42:50 vdr vdr[14711]: Streamdev: Channel streamer thread ended
(pid=14711, tid=1112546224)
Oct  9 01:42:50 vdr vdr[14711]: receiver on device 2 thread ended
(pid=14711, tid=1121999792)
Oct  9 01:42:50 vdr vdr[14711]: buffer stats: 13348 (0%) used
Oct  9 01:50:43 vdr kernel: irq 18: nobody cared!
Oct  9 01:50:43 vdr kernel:  [__report_bad_irq+36/144]
__report_bad_irq+0x24/0x90
Oct  9 01:50:43 vdr kernel:  [<c013c824>] __report_bad_irq+0x24/0x90
Oct  9 01:50:43 vdr kernel:  [note_interrupt+123/160]
note_interrupt+0x7b/0xa0
Oct  9 01:50:43 vdr kernel:  [<c013c93b>] note_interrupt+0x7b/0xa0
Oct  9 01:50:43 vdr kernel:  [handle_IRQ_event+52/112]
handle_IRQ_event+0x34/0x70
Oct  9 01:50:43 vdr kernel:  [<c013c114>] handle_IRQ_event+0x34/0x70
Oct  9 01:50:43 vdr kernel:  [__do_IRQ+353/384] __do_IRQ+0x161/0x180
Oct  9 01:50:43 vdr kernel:  [<c013c2b1>] __do_IRQ+0x161/0x180
Oct  9 01:50:43 vdr kernel:  [do_IRQ+49/96] do_IRQ+0x31/0x60
Oct  9 01:50:43 vdr kernel:  [<c01086a1>] do_IRQ+0x31/0x60
Oct  9 01:50:43 vdr kernel:  [common_interrupt+24/32]
common_interrupt+0x18/0x20
Oct  9 01:50:43 vdr kernel:  [<c0106b3c>] common_interrupt+0x18/0x20
Oct  9 01:50:43 vdr kernel:  [pg0+545299025/1069110272]
uhci_free_td+0x1/0xe0 [uhci_hcd]
Oct  9 01:50:43 vdr kernel:  [<e0c72a51>] uhci_free_td+0x1/0xe0
[uhci_hcd]
Oct  9 01:50:43 vdr kernel:  [pg0+545307068/1069110272]
uhci_free_pending_tds+0x4c/0x60 [uhci_hcd]
Oct  9 01:50:43 vdr kernel:  [<e0c749bc>]
uhci_free_pending_tds+0x4c/0x60 [uhci_hcd]
Oct  9 01:50:43 vdr kernel:  [pg0+545307617/1069110272]
uhci_irq+0x111/0x210 [uhci_hcd]
Oct  9 01:50:43 vdr kernel:  [<e0c74be1>] uhci_irq+0x111/0x210
[uhci_hcd]
Oct  9 01:50:43 vdr kernel:  [pg0+543206036/1069110272]
usb_hcd_irq+0x34/0x70 [usbcore]
Oct  9 01:50:43 vdr kernel:  [<e0a73a94>] usb_hcd_irq+0x34/0x70
[usbcore]
Oct  9 01:50:43 vdr kernel:  [handle_IRQ_event+52/112]
handle_IRQ_event+0x34/0x70
Oct  9 01:50:43 vdr kernel:  [<c013c114>] handle_IRQ_event+0x34/0x70
Oct  9 01:50:43 vdr kernel:  [__do_IRQ+247/384] __do_IRQ+0xf7/0x180
Oct  9 01:50:43 vdr kernel:  [<c013c247>] __do_IRQ+0xf7/0x180
Oct  9 01:50:43 vdr kernel:  [do_IRQ+49/96] do_IRQ+0x31/0x60
Oct  9 01:50:43 vdr kernel:  [<c01086a1>] do_IRQ+0x31/0x60
Oct  9 01:50:43 vdr kernel:  [common_interrupt+24/32]
common_interrupt+0x18/0x20
Oct  9 01:50:43 vdr kernel:  [<c0106b3c>] common_interrupt+0x18/0x20
Oct  9 01:50:43 vdr kernel: handlers:
Oct  9 01:50:43 vdr kernel: [pg0+545202560/1069110272]
(interrupt_hw+0x0/0x350 [saa7146])
Oct  9 01:50:43 vdr kernel: [<e0c5b180>] (interrupt_hw+0x0/0x350
[saa7146])
Oct  9 01:50:43 vdr kernel: Disabling IRQ #18
<SNIP>

Now I program a recording (no I don't watch that crap ;) ) : 

Oct  9 02:01:02 vdr vdr[14711]: timer 37 (4 0201-0232 'Das
Familiengericht') start
Oct  9 02:01:02 vdr vdr[14711]: Title: 'Das Familiengericht' Subtitle:
'(null)'
Oct  9 02:01:02 vdr vdr[14711]: executing '/usr/local/bin/nq.sh before
"/video0/Das_Familiengericht/2004-10-09.02.01.30.99.rec"'
Oct  9 02:01:02 vdr vdr[14711]: record
/video0/Das_Familiengericht/2004-10-09.02.01.30.99.rec
Oct  9 02:01:03 vdr vdr[14711]: recording to
'/video0/Das_Familiengericht/2004-10-09.02.01.30.99.rec/001.vdr'
Oct  9 02:01:03 vdr vdr[14711]: recording thread started (pid=14711,
tid=1121999792)
Oct  9 02:01:03 vdr vdr[14711]: receiver on device 2 thread started
(pid=14711,tid=1112546224)
Oct  9 02:01:34 vdr vdr[14711]: ERROR: video data stream broken
Oct  9 02:01:34 vdr vdr[14711]: initiating emergency exit
Oct  9 02:01:34 vdr vdr[14711]: emergency exit requested - shutting down



#  cat /proc/interrupts
           CPU0
  0:    7533736    IO-APIC-edge  timer
  1:         10    IO-APIC-edge  i8042
  8:          2    IO-APIC-edge  rtc
  9:          0   IO-APIC-level  acpi
 10:    1502384   IO-APIC-level  uhci_hcd, uhci_hcd
 12:         93    IO-APIC-edge  i8042
 14:     196054    IO-APIC-edge  ide0
 15:         34    IO-APIC-edge  ide1
 17:    1152976   IO-APIC-level  eth0, CMI8738, saa7146 (0)
 18:    2500000   IO-APIC-level  saa7146 (1)
NMI:          0
LOC:    7533844
ERR:          0
MIS:          0

# lspci -v
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo 
PRO133x] (rev c4)
        Flags: bus master, medium devsel, latency 8
        Memory at f0000000 (32-bit, prefetchable)
        Capabilities: [a0] AGP version 2.0
        Capabilities: [c0] Power Management version 2

0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo 
MVP3/Pro133x AGP] (prog-if 00 [Normal decode])
        Flags: bus master, 66Mhz, medium devsel, latency 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        Capabilities: [80] Power Management version 2

0000:00:06.0 VGA compatible controller: ATI Technologies Inc Rage XL 
(rev 27) (prog-if 00 [VGA])
        Subsystem: ATI Technologies Inc Rage XL
        Flags: bus master, stepping, medium devsel, latency 32, IRQ 10
        Memory at f4000000 (32-bit, non-prefetchable)
        I/O ports at d000 [size=256]
        Memory at f6200000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [5c] Power Management version 2

0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super 
South] (rev 40)
        Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge
        Flags: bus master, stepping, medium devsel, latency 0
        Capabilities: [c0] Power Management version 2

0000:00:07.1 IDE interface: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06) 
(prog-if 8a [Master SecP PriP])
        Subsystem: VIA Technologies, Inc. 
VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
        Flags: bus master, medium devsel, latency 32
        I/O ports at d400 [size=16]
        Capabilities: [c0] Power Management version 2

0000:00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 1a) 
(prog-if 00 [UHCI])
        Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
        Flags: bus master, medium devsel, latency 32, IRQ 10
        I/O ports at d800 [size=32]
        Capabilities: [80] Power Management version 2

0000:00:07.3 USB Controller: VIA Technologies, Inc. USB (rev 1a) 
(prog-if 00 [UHCI])
        Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
        Flags: bus master, medium devsel, latency 32, IRQ 10
        I/O ports at dc00 [size=32]
        Capabilities: [80] Power Management version 2

0000:00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]

(rev 40)
        Subsystem: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
        Flags: medium devsel, IRQ 9
        Capabilities: [68] Power Management version 2

0000:00:0d.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 
100] (rev 08)
        Subsystem: Intel Corp. EtherExpress PRO/100+ Server Adapter 
(PILA8470B)
        Flags: bus master, medium devsel, latency 32, IRQ 17
        Memory at f6202000 (32-bit, non-prefetchable)
        I/O ports at e000 [size=64]
        Memory at f6000000 (32-bit, non-prefetchable) [size=1M]
        Capabilities: [dc] Power Management version 2

0000:00:0f.0 Multimedia controller: Philips Semiconductors SAA7146 (rev
01)
        Subsystem: Technotrend Systemtechnik GmbH: Unknown device 0000
        Flags: bus master, medium devsel, latency 128, IRQ 17
        Memory at f6203000 (32-bit, non-prefetchable)

0000:00:10.0 Multimedia controller: Philips Semiconductors SAA7146 (rev
01)
        Subsystem: Technotrend Systemtechnik GmbH: Unknown device 1003
        Flags: bus master, medium devsel, latency 128, IRQ 18
        Memory at f6204000 (32-bit, non-prefetchable)

0000:00:12.0 Multimedia audio controller: C-Media Electronics Inc CM8738

(rev 10)
        Subsystem: C-Media Electronics Inc CMI8738/C3DX PCI Audio Device
        Flags: bus master, medium devsel, latency 64, IRQ 17
        I/O ports at e800
        Capabilities: [c0] Power Management version 2

Greeting
Christian Jacobsen

Prev by Date: [linux-dvb] Re: refactoring
Next by Date: [linux-dvb] Re: Which DVB-T card has best reception characteristics(was: Visionplus DVB-T USB strange reception quality...)
Previous by thread: [linux-dvb] Re: 5 Months and counting...
Next by thread: [linux-dvb] Trying to get Nexus card running
Index(es):
- Date
- Thread

Home | Main Index | Thread Index