[valgrind] [Bug 350228] Unhandled ioctl 0x6458 (i965/mesa)

2019-07-11 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=350228 Julian Seward changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED

[valgrind] [Bug 350228] Unhandled ioctl 0x6458 (i965/mesa)

2019-04-19 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=350228 --- Comment #9 from Austin English --- Created attachment 119495 --> https://bugs.kde.org/attachment.cgi?id=119495=edit add DRM_IOCTL_I915_GEM_THROTTLE -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 350228] Unhandled ioctl 0x6458 (i965/mesa)

2019-04-19 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=350228 --- Comment #8 from Austin English --- Created attachment 119494 --> https://bugs.kde.org/attachment.cgi?id=119494=edit Patch: mention strace as a data source for syscall/ioctl information -- You are receiving this mail because: You are watching

[valgrind] [Bug 350228] Unhandled ioctl 0x6458 (i965/mesa)

2019-04-13 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=350228 Austin English changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|NOT A BUG

[valgrind] [Bug 350228] Unhandled ioctl 0x6458 (i965/mesa)

2019-04-13 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=350228 --- Comment #6 from Austin English --- (In reply to Austin English from comment #5) > I asked in the intel-gfx and xorg IRC channels about these ioctls, and the > answers were basically "try newer Valgrind" and "look at the source..oh > they're not

[valgrind] [Bug 350228] Unhandled ioctl 0x6458 (i965/mesa)

2017-01-25 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=350228 Austin English changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED