From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110354] Confusing Junk in the results: Last errno: 25, Inappropriate ioctl for device
Date: Mon, 08 Apr 2019 11:43:38 +0000 [thread overview]
Message-ID: <bug-110354-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1060 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110354
Bug ID: 110354
Summary: Confusing Junk in the results: Last errno: 25,
Inappropriate ioctl for device
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: major
Priority: medium
Component: IGT
Assignee: dri-devel@lists.freedesktop.org
Reporter: arkadiusz.hiler@intel.com
IGT's asserts log the last errno if it's not 0, and it seems like we get this
"Inappropriate ioctl for device" quite often polluting the CI results and
confusing people.
We have to locate where is it originating from and set errno to 0 after
handling it to stop the pollution.
Some examples:
https://bugs.freedesktop.org/show_bug.cgi?id=109358
https://bugs.freedesktop.org/show_bug.cgi?id=110037
https://bugs.freedesktop.org/show_bug.cgi?id=110279
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3147 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-04-08 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 11:43 bugzilla-daemon [this message]
2019-04-08 14:53 ` [Bug 110354] Confusing Junk in the results: Last errno: 25, Inappropriate ioctl for device bugzilla-daemon
2019-08-06 8:30 ` bugzilla-daemon
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-110354-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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 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).