linux-kernel - Re: inux-next: Tree for Aug 21 (call-trace when suspending: PM?)

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]

Date:	Tue, 21 Aug 2012 13:53:10 +0200
From:	Daniel Vetter <daniel@...ll.ch>
To:	sedat.dilek@...il.com
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, Ingo Molnar <mingo@...e.hu>,
	Al Viro <viro@...iv.linux.org.uk>
Subject: Re: inux-next: Tree for Aug 21 (call-trace when suspending: PM?)

On Tue, Aug 21, 2012 at 1:14 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
> On Tue, Aug 21, 2012 at 1:03 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
>> On Tue, Aug 21, 2012 at 1:02 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
>>> On Tue, Aug 21, 2012 at 8:04 AM, Stephen Rothwell <sfr@...b.auug.org.au> 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?

Without the backtrace it's kinda hard to tell ... Also, if you can
dump a git log of the commits from -fixes that you don't yet have.
-Daniel

>
> [1] http://cgit.freedesktop.org/~danvet/drm-intel/log/?h=drm-intel-fixes



-- 
Daniel Vetter
daniel.vetter@...ll.ch - +41 (0) 79 364 57 48 - http://blog.ffwll.ch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/