All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce-QgLWrMLu8clzjhtm8Ag3mw@public.gmane.org>
To: Paul Bolle <pebolle-IWqWACnzNjzz+pZb47iToQ@public.gmane.org>
Cc: Mark Hounschell <markh-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>,
	nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: 3.19.0-rc1 nouvea build failure on GeForce GT 610 only
Date: Mon, 22 Dec 2014 15:48:54 +0000	[thread overview]
Message-ID: <54983D66.6020506@blueyonder.co.uk> (raw)
In-Reply-To: <1419256493.30945.53.camel@x220>

On 22/12/14 13:54, Paul Bolle wrote:
> On Mon, 2014-12-22 at 14:37 +0100, Paul Bolle wrote:
>> On Mon, 2014-12-22 at 13:01 +0000, Sid Boyce wrote:
>>>     CHK     kernel/config_data.h
>>>     CC [M]  drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o
>>> drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c: In function
>>> ‘nvd0_dmaobj_bind’:
>>> drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c:54:8: error:
>>> ‘GM204_DISP_CORE_CHANNEL_DMA’ undeclared (first use in this function)
>>>      case GM204_DISP_CORE_CHANNEL_DMA:
>>>           ^
>>> drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c:54:8: note: each
>>> undeclared identifier is reported only once for each function it appears in
>>> scripts/Makefile.build:257: recipe for target
>>> 'drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o' failed
>>> make[4]: *** [drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o] Error 1
>>> scripts/Makefile.build:402: recipe for target 'drivers/gpu/drm/nouveau'
>>> failed
>>> make[3]: *** [drivers/gpu/drm/nouveau] Error 2
>>> scripts/Makefile.build:402: recipe for target 'drivers/gpu/drm' failed
>>> make[2]: *** [drivers/gpu/drm] Error 2
>>> scripts/Makefile.build:402: recipe for target 'drivers/gpu' failed
>>> make[1]: *** [drivers/gpu] Error 2
>>> Makefile:938: recipe for target 'drivers' failed
>>> make: *** [drivers] Error 2
>>>
>>> 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT
>>> 610] (rev a1)
>> Why would that controller influence the build?
>>
>>> No problems on 2 other boxes with GeForce 8600 GT] (rev a1)
>> I ran into this error twice, while building Fedora 21 kernel rpms for
>> v3.19-rc1 on my outdated ThinkPad X41 (which uses i915, for what it's
>> worth). The error made very little sense to me. Especially since it
>> didn't happen when building in the local git repository.
>>
>> So I basically, well, scrubbed the rpmbuild environment. And then the
>> the third attempt to build kernels rpm succeeded! I assumed a hardware
>> failure (see outdated above) and made a mental note to investigate that
>> one of these days.
>>
>> But your report makes me think it's not my hardware. Could there be some
>> _random_ failure with this driver in the build? Very odd...
> A theory based on Mark's message in
> https://lkml.org/lkml/2014/12/8/602 :
>
> My two failed builds somehow used previous version of class.h, that
> didn't yet have commit 1f89b4756fb8 ("drm/gm204/disp: initial support")
> applied. It's that commit which added the define for
> GM204_DISP_CORE_CHANNEL_DMA.
>
> Is that even possible? Perhaps rpmbuild has a surprising way to handle
> symlinks? All very puzzling...
>
>
> Paul Bolle
>
>
I did a git pull up to 3.19-rc1 separately on the 3 boxes and used the 
.config from 3.18.0 as the base of make oldconfig.

When the build failed I did "make mrproper" and used the .config from 
one of the other boxes, then from the other, all 3 .config gave the same 
error.

Successfully rebooted one of the boxes.
sabre:~ # uname -r
3.19.0-rc1-smp+

Regards ... Sid.
-- 
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus 
IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff 
Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for 
all Computing Tasks
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

WARNING: multiple messages have this Message-ID (diff)
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Mark Hounschell <markh@compro.net>,
	linux-kernel@vger.kernel.org, nouveau@lists.freedesktop.org
