intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Sun, Yi" <yi.sun@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: SSD-OTC GFX QA <ssd-otc.gfx.qa@intel.com>,
	"Yang, Guang A" <guang.a.yang@intel.com>,
	"Tian, YeX" <yex.tian@intel.com>
Subject: Re: Updated -next
Date: Wed, 11 Apr 2012 03:20:27 +0000	[thread overview]
Message-ID: <D9F66AA509623343B6A9A3D4502D5A520FCF48BA@SHSMSX102.ccr.corp.intel.com> (raw)
In-Reply-To: <20120405094529.GB4291@phenom.ffwll.local>

Hi all,

We finished a new round of kernel testing. The version of kernel is:
Kernel: (drm-intel-testing)9d0b5b5468650e0ac72a7786cf6625963f926d4d
Merge: ec34a01 b4db1e3
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Mon Apr 9 18:12:03 2012 +0200

We covered the platform IvyBridge, SandyBridge, IronLake, G45 and Pineview. 	We haven't any available HasWell machine, so didn't do testing on that.
General, in this circle, 11 bugs are fixed, 4 bugs are still open, and 2 new bugs about suspending are filed. The detail of bugs are as following:

Fixed bugs
Bug 38138 - [SNB] mplayer -vo fbdev videofile will cause system hang on HuronRiver (https://bugs.freedesktop.org/show_bug.cgi?id=38138)
Bug 40031 - [Regression] testdisplay can't display correctly with 30 bpp (https://bugs.freedesktop.org/show_bug.cgi?id=40031)
Bug 42180 - System hang while running gem_linear_blits of Intel-gpu-tools (https://bugs.freedesktop.org/show_bug.cgi?id=42180)
Bug 47990 - [PNV]I-G-T/gem_tiled_after_untiled_blt fail (https://bugs.freedesktop.org/show_bug.cgi?id=47990)
Bug 48026 - [Regression]I-G-T/gem_linear_blits fail (https://bugs.freedesktop.org/show_bug.cgi?id=48026)
Bug 47085 - [ILK]I-G-T/gem_pipe_control_store_loop fail unstablely (https://bugs.freedesktop.org/show_bug.cgi?id=47085)
Bug 48028 - [Regression ILK]I-G-T/gem_tiled_blits fail (https://bugs.freedesktop.org/show_bug.cgi?id=48028)
Bug 48030 - [Regression ILK]I-G-T /gem_tiled_fence_blits fail (https://bugs.freedesktop.org/show_bug.cgi?id=48030)
Bug 42943 - [IVB] Boot with a vga monitor can't light the DP screen while plugin it (https://bugs.freedesktop.org/show_bug.cgi?id=42943)
Bug 44305 - [IVB]The Edp can't work while booting with a monitor (https://bugs.freedesktop.org/show_bug.cgi?id=44305)

Open bugs:
Bug 41976 - [IVB] screen turn to be black while switching between console and x-window with 3-pipe active (https://bugs.freedesktop.org/show_bug.cgi?id=41976)
Bug 47990 - [PNV]I-G-T/gem_tiled_after_untiled_blt fail (https://bugs.freedesktop.org/show_bug.cgi?id=47990)
Bug 45867 - [IVB 3pipe] 3 Pipe Doesn't Work with Eaglemont Card (https://bugs.freedesktop.org/show_bug.cgi?id=45867)
Bug 45870 - [IVB PCH eDP] PCH eDP doesn't work (https://bugs.freedesktop.org/show_bug.cgi?id=45870)

Thanks
   --Yi,Sun


> -----Original Message-----
> From: Daniel Vetter [mailto:daniel.vetter@ffwll.ch] On Behalf Of Daniel Vetter
> Sent: Thursday, April 05, 2012 5:45 PM
> To: Intel Graphics Development; Sun, Yi
> Subject: Updated -next
> 
> Hi all,
> 
> I've pushed out a new -next and testing tree. Highlights:
> - first batch of hsw enabling (Eugeni)
> - first batch of vlv enabling (Jesse and others)
> - a few cleanups spurred by the above items
> - pwrite/pread rework and speedups
> - less mappable pressure and reloc optimizations (Chris)
> - mmap_offset exhaustion mitigation (Chris)
> - more gmbus cleanups and fixes (Daniel Kurtz), now also enabled for gen2
> - a start at figuring out what code of our gem+ums/kms/dri1 codebase is
>   actually support by disallowing these ioctls
> 
> Happy testing!
> 
> Cheers, Daniel
> --
> Daniel Vetter
> Mail: daniel@ffwll.ch
> Mobile: +41 (0)79 365 57 48

  parent reply	other threads:[~2012-04-11  3:20 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05  9:45 Updated -next Daniel Vetter
2012-04-09 16:19 ` Daniel Vetter
2012-04-10  2:09   ` Sun, Yi
2012-04-11  3:20 ` Sun, Yi [this message]
2012-04-11  7:54   ` Paul Menzel
2012-04-11  8:24     ` Sun, Yi
2012-04-11  9:45       ` Paul Menzel
  -- strict thread matches above, loose matches on Subject: below --
2012-07-22 14:33 updated -next Daniel Vetter
2012-06-21  8:25 Updated -next Daniel Vetter
2012-06-04 20:59 Daniel Vetter
2012-06-12  8:37 ` Daniel Vetter
2012-05-06 19:09 Daniel Vetter
2012-04-21 16:40 Daniel Vetter
2012-04-23  7:39 ` Daniel Vetter
2012-04-23  7:40   ` Sun, Yi
2012-04-27 11:45 ` Daniel Vetter
2012-04-27 13:44   ` Daniel Vetter
2012-03-23 10:03 Daniel Vetter
2012-03-29  7:38 ` Sun, Yi
2012-03-01 20:59 Daniel Vetter
2012-03-08  8:10 ` Sun, Yi
2012-03-18 21:20   ` Daniel Vetter
2012-02-16 17:27 updated -next Daniel Vetter
2012-02-17 17:56 ` Jesse Barnes
2012-02-21  7:45 ` Sun, Yi
2012-02-07 22:59 Daniel Vetter
2012-01-20 10:10 Updated -next Daniel Vetter
2012-01-21  4:15 ` Sun, Yi
2012-01-21 14:12   ` Daniel Vetter
2012-01-21 19:45     ` Alan W. Irwin
2012-01-31  9:07       ` Jin, Gordon

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=D9F66AA509623343B6A9A3D4502D5A520FCF48BA@SHSMSX102.ccr.corp.intel.com \
    --to=yi.sun@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=guang.a.yang@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ssd-otc.gfx.qa@intel.com \
    --cc=yex.tian@intel.com \
    /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).