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 18:01:44 +0100 [thread overview]
Message-ID: <20130725170144.GE6493@cantiga.alporthouse.com> (raw)
In-Reply-To: <CA+icZUWmpZK0jO_G1ec446WftzXDvSdnHLcQrkmBSHA7fSAqcw@mail.gmail.com>
On Thu, Jul 25, 2013 at 06:35:10PM +0200, Sedat Dilek wrote:
> On Thu, Jul 25, 2013 at 6:31 PM, Chris Wilson <chris@chris-wilson•co.uk> wrote:
> > On Thu, Jul 25, 2013 at 06:11:18PM +0200, Sedat Dilek wrote:
> >> Might be OT, but I cannot use my X graphics stack containing
> >> libdrm-2.4.46, mesa-9.1.5 and intel-ddx 2.21.12-git (tried also
> >> v2.21.11).
> >> Switching back to the one from Ubuntu/precise lets my X start.
> >>
> >>
> >> [ 40.379] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
> >> [ 40.379] (II) AIGLX: enabled GLX_INTEL_swap_event
> >> [ 40.380] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
> >> [ 40.380] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
> >> [ 40.380] (II) AIGLX: Loaded and initialized i965
> >> [ 40.380] (II) GLX: Initialized DRI2 GL provider for screen 0
> >> [ 40.380]
> >> Fatal server error:
> >> [ 40.380] failed to create screen resources
> >> [ 40.380]
> >> Please consult the The X.Org Foundation support
> >> at http://wiki.x.org
> >> for help.
> >> [ 40.380] Please also check the log file at "/var/log/Xorg.0.log"
> >> for additional information.
> >> [ 40.380]
> >> [ 40.380] (II) AIGLX: Suspending AIGLX clients for VT switch
> >> [ 40.396] ddxSigGiveUp: Closing log
> >> [ 40.398] Server terminated with error (1). Closing log file.
> >
> > Please attach the full Xorg.0.log so that I can make a few guesses.
>
> Linux-kernel: This happens with drm-intel-nightly pulled into next-20130725.
Basically boils down to either an object allocation failure or mmaping
failure. I think dmesg with drm.debug=7 is the next step.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-07-25 17:01 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 ` [Intel-gfx] " 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 [this message]
2013-07-25 17:15 ` Sedat Dilek
2013-07-25 17:26 ` [Intel-gfx] " 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 ` [Intel-gfx] " 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
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 ` [Intel-gfx] " 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=20130725170144.GE6493@cantiga.alporthouse.com \
--to=chris@chris-wilson$(echo .)co.uk \
--cc=daniel.vetter@ffwll$(echo .)ch \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=jani.nikula@linux$(echo .)intel.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sedat.dilek@gmail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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