Thanks for all your efforts. It is really fun to see such an immediate response.
Daniel Vetter wrote:
>On Sat, Apr 6, 2013 at 6:24 PM, George Amanakis wrote:
>> Indeed, I set explicitly drm_kms_helper.poll=0 since 2.35.x. See here:
>> http://souriguha.wordpress.com/2011/03/08/how-to-solve-probl
PM
Subject: Re: BUG: kworker hangs the GPU on drm and i915 since 3.8.x under X11
Indeed, the commit you've bisected too accidentally removed this
check. I'll submit a patch.So I guess you've explicitly set
drm_kms_helper.poll=0. Can you please elaborate what you're working
around
I mean that I can type, move the mouse pointer, open new windows but there is a
lag until these changes are displayed. Stuttering like.
I ended up not reverting the aforementioned commit but modifying it. This also
solves the issue. Here is the patch:
diff -rupN a/drivers/gpu/drm/drm_crtc_help
Thanks for all your efforts. It is really fun to see such an immediate response.
Daniel Vetter wrote:
>On Sat, Apr 6, 2013 at 6:24 PM, George Amanakis
>wrote:
>> Indeed, I set explicitly drm_kms_helper.poll=0 since 2.35.x. See here:
>> http://souriguha.wordpress.com/2011/03/08/how-to-solve-pro
On Sat, Apr 6, 2013 at 6:24 PM, George Amanakis wrote:
> Indeed, I set explicitly drm_kms_helper.poll=0 since 2.35.x. See here:
> http://souriguha.wordpress.com/2011/03/08/how-to-solve-problem-with-thinkpadkslowd-kworker-on-linux-kernel-2-35-2-36/
>
> Mouse and keyboard freezes intermittently some
On Sat, Apr 6, 2013 at 12:01 AM, George Amanakis
wrote:
> I mean that I can type, move the mouse pointer, open new windows but there
> is a lag until these changes are displayed. Stuttering like.
>
> I ended up not reverting the aforementioned commit but modifying it. This
> also solves the issue
On Sat, Apr 6, 2013 at 6:24 PM, George Amanakis wrote:
> Indeed, I set explicitly drm_kms_helper.poll=0 since 2.35.x. See here:
> http://souriguha.wordpress.com/2011/03/08/how-to-solve-problem-with-thinkpadkslowd-kworker-on-linux-kernel-2-35-2-36/
>
> Mouse and keyboard freezes intermittently some
PM
Subject: Re: BUG: kworker hangs the GPU on drm and i915 since 3.8.x under X11
Indeed, the commit you've bisected too accidentally removed this
check. I'll submit a patch.So I guess you've explicitly set
drm_kms_helper.poll=0. Can you please elaborate what you're working
around
On Sat, Apr 6, 2013 at 12:01 AM, George Amanakis wrote:
> I mean that I can type, move the mouse pointer, open new windows but there
> is a lag until these changes are displayed. Stuttering like.
>
> I ended up not reverting the aforementioned commit but modifying it. This
> also solves the issue.
On Thu, Apr 4, 2013 at 11:53 PM, George Amanakis
wrote:
> Compiled und run the kernel as you instructed.
> Although the GPU did hang momentarily the dmesg showed no abnormalities.
Can you please explain in more detail what you mean by "did hang
momentarily"? If it's a real gpu hang it should be
I mean that I can type, move the mouse pointer, open new windows but there is a
lag until these changes are displayed. Stuttering like.
I ended up not reverting the aforementioned commit but modifying it. This also
solves the issue. Here is the patch:
diff -rupN a/drivers/gpu/drm/drm_crtc_help
On Thu, Apr 4, 2013 at 11:53 PM, George Amanakis wrote:
> Compiled und run the kernel as you instructed.
> Although the GPU did hang momentarily the dmesg showed no abnormalities.
Can you please explain in more detail what you mean by "did hang
momentarily"? If it's a real gpu hang it should be
Two things:
- Please always cc relevant mailing lists when reporting a bug.
- With lockdep enabled (CONFIG_PROVE_LOCKING) you should get detailed
backtraces and lists of held lock when the kworker gets stuck. Can you
please reproduce with that option enabled and then attach the dmesg?
Thanks, Dani
Compiled und run the kernel as you instructed.
Although the GPU did hang momentarily the dmesg showed no abnormalities.
dmesg:
[??? 0.00] Initializing cgroup subsys cpuset
[??? 0.00] Initializing cgroup subsys cpu
[??? 0.00] Linux version 3.8.4-1-mine (root at x3200) (gcc version 4.7.
Two things:
- Please always cc relevant mailing lists when reporting a bug.
- With lockdep enabled (CONFIG_PROVE_LOCKING) you should get detailed
backtraces and lists of held lock when the kworker gets stuck. Can you
please reproduce with that option enabled and then attach the dmesg?
Thanks, Dani
15 matches
Mail list logo
