New kernel error after syncing

New kernel error after syncing

[akuster808]

Hello,

Is anyone else seeing kernel build issue on 3.14 with the resent updates?


I am getting the following errors on ppc64 (standard/qemuppc). x86-64 
built fine (core-image-minimal). building ppc now.

|   LD      init/built-in.o
| mm/built-in.o: In function `.vm_cgroup_css_alloc':
| vm_cgroup.c:(.text+0x7103c): undefined reference to `.res_counter_init'
| vm_cgroup.c:(.text+0x71090): undefined reference to `.res_counter_init'
| mm/built-in.o: In function `.vm_cgroup_read_u64':
| vm_cgroup.c:(.text+0x711c4): undefined reference to 
`.res_counter_read_u64'
| mm/built-in.o: In function `.vm_cgroup_charge_memory_mm':
| (.text+0x71348): undefined reference to `.res_counter_charge'
| mm/built-in.o: In function `.vm_cgroup_uncharge_memory_mm':
| (.text+0x713a0): undefined reference to `.res_counter_uncharge'
| mm/built-in.o: In function `.vm_cgroup_charge_shmem':
| (.text+0x71508): undefined reference to `.res_counter_charge'
| mm/built-in.o: In function `.vm_cgroup_uncharge_shmem':
| (.text+0x71560): undefined reference to `.res_counter_uncharge'
| make[2]: *** [vmlinux] Error 1
| make[1]: *** [sub-make] Error 2
| make: *** [all] Error 2

- armin

Re: New kernel error after syncing

[Khem Raj]

On Sun, Aug 24, 2014 at 4:02 PM, akuster808 <akuster808@gmail.com> wrote:
>
> Hello,
>
> Is anyone else seeing kernel build issue on 3.14 with the resent updates?
>
>
> I am getting the following errors on ppc64 (standard/qemuppc). x86-64 built
> fine (core-image-minimal). building ppc now.
>
> |   LD      init/built-in.o
> | mm/built-in.o: In function `.vm_cgroup_css_alloc':
> | vm_cgroup.c:(.text+0x7103c): undefined reference to `.res_counter_init'
> | vm_cgroup.c:(.text+0x71090): undefined reference to `.res_counter_init'
> | mm/built-in.o: In function `.vm_cgroup_read_u64':
> | vm_cgroup.c:(.text+0x711c4): undefined reference to
> `.res_counter_read_u64'
> | mm/built-in.o: In function `.vm_cgroup_charge_memory_mm':
> | (.text+0x71348): undefined reference to `.res_counter_charge'
> | mm/built-in.o: In function `.vm_cgroup_uncharge_memory_mm':
> | (.text+0x713a0): undefined reference to `.res_counter_uncharge'
> | mm/built-in.o: In function `.vm_cgroup_charge_shmem':
> | (.text+0x71508): undefined reference to `.res_counter_charge'
> | mm/built-in.o: In function `.vm_cgroup_uncharge_shmem':
> | (.text+0x71560): undefined reference to `.res_counter_uncharge'
> | make[2]: *** [vmlinux] Error 1
> | make[1]: *** [sub-make] Error 2
> | make: *** [all] Error 2

Do you have CONFIG_CGROUP_VM turned off ?

>
> - armin
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: New kernel error after syncing

[Khem Raj]

On Sun, Aug 24, 2014 at 4:22 PM, Khem Raj <raj.khem@gmail.com> wrote:
> On Sun, Aug 24, 2014 at 4:02 PM, akuster808 <akuster808@gmail.com> wrote:
>>
>> Hello,
>>
>> Is anyone else seeing kernel build issue on 3.14 with the resent updates?
>>
>>
>> I am getting the following errors on ppc64 (standard/qemuppc). x86-64 built
>> fine (core-image-minimal). building ppc now.
>>
>> |   LD      init/built-in.o
>> | mm/built-in.o: In function `.vm_cgroup_css_alloc':
>> | vm_cgroup.c:(.text+0x7103c): undefined reference to `.res_counter_init'
>> | vm_cgroup.c:(.text+0x71090): undefined reference to `.res_counter_init'
>> | mm/built-in.o: In function `.vm_cgroup_read_u64':
>> | vm_cgroup.c:(.text+0x711c4): undefined reference to
>> `.res_counter_read_u64'
>> | mm/built-in.o: In function `.vm_cgroup_charge_memory_mm':
>> | (.text+0x71348): undefined reference to `.res_counter_charge'
>> | mm/built-in.o: In function `.vm_cgroup_uncharge_memory_mm':
>> | (.text+0x713a0): undefined reference to `.res_counter_uncharge'
>> | mm/built-in.o: In function `.vm_cgroup_charge_shmem':
>> | (.text+0x71508): undefined reference to `.res_counter_charge'
>> | mm/built-in.o: In function `.vm_cgroup_uncharge_shmem':
>> | (.text+0x71560): undefined reference to `.res_counter_uncharge'
>> | make[2]: *** [vmlinux] Error 1
>> | make[1]: *** [sub-make] Error 2
>> | make: *** [all] Error 2
>
> Do you have CONFIG_CGROUP_VM turned off ?

if this is on make sure CONFIG_RESOURCE_COUNTERS is enbled too.
>
>>
>> - armin
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto

Re: New kernel error after syncing

[Bruce Ashfield]

On Sun, Aug 24, 2014 at 7:02 PM, akuster808 <akuster808@gmail.com> wrote:
>
> Hello,
>
> Is anyone else seeing kernel build issue on 3.14 with the resent updates?
>
>
> I am getting the following errors on ppc64 (standard/qemuppc). x86-64 built
> fine (core-image-minimal). building ppc now.

Hopefully qemuppc is building 32 bit :) .. but outside of that, I was
able to build 3.14
fine on Friday.  But I just started another build to see if something
snuck past in the
recent feature merges.

Bruce

>
> |   LD      init/built-in.o
> | mm/built-in.o: In function `.vm_cgroup_css_alloc':
> | vm_cgroup.c:(.text+0x7103c): undefined reference to `.res_counter_init'
> | vm_cgroup.c:(.text+0x71090): undefined reference to `.res_counter_init'
> | mm/built-in.o: In function `.vm_cgroup_read_u64':
> | vm_cgroup.c:(.text+0x711c4): undefined reference to
> `.res_counter_read_u64'
> | mm/built-in.o: In function `.vm_cgroup_charge_memory_mm':
> | (.text+0x71348): undefined reference to `.res_counter_charge'
> | mm/built-in.o: In function `.vm_cgroup_uncharge_memory_mm':
> | (.text+0x713a0): undefined reference to `.res_counter_uncharge'
> | mm/built-in.o: In function `.vm_cgroup_charge_shmem':
> | (.text+0x71508): undefined reference to `.res_counter_charge'
> | mm/built-in.o: In function `.vm_cgroup_uncharge_shmem':
> | (.text+0x71560): undefined reference to `.res_counter_uncharge'
> | make[2]: *** [vmlinux] Error 1
> | make[1]: *** [sub-make] Error 2
> | make: *** [all] Error 2
>
> - armin
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: New kernel error after syncing

