Intensity Pro died while updating firmware on gentoo 4.0.5

Hello.
I wrote to support about my problem, and they asked me to send e-mail to developers@blackmagicdesign.com. I tried, but message was not sent due to "Relay access denied" from my mail server. Now I am here with my problem.

when I tried to update firmware on capture card, it failed (dmesg output following). After a reboot - the card is not working, it's not visible with lspci.

This is Intensity Pro.

I have a Gentoo system with kernel 4.0.5:

#uname -a
Linux fp-gentoo 4.0.5-gentoo #1 SMP PREEMPT Wed Oct 28 19:44:32 UTC 2015 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux

When I tried to update firmware for Intencity Pro capture card with blackmagic firmware updater from Blackmagic_Desktop_Video_Linux_10.5, the process freezed at 0% for a long time (>15 minutes). Then I looked into dmesg output and found this:

Code: Select all

[ 1582.757602] blackmagic: Loading driver (version: 10.5a17)
[ 1582.757916] blackmagic[WARNING]: Hardware device is not usable, please run firmware utility to check firmware version status
[ 1582.757918] blackmagic: Successfully loaded device "blackmagic!dv0" [pci@0000:03:00.0]
[ 1612.695809] BUG: unable to handle kernel paging request at ffffc90010b01010
[ 1612.695812] IP: [<ffffffffa06a1296>] _ZN41HardwareAbstractionDeckLinkHDExtremeClass17programEEPROM_SPIEPcjPb+0x1f6/0x460 [blackmagic]
[ 1612.695827] PGD 26584b067 PUD 26584c067 PMD 26224b067 PTE 800000021c1e0027
[ 1612.695829] Oops: 0001 [#1] PREEMPT SMP
[ 1612.695831] Modules linked in: blackmagic(PO) ipv6 binfmt_misc joydev snd_hda_codec_hdmi nvidia(PO) snd_hda_codec_realtek snd_hda_codec_generic rgb133(PO) snd_hda_intel x86_pkg_temp_thermal snd_hda_controller coretemp snd_hda_codec microcode r8169 snd_hwdep pcspkr mii snd_pcm drm snd_timer snd i2c_i801 xhci_pci thermal fan battery rtc_cmos video backlight acpi_cpufreq processor button thermal_sys xts aesni_intel glue_helper lrw gf128mul ablk_helper cryptd aes_x86_64 cbc sha256_generic libiscsi scsi_transport_iscsi e1000 fuse nfs lockd grace sunrpc jfs multipath linear raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq raid1 raid0 dm_snapshot dm_bufio dm_crypt dm_mirror dm_region_hash dm_log dm_mod firewire_core hid_sunplus hid_sony led_class hid_samsung hid_pl
[ 1612.695854] hid_petalynx hid_gyration sl811_hcd usbhid xhci_hcd ohci_hcd uhci_hcd usb_storage ehci_pci ehci_hcd usbcore usb_common sx8 DAC960 mptsas scsi_transport_sas mptfc scsi_transport_fc mptspi scsi_transport_spi mptscsih mptbase gdth arcmsr sg pdc_adma sata_inic162x sata_mv ata_piix ahci libahci sata_qstor sata_sx4 sata_sil24 pata_sl82c105 pata_marvell pata_oldpiix pata_mpiix libata
[ 1612.695866] CPU: 0 PID: 14461 Comm: blackmagicd Tainted: P W O 4.0.5-gentoo #1
[ 1612.695867] Hardware name: System manufacturer System Product Name/Z170-K, BIOS 0323 07/17/2015
[ 1612.695868] task: ffff880264d53120 ti: ffff880257478000 task.ti: ffff880257478000
[ 1612.695869] RIP: 0010:[<ffffffffa06a1296>] [<ffffffffa06a1296>] _ZN41HardwareAbstractionDeckLinkHDExtremeClass17programEEPROM_SPIEPcjPb+0x1f6/0x460 [blackmagic]
[ 1612.695881] RSP: 0018:ffff88025747bde8 EFLAGS: 00010246
[ 1612.695882] RAX: 0000000000008424 RBX: ffffc90010b01010 RCX: ffffffffa06d53b0
[ 1612.695882] RDX: 0000000000008424 RSI: ffffc90010a00224 RDI: ffffc90010a00224
[ 1612.695883] RBP: 0000000000000000 R08: ffff880257478000 R09: 0000000000007e43
[ 1612.695884] R10: 000000000000ba0b R11: ffffffffa06a9160 R12: ffff8802063f8000
[ 1612.695884] R13: ffffffffa06c8019 R14: 0000000000000100 R15: 0000000000000000
[ 1612.695885] FS: 0000000000000000(0000) GS:ffff88026ec00000(0000) knlGS:0000000000000000
[ 1612.695886] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1612.695887] CR2: ffffc90010b01010 CR3: 0000000001717000 CR4: 00000000003406f0
[ 1612.695887] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 1612.695888] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 1612.695888] Stack:
[ 1612.695889] ffff88025747be08 000710748153ab19 ffffc90010b01010 0000000300000000
[ 1612.695890] ffff88025747be28 ffffffffa06c92fa ffff880264000000 0000000000000000
[ 1612.695892] 0000000000000000 ffff880205c34000 0000000000000000 ffffffffa06a1500
[ 1612.695893] Call Trace:
[ 1612.695900] [<ffffffffa06c92fa>] ? dl_gate_unlock+0x25/0x2a [blackmagic]
[ 1612.695911] [<ffffffffa06a1500>] ? _ZN41HardwareAbstractionDeckLinkHDExtremeClass17programEEPROM_SPIEPcjPb+0x460/0x460 [blackmagic]
[ 1612.695918] [<ffffffffa06c8019>] ? dl_pci_unregister_interrupt+0x30/0x30 [blackmagic]
[ 1612.695928] [<ffffffffa06a155b>] ? _ZN41HardwareAbstractionDeckLinkHDExtremeClass13programEEPROMEPcjPb+0x5b/0xb0 [blackmagic]
[ 1612.695936] [<ffffffffa06c0eb3>] ? _ZN15UserClientClass27programEEPROMThreadFunctionEPS_i+0xe3/0x130 [blackmagic]
[ 1612.695943] [<ffffffffa06c802a>] ? dl_thread_wrapper+0x11/0x1f [blackmagic]
[ 1612.695945] [<ffffffff8104e8ba>] ? kthread+0xcd/0xd5
[ 1612.695947] [<ffffffff8104e7ed>] ? kthread_create_on_node+0x173/0x173
[ 1612.695949] [<ffffffff8153b248>] ? ret_from_fork+0x58/0x90
[ 1612.695951] [<ffffffff8104e7ed>] ? kthread_create_on_node+0x173/0x173
[ 1612.695951] Code: ff 0f 85 3a 01 00 00 83 6c 24 1c 01 0f 84 c6 00 00 00 48 8d 54 24 30 be 01 00 00 00 4c 89 e7 e8 d1 bd ff ff 48 8b 5c 24 10 31 ed <0f> b6 33 4c 89 e7 83 c5 01 48 83 c3 01 e8 88 be ff ff 44 39 f5
[ 1612.695970] RIP [<ffffffffa06a1296>] _ZN41HardwareAbstractionDeckLinkHDExtremeClass17programEEPROM_SPIEPcjPb+0x1f6/0x460 [blackmagic]
[ 1612.695981] RSP <ffff88025747bde8>
[ 1612.695981] CR2: ffffc90010b01010
[ 1612.695983] ---[ end trace af75ddde8d305163 ]---


