Bug 68003

Summary:

igt/gem_pwrite segfault

Product:

DRI

Reporter:

lu hua <huax.lu>

Component:

DRM/Intel

Assignee:

Chris Wilson <chris>

Status:

CLOSED FIXED

QA Contact:

Intel GFX Bugs mailing list <intel-gfx-bugs>

Severity:

major

Priority:

high

Version:

unspecified

Hardware:

All

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
dmesg	none

Description lu hua 2013-08-12 05:27:30 UTC

Created attachment 83954 [details]
dmesg

System Environment:
--------------------------
Platform:  PNV/ILK/SNB/IVB/HSW
Kernel:   drm-intel-nightly(8894ac87e4db055bbdd44647c1ce2df274400264)

Bug detailed description:
-----------------------------
It fails on all platforms: PNV/ILK/SNB/IVB/HSW.It happens on drm-intel-nightly, drm-intel-next-queued, drm-intel-fixes kernel.
Bisect shows: 467796acc80ced3440740d267c2e2a4f246d4b8a is the first bad commit.
commit 467796acc80ced3440740d267c2e2a4f246d4b8a
Author:     Chris Wilson <chris@chris-wilson.co.uk>
AuthorDate: Sat Aug 10 15:49:33 2013 +0100
Commit:     Chris Wilson <chris@chris-wilson.co.uk>
CommitDate: Sat Aug 10 15:49:33 2013 +0100

    Expand gem_set_cacheing testing to handle the proposed DISPLAY domain

output:
Time to pwrite 16384 bytes x      1:     22.000µs, 744.7MiB/s
Time to pwrite 16384 bytes x      2:      5.000µs, 3.3GiB/s
Time to pwrite 16384 bytes x      4:      3.750µs, 4.4GiB/s
Time to pwrite 16384 bytes x      8:      3.625µs, 4.5GiB/s
Time to pwrite 16384 bytes x     16:      3.500µs, 4.7GiB/s
Time to pwrite 16384 bytes x     32:      3.844µs, 4.3GiB/s
Time to pwrite 16384 bytes x     64:      4.516µs, 3.6GiB/s
Time to pwrite 16384 bytes x    128:      3.664µs, 4.5GiB/s
Time to pwrite 16384 bytes x    256:      3.551µs, 4.6GiB/s
Time to pwrite 16384 bytes x    512:      3.482µs, 4.7GiB/s
Time to pwrite 16384 bytes x   1024:      3.450µs, 4.7GiB/s
Time to pwrite 16384 bytes x   2048:      3.433µs, 4.8GiB/s
Time to pwrite 16384 bytes x   4096:      3.433µs, 4.8GiB/s
Time to pwrite 16384 bytes x   8192:      3.433µs, 4.8GiB/s
Time to pwrite 16384 bytes x  16384:      3.431µs, 4.8GiB/s
Time to pwrite 16384 bytes x  32768:      3.424µs, 4.8GiB/s
Time to pwrite 16384 bytes x  65536:      3.427µs, 4.8GiB/s
Time to pwrite 16384 bytes x 131072:      3.430µs, 4.8GiB/s
Time to (null) pwrite 16384 bytes x      1:       4.000µs, 4.1GiB/s
Time to (null) pwrite 16384 bytes x      2:       3.500µs, 4.7GiB/s
Time to (null) pwrite 16384 bytes x      4:       3.750µs, 4.4GiB/s
Time to (null) pwrite 16384 bytes x      8:       3.500µs, 4.7GiB/s
Time to (null) pwrite 16384 bytes x     16:       3.500µs, 4.7GiB/s
Time to (null) pwrite 16384 bytes x     32:       3.469µs, 4.7GiB/s
Time to (null) pwrite 16384 bytes x     64:       4.250µs, 3.9GiB/s
Time to (null) pwrite 16384 bytes x    128:       3.742µs, 4.4GiB/s
Time to (null) pwrite 16384 bytes x    256:       3.559µs, 4.6GiB/s
Time to (null) pwrite 16384 bytes x    512:       3.498µs, 4.7GiB/s
Time to (null) pwrite 16384 bytes x   1024:       3.459µs, 4.7GiB/s
Time to (null) pwrite 16384 bytes x   2048:       3.444µs, 4.8GiB/s
Time to (null) pwrite 16384 bytes x   4096:       3.437µs, 4.8GiB/s
Time to (null) pwrite 16384 bytes x   8192:       3.419µs, 4.8GiB/s
Time to (null) pwrite 16384 bytes x  16384:       3.423µs, 4.8GiB/s
Time to (null) pwrite 16384 bytes x  32768:       3.431µs, 4.8GiB/s
Time to (null) pwrite 16384 bytes x  65536:       3.433µs, 4.8GiB/s
Time to (null) pwrite 16384 bytes x 131072:       3.429µs, 4.8GiB/s
Segmentation fault (core dumped)


Reproduce steps:
----------------------------
1. ./gem_pwrite

Comment 1 Chris Wilson 2013-08-12 07:41:38 UTC

commit 7b254f193933eda7c9761a7f10ac49049103b259
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Mon Aug 12 08:39:26 2013 +0100

    gem_pwrite: Print the cache name not the number
    
    Bugzilla: https://bugzilla.freedesktop.org/show_bug.cgi?id=68003

Comment 2 lu hua 2013-08-12 08:20:48 UTC

Verified.Fixed.

Comment 3 Elizabeth 2017-10-06 14:44:14 UTC

Closing old verified.

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.