Have been setting up zoneminder on CentOS 6. I have the cameras up and running just as monitor's and they appear to work fine. However as soon as I activate the Record function I get a kernel panic of:
Dec 17 19:01:48 cctv kernel: ------------[ cut here ]------------
Dec 17 19:01:48 cctv kernel: WARNING: at lib/list_debug.c:48 list_del+0x56/0x90() (Not tainted)
Dec 17 19:01:48 cctv kernel: Hardware name:
Dec 17 19:01:48 cctv kernel: list_del corruption. prev->next should be f294f000, but was 625e5b59
Dec 17 19:01:48 cctv kernel: Modules linked in: autofs4 sunrpc p4_clockmod ipv6 dm_mirror dm_region_hash dm_log ppdev parport_pc parport tuner tvaudio tda7432 bttv v4l2_common videodev ir_common videobuf_dma_sg videobuf_core btcx_risc t$
Dec 17 19:01:48 cctv kernel: Pid: 1643, comm: zmc Not tainted 2.6.32-71.29.1.el6.i686 #1
Dec 17 19:01:48 cctv kernel: Call Trace:
Dec 17 19:01:48 cctv kernel: [<c0450201>] ? warn_slowpath_common+0x81/0xc0
Dec 17 19:01:48 cctv kernel: [<c05efc66>] ? list_del+0x56/0x90
Dec 17 19:01:48 cctv kernel: [<c05efc66>] ? list_del+0x56/0x90
Dec 17 19:01:48 cctv kernel: [<c04502d3>] ? warn_slowpath_fmt+0x33/0x40
Dec 17 19:01:48 cctv kernel: [<c05efc66>] ? list_del+0x56/0x90
Dec 17 19:01:48 cctv kernel: [<c0511cc2>] ? free_block+0xa2/0x130
Dec 17 19:01:48 cctv kernel: [<c0511b9a>] ? kmem_cache_free+0x14a/0x160
Dec 17 19:01:48 cctv kernel: [<c04d80a1>] ? mempool_free+0x81/0x90
Dec 17 19:01:48 cctv kernel: [<c04d80a1>] ? mempool_free+0x81/0x90
Dec 17 19:01:48 cctv kernel: [<c054a664>] ? bio_put+0x24/0x30
Dec 17 19:01:48 cctv kernel: [<f7e454d4>] ? clone_endio+0x84/0xe0 [dm_mod]
Dec 17 19:01:48 cctv kernel: [<c054a552>] ? bio_endio+0x12/0x30
Dec 17 19:01:48 cctv kernel: [<c05cd35d>] ? blk_update_request+0xed/0x3e0
Dec 17 19:01:48 cctv kernel: [<c05cd663>] ? blk_update_bidi_request+0x13/0x60
Dec 17 19:01:48 cctv kernel: [<c05ce5f8>] ? blk_end_bidi_request+0x28/0x70
Dec 17 19:01:48 cctv kernel: [<c05ce68f>] ? blk_end_request+0xf/0x20
Dec 17 19:01:48 cctv kernel: [<c06b870b>] ? scsi_io_completion+0x8b/0x4e0
Dec 17 19:01:48 cctv kernel: [<c06b8546>] ? scsi_device_unbusy+0x76/0xa0
Dec 17 19:01:48 cctv kernel: [<c05d30fa>] ? blk_done_softirq+0x5a/0x70
Dec 17 19:01:48 cctv kernel: [<c045726f>] ? __do_softirq+0x8f/0x1b0
Dec 17 19:01:48 cctv kernel: [<c04b0a71>] ? move_native_irq+0x11/0x50
Dec 17 19:01:48 cctv kernel: [<c04573cd>] ? do_softirq+0x3d/0x50
Dec 17 19:01:48 cctv kernel: [<c0457525>] ? irq_exit+0x65/0x70
Dec 17 19:01:48 cctv kernel: [<c040b7d0>] ? do_IRQ+0x50/0xc0
Dec 17 19:01:48 cctv kernel: [<c04574f5>] ? irq_exit+0x35/0x70
Dec 17 19:01:48 cctv kernel: [<c0425ae4>] ? smp_apic_timer_interrupt+0x54/0x90
Dec 17 19:01:48 cctv kernel: [<c040a0f0>] ? common_interrupt+0x30/0x38
Dec 17 19:01:48 cctv kernel: ---[ end trace 4e5f786c71cd6b27 ]---
Dec 17 19:01:49 cctv kernel: bttv3: OCERR @ 348a2000,bits: HSYNC FDSR OCERR*
Dec 17 19:01:49 cctv kernel: bttv3: OCERR @ 348a2014,bits: HSYNC FDSR OCERR*
Dec 17 19:01:49 cctv kernel: bttv3: OCERR @ 348a2000,bits: HSYNC FDSR OCERR*
Dec 17 19:01:49 cctv kernel: bttv3: OCERR @ 348a2000,bits: HSYNC FDSR OCERR*
Dec 17 19:01:49 cctv kernel: bttv3: OCERR @ 348a2000,bits: HSYNC FDSR OCERR*
Dec 17 19:01:49 cctv kernel: bttv3: OCERR @ 348a2000,bits: HSYNC FDSR OCERR*
Dec 17 19:01:49 cctv kernel: bttv3: OCERR @ 348a2014,bits: HSYNC FDSR OCERR*
Dec 17 19:01:49 cctv kernel: bttv3: OCERR @ 348a2014,bits: HSYNC FDSR OCERR*
Dec 17 19:01:49 cctv kernel: bttv3: OCERR @ 348a2000,bits: HSYNC FDSR OCERR*
Dec 17 19:01:49 cctv kernel: bttv3: OCERR @ 348a2000,bits: HSYNC FDSR OCERR*
Dec 17 19:01:50 cctv kernel: bttv3: OCERR @ 348a2000,bits: HSYNC FDSR OCERR*
Dec 17 19:01:50 cctv kernel: bttv3: OCERR @ 348a2000,bits: HSYNC FDSR OCERR*
Dec 17 19:01:50 cctv kernel: bttv3: OCERR @ 348a2000,bits: HSYNC FDSR OCERR*
Dec 17 19:01:50 cctv kernel: bttv3: OCERR @ 348a2000,bits: HSYNC FDSR OCERR*
Dec 17 19:01:50 cctv kernel: bttv3: OCERR @ 348a2000,bits: HSYNC FDSR OCERR*
Dec 17 19:01:50 cctv zmc_dvideo3[1651]: WAR [Capture failure, possible signal loss?: Input/output error]
Dec 17 19:01:50 cctv kernel: bttv3: timeout: drop=0 irq=1288/1289, risc=348a201c, bits: HSYNC
Dec 17 19:01:50 cctv zmc_dvideo3[1651]: ERR [Failed to capture image from monitor 3 (0/1)]
Dec 17 19:01:50 cctv zmdc[1601]: ERR ['zmc -d /dev/video3' exited abnormally, exit status 255]
Dec 17 19:01:50 cctv zmdc[1601]: INF [Starting pending process, zmc -d /dev/video3]
Dec 17 19:01:50 cctv zmdc[1601]: INF ['zmc -d /dev/video3' starting at 11/12/17 19:01:50, pid = 1730]
Dec 17 19:01:50 cctv zmdc[1730]: INF ['zmc -d /dev/video3' started at 11/12/17 19:01:50]
Dec 17 19:01:50 cctv zmc_dvideo3[1730]: INF [Starting Capture]
Dec 17 19:01:53 cctv zmpkg[1738]: INF [Command: stop]
--
I understand that this is maybe a hardware/driver issue, but I have no idea how to read the panic to get an idea of what I should be looking for?
thanks
Simon
CentOS Record causing kernel panic
Re: CentOS Record causing kernel panic
Out of memory??? Check your free memory while ZM is working.
After more than 15 years, no longer using ZM as surveillance system.
Now in the dark side, using a commercial system...
Re: CentOS Record causing kernel panic
I don't think im out of memory, its a clear install and the computer has 4GB of ram with no other programs running.
Re: CentOS Record causing kernel panic
Tried upgrading to the latest version of the kernel and i'm still getting panics.
Re: CentOS Record causing kernel panic
If you've already versioned your kernel with no effect, you might try replacing your memory modules. This could also be a bug in the direct memory access to your display buffer. What video chipset are you using? Have you tried other programs like DirectFB?
-
sergio_cab
- Posts: 1
- Joined: Fri Jul 08, 2011 5:49 pm
Re: CentOS Record causing kernel panic
Hi. Try to compile zm wtith "--enable-mmap=yes". I had the same problem, when I compile zm with that opcion the problem finish.
bye
bye