linux-kernel - RE: [Intel-gfx] [Linux v4.10.0-rc1] call-traces after suspend-resume (pm? i915? cpu/hotplug?)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <43D4F724E12AB6478FC1572B3FBE89D04C0D6A10@IRSMSX106.ger.corp.intel.com>
Date:   Wed, 28 Dec 2016 09:04:29 +0000
From:   "Saarinen, Jani" <jani.saarinen@...el.com>
To:     "sedat.dilek@...il.com" <sedat.dilek@...il.com>,
        Chris Wilson <chris@...is-wilson.co.uk>,
        "Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        intel-gfx <intel-gfx@...ts.freedesktop.org>,
        Linux PM List <linux-pm@...ts.linux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>,
        the arch/x86 maintainers <x86@...nel.org>
CC:     Daniel Vetter <daniel.vetter@...ll.ch>
Subject: RE: [Intel-gfx] [Linux v4.10.0-rc1] call-traces after
        suspend-resume (pm? i915? cpu/hotplug?)

HI, 
> -----Original Message-----
> From: Intel-gfx [mailto:intel-gfx-bounces@...ts.freedesktop.org] On Behalf
> Of Sedat Dilek
> Sent: Tuesday, December 27, 2016 6:07 PM
> To: Chris Wilson <chris@...is-wilson.co.uk>; Sedat Dilek
> <sedat.dilek@...il.com>; Wysocki, Rafael J <rafael.j.wysocki@...el.com>;
> Thomas Gleixner <tglx@...utronix.de>; intel-gfx <intel-
> gfx@...ts.freedesktop.org>; Linux PM List <linux-pm@...ts.linux-
> foundation.org>; LKML <linux-kernel@...r.kernel.org>; the arch/x86
> maintainers <x86@...nel.org>
> Cc: Daniel Vetter <daniel.vetter@...ll.ch>
> Subject: Re: [Intel-gfx] [Linux v4.10.0-rc1] call-traces after suspend-resume
> (pm? i915? cpu/hotplug?)
> 
> >> Also note that our CI is unhappy with -rc1, and it was not due to
> >> i915 patches. So very likely something else is also broken.
> >>
> >
> > Can you explain what "CI" means and its function in drm-intel development?
> >
See https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-intel.html (Pre-Merge Testing) and 
https://01.org/linuxgraphics/documentation/reproducing-patchwork-test-results
and (next link also on above documentation) https://intel-gfx-ci.01.org/CI/

Br

Jani Saarinen
Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo