On Thu, 24 Oct 2013, Egbert Eich wrote:
> > > > > Can you please attach full dmesg from boot up to the first WARN with
> > > > > drm.debug=0xe? This really shouldn't happen and indicates a bug
> > > > > somewhere ...
> > > >
> > > > A bit difficult ... I originally thought that it was
Jiri Kosina writes:
> On Mon, 21 Oct 2013, Egbert Eich wrote:
>
> > > On Thu, 3 Oct 2013, Daniel Vetter wrote:
> > >
> > > > Can you please attach full dmesg from boot up to the first WARN with
> > > > drm.debug=0xe? This really shouldn't happen and indicates a bug
> > > > somewhere
On Thu, 24 Oct 2013, Jiri Kosina wrote:
> I have this:
>
> [357128.184113] [drm] HPD interrupt storm detected on connector DP-3:
> switching from hotplug detection to polling
>
> It appeared in the log approximately 5 seconds after resume has been
> completed.
Okay, and it just happened
On Mon, 21 Oct 2013, Egbert Eich wrote:
> > On Thu, 3 Oct 2013, Daniel Vetter wrote:
> >
> > > Can you please attach full dmesg from boot up to the first WARN with
> > > drm.debug=0xe? This really shouldn't happen and indicates a bug
> > > somewhere ...
> >
> > A bit difficult ... I
On Mon, 21 Oct 2013, Egbert Eich wrote:
On Thu, 3 Oct 2013, Daniel Vetter wrote:
Can you please attach full dmesg from boot up to the first WARN with
drm.debug=0xe? This really shouldn't happen and indicates a bug
somewhere ...
A bit difficult ... I originally thought
On Thu, 24 Oct 2013, Jiri Kosina wrote:
I have this:
[357128.184113] [drm] HPD interrupt storm detected on connector DP-3:
switching from hotplug detection to polling
It appeared in the log approximately 5 seconds after resume has been
completed.
Okay, and it just happened during
Jiri Kosina writes:
On Mon, 21 Oct 2013, Egbert Eich wrote:
On Thu, 3 Oct 2013, Daniel Vetter wrote:
Can you please attach full dmesg from boot up to the first WARN with
drm.debug=0xe? This really shouldn't happen and indicates a bug
somewhere ...
A bit
On Thu, 24 Oct 2013, Egbert Eich wrote:
Can you please attach full dmesg from boot up to the first WARN with
drm.debug=0xe? This really shouldn't happen and indicates a bug
somewhere ...
A bit difficult ... I originally thought that it was reliably
Hi Jiri,
Just found your email, it got missed do to a temporary inaccessibility to
my email.
Jiri Kosina writes:
> On Thu, 3 Oct 2013, Daniel Vetter wrote:
>
> > Can you please attach full dmesg from boot up to the first WARN with
> > drm.debug=0xe? This really shouldn't happen and
Hi Jiri,
Just found your email, it got missed do to a temporary inaccessibility to
my email.
Jiri Kosina writes:
On Thu, 3 Oct 2013, Daniel Vetter wrote:
Can you please attach full dmesg from boot up to the first WARN with
drm.debug=0xe? This really shouldn't happen and indicates a
On Thu, 3 Oct 2013, Daniel Vetter wrote:
> Can you please attach full dmesg from boot up to the first WARN with
> drm.debug=0xe? This really shouldn't happen and indicates a bug
> somewhere ...
OK, I haven't been able to reproduce this any more for ~week ... so please
disregard this, and I'll
On Thu, 3 Oct 2013, Daniel Vetter wrote:
Can you please attach full dmesg from boot up to the first WARN with
drm.debug=0xe? This really shouldn't happen and indicates a bug
somewhere ...
OK, I haven't been able to reproduce this any more for ~week ... so please
disregard this, and I'll
On Thu, 3 Oct 2013, Daniel Vetter wrote:
> Can you please attach full dmesg from boot up to the first WARN with
> drm.debug=0xe? This really shouldn't happen and indicates a bug
> somewhere ...
A bit difficult ... I originally thought that it was reliably
reproducible, but now I didn't get it
Can you please attach full dmesg from boot up to the first WARN with
drm.debug=0xe? This really shouldn't happen and indicates a bug
somewhere ...
Cheers, Daniel
On Thu, Oct 3, 2013 at 11:46 AM, Jiri Kosina wrote:
> During resume from hibernation, I started to see the warning below since
>
>
During resume from hibernation, I started to see the warning below since
commit b8f102e8bf71cacf33326360fdf9dcfd1a63925b
Author: Egbert Eich
Date: Fri Jul 26 14:14:24 2013 +0200
drm/i915: Add messages useful for HPD storm detection debugging (v2)
the
During resume from hibernation, I started to see the warning below since
commit b8f102e8bf71cacf33326360fdf9dcfd1a63925b
Author: Egbert Eich e...@suse.de
Date: Fri Jul 26 14:14:24 2013 +0200
drm/i915: Add messages useful for HPD storm detection debugging
Can you please attach full dmesg from boot up to the first WARN with
drm.debug=0xe? This really shouldn't happen and indicates a bug
somewhere ...
Cheers, Daniel
On Thu, Oct 3, 2013 at 11:46 AM, Jiri Kosina jkos...@suse.cz wrote:
During resume from hibernation, I started to see the warning
On Thu, 3 Oct 2013, Daniel Vetter wrote:
Can you please attach full dmesg from boot up to the first WARN with
drm.debug=0xe? This really shouldn't happen and indicates a bug
somewhere ...
A bit difficult ... I originally thought that it was reliably
reproducible, but now I didn't get it
18 matches
Mail list logo