p.s. Firmware updater worked fine before on gentoo 3.18 (64bit) and Desktop Video version 10.3.

Maybe, it’s a firmware updater program fails to work on 4.x.x kerenel. According to thread 38702 (can't insert url) on this forum, other users have observed same behavior on 4.1.6 kernel with blackmagic v10.4.3.

I am not worrying about warranty or a replacement, we don’t need that. The problem is – we use these blackmagic capture cards a lot, and now we want to migrate all our systems to gentoo with 4.x.x kernel, we need a working blackmagic driver for that.

How can I debug such behavior of a firmware updater? Because, If I try different versions of a kernel or a blackmagic driver, and when I will be updating, it will kill a card each time?
Can someone test blackmagic software on 4.x.x kernel and post results, please?

The card has a USB jack on it. Can it be restored through this USB, or with some debugging electronic tools?

Thank you

The Blackmagic response to inquiry about 4.x.x kernels was that it supports whatever kernel the latest Ubuntu is using. Since latest Ubuntu 15.10 looks like it has kernel 4.2.1, we could assume that a new driver to support it will be released real soon now.

Hi,

If you know what you are doing, you can compile your own modules. I updated the blackmagic kernel modules from 10.5 to compile for kernels >4.2.0. It works for me, but of course your mileage may vary.

https://github.com/iperry/blackmagic
https://github.com/iperry/blackmagic-io/commits/master

I'm running these modules successfully on a 4.2.3 kernel.

If you know what you are doing, you can compile your own modules. I updated the blackmagic kernel modules from 10.5 to compile for kernels >4.2.0. It works for me, but of course your mileage may vary.
...
I'm running these modules successfully on a 4.2.3 kernel.

Thank you for your reply.
First I tried 10.3 modules, got copmile errors, but 10.5 modules compiled fine on 4.0.5 kernel.
For now, we'll stay on 3.18 kernel and 10.3 modules for some time. If there will be a need to migrate to 4.x.x (because of some new hardware, that don't work on gentoo 3.18), I will reflash card on 3.18 kernel and then work with it on 4.x.x. I think, this is the safest what to do.
I'm just scare to burn out another card here.