Hauppag nova s2 and kernel panic

Raymond Paulsen

Anyone have problems with hauppag win tv nova s2 dvb-s2 cards and debian 7

I have a dell poweredge 2650 with 3 dvb-s2 cards.
This server is kernel panicking after a day or two running.

Same server did run with debian 6 for 3 years without kernel panic.

Hardware error is ruled out . I have swaped 3 identical servers. Ram, disk, tuners. Evrything is changed.

This is a software error some place. I think it might be the hauppag driver or debian7

Anders Lund

I have some kind of similar problem. Running Ubuntu 12.04. What does your log say when you get the kernel panic?

Raymond Paulsen

I did never find the couse for this. But i ha e some teorys :)

There is a bug in the newest debian kernel, related with apic
Follow boot closly and you see some apic error. This can be disabled in grub with option noapic

But this is a hard error. Kernel have trouble with bios api. You need to have latest bios on your server.

The other probable couse is the firmware to the dvb cards. Its so crapy this hauppage shit.. :)

I have orderd a new tbs 4 tuner cards similar to what adam use.

I did a freesh install of debian when the new tvheadend was released with new framwork, sins that time i have had no issues.

My server was also cloged up with some dust. I dont have overpressurized server rom ready yet.

I took out the dvb cards and refitted them.

After i did this i have had no issues.. kernel panic is not coused by tvheadend but hardware or driver issues related to dvb cards. What drivers did you use? And how did you install it?

Memory can also couse this issues. I bought new ram for my server just to eliminate that issue. ECC was triggered a couple of times with old ram. This indicates its lived its life. ECC ram is not something that is commonly found in home computers.

Anders Lund

At the moment I use the standard firmware that comes with the package "linux-firmware" (from standard Ubuntu 12.04 repositories). dmesg shows:

cx24116_load_firmware: FW version 1.26.90.0

But this machine is a crappy old Dell Optiplex 745, so it could perhaps be many reasons. I've used this firmware before without problems. That was on another machine and older software (Ubuntu and tvheadend).

Also see a lot of messages like these in dmesg:


[45312.097803] cx88[0]: irq mpeg  [0x80000] pci_abort*
[45312.097809] cx88[0]/2-mpeg: general errors: 0x00080000

But problem is the real crash is not something that is consistent. It is hard to reproduce the problem when I want.

Rachel Greenham

FWIW I believe I have one of these cards. (It's called the same thing but may differ in detail. lscpi gives:


09:01.0 Multimedia video controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
09:01.1 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05)
09:01.2 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05)
09:01.4 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [IR Port] (rev 05)

I'm not suffering your problems. Currently on Ubuntu 13.10, but have also used it since 12.04, possibly even earlier.

FWIW I believe the cx24116 firmware in use is the dvb-fe-cx24116.fw which is actually from linux-firmware-nonfree. Maybe that makes a difference. However, my dmesg output for load_firmware is identical to yours. (Actually from rotated syslog; I just realised, because of looking for this, that the kernel's dumping tons of stack traces to my logs because, i think, of the fglrx driver, so dmesg from boot had scrolled out of existence, but that's another story):

syslog.2.gz:Nov 17 14:01:32 twilight kernel: [ 20.675718] cx24116_load_firmware: FW version 1.26.90.0

also


