From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Norbert Preining <preining@logic.at>
Cc: dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: Lenovo resume from suspends hangs in i915_gpu_busy or so
Date: Fri, 1 Apr 2011 09:08:17 -0700 [thread overview]
Message-ID: <20110401090817.01717af0@jbarnes-desktop> (raw)
In-Reply-To: <20110401051511.GE9128@gamma.logic.tuwien.ac.at>
On Fri, 1 Apr 2011 14:15:11 +0900
Norbert Preining <preining@logic.at> wrote:
> Hi all,
>
> adding dri-devel as I found it is actually not completely dead,
> but hanging in some i915 problem.
>
> Copyied from screen:
> Process ips-adjust (....
> Stack:
> ....
> ....
> ...
> Call Trace:
> <IRQ>
> ... ? tick_program_event
> call_sortirq
> do_softirq
> irq_exit
> smp_apic_timer_interrupt
> apic_timer_interrupt
> <EOI>
> ? _raw_spin_lock
> i915_gpu_busy
> ips_adjust
> ? show_cpu_temp
> kthread
> kernel_thread_helper
> ? kthread_worker_fn
> ? gs_change
> Code: ...
> (once more more or less the same as above)
Hm, ok so on resume we're checking GPU busyness, which is normal, but
end up hanging on the spinlock? Do you see what scrolls by above the
text you took a picture of (probably a "task hung" message?).
Does this happen reliably? Does a previous kernel work ok?
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-04-01 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 2:10 Lenovo Thinkpad Edge: suspend to ram works, but wake up not Norbert Preining
2011-04-01 5:15 ` Lenovo resume from suspends hangs in i915_gpu_busy or so Norbert Preining
2011-04-01 16:08 ` Jesse Barnes [this message]
2011-04-02 0:24 ` Norbert Preining
2011-04-02 2:21 ` Jesse Barnes
2011-04-04 14:16 ` Norbert Preining
2011-04-03 1:30 ` Peter Stuge
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=20110401090817.01717af0@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
/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
all inboxes | Powered by JetHome®