[akuster808]

Khem

it was the config option not being set..

seems like a kernel bug to me.. kconfig or otherwise.

thanks for the help.
- Armin

On 08/24/2014 05:14 PM, Bruce Ashfield wrote:
> On Sun, Aug 24, 2014 at 7:02 PM, akuster808 <akuster808@gmail.com> wrote:
>>
>> Hello,
>>
>> Is anyone else seeing kernel build issue on 3.14 with the resent updates?
>>
>>
>> I am getting the following errors on ppc64 (standard/qemuppc). x86-64 built
>> fine (core-image-minimal). building ppc now.
>
> Hopefully qemuppc is building 32 bit :) .. but outside of that, I was
> able to build 3.14
> fine on Friday.  But I just started another build to see if something
> snuck past in the
> recent feature merges.
>
> Bruce
>
>>
>> |   LD      init/built-in.o
>> | mm/built-in.o: In function `.vm_cgroup_css_alloc':
>> | vm_cgroup.c:(.text+0x7103c): undefined reference to `.res_counter_init'
>> | vm_cgroup.c:(.text+0x71090): undefined reference to `.res_counter_init'
>> | mm/built-in.o: In function `.vm_cgroup_read_u64':
>> | vm_cgroup.c:(.text+0x711c4): undefined reference to
>> `.res_counter_read_u64'
>> | mm/built-in.o: In function `.vm_cgroup_charge_memory_mm':
>> | (.text+0x71348): undefined reference to `.res_counter_charge'
>> | mm/built-in.o: In function `.vm_cgroup_uncharge_memory_mm':
>> | (.text+0x713a0): undefined reference to `.res_counter_uncharge'
>> | mm/built-in.o: In function `.vm_cgroup_charge_shmem':
>> | (.text+0x71508): undefined reference to `.res_counter_charge'
>> | mm/built-in.o: In function `.vm_cgroup_uncharge_shmem':
>> | (.text+0x71560): undefined reference to `.res_counter_uncharge'
>> | make[2]: *** [vmlinux] Error 1
>> | make[1]: *** [sub-make] Error 2
>> | make: *** [all] Error 2
>>
>> - armin
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>

Re: New kernel error after syncing

[Khem Raj]

On 14-08-25 15:56:57, akuster808 wrote:
> Khem
> 
> it was the config option not being set..
> 
> seems like a kernel bug to me.. kconfig or otherwise.

OK, I was thinking may be it would help if we should somehow review the 
linux-yocto kernel patches may be on this mailing list too may be just a FYI
pointing to a git.yp.org showing the commits that went between the SRCREV 
bumps in metadata, Bruce does a great job of explaining what has changed 
but hey show me the code :). But if they already are then ignore me.

-Khem

Re: New kernel error after syncing

[Bruce Ashfield]

On Mon, Aug 25, 2014 at 7:30 PM, Khem Raj <raj.khem@gmail.com> wrote:
> On 14-08-25 15:56:57, akuster808 wrote:
>> Khem
>>
>> it was the config option not being set..
>>
>> seems like a kernel bug to me.. kconfig or otherwise.
>
> OK, I was thinking may be it would help if we should somehow review the
> linux-yocto kernel patches may be on this mailing list too may be just a FYI
> pointing to a git.yp.org showing the commits that went between the SRCREV
> bumps in metadata, Bruce does a great job of explaining what has changed
> but hey show me the code :). But if they already are then ignore me.

No worries .. the suggestion is a good one. We have the patches posted on the
dedicated linux-yocto mailing list, so if anyone is interested in seeing them as
they scroll by, that's the place to be.

Also, if we've got a Kconfig or other default that doesn't make sense
to everyone,
let me know, and we'll get it fixed up.

Cheers,

Bruce

>
> -Khem



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"