root@twilight:/var/log# zgrep cx88 syslog.2.gz 
Nov 17 14:01:25 twilight kernel: [   13.506245] cx88/0: cx2388x v4l2 driver version 0.0.9 loaded
Nov 17 14:01:25 twilight kernel: [   13.509617] cx88[0]: subsystem: 0070:6906, board: Hauppauge WinTV-HVR4000(Lite) DVB-S/S2 [card=69,autodetected], frontend(s): 1
Nov 17 14:01:25 twilight kernel: [   13.519861] cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.9 loaded
Nov 17 14:01:25 twilight kernel: [   13.687625] cx88[0]: hauppauge eeprom: model=69100
Nov 17 14:01:25 twilight kernel: [   13.714842] input: cx88 IR (Hauppauge WinTV-HVR400 as /devices/pci0000:00/0000:00:1e.0/0000:09:01.1/rc/rc0/input20
Nov 17 14:01:25 twilight kernel: [   13.714884] rc0: cx88 IR (Hauppauge WinTV-HVR400 as /devices/pci0000:00/0000:00:1e.0/0000:09:01.1/rc/rc0
Nov 17 14:01:25 twilight kernel: [   13.717907] cx88[0]/1: CX88x/0: ALSA support for cx2388x boards
Nov 17 14:01:25 twilight kernel: [   13.718506] cx88[0]/0: found at 0000:09:01.0, rev: 5, irq: 17, latency: 64, mmio: 0xf7000000
Nov 17 14:01:25 twilight kernel: [   13.718616] cx88[0]/0: registered device video0 [v4l2]
Nov 17 14:01:25 twilight kernel: [   13.718683] cx88[0]/0: registered device vbi0
Nov 17 14:01:25 twilight kernel: [   13.718725] cx88[0]/2: cx2388x 8802 Driver Manager
Nov 17 14:01:25 twilight kernel: [   13.718867] cx88[0]/2: found at 0000:09:01.2, rev: 5, irq: 17, latency: 64, mmio: 0xf9000000
Nov 17 14:01:25 twilight kernel: [   13.720825] input: MCE IR Keyboard/Mouse (cx88xx) as /devices/virtual/input/input21
Nov 17 14:01:25 twilight kernel: [   13.721435] rc rc0: lirc_dev: driver ir-lirc-codec (cx88xx) registered at minor = 0
Nov 17 14:01:25 twilight kernel: [   13.732168] cx88/2: cx2388x dvb driver version 0.0.9 loaded
Nov 17 14:01:25 twilight kernel: [   13.732172] cx88/2: registering cx8802 driver, type: dvb access: shared
Nov 17 14:01:25 twilight kernel: [   13.732174] cx88[0]/2: subsystem: 0070:6906, board: Hauppauge WinTV-HVR4000(Lite) DVB-S/S2 [card=69]
Nov 17 14:01:25 twilight kernel: [   13.732176] cx88[0]/2: cx2388x based DVB/ATSC card
Nov 17 14:01:25 twilight kernel: [   13.732177] cx8802_alloc_frontends() allocating 1 frontend(s)
Nov 17 14:01:25 twilight kernel: [   13.739601] DVB: registering new adapter (cx88[0])
Nov 17 14:01:25 twilight kernel: [   13.739607] cx88-mpeg driver manager 0000:09:01.2: DVB: registering adapter 0 frontend 0 (Conexant CX24116/CX24118)...
Nov 17 14:01:25 twilight tvheadend[1230]: v4l: /dev/video0: cx8800 Hauppauge WinTV-HVR4000(Lite) D PCI:0000:09:01.0 capabilities: 0x85010011
Nov 17 14:01:33 twilight kernel: [   21.537398] cx88[0]: irq mpeg  [0x100000] ts_err?*
Nov 17 14:01:33 twilight kernel: [   21.537401] cx88[0]/2-mpeg: general errors: 0x00100000

I notice at the end of that I am getting the same thing you reported... but only that once, in all my syslogs still in rotation, during the last boot; not even in a couple of other earlier boots still in logrotate. Not all the time, not happening a lot, and the one time it did happen, I don't believe it was associated with a kernel panic. (I don't remember a failed boot lately.)

Could it possibly be the problem is using three of these cards at once in the same machine? :)

Anders Lund

