On Tue, 2013-12-03 at 16:19 +0100, Daniel Vetter wrote:
> I'd like to confirm the actual cause (I suspect that we switch
> pipes around) for why you see this but other machines don't show
> this to augment the commit message. But I've merged the fix already.
The dmesg, up to and including the
On Mon, Dec 02, 2013 at 07:05:25PM +0100, Paul Bolle wrote:
> On Mon, 2013-12-02 at 15:23 +0100, Daniel Vetter wrote:
> > On Mon, Dec 2, 2013 at 10:53 AM, Paul Bolle wrote:
> > > This generated quite a bit of debug messages so I only copied the
> > > WARNING and the drm (related) messages
On Mon, Dec 02, 2013 at 07:05:25PM +0100, Paul Bolle wrote:
On Mon, 2013-12-02 at 15:23 +0100, Daniel Vetter wrote:
On Mon, Dec 2, 2013 at 10:53 AM, Paul Bolle pebo...@tiscali.nl wrote:
This generated quite a bit of debug messages so I only copied the
WARNING and the drm (related)
On Tue, 2013-12-03 at 16:19 +0100, Daniel Vetter wrote:
I'd like to confirm the actual cause (I suspect that we switch
pipesplanes around) for why you see this but other machines don't show
this to augment the commit message. But I've merged the fix already.
The dmesg, up to and including the
On Mon, 2013-12-02 at 15:23 +0100, Daniel Vetter wrote:
> On Mon, Dec 2, 2013 at 10:53 AM, Paul Bolle wrote:
> > This generated quite a bit of debug messages so I only copied the
> > WARNING and the drm (related) messages immediately preceding it. Please
> > feel free to prod again if that's
On Mon, Dec 2, 2013 at 10:53 AM, Paul Bolle wrote:
> On Mon, 2013-12-02 at 08:33 +0100, Daniel Vetter wrote:
>> On Sun, Dec 1, 2013 at 5:57 PM, Paul Bolle wrote:
>> > The WARNING is now gone during suspend and resume (having tested that
>> > thoroughly - ie, twice). But I still see it at boot.
On Mon, 2013-12-02 at 08:33 +0100, Daniel Vetter wrote:
> On Sun, Dec 1, 2013 at 5:57 PM, Paul Bolle wrote:
> > The WARNING is now gone during suspend and resume (having tested that
> > thoroughly - ie, twice). But I still see it at boot. Is there a related
> > fix for that WARNING during boot?
>
On Mon, 2013-12-02 at 08:33 +0100, Daniel Vetter wrote:
On Sun, Dec 1, 2013 at 5:57 PM, Paul Bolle pebo...@tiscali.nl wrote:
The WARNING is now gone during suspend and resume (having tested that
thoroughly - ie, twice). But I still see it at boot. Is there a related
fix for that WARNING
On Mon, Dec 2, 2013 at 10:53 AM, Paul Bolle pebo...@tiscali.nl wrote:
On Mon, 2013-12-02 at 08:33 +0100, Daniel Vetter wrote:
On Sun, Dec 1, 2013 at 5:57 PM, Paul Bolle pebo...@tiscali.nl wrote:
The WARNING is now gone during suspend and resume (having tested that
thoroughly - ie, twice).
On Mon, 2013-12-02 at 15:23 +0100, Daniel Vetter wrote:
On Mon, Dec 2, 2013 at 10:53 AM, Paul Bolle pebo...@tiscali.nl wrote:
This generated quite a bit of debug messages so I only copied the
WARNING and the drm (related) messages immediately preceding it. Please
feel free to prod again if
On Sun, Dec 1, 2013 at 5:57 PM, Paul Bolle wrote:
> On Sun, 2013-12-01 at 10:58 +0100, Daniel Vetter wrote:
>> Should be fixed with
>>
>> commit 7c063c725987406d743cc7de7625ff224fab75de
>> Author: Jesse Barnes
>> Date: Tue Nov 26 09:13:41 2013 -0800
>>
>> drm/i915: take mode config lock
On Sun, 2013-12-01 at 10:58 +0100, Daniel Vetter wrote:
> Should be fixed with
>
> commit 7c063c725987406d743cc7de7625ff224fab75de
> Author: Jesse Barnes
> Date: Tue Nov 26 09:13:41 2013 -0800
>
> drm/i915: take mode config lock around crtc disable at suspend
>
> which is currently in
Should be fixed with
commit 7c063c725987406d743cc7de7625ff224fab75de
Author: Jesse Barnes
Date: Tue Nov 26 09:13:41 2013 -0800
drm/i915: take mode config lock around crtc disable at suspend
which is currently in drm-intel-fixes. I'll forward it early next week.
-Daniel
On Sat, Nov 30,
Should be fixed with
commit 7c063c725987406d743cc7de7625ff224fab75de
Author: Jesse Barnes jbar...@virtuousgeek.org
Date: Tue Nov 26 09:13:41 2013 -0800
drm/i915: take mode config lock around crtc disable at suspend
which is currently in drm-intel-fixes. I'll forward it early next week.
On Sun, 2013-12-01 at 10:58 +0100, Daniel Vetter wrote:
Should be fixed with
commit 7c063c725987406d743cc7de7625ff224fab75de
Author: Jesse Barnes jbar...@virtuousgeek.org
Date: Tue Nov 26 09:13:41 2013 -0800
drm/i915: take mode config lock around crtc disable at suspend
which is
On Sun, Dec 1, 2013 at 5:57 PM, Paul Bolle pebo...@tiscali.nl wrote:
On Sun, 2013-12-01 at 10:58 +0100, Daniel Vetter wrote:
Should be fixed with
commit 7c063c725987406d743cc7de7625ff224fab75de
Author: Jesse Barnes jbar...@virtuousgeek.org
Date: Tue Nov 26 09:13:41 2013 -0800
On both v3.13-rc1 and v3.13-rc2 is see this at every boot and during
every suspend and resume cycle:
<4>[2.682468] WARNING: CPU: 0 PID: 173 at
drivers/gpu/drm/i915/intel_display.c:9948
intel_get_pipe_from_connector+0x42/0x50 [i915]()
<5>[2.682470] Modules linked in: i915(F+)
On both v3.13-rc1 and v3.13-rc2 is see this at every boot and during
every suspend and resume cycle:
4[2.682468] WARNING: CPU: 0 PID: 173 at
drivers/gpu/drm/i915/intel_display.c:9948
intel_get_pipe_from_connector+0x42/0x50 [i915]()
5[2.682470] Modules linked in: i915(F+) ata_generic(F)
18 matches
Mail list logo
