Bug 106621

Summary:	[CI] Piglit spec@!opengl 1.1@copypixels-sync - fail - i965: Failed to submit batchbuffer: Bad address
Product:	Mesa	Reporter:	Martin Peres <martin.peres>
Component:	Drivers/DRI/i965	Assignee:	Intel 3D Bugs Mailing List <intel-3d-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity:	normal
Priority:	medium	CC:	intel-gfx-bugs
Version:	18.0
Hardware:	Other
OS:	All
Whiteboard:	ReadyForDev
i915 platform:	SNB	i915 features:	GEM/Other

Description Martin Peres 2018-05-22 21:47:33 UTC

We once had the following error in stderr when running piglit's spec@!opengl 1.1@copypixels-sync on sandybridge:

i965: Failed to submit batchbuffer: Bad address

Should I move this bug to mesa?

Comment 1 Chris Wilson 2018-05-22 21:55:53 UTC

EFAULT means one of the bo was MADV_DONTNEED. We don't do a strict validation pass, so only fail if we happen to try and page in the object in question. (Less likely possibility is the user pointers passed to the ioctl are bogus.) Sounds like we could do with a validation layer.

Comment 2 Martin Peres 2018-05-22 22:13:56 UTC

(In reply to Chris Wilson from comment #1)
> EFAULT means one of the bo was MADV_DONTNEED. We don't do a strict
> validation pass, so only fail if we happen to try and page in the object in
> question. (Less likely possibility is the user pointers passed to the ioctl
> are bogus.) Sounds like we could do with a validation layer.

Where do you need the validation, mesa or i915? I am wondering where this bug should reside.

Comment 3 Chris Wilson 2018-05-22 22:20:59 UTC

I'd make the validation layer in userspace; part of the ioctl interception scrubbing tools.

My gut feeling is that is a userspace bug; certainly easier to diagnose in userspace, and if that rules it out being a mesa bug then to delve back into the kernel.

Comment 4 Martin Peres 2018-05-22 23:42:53 UTC

(In reply to Chris Wilson from comment #3)
> I'd make the validation layer in userspace; part of the ioctl interception
> scrubbing tools.
> 
> My gut feeling is that is a userspace bug; certainly easier to diagnose in
> userspace, and if that rules it out being a mesa bug then to delve back into
> the kernel.

That makes sense, I am moving it to Mesa for their input.

Comment 5 Mark Janes 2018-05-23 05:36:21 UTC

We've seen this for a while, and can't pinpoint it.

*** This bug has been marked as a duplicate of bug 104778 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.