warn_slowpath_common solo_p2m_dma

[luogni]

Hi, i'm using a BC-H16480A with 16 inputs connected. When i load the solo6x10-edge (latest git) i get this warning in /var/log/messages. I'm using kernel 3.2.9:

Feb 19 15:57:38 ay4 kernel: [ 1519.575914] solo6x10-edge 0000:02:05.0: Probing Softlogic 6110 Feb 19 15:57:38 ay4 kernel: [ 1519.575957] solo6x10-edge 0000:02:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Feb 19 15:57:38 ay4 kernel: [ 1519.580804] ------------[ cut here ]------------ Feb 19 15:57:38 ay4 kernel: [ 1519.580839] WARNING: at /root/solo6x10/solo6010-p2m.c:47 solo_p2m_dma+0x11f/0x150 [solo6x10_edge]() Feb 19 15:57:38 ay4 kernel: [ 1519.580886] Hardware name: System Product Name Feb 19 15:57:38 ay4 kernel: [ 1519.580909] Modules linked in: solo6x10_edge(O+) bttv btcx_risc v4l2_common videodev i2c_algo_bit ir_lirc_codec lirc_dev ir_mce_kbd_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder ir_nec_decoder rc_core tveeprom coretemp hwmon_vid ip6table_filter ip6_tables iptable_raw xt_comment xt_recent xt_policy ipt_ULOG ipt_REJECT ipt_REDIRECT ipt_NETMAP ipt_MASQUERADE ipt_LOG ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah nf_nat_tftp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_tcpmss xt_pkttype xt_physdev xt_owner xt_NFQUEUE xt_NFLOG nfnetlink_log xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_helper xt_hashlimit xt_DSCP xt_dscp xt_dccp xt_conntrack xt_connmark xt_CLASSIFY xt Feb 19 15:57:38 ay4 kernel: tcpudp xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_mangle nfnetlink iptable_filter ip_tables x_tables r8169 atl1e atl1 mii e1000e lp snd_pcm ppdev snd_timer snd psmouse soundcore parport_pc snd_page_alloc parport videobuf_dma_sg videobuf_core font video intel_agp intel_gtt shpchp agpgart pcspkr serio_raw usb_wdg_drv(O) raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear [last unloaded: videodev] Feb 19 15:57:38 ay4 kernel: [ 1519.582142] Pid: 15452, comm: modprobe Tainted: G W O 3.2.9 #2 Feb 19 15:57:38 ay4 kernel: [ 1519.582171] Call Trace: Feb 19 15:57:38 ay4 kernel: [ 1519.582196] [] ? solo_p2m_dma+0x11f/0x150 [solo6x10_edge] Feb 19 15:57:38 ay4 kernel: [ 1519.582228] [] warn_slowpath_common+0x6c/0xa0 Feb 19 15:57:38 ay4 kernel: [ 1519.582258] [] ? solo_p2m_dma+0x11f/0x150 [solo6x10_edge] Feb 19 15:57:38 ay4 kernel: [ 1519.582288] [] warn_slowpath_null+0x1d/0x20 Feb 19 15:57:38 ay4 kernel: [ 1519.582317] [] solo_p2m_dma+0x11f/0x150 [solo6x10_edge] Feb 19 15:57:38 ay4 kernel: [ 1519.582348] [] ? pci_bus_read_config_word+0x66/0x80 Feb 19 15:57:38 ay4 kernel: [ 1519.582380] [] solo_disp_init+0x530/0xef0 [solo6x10_edge] Feb 19 15:57:38 ay4 kernel: [ 1519.582412] [] ? free_pages+0x1e/0x40 Feb 19 15:57:38 ay4 kernel: [ 1519.582442] [] solo6010_pci_probe+0x2cd/0x4d0 [solo6x10_edge] Feb 19 15:57:38 ay4 kernel: [ 1519.582473] [] local_pci_probe+0xe/0x10 Feb 19 15:57:38 ay4 kernel: [ 1519.582500] [] pci_device_probe+0x60/0x80 Feb 19 15:57:38 ay4 kernel: [ 1519.582531] [] driver_probe_device+0x6d/0x190 Feb 19 15:57:38 ay4 kernel: [ 1519.582558] [] ? pci_match_device+0xa8/0xb0 Feb 19 15:57:38 ay4 kernel: [ 1519.582586] [] driver_attach+0x81/0x90 Feb 19 15:57:38 ay4 kernel: [ 1519.582613] [] bus_for_each_dev+0x5b/0x80 Feb 19 15:57:38 ay4 kernel: [ 1519.582639] [] ? pci_dev_put+0x20/0x20 Feb 19 15:57:38 ay4 kernel: [ 1519.582666] [] driver_attach+0x19/0x20 Feb 19 15:57:38 ay4 kernel: [ 1519.582693] [] ? driver_probe_device+0x190/0x190 Feb 19 15:57:38 ay4 kernel: [ 1519.582721] [] bus_add_driver+0x197/0x260 Feb 19 15:57:38 ay4 kernel: [ 1519.582748] [] ? pci_dev_put+0x20/0x20 Feb 19 15:57:38 ay4 kernel: [ 1519.582774] [] driver_register+0x75/0x160 Feb 19 15:57:38 ay4 kernel: [ 1519.582802] [] ? tracepoint_module_notify+0x177/0x190 Feb 19 15:57:38 ay4 kernel: [ 1519.582834] [] ? 0xf8550fff Feb 19 15:57:38 ay4 kernel: [ 1519.582858] [] __pci_register_driver+0x3f/0xb0 Feb 19 15:57:38 ay4 kernel: [ 1519.582887] [] ? 0xf8550fff Feb 19 15:57:38 ay4 kernel: [ 1519.582915] [] solo6010_pci_driver_init+0x17/0x19 [solo6x10_edge] Feb 19 15:57:38 ay4 kernel: [ 1519.582946] [] do_one_initcall+0x2b/0x160 Feb 19 15:57:38 ay4 kernel: [ 1519.582979] [] sys_init_module+0x117/0x1800 Feb 19 15:57:38 ay4 kernel: [ 1519.583029] [] sysenter_do_call+0x12/0x28 Feb 19 15:57:38 ay4 kernel: [ 1519.583055] ---[ end trace 22a102228b8cdb2a ]---

[curtishall]

Thanks for the report. It seems like a bug we dealt with and fixed last year (https://getsatisfaction.com/bluecherry/topics/bluecherrydvr_crashes_due_to_solo_driver_issue_both_10_04_12_04_lts_compiled_latest_solo_driver).

We are pretty busy this week, but I'll see if we can look at this and let you know.

[luogni]

Ok, let me know if you need anything. btw, is this a serious warning? I'm also sometime having decoding errors from the h264 streams, can it be related to this problem or should i report it in a different ticket?

[curtishall]

I was wrong about the link I posted earlier, this is not related. I would try downgrading the driver to 2.4.2 (https://github.com/bluecherrydvr/solo6x10/tree/2.4.1-2) and see if you have the same problems.

[luogni]

I've tried but they don't compile with my kernel (3.2.9). I can try to upgrade it if you know a kernel version that is working fine.

[ismaell]

Is this issue gone?

[alexxxwork]

It's not easy to compile 2.4.2-1. I added some kernel headers to *.c files and files from kernel source (videobuf_dma_sg), and now the driver works fine. Should I commit this version? The only problem (also on latest driver) is that I can't set fps with v4l2-ctl to values other than 25 fps or 1.667 fps. When I try to capture at 704x576@25 I get a 'device or resource busy' error on 3 channels, so I think I should try 25/2 or something.

[ismaell]

It is due to the buffer not being properly aligned, but I've not been able to reproduce it.

@alexxxwork It's better to work with the latest version if this problem doesn't show up for you. If it does, just use git-bisect until you find the culprit.

I know it can be tiresome, but otherwise you'll be missing a lot of improvements.

[ismaell]

Closing because it can't be reproduced.