Rachel Greenham wrote:
> FWIW I believe I have one of these cards. (It's called the same thing but may differ in detail. lscpi gives:
>
> [...]
>
> I'm not suffering your problems. Currently on Ubuntu 13.10, but have also used it since 12.04, possibly even earlier.
>

> FWIW I believe the cx24116 firmware in use is the dvb-fe-cx24116.fw which is actually from linux-firmware-nonfree. Maybe that makes a difference. However, my dmesg output for load_firmware is identical to yours. (Actually from rotated syslog; I just realised, because of looking for this, that the kernel's dumping tons of stack traces to my logs because, i think, of the fglrx driver, so dmesg from boot had scrolled out of existence, but that's another story):

I wrote wrong. I'm using the same firmware, from linux-firmware-nonfree.

> [...]
>
> also
>
> [...]
>
> I notice at the end of that I am getting the same thing you reported... but only that once, in all my syslogs still in rotation, during the last boot; not even in a couple of other earlier boots still in logrotate. Not all the time, not happening a lot, and the one time it did happen, I don't believe it was associated with a kernel panic. (I don't remember a failed boot lately.)
>

> Could it possibly be the problem is using three of these cards at once in the same machine? :)

In my machine I only have one card, but the OP had three it seemed like.

Raymond Paulsen

You use outdated firmware. That is the problem.
Look ant linuxtv for a updated guide how to install the correct firware.

Do not use apt. Install it from scratch.

I will upload firmware latertoday and a guide how to install.

Anders Lund

It doesn't say in the wiki of linuxtv that 1.26.90.0 is "broken", and updated firmware isn't necessary more "correct". I'm missing some kind of information stating that 1.26.90.0 is broken in Ubuntu 12.04. That would help, and could also be good to bring on to others so that linux-firmware-nonfree is updated with latest "correct" version of the firmware...

But, please, specific guide on installation and version you're referring to would be nice to have, so happy if you post this. It is worth the shot. As of now I'm kind of out of ideas on how to solve this.

Raymond Paulsen

1.26.90.0 has many firmware types...

24116 is outdated.. averything with hauppage is crap they cant do properly version controll either

88x_2_126_28225_WHQL.zip

this is the correct you should use

Note: There seems to be a more recent version of this firmware:

There´s a forum article describing how to extract the firmware: [1] --- see post #3. The download link to get the driver now seems to be [2]. Download it with:

wget http://www.wintvcd.co.uk/drivers/88x_2_126_28225_WHQL.zip

Extract the firmware and put it in the firmware directory :

unzip -jo 88x_2_126_28225_WHQL.zip Driver88/hcw88bda.sys

sudo dd if=hcw88bda.sys of=/lib/firmware/dvb-fe-cx24116-1.26.90.0.fw bs=1 skip=105768 count=32290

sudo ln -s /lib/firmware/dvb-fe-cx24116-1.26.90.0.fw /lib/firmware/dvb-fe-cx24116.fw

For verification of hcw88bda.sys in this version of the driver:

md5sum -b hcw88bda.sys

3f685a2ca6d1dae35b10c06f3a538d82 *hcw88bda.sys

The firmware will be reported as

sudo dmesg|grep cx

cx24116_load_firmware: FW version 1.26.90.0

Anders Lund

I'm giving it a shot. Rebooted with new "version" now.

Raymond Paulsen

Let us know how it goes :)

Anders Lund

John Cruzo wrote:

> Let us know how it goes :)

Didn't seem to change anything. I can see some messages like this in syslog before it hangs:


[37601.824004] WARNING: at /build/buildd/linux-3.2.0/kernel/watchdog.c:241 watchdog_overflow_callback+0x9a/0xc0()
[37601.824004] Hardware name: OptiPlex 745                 
[37601.824004] Watchdog detected hard LOCKUP on cpu 1
[37601.824004] Modules linked in: isl6421 cx24116 cx88_dvb cx88_vp3054_i2c videobuf_dvb dvb_core rc_hauppauge cx88_alsa snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep tuner dcdbas snd_pcm cx8800 snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq ir_lirc_codec lirc_dev ir_
nd_timer snd_seq_device ir_jvc_decoder ir_rc6_decoder radeon ir_rc5_decoder ir_nec_decoder cx8802 cx88xx rc_core videobuf_dma_sg tveeprom v4l2_common videodev v4l2_compat_ioctl32 videobuf_core psmouse rfcomm serio_raw btcx_risc snd ttm drm_kms_helper drm soundcore snd_page_alloc parpo
_hid bluetooth lp parport raid10 raid456 async_pq async_xor xor async_memcpy async_raid6_recov tg3 raid6_pq async_tx raid1 raid0 multipath linear
[37601.824004] Pid: 4617, comm: cx88[0] dvb Not tainted 3.2.0-56-generic #86-Ubuntu
[37601.824004] Call Trace:
[37601.824004]  <NMI>  [<ffffffff810681df>] warn_slowpath_common+0x7f/0xc0
[37601.824004]  [<ffffffff810682d6>] warn_slowpath_fmt+0x46/0x50
[37601.824004]  [<ffffffff810d98ba>] watchdog_overflow_callback+0x9a/0xc0
[37601.824004]  [<ffffffff81113656>] __perf_event_overflow+0x96/0x1f0
[37601.824004]  [<ffffffff81110c11>] ? perf_event_update_userpage+0x11/0xc0
[37601.824004]  [<ffffffff810249da>] ? x86_perf_event_set_period+0xda/0x150
[37601.824004]  [<ffffffff81113bb4>] perf_event_overflow+0x14/0x20
[37601.824004]  [<ffffffff810290f3>] intel_pmu_handle_irq+0x163/0x210
[37601.824004]  [<ffffffff81662d11>] perf_event_nmi_handler+0x21/0x30
[37601.824004]  [<ffffffff816625c9>] default_do_nmi+0x69/0x220
[37601.824004]  [<ffffffff81662800>] do_nmi+0x80/0x90
[37601.824004]  [<ffffffff81661bf0>] nmi+0x20/0x30
[37601.824004]  [<ffffffff8103ebc0>] ? __ticket_spin_lock+0x20/0x30
[37601.824004]  <<EOE>>  [<ffffffff8103ec59>] default_spin_lock_flags+0x9/0x10
[37601.824004]  [<ffffffff8166146e>] _raw_spin_lock_irqsave+0x2e/0x40
[37601.824004]  [<ffffffff8104f192>] __wake_up+0x32/0x70
[37601.824004]  [<ffffffffa02c2842>] dvb_dmxdev_ts_callback+0xb2/0x130 [dvb_core]
[37601.824004]  [<ffffffffa02c502c>] dvb_dmx_swfilter_packet+0x11c/0x440 [dvb_core]
[37601.824004]  [<ffffffff8108c217>] ? finish_wait+0x67/0x80
[37601.824004]  [<ffffffffa02c61ed>] dvb_dmx_swfilter+0xfd/0x180 [dvb_core]
[37601.824004]  [<ffffffffa01e9960>] videobuf_dvb_thread+0x150/0x7f0 [videobuf_dvb]
[37601.824004]  [<ffffffffa01e9810>] ? videobuf_dvb_start_feed+0xe0/0xe0 [videobuf_dvb]
[37601.824004]  [<ffffffff8108b67c>] kthread+0x8c/0xa0
[37601.824004]  [<ffffffff8166b974>] kernel_thread_helper+0x4/0x10
[37601.824004]  [<ffffffff8108b5f0>] ? flush_kthread_worker+0xa0/0xa0
[37601.824004]  [<ffffffff8166b970>] ? gs_change+0x13/0x13

Peter Smith

Same problem here (Nova S2 + Gigabyte Mobo). The system ran without any error for some years (Debian Squeeze). After upgrading to wheezy, it freezes every 3-5 days or so :-(

BIOS and cx24116-firmware are the newest versions ...

Raymond Paulsen

Iam still having problems with my dell poweredge 2850 with 3 of those cards, i use wheezy on it with manualy installed drivers, i havent tried the apt firmware yet.

but in general it get unstable, one card will fail to decode or some other weird shit happens after around 4-5 days. i think its related to debian, firmware or something.

the image cache function for icons does not work in debian either