Subject: Re: 3.19.0-rc1 nouvea build failure on GeForce GT 610 only
Date: Mon, 22 Dec 2014 15:48:54 +0000	[thread overview]
Message-ID: <54983D66.6020506@blueyonder.co.uk> (raw)
In-Reply-To: <1419256493.30945.53.camel@x220>

On 22/12/14 13:54, Paul Bolle wrote:
> On Mon, 2014-12-22 at 14:37 +0100, Paul Bolle wrote:
>> On Mon, 2014-12-22 at 13:01 +0000, Sid Boyce wrote:
>>>     CHK     kernel/config_data.h
>>>     CC [M]  drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o
>>> drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c: In function
>>> ‘nvd0_dmaobj_bind’:
>>> drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c:54:8: error:
>>> ‘GM204_DISP_CORE_CHANNEL_DMA’ undeclared (first use in this function)
>>>      case GM204_DISP_CORE_CHANNEL_DMA:
>>>           ^
>>> drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c:54:8: note: each
>>> undeclared identifier is reported only once for each function it appears in
>>> scripts/Makefile.build:257: recipe for target
>>> 'drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o' failed
>>> make[4]: *** [drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o] Error 1
>>> scripts/Makefile.build:402: recipe for target 'drivers/gpu/drm/nouveau'
>>> failed
>>> make[3]: *** [drivers/gpu/drm/nouveau] Error 2
>>> scripts/Makefile.build:402: recipe for target 'drivers/gpu/drm' failed
>>> make[2]: *** [drivers/gpu/drm] Error 2
>>> scripts/Makefile.build:402: recipe for target 'drivers/gpu' failed
>>> make[1]: *** [drivers/gpu] Error 2
>>> Makefile:938: recipe for target 'drivers' failed
>>> make: *** [drivers] Error 2
>>>
>>> 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT
>>> 610] (rev a1)
>> Why would that controller influence the build?
>>
>>> No problems on 2 other boxes with GeForce 8600 GT] (rev a1)
>> I ran into this error twice, while building Fedora 21 kernel rpms for
>> v3.19-rc1 on my outdated ThinkPad X41 (which uses i915, for what it's
>> worth). The error made very little sense to me. Especially since it
>> didn't happen when building in the local git repository.
>>
>> So I basically, well, scrubbed the rpmbuild environment. And then the
>> the third attempt to build kernels rpm succeeded! I assumed a hardware
>> failure (see outdated above) and made a mental note to investigate that
>> one of these days.
>>
>> But your report makes me think it's not my hardware. Could there be some
>> _random_ failure with this driver in the build? Very odd...
> A theory based on Mark's message in
> https://lkml.org/lkml/2014/12/8/602 :
>
> My two failed builds somehow used previous version of class.h, that
> didn't yet have commit 1f89b4756fb8 ("drm/gm204/disp: initial support")
> applied. It's that commit which added the define for
> GM204_DISP_CORE_CHANNEL_DMA.
>
> Is that even possible? Perhaps rpmbuild has a surprising way to handle
> symlinks? All very puzzling...
>
>
> Paul Bolle
>
>
I did a git pull up to 3.19-rc1 separately on the 3 boxes and used the 
.config from 3.18.0 as the base of make oldconfig.

When the build failed I did "make mrproper" and used the .config from 
one of the other boxes, then from the other, all 3 .config gave the same 
error.

Successfully rebooted one of the boxes.
sabre:~ # uname -r
3.19.0-rc1-smp+

Regards ... Sid.
-- 
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus 
IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff 
Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for 
all Computing Tasks

  reply	other threads:[~2014-12-22 15:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22 13:01 3.19.0-rc1 nouvea build failure on GeForce GT 610 only Sid Boyce
2014-12-22 13:01 ` Sid Boyce
2014-12-22 13:37 ` Paul Bolle
2014-12-22 13:54   ` Paul Bolle
2014-12-22 15:48     ` Sid Boyce [this message]
2014-12-22 15:48       ` Sid Boyce

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=54983D66.6020506@blueyonder.co.uk \
    --to=sboyce-qglwrmlu8clzjhtm8ag3mw@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=markh-n2QNKt385d+sTnJN9+BGXg@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=pebolle-IWqWACnzNjzz+pZb47iToQ@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.