From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 98997] New: Invalid ioctl during Xorg startup
Date: Mon, 05 Dec 2016 12:20:46 +0000 [thread overview]
Message-ID: <bug-98997-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3317 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98997
Bug ID: 98997
Summary: Invalid ioctl during Xorg startup
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: reptm-O5WfVfzUwx8@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
OS: Ubuntu 16.10
Kernel: 4.8.0-28-generic
xorg-server: 1.18.4
cpu: Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz
After connecting UDL device and restarting Xorg, Xorg tries to send invalid
ioctl to that device.
Looks like Xorg enumerates existing drm devices and performs driver's
platformprobe function on them regardless of their type.
syslog:
Dec 5 11:31:55 kernel: [ 1026.543315] [drm:drm_stub_open]
Dec 5 11:31:55 kernel: [ 1026.543317] [drm:drm_open_helper] pid = 4642, minor
= 0
Dec 5 11:31:55 kernel: [ 1026.543341] [drm:drm_setup]
Dec 5 11:31:55 kernel: [ 1026.543349] [drm:drm_ioctl] pid=4642, dev=0xe200,
auth=1, DRM_IOCTL_VERSION
Dec 5 11:31:55 kernel: [ 1026.543351] [drm:drm_ioctl] pid=4642, dev=0xe200,
auth=1, DRM_IOCTL_VERSION
Dec 5 11:31:55 kernel: [ 1026.543355] [drm:drm_ioctl] pid=4642, dev=0xe200,
auth=1, NOUVEAU_GETPARAM
Dec 5 11:31:55 kernel: [ 1026.543357] [drm:drm_ioctl] pid=4642, dev=0xe200,
auth=1, NOUVEAU_GETPARAM
Dec 5 11:31:55 kernel: [ 1026.543358] [drm:drm_ioctl] pid=4642, dev=0xe200,
auth=1, NOUVEAU_GETPARAM
Dec 5 11:31:55 kernel: [ 1026.543359] [drm:drm_ioctl] pid=4642, dev=0xe200,
auth=1, NOUVEAU_GETPARAM
Dec 5 11:31:55 kernel: [ 1026.543362] [drm:drm_ioctl] pid=4642, dev=0xe200,
auth=1, DRM_IOCTL_VERSION
Dec 5 11:31:55 kernel: [ 1026.543364] [drm:drm_ioctl] pid=4642, dev=0xe200,
auth=1, DRM_IOCTL_VERSION
Dec 5 11:31:55 kernel: [ 1026.543393] [drm:drm_release] open_count = 1
Dec 5 11:31:55 kernel: [ 1026.543394] [drm:drm_release] pid = 4642, device =
0xe200, open_count = 1
Dec 5 11:31:55 kernel: [ 1026.543401] [drm:drm_lastclose]
Dec 5 11:31:55 kernel: [ 1026.543401] [drm:drm_lastclose] driver lastclose
completed
Dec 5 11:31:55 kernel: [ 1026.543414] [drm:drm_stub_open]
Dec 5 11:31:55 kernel: [ 1026.543415] [drm:drm_open_helper] pid = 4642, minor
= 2
Dec 5 11:31:55 kernel: [ 1026.543416] [drm:drm_setup]
Dec 5 11:31:55 kernel: [ 1026.543418] [drm:drm_ioctl] pid=4642, dev=0xe202,
auth=1, DRM_IOCTL_VERSION
Dec 5 11:31:55 kernel: [ 1026.543419] [drm:drm_ioctl] pid=4642, dev=0xe202,
auth=1, DRM_IOCTL_VERSION
Dec 5 11:31:55 kernel: [ 1026.543421] [drm:drm_ioctl] invalid ioctl: pid=4642,
dev=0xe202, auth=1, cmd=0xc0106440, nr=0x40
Dec 5 11:31:55 kernel: [ 1026.543422] [drm:drm_ioctl] ret = -22
Dec 5 11:31:55 kernel: [ 1026.543425] [drm:drm_release] open_count = 1
Dec 5 11:31:55 kernel: [ 1026.543426] [drm:drm_release] pid = 4642, device =
0xe202, open_count = 1
Dec 5 11:31:55 kernel: [ 1026.543427] [drm:drm_lastclose]
Dec 5 11:31:55 kernel: [ 1026.543427] [drm:drm_lastclose] driver lastclose
completed
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4603 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2016-12-05 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 12:20 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-98997-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-12-04 9:22 ` [Bug 98997] Invalid ioctl during Xorg startup bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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=bug-98997-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.