From: Sander Eikelenboom <linux@eikelenboom.it>
To: Mike Isely <isely@pobox.com>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
<linux-kernel@vger.kernel.org>, <linux-media@vger.kernel.org>
Subject: media
Date: Sat, 10 Jan 2015 19:36:33 +0100 [thread overview]
Message-ID: <1463471745.20150110193633@eikelenboom.it> (raw)
Hi all,
With a 3.19-rc3 kernel i'm running into the warning below on boot with a pvrusb2 device.
It's hitting this warn:
/*
* Drivers MUST fill in device_caps, so check for this and
* warn if it was forgotten.
*/
WARN_ON(!(cap->capabilities & V4L2_CAP_DEVICE_CAPS) ||
!cap->device_caps);
--
Sander
[ 25.604846] ------------[ cut here ]------------
[ 25.622165] WARNING: CPU: 4 PID: 2133 at drivers/media/v4l2-core/v4l2-ioctl.c:1025 v4l_querycap+0x3e/0x70()
[ 25.654888] Modules linked in:
[ 25.667494] CPU: 4 PID: 2133 Comm: v4l_id Not tainted 3.19.0-rc3-20150110-pciback-doflr+ #1
[ 25.695927] Hardware name: MSI MS-7640/890FXA-GD70 (MS-7640) , BIOS V1.8B1 09/13/2010
[ 25.723022] ffffffff81fcf468 ffff880546fefbc8 ffffffff81bb3fc9 ffff880544a83240
[ 25.748684] 0000000000000000 ffff880546fefc08 ffffffff810c738d ffff880544a83240
[ 25.774301] ffff880546fefd38 0000000080685600 0000000000000000 ffff880544b78e00
[ 25.799936] Call Trace:
[ 25.810584] [<ffffffff81bb3fc9>] dump_stack+0x45/0x57
[ 25.829319] [<ffffffff810c738d>] warn_slowpath_common+0x8d/0xd0
[ 25.850669] [<ffffffff810c73e5>] warn_slowpath_null+0x15/0x20
[ 25.871477] [<ffffffff81851fae>] v4l_querycap+0x3e/0x70
[ 25.890692] [<ffffffff818513f4>] __video_do_ioctl+0x284/0x300
[ 25.911478] [<ffffffff81103556>] ? __lock_acquire+0x4e6/0x21a0
[ 25.932412] [<ffffffff818521d1>] video_usercopy+0x1f1/0x4e0
[ 25.952525] [<ffffffff81851170>] ? v4l_printk_ioctl+0xa0/0xa0
[ 25.973136] [<ffffffff811018dd>] ? trace_hardirqs_on+0xd/0x10
[ 25.993791] [<ffffffff818524d0>] video_ioctl2+0x10/0x20
[ 26.012844] [<ffffffff81892df7>] pvr2_v4l2_ioctl+0xa7/0x180
[ 26.032939] [<ffffffff8184e2ff>] v4l2_ioctl+0x12f/0x150
[ 26.051927] [<ffffffff811d6163>] do_vfs_ioctl+0x83/0x5b0
[ 26.071161] [<ffffffff811d3321>] ? final_putname+0x21/0x50
[ 26.090911] [<ffffffff81bbf995>] ? sysret_check+0x22/0x5d
[ 26.110395] [<ffffffff811d66d7>] SyS_ioctl+0x47/0x90
[ 26.128537] [<ffffffff81bbf969>] system_call_fastpath+0x12/0x17
[ 26.149531] ---[ end trace 52e366625e9023ef ]---
[ 26.166528] ------------[ cut here ]------------
reply other threads:[~2015-01-10 18:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1463471745.20150110193633@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=isely@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®