dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: Julian Margetson <runaway@candw.ms>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [Powerpc] Sam460ex Canyonlands issue -Kernel 4.4.6-rc1
Date: Tue, 29 Mar 2016 12:15:37 +0900	[thread overview]
Message-ID: <56F9F359.5040108@daenzer.net> (raw)
In-Reply-To: <56F9C2A5.5070808@candw.ms>

On 29.03.2016 08:47, Julian Margetson wrote:
> 
> Seeing the following when booting kernel 4.6-rc1 on Acube Sam460ex Canyonlands board.
> This loops for a few times then the kernel boots.
> No problem with the 4.6-rc1 with an A-eon Tabor Freescale e500v2 board.
> 
> Regards
> 
> Julian
> 
> 
>  [    2.197839] ------------[ cut here ]------------
>  [    2.197850] WARNING: CPU: 0 PID: 1 at drivers/gpu/drm/drm_irq.c:1368 drm_vblank_off+0x2c/0x1e0

That's

	if (WARN_ON(pipe >= dev->num_crtcs))

My best guess is that drm_vblank_off is called before drm_vblank_init,
so dev->num_crtcs is still 0.


Please provide the full dmesg output corresponding to the problem.


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-03-29  3:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28 23:47 [Powerpc] Sam460ex Canyonlands issue -Kernel 4.4.6-rc1 Julian Margetson
2016-03-29  3:15 ` Michel Dänzer [this message]
2016-03-29  9:55   ` Julian Margetson
2016-03-30  3:49     ` Michel Dänzer
2016-03-30 10:36       ` Julian Margetson
2016-03-31  6:50         ` Michel Dänzer
2016-03-31 10:00           ` Julian Margetson
2016-04-01  8:31             ` Michel Dänzer
2016-04-01 10:33               ` Julian Margetson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56F9F359.5040108@daenzer.net \
    --to=michel@daenzer.net \
    --cc=alexander.deucher@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=runaway@candw.ms \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox