linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Nathaniel Russell <naterussell83@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	intel-gfx@lists.freedesktop.org
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-media@vger.kernel.org
Subject: Re: Linux Kernel 5.2.8 (uvc or i915?)
Date: Thu, 15 Aug 2019 18:53:36 -0700	[thread overview]
Message-ID: <abcae5c9-b3dc-7403-d628-5d7543d19702@infradead.org> (raw)
In-Reply-To: <CAONH+Jm-O6=DQ+K2n5pNTNMg2Sq1KcVNFLuweVh6W82OPEFJoQ@mail.gmail.com>

On 8/15/19 6:15 PM, Nathaniel Russell wrote:
> I would really like help with the kernel error with my uvcvideo driver.
> 

Hi again.

What makes you think that the problem is related to the uvcvideo driver?
Does some previous kernel version work correctly?  If so, what version(s)?


Does this warning message only happen when the uvcvideo driver is being loaded?
Can you suppress loading of the uvcvideo driver to find out?

Most of the problems/errors/warnings that I see are related to the i915 driver:

[   13.032341] timed out waiting for port C ready: got 0x20, expected 0xe0
[   13.032872] WARNING: CPU: 1 PID: 239 at drivers/gpu/drm/i915/intel_display.c:1597 vlv_wait_port_ready+0x99/0xe0 [i915]
[   13.033632] RIP: 0010:vlv_wait_port_ready+0x99/0xe0 [i915]

although there are a few uvcvideo warnings:
[   13.039305] uvcvideo 1-5:1.0: Entity type for entity Extension 4 was not initialized!
[   13.039318] uvcvideo 1-5:1.0: Entity type for entity Extension 3 was not initialized!
[   13.039330] uvcvideo 1-5:1.0: Entity type for entity Processing 2 was not initialized!
[   13.039339] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not initialized!


Laurent, do you see any uvc issues here?  Any ideas/suggestions?


@intel-gfx:  any ideas about what is going on here with the i915 driver?



Original message to lkml:
https://lore.kernel.org/lkml/CAONH+Jm-O6=DQ+K2n5pNTNMg2Sq1KcVNFLuweVh6W82OPEFJoQ@mail.gmail.com/T/#u

Previous message for 5.1.21 kernel:
https://lore.kernel.org/lkml/CAONH+JkTFujY9vEyNNuem+9rJ2qBKkf-PbKk9=DBSVEp6kW=yw@mail.gmail.com/


thanks.
-- 
~Randy

       reply	other threads:[~2019-08-16  1:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAONH+Jm-O6=DQ+K2n5pNTNMg2Sq1KcVNFLuweVh6W82OPEFJoQ@mail.gmail.com>
2019-08-16  1:53 ` Randy Dunlap [this message]
     [not found]   ` <CAONH+JnZpbpdiwdajP7ke7X7wQGU7m4YoyZRDbLHKmRufkD6mQ@mail.gmail.com>
2019-08-16  3:10     ` Linux Kernel 5.2.8 (uvc or i915? <<<) Randy Dunlap
2019-08-16  9:58       ` Laurent Pinchart
2019-08-16 21:35         ` Nathaniel Russell
2019-08-16 13:47   ` [Intel-gfx] Linux Kernel 5.2.8 (uvc or i915?) Jani Nikula
2019-08-16 21:08     ` Nathaniel Russell
2019-08-21 11:48       ` Jani Nikula

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=abcae5c9-b3dc-7403-d628-5d7543d19702@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=naterussell83@gmail.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;
as well as URLs for NNTP newsgroup(s).