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

[Sedat Dilek <sedat.dilek@xxxxxxxxx>]

On Tue, Aug 21, 2012 at 8:04 AM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> 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 -
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/