From: Chris Wilson <chris@chris-wilson.co.uk>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI <dri-devel@lists.freedesktop.org>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]
Date: Thu, 25 Jul 2013 20:22:48 +0100 [thread overview]
Message-ID: <20130725192248.GA13295@cantiga.alporthouse.com> (raw)
In-Reply-To: <CA+icZUW6oLE6cdnCkekz+43SrUn=vThqdfSKzz=XP-vmvB7Amw@mail.gmail.com>
On Thu, Jul 25, 2013 at 09:12:41PM +0200, Sedat Dilek wrote:
> New -3 dmesg.
That puts the ball back in the ddx's court. Next debugging patch:
diff --git a/src/intel_driver.c b/src/intel_driver.c
index f4d76bb..1f4f299 100644
--- a/src/intel_driver.c
+++ b/src/intel_driver.c
@@ -170,6 +170,7 @@ static Bool i830CreateScreenResources(ScreenPtr screen)
return FALSE;
intel_copy_fb(scrn);
+ ErrorF("%s: Success\n", __func__);
return TRUE;
}
diff --git a/src/intel_uxa.c b/src/intel_uxa.c
index 2f14173..6be7ebe 100644
--- a/src/intel_uxa.c
+++ b/src/intel_uxa.c
@@ -1150,11 +1150,15 @@ Bool intel_uxa_create_screen_resources(ScreenPtr screen)
intel_screen_private *intel = intel_get_screen_private(scrn);
dri_bo *bo = intel->front_buffer;
- if (!uxa_resources_init(screen))
+ if (!uxa_resources_init(screen)) {
+ ErrorF("bang: %d\n", __LINE__);
return FALSE;
+ }
- if (drm_intel_gem_bo_map_gtt(bo))
+ if (drm_intel_gem_bo_map_gtt(bo)) {
+ ErrorF("bang: %d\n", __LINE__);
return FALSE;
+ }
pixmap = screen->GetScreenPixmap(screen);
intel_set_pixmap_bo(pixmap, bo);
@@ -1167,8 +1171,10 @@ Bool intel_uxa_create_screen_resources(ScreenPtr screen)
NULL);
scrn->displayWidth = intel->front_pitch / intel->cpp;
- if (!intel_glamor_create_screen_resources(screen))
+ if (!intel_glamor_create_screen_resources(screen)) {
+ ErrorF("bang: %d\n", __LINE__);
return FALSE;
+ }
return TRUE;
}
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-07-25 19:23 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 8:54 linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ] Sedat Dilek
2013-07-25 9:44 ` [Intel-gfx] " Jani Nikula
2013-07-25 10:02 ` Sedat Dilek
2013-07-25 10:05 ` Sedat Dilek
2013-07-25 10:21 ` Jani Nikula
2013-07-25 10:37 ` Sedat Dilek
2013-07-25 13:36 ` Daniel Vetter
2013-07-25 14:23 ` Sedat Dilek
2013-07-25 14:27 ` Daniel Vetter
2013-07-25 15:03 ` Sedat Dilek
2013-07-25 15:05 ` Daniel Vetter
2013-07-25 15:34 ` Sedat Dilek
2013-07-25 16:11 ` Sedat Dilek
2013-07-25 16:31 ` Chris Wilson
2013-07-25 16:35 ` Sedat Dilek
2013-07-25 17:01 ` Chris Wilson
2013-07-25 17:15 ` Sedat Dilek
2013-07-25 17:26 ` Chris Wilson
2013-07-25 17:52 ` Sedat Dilek
2013-07-25 17:55 ` Sedat Dilek
2013-07-25 18:03 ` Sedat Dilek
2013-07-25 18:45 ` Chris Wilson
2013-07-25 18:50 ` Sedat Dilek
2013-07-25 19:00 ` Chris Wilson
2013-07-25 19:12 ` Sedat Dilek
2013-07-25 19:22 ` Chris Wilson [this message]
2013-07-25 19:32 ` Sedat Dilek
2013-07-25 20:07 ` Sedat Dilek
2013-07-25 21:52 ` Chris Wilson
2013-07-25 23:21 ` Sedat Dilek
2013-07-25 23:25 ` Chris Wilson
2013-07-26 7:15 ` Sedat Dilek
2013-07-26 7:26 ` Chris Wilson
2013-07-26 8:25 ` Sedat Dilek
2013-07-26 8:27 ` Sedat Dilek
2013-07-26 8:50 ` Chris Wilson
2013-07-26 8:52 ` Daniel Vetter
2013-07-26 9:02 ` Sedat Dilek
2013-07-26 9:11 ` Sedat Dilek
2013-07-26 9:16 ` Daniel Vetter
2013-07-26 9:32 ` Sedat Dilek
2013-07-26 10:34 ` Sedat Dilek
2013-07-25 18:03 ` Chris Wilson
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=20130725192248.GA13295@cantiga.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/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