From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Edgar Thier <info@edgarthier.net>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
lkp@01.org
Subject: Re: [lkp-robot] [media] 859086ae36: kmsg.uvcvideo:Failed_to_query(GET_INFO)UVC_control#on_unit#:-#(exp.#)
Date: Wed, 21 Mar 2018 12:32:07 +0200 [thread overview]
Message-ID: <1637940.NKPajzO43a@avalon> (raw)
In-Reply-To: <20180316020039.GU8942@yexl-desktop>
Hello,
On Friday, 16 March 2018 04:00:39 EET kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 859086ae3636eae0bf9f0fbbce2daf4d41ae9474 ("media: uvcvideo: Apply
> flags from device to actual properties")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> in testcase: netperf
> with following parameters:
>
> ip: ipv4
> runtime: 300s
> nr_threads: 1
> cluster: cs-localhost
> test: SCTP_STREAM
> cpufreq_governor: performance
>
> test-description: Netperf is a benchmark that can be use to measure various
> aspect of networking performance. test-url: http://www.netperf.org/netperf/
>
>
> on test machine: 4 threads Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz with 4G
> memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire
> log/backtrace):
>
>
> [ 76.108373] uvcvideo: Failed to query (GET_INFO) UVC control 11 on unit
> 1: -32 (exp. 1).
Just for the record, Kieran is working on this.
> To reproduce:
>
> git clone https://github.com/intel/lkp-tests.git
> cd lkp-tests
> bin/lkp install job.yaml # job file is attached in this email
> bin/lkp run job.yaml
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2018-03-21 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 2:00 [lkp-robot] [media] 859086ae36: kmsg.uvcvideo:Failed_to_query(GET_INFO)UVC_control#on_unit#:-#(exp.#) kernel test robot
2018-03-21 10:32 ` Laurent Pinchart [this message]
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=1637940.NKPajzO43a@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=info@edgarthier.net \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mchehab@s-opensource.com \
--cc=sfr@canb.auug.org.au \
--cc=xiaolong.ye@intel.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