On 4/7/20 12:35 PM, Chris Wilson wrote:
2 possible causes for 2 very different symptoms are in flight.
But neither would strictly be a hang; the most blatant one would be the
display server triggering an EFAULT. The patches are currently sitting
in the drm-intel-next-fixes queue; a quick test of
Quoting Larry Finger (2020-04-07 18:27:52)
> Chris,
>
> With a recent pull of kernel head, my Toshiba laptop with an i915 graphics
> card
> fails to boot. It hangs at the point where it should switch to a graphics
> screen. I bisected the problem to
>
> commit 7dc8f1143778a35b190f9413f228b3cf2
Chris,
With a recent pull of kernel head, my Toshiba laptop with an i915 graphics card
fails to boot. It hangs at the point where it should switch to a graphics
screen. I bisected the problem to
commit 7dc8f1143778a35b190f9413f228b3cf28f67f8d
Author: Chris Wilson
Date: Wed Mar 11 16:03:10
On 03/23/2017 03:44 PM, Chris Wilson wrote:
On Thu, Mar 23, 2017 at 01:19:43PM -0500, Larry Finger wrote:
Since kernel 4.11-rc1, my desktop (Plasma5/KDE) has encountered
intermittent hangs with the following information in the logs:
linux-4v1g.suse kernel: [drm] GPU HANG: ecode 7:0:0xf3ce,
On Thu, Mar 23, 2017 at 01:19:43PM -0500, Larry Finger wrote:
> Since kernel 4.11-rc1, my desktop (Plasma5/KDE) has encountered
> intermittent hangs with the following information in the logs:
>
> linux-4v1g.suse kernel: [drm] GPU HANG: ecode 7:0:0xf3ce, in
> plasmashell [1283], reason: Hang o
Since kernel 4.11-rc1, my desktop (Plasma5/KDE) has encountered intermittent
hangs with the following information in the logs:
linux-4v1g.suse kernel: [drm] GPU HANG: ecode 7:0:0xf3ce, in plasmashell
[1283], reason: Hang on render ring, action: reset
linux-4v1g.suse kernel: [drm] GPU hangs
The latest mainline kernel (commit 3f59de0) shows a regression. The symptom is
that as soon as the kernel is started, the display is blanked, and it is never
turned on again. This problem was bisected to commit
f21a21983ef13a031250c4c3f6018e29a549d0f1
("drm/i915: Splitting intel_dp_detect"). The
The latest mainline kernel (commit 3f59de0) shows a regression. The symptom is
that as soon as the kernel is started, the display is blanked, and it is never
turned on again. This problem was bisected to commit
f21a21983ef13a031250c4c3f6018e29a549d0f1
("drm/i915: Splitting intel_dp_detect"). The
[This is in reply to https://lkml.org/lkml/2014/10/3/415 - I just don't
have the message to reply to.]
Daniel, the bug you describe is likely [1]. We're on it.
Thanks,
Jani.
[1] https://bugzilla.kernel.org/show_bug.cgi?id=86551
--
Jani Nikula, Intel Open Source Technology Center
On Wed, 25 Jun 2014, Alan Stern wrote:
> On Wed, 25 Jun 2014, Ville [iso-8859-1] Syrjl wrote:
>
>> On Wed, Jun 25, 2014 at 02:06:55PM -0400, Alan Stern wrote:
>> > Daniel:
>> >
>> > I encountered a new problem in the i915 driver the first time I booted
>> > a 3.16-rc kernel on this computer. Wh
On Wed, 25 Jun 2014, Ville [iso-8859-1] Syrj�l� wrote:
> On Wed, Jun 25, 2014 at 02:06:55PM -0400, Alan Stern wrote:
> > Daniel:
> >
> > I encountered a new problem in the i915 driver the first time I booted
> > a 3.16-rc kernel on this computer. When it switched over to the frame
> > buffer d
On Wed, Jun 25, 2014 at 02:06:55PM -0400, Alan Stern wrote:
> Daniel:
>
> I encountered a new problem in the i915 driver the first time I booted
> a 3.16-rc kernel on this computer. When it switched over to the frame
> buffer driver, the screen went blank and stayed that way.
>
> 3.15 works ok
Daniel:
I encountered a new problem in the i915 driver the first time I booted
a 3.16-rc kernel on this computer. When it switched over to the frame
buffer driver, the screen went blank and stayed that way.
3.15 works okay.
Attached are log extracts from 3.15 and 3.16 (both with drm.debug=0xe
13 matches
Mail list logo
