New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 674783 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 2
Type: Bug



Sign in to add a comment

__fill_vb2_buffer kernel warnings on dev channel

Project Member Reported by cernekee@chromium.org, Dec 16 2016

Issue description

These make up 91% of the crash.corp reports on minnie for 9086.0.0:

https://goto.google.com/jjgfj

f79ae1c3-__fill_vb2_buffer+0x80/0x34c()
/mnt/host/source/src/third_party/kernel/v3.14/drivers/media/v4l2-core/videobuf2-core.c:1185 __fill_vb2_buffer+0x80/0x34c()
2016-12-15T17:55:40.685615-05:00 NOTICE kernel: [ 1911.007174] Modules linked in: ip6t_REJECT ip6table_raw ip6table_mangle xt_TCPMSS veth uinput cmac ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat i2c_dev xt_mark rfcomm uvcvideo videobuf2_vmalloc bridge fuse stp llc zram ip6table_filter ip6_tables hci_uart bluetooth snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iio_trig_sysfs brcmfmac brcmutil cfg80211 joydev cros_ec_accel kfifo_buf
2016-12-15T17:55:40.685619-05:00 NOTICE kernel: [ 1911.007303] CPU: 2 PID: 8680 Comm: V4L2SliceVideoD Not tainted 3.14.0 #1
2016-12-15T17:55:40.686424-05:00 NOTICE kernel: [ 1911.007328] [<c010e4bc>] (unwind_backtrace) from [<c010a910>] (show_stack+0x20/0x24)
2016-12-15T17:55:40.686437-05:00 NOTICE kernel: [ 1911.007346] [<c010a910>] (show_stack) from [<c06e1a54>] (dump_stack+0x7c/0xc0)
2016-12-15T17:55:40.686440-05:00 NOTICE kernel: [ 1911.007361] [<c06e1a54>] (dump_stack) from [<c0123574>] (warn_slowpath_common+0x7c/0xa0)
2016-12-15T17:55:40.686444-05:00 NOTICE kernel: [ 1911.007375] [<c0123574>] (warn_slowpath_common) from [<c012369c>] (warn_slowpath_null+0x2c/0x34)
2016-12-15T17:55:40.686447-05:00 NOTICE kernel: [ 1911.007388] [<c012369c>] (warn_slowpath_null) from [<c04fdb88>] (__fill_vb2_buffer+0x80/0x34c)
2016-12-15T17:55:40.686449-05:00 NOTICE kernel: [ 1911.007405] [<c04fdb88>] (__fill_vb2_buffer) from [<c04ff908>] (__buf_prepare+0x1a8/0x2c0)
2016-12-15T17:55:40.686453-05:00 NOTICE kernel: [ 1911.007421] [<c04ff908>] (__buf_prepare) from [<c0500518>] (vb2_internal_qbuf+0x90/0x230)
2016-12-15T17:55:40.686458-05:00 NOTICE kernel: [ 1911.007437] [<c0500518>] (vb2_internal_qbuf) from [<c05006fc>] (vb2_qbuf+0x44/0x5c)
2016-12-15T17:55:40.686461-05:00 NOTICE kernel: [ 1911.007451] [<c05006fc>] (vb2_qbuf) from [<c0505344>] (vidioc_qbuf+0xbc/0x150)
2016-12-15T17:55:40.686465-05:00 NOTICE kernel: [ 1911.007465] [<c0505344>] (vidioc_qbuf) from [<c04f1cc8>] (v4l_qbuf+0x4c/0x50)
2016-12-15T17:55:40.686467-05:00 NOTICE kernel: [ 1911.007482] [<c04f1cc8>] (v4l_qbuf) from [<c04f2bd8>] (__video_do_ioctl+0x1d0/0x2d0)
2016-12-15T17:55:40.686470-05:00 NOTICE kernel: [ 1911.007496] [<c04f2bd8>] (__video_do_ioctl) from [<c04f269c>] (video_usercopy+0x204/0x54c)
2016-12-15T17:55:40.686473-05:00 NOTICE kernel: [ 1911.007511] [<c04f269c>] (video_usercopy) from [<c04f2a00>] (video_ioctl2+0x1c/0x24)
2016-12-15T17:55:40.686475-05:00 NOTICE kernel: [ 1911.007536] [<c04f2a00>] (video_ioctl2) from [<c04ed0d8>] (v4l2_ioctl+0x70/0x134)
2016-12-15T17:55:40.686478-05:00 NOTICE kernel: [ 1911.007556] [<c04ed0d8>] (v4l2_ioctl) from [<c02386e8>] (do_vfs_ioctl+0x494/0x5a8)
2016-12-15T17:55:40.686481-05:00 NOTICE kernel: [ 1911.007576] [<c02386e8>] (do_vfs_ioctl) from [<c0238858>] (SyS_ioctl+0x5c/0x84)
2016-12-15T17:55:40.686508-05:00 NOTICE kernel: [ 1911.007594] [<c0238858>] (SyS_ioctl) from [<c0106678>] (__sys_trace_return+0x0/0x28)
2016-12-15T17:55:40.686510-05:00 WARNING kernel: [ 1911.007766] ---[ end trace e41346ced358170d ]---

I see references to this warning in  bug 670462  and  bug 660628 , but both of those reports seemed to be concerned with different issues.  Bug 599783 might also be related.
 
Cc: wuchengli@chromium.org
Status: WontFix (was: Unconfirmed)
This is an API deprecation warning (https://chromium.googlesource.com/chromiumos/third_party/kernel/+/refs/heads/chromeos-3.14/drivers/media/v4l2-core/videobuf2-core.c#1185). We have to keep using it until all drivers start supporting the new API, but it is completely harmless.

Sign in to add a comment