[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-26 Thread Daniel Vetter
On Fri, Jul 26, 2013 at 11:11 AM, Sedat Dilek wrote: > I have compared next-20130725 VS. next-20130726: > > $ head -2313 next-20130725-VS-next-20130726.diff | grep ^+ | grep i915 > + drm/i915: Colocate all GT access routines in the same file > + drm/i915: Use a private interface for reg

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-26 Thread Daniel Vetter
On Fri, Jul 26, 2013 at 10:50 AM, Chris Wilson wrote: > On Fri, Jul 26, 2013 at 10:27:03AM +0200, Sedat Dilek wrote: >> On Fri, Jul 26, 2013 at 10:25 AM, Sedat Dilek >> wrote: >> > ... >> > ... but does not start as well, so it seems to be a kernel-issue as >> > assumed (2nd confirmation). >> >

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-26 Thread Chris Wilson
On Fri, Jul 26, 2013 at 10:27:03AM +0200, Sedat Dilek wrote: > On Fri, Jul 26, 2013 at 10:25 AM, Sedat Dilek > wrote: > > ... > > ... but does not start as well, so it seems to be a kernel-issue as > > assumed (2nd confirmation). > > > > X.log attached. > > > > Now, really w/ promised attachment

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-26 Thread Chris Wilson
On Fri, Jul 26, 2013 at 09:15:14AM +0200, Sedat Dilek wrote: > For example: I could start my X with even doing ugly hacks like this... > > [ intel-ddx (git) ] > ... > Bool intel_uxa_create_screen_resources(ScreenPtr screen) > ... > #if 0 > if (drm_intel_gem_bo_map_gtt(bo)) > re

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-26 Thread Daniel Vetter
On Fri, Jul 26, 2013 at 11:11 AM, Sedat Dilek wrote: > I have compared next-20130725 VS. next-20130726: > > $ head -2313 next-20130725-VS-next-20130726.diff | grep ^+ | grep i915 > + drm/i915: Colocate all GT access routines in the same file > + drm/i915: Use a private interface for reg

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-26 Thread Daniel Vetter
On Fri, Jul 26, 2013 at 10:50 AM, Chris Wilson wrote: > On Fri, Jul 26, 2013 at 10:27:03AM +0200, Sedat Dilek wrote: >> On Fri, Jul 26, 2013 at 10:25 AM, Sedat Dilek wrote: >> > ... >> > ... but does not start as well, so it seems to be a kernel-issue as >> > assumed (2nd confirmation). >> > >> >

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-26 Thread Chris Wilson
On Fri, Jul 26, 2013 at 10:27:03AM +0200, Sedat Dilek wrote: > On Fri, Jul 26, 2013 at 10:25 AM, Sedat Dilek wrote: > > ... > > ... but does not start as well, so it seems to be a kernel-issue as > > assumed (2nd confirmation). > > > > X.log attached. > > > > Now, really w/ promised attachment.

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-26 Thread Chris Wilson
On Fri, Jul 26, 2013 at 09:15:14AM +0200, Sedat Dilek wrote: > For example: I could start my X with even doing ugly hacks like this... > > [ intel-ddx (git) ] > ... > Bool intel_uxa_create_screen_resources(ScreenPtr screen) > ... > #if 0 > if (drm_intel_gem_bo_map_gtt(bo)) > re

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-26 Thread Chris Wilson
On Fri, Jul 26, 2013 at 01:21:07AM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 11:52 PM, Chris Wilson > wrote: > > On Thu, Jul 25, 2013 at 10:07:02PM +0200, Sedat Dilek wrote: > >> What means the bang line? > >> > >> [54.564] (II) GLX: Initialized DRI2 GL provider for screen 0 > >> [

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
On Thu, Jul 25, 2013 at 10:07:02PM +0200, Sedat Dilek wrote: > What means the bang line? > > [54.564] (II) GLX: Initialized DRI2 GL provider for screen 0 > [54.565] bang: 1159 > [54.565] > Fatal server error: > [54.565] failed to create screen resources That means between the kern

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
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 @@ s

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
On Thu, Jul 25, 2013 at 08:50:59PM +0200, Sedat Dilek wrote: > Against what tree is this applicable? It is definitely not drm-intel-nightly. Applied cleanly to nightly here, but just in case here's a rebased version: diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c i

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
On Thu, Jul 25, 2013 at 08:03:06PM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 7:55 PM, Sedat Dilek wrote: > > F*ck. Wrong patch refreshed. > > > > New dmesg attached. Hmm, not seeing any difference, so let's add a couple more lines just to be sure: (apologies I didn't stash the previou

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
On Thu, Jul 25, 2013 at 07:52:22PM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 7:26 PM, Chris Wilson > wrote: > > On Thu, Jul 25, 2013 at 07:15:03PM +0200, Sedat Dilek wrote: > >> On Thu, Jul 25, 2013 at 7:01 PM, Chris Wilson >> chris-wilson.co.uk> wrote: > >> > Basically boils down to e

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
On Thu, Jul 25, 2013 at 07:15:03PM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 7:01 PM, Chris Wilson > wrote: > > Basically boils down to either an object allocation failure or mmaping > > failure. I think dmesg with drm.debug=7 is the next step. > > Attached! Thanks for taking care. Hm

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
On Thu, Jul 25, 2013 at 06:35:10PM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 6:31 PM, Chris Wilson > 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.2

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
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

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Daniel Vetter
On Thu, Jul 25, 2013 at 5:03 PM, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 4:27 PM, Daniel Vetter wrote: >> On Thu, Jul 25, 2013 at 04:23:40PM +0200, Sedat Dilek wrote: >>> On Thu, Jul 25, 2013 at 3:36 PM, Daniel Vetter wrote: >>> > On Thu, Jul 25, 2013 at 12:37:44PM +0200, Sedat Dilek wrote:

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
On Fri, Jul 26, 2013 at 01:21:07AM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 11:52 PM, Chris Wilson > wrote: > > On Thu, Jul 25, 2013 at 10:07:02PM +0200, Sedat Dilek wrote: > >> What means the bang line? > >> > >> [54.564] (II) GLX: Initialized DRI2 GL provider for screen 0 > >> [

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Daniel Vetter
On Thu, Jul 25, 2013 at 04:23:40PM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 3:36 PM, Daniel Vetter wrote: > > On Thu, Jul 25, 2013 at 12:37:44PM +0200, Sedat Dilek wrote: > >> On Thu, Jul 25, 2013 at 12:21 PM, Jani Nikula > >> wrote: > >> > On Thu, 25 Jul 2013, Sedat Dilek wrote: > >>

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Daniel Vetter
On Thu, Jul 25, 2013 at 12:37:44PM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 12:21 PM, Jani Nikula > wrote: > > On Thu, 25 Jul 2013, Sedat Dilek wrote: > >> On Thu, Jul 25, 2013 at 12:02 PM, Sedat Dilek > >> wrote: > >>> On Thu, Jul 25, 2013 at 11:44 AM, Jani Nikula > >>> wrote: > >>

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
On Thu, Jul 25, 2013 at 10:07:02PM +0200, Sedat Dilek wrote: > What means the bang line? > > [54.564] (II) GLX: Initialized DRI2 GL provider for screen 0 > [54.565] bang: 1159 > [54.565] > Fatal server error: > [54.565] failed to create screen resources That means between the kern

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Jani Nikula
On Thu, 25 Jul 2013, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 12:02 PM, Sedat Dilek > wrote: >> On Thu, Jul 25, 2013 at 11:44 AM, Jani Nikula >> wrote: >>> On Thu, 25 Jul 2013, Sedat Dilek wrote: On Thu, Jul 25, 2013 at 7:12 AM, Stephen Rothwell >>> canb.auug.org.au> wrote: > Hi a

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Jani Nikula
On Thu, 25 Jul 2013, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 7:12 AM, Stephen Rothwell > wrote: >> Hi all, >> >> Changes since 20130724: >> >> Removed tree: >> arm-dt (at maintainer's request) >> >> The wireless-next tree lost its build failure and gained a conflict >> against Linus

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Sedat Dilek
On Thu, Jul 25, 2013 at 12:21 PM, Jani Nikula wrote: > On Thu, 25 Jul 2013, Sedat Dilek wrote: >> On Thu, Jul 25, 2013 at 12:02 PM, Sedat Dilek >> wrote: >>> On Thu, Jul 25, 2013 at 11:44 AM, Jani Nikula >>> wrote: On Thu, 25 Jul 2013, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 7:1

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
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 @@ s

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
On Thu, Jul 25, 2013 at 08:50:59PM +0200, Sedat Dilek wrote: > Against what tree is this applicable? It is definitely not drm-intel-nightly. Applied cleanly to nightly here, but just in case here's a rebased version: diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c i

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Sedat Dilek
On Thu, Jul 25, 2013 at 12:02 PM, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 11:44 AM, Jani Nikula > wrote: >> On Thu, 25 Jul 2013, Sedat Dilek wrote: >>> On Thu, Jul 25, 2013 at 7:12 AM, Stephen Rothwell >>> wrote: Hi all, Changes since 20130724: Removed tree:

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Sedat Dilek
On Thu, Jul 25, 2013 at 11:44 AM, Jani Nikula wrote: > On Thu, 25 Jul 2013, Sedat Dilek wrote: >> On Thu, Jul 25, 2013 at 7:12 AM, Stephen Rothwell >> wrote: >>> Hi all, >>> >>> Changes since 20130724: >>> >>> Removed tree: >>> arm-dt (at maintainer's request) >>> >>> The wireless-next

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
On Thu, Jul 25, 2013 at 08:03:06PM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 7:55 PM, Sedat Dilek wrote: > > F*ck. Wrong patch refreshed. > > > > New dmesg attached. Hmm, not seeing any difference, so let's add a couple more lines just to be sure: (apologies I didn't stash the previou

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
On Thu, Jul 25, 2013 at 07:52:22PM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 7:26 PM, Chris Wilson > wrote: > > On Thu, Jul 25, 2013 at 07:15:03PM +0200, Sedat Dilek wrote: > >> On Thu, Jul 25, 2013 at 7:01 PM, Chris Wilson > >> wrote: > >> > Basically boils down to either an object a

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
On Thu, Jul 25, 2013 at 07:15:03PM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 7:01 PM, Chris Wilson > wrote: > > Basically boils down to either an object allocation failure or mmaping > > failure. I think dmesg with drm.debug=7 is the next step. > > Attached! Thanks for taking care. Hm

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
On Thu, Jul 25, 2013 at 06:35:10PM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 6:31 PM, Chris Wilson > 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.2

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Chris Wilson
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

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Daniel Vetter
On Thu, Jul 25, 2013 at 5:03 PM, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 4:27 PM, Daniel Vetter wrote: >> On Thu, Jul 25, 2013 at 04:23:40PM +0200, Sedat Dilek wrote: >>> On Thu, Jul 25, 2013 at 3:36 PM, Daniel Vetter wrote: >>> > On Thu, Jul 25, 2013 at 12:37:44PM +0200, Sedat Dilek wrote:

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Daniel Vetter
On Thu, Jul 25, 2013 at 04:23:40PM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 3:36 PM, Daniel Vetter wrote: > > On Thu, Jul 25, 2013 at 12:37:44PM +0200, Sedat Dilek wrote: > >> On Thu, Jul 25, 2013 at 12:21 PM, Jani Nikula > >> wrote: > >> > On Thu, 25 Jul 2013, Sedat Dilek wrote: > >>

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Daniel Vetter
On Thu, Jul 25, 2013 at 12:37:44PM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 12:21 PM, Jani Nikula > wrote: > > On Thu, 25 Jul 2013, Sedat Dilek wrote: > >> On Thu, Jul 25, 2013 at 12:02 PM, Sedat Dilek > >> wrote: > >>> On Thu, Jul 25, 2013 at 11:44 AM, Jani Nikula > >>> wrote: > >>

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

2013-07-25 Thread Jani Nikula
On Thu, 25 Jul 2013, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 12:02 PM, Sedat Dilek wrote: >> On Thu, Jul 25, 2013 at 11:44 AM, Jani Nikula >> wrote: >>> On Thu, 25 Jul 2013, Sedat Dilek wrote: On Thu, Jul 25, 2013 at 7:12 AM, Stephen Rothwell wrote: > Hi all, > > Ch