Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756889Ab2HULOk (ORCPT ); Tue, 21 Aug 2012 07:14:40 -0400 Received: from mail-lpp01m010-f46.google.com ([209.85.215.46]:47392 "EHLO mail-lpp01m010-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751643Ab2HULOi (ORCPT ); Tue, 21 Aug 2012 07:14:38 -0400 MIME-Version: 1.0 Reply-To: sedat.dilek@gmail.com In-Reply-To: References: Date: Tue, 21 Aug 2012 13:14:36 +0200 Message-ID: Subject: Re: inux-next: Tree for Aug 21 (call-trace when suspending: PM?) From: Sedat Dilek To: Stephen Rothwell Cc: linux-next@vger.kernel.org, LKML , "Rafael J. Wysocki" , Ingo Molnar , Al Viro , Daniel Vetter Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1889 Lines: 57 On Tue, Aug 21, 2012 at 1:03 PM, Sedat Dilek wrote: > On Tue, Aug 21, 2012 at 1:02 PM, Sedat Dilek wrote: >> On Tue, Aug 21, 2012 at 8:04 AM, Stephen Rothwell wrote: >>> Hi all, >>> >>> Changes since 20120820: >>> >>> The rr tree gained a conflict against Linus' tree. >>> >>> The tip tree still has its build failure so I used the version from >>> next-20120814. >>> >>> The workqueues tree gained a conflict against the hid tree. >>> >>> The drivers-x86 tree still has its build failure so I used the version >>> from next-20120817. >>> >>> The signal tree gained a conflict against Linus' tree. I have still >>> reverted 3 commits from the signal tree at the request of the arm >>> maintainer. >>> >>> ---------------------------------------------------------------------------- >>> >> >> Hi, >> >> I have compiled linux-next (next-20120821) and see the attached >> call-trace when suspending. >> Suspending did NOT work (Xorg seems to cause it) - machine came back to desktop. >> >> With yesterday's next-20120820 I haven't seen this. >> >> I am not sure what is this causing... PM, x86/sched or even VFS? >> Any help for debugging appreciated. >> >> I am on Ubuntu/precise AMD64 and use systemd-v43 as init-system. >> >> Regards, >> - Sedat - > > Forgot attachment! > If you don't succeed - try try try... > > - Sedat - [ CC danvet ] I have pulled in drm-intel-fixes into my local GIT tree and rebuilt i915 - this seems to fix the problem. Daniel any suggestion which patch in d-i-f did it? [1] http://cgit.freedesktop.org/~danvet/drm-intel/log/?h=drm-intel-fixes -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/