On Sat, 2012-04-21 at 14:54 +0200, Daniel Vetter wrote:
> Please file a bug report with the error state attach (the
> entire thing), complete dmesg showing when the problem happens and a short
> description of the issue at bugs.freedesktop.org against DRI, component
> DRM/Intel.
See https://bugs.f
On Sat, Apr 21, 2012 at 02:58:39PM +0200, Paul Bolle wrote:
> On Sat, 2012-04-21 at 14:54 +0200, Daniel Vetter wrote:
> > On Sat, Apr 21, 2012 at 02:25:55PM +0200, Paul Bolle wrote:
> > > What part of that almost 700K file could be of interest?
> >
> > All of it. Please file a bug report with the
On Sat, 2012-04-21 at 14:54 +0200, Daniel Vetter wrote:
> On Sat, Apr 21, 2012 at 02:25:55PM +0200, Paul Bolle wrote:
> > What part of that almost 700K file could be of interest?
>
> All of it. Please file a bug report with the error state attach (the
> entire thing), complete dmesg showing when t
On Sat, Apr 21, 2012 at 02:25:55PM +0200, Paul Bolle wrote:
> On Thu, 2012-04-19 at 11:04 +0200, Paul Bolle wrote:
> > <6>[14673.824599] [drm] capturing error event; look for more information in
> > /debug/dri/0/i915_error_state
>
> I triggered this issue once again in the session I run currently
On Thu, 2012-04-19 at 11:04 +0200, Paul Bolle wrote:
> <6>[14673.824599] [drm] capturing error event; look for more information in
> /debug/dri/0/i915_error_state
I triggered this issue once again in the session I run currently:
$ cat /sys/kernel/debug/dri/0/i915_error_state | wc -c
68968
On Sat, 2012-04-21 at 14:54 +0200, Daniel Vetter wrote:
> Please file a bug report with the error state attach (the
> entire thing), complete dmesg showing when the problem happens and a short
> description of the issue at bugs.freedesktop.org against DRI, component
> DRM/Intel.
See https://bugs.f
On Sat, Apr 21, 2012 at 02:58:39PM +0200, Paul Bolle wrote:
> On Sat, 2012-04-21 at 14:54 +0200, Daniel Vetter wrote:
> > On Sat, Apr 21, 2012 at 02:25:55PM +0200, Paul Bolle wrote:
> > > What part of that almost 700K file could be of interest?
> >
> > All of it. Please file a bug report with the
On Sat, 2012-04-21 at 14:54 +0200, Daniel Vetter wrote:
> On Sat, Apr 21, 2012 at 02:25:55PM +0200, Paul Bolle wrote:
> > What part of that almost 700K file could be of interest?
>
> All of it. Please file a bug report with the error state attach (the
> entire thing), complete dmesg showing when t
On Sat, Apr 21, 2012 at 02:25:55PM +0200, Paul Bolle wrote:
> On Thu, 2012-04-19 at 11:04 +0200, Paul Bolle wrote:
> > <6>[14673.824599] [drm] capturing error event; look for more information in
> > /debug/dri/0/i915_error_state
>
> I triggered this issue once again in the session I run currently
On Thu, 2012-04-19 at 11:04 +0200, Paul Bolle wrote:
> <6>[14673.824599] [drm] capturing error event; look for more information in
> /debug/dri/0/i915_error_state
I triggered this issue once again in the session I run currently:
$ cat /sys/kernel/debug/dri/0/i915_error_state | wc -c
68968
0) On a laptop I use I've ran into i915 kernel errors at resume. I see
these only every now and then: not on all resumes. The pattern of these
errors (and preceding messages) is basically always like this:
<6>[14673.762529] [drm] Changing LVDS panel from (+hsync, +vsync) to (-hsync,
0) On a laptop I use I've ran into i915 kernel errors at resume. I see
these only every now and then: not on all resumes. The pattern of these
errors (and preceding messages) is basically always like this:
<6>[14673.762529] [drm] Changing LVDS panel from (+hsync, +vsync) to (-hsync,
12 matches
Mail list logo
