[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2014-08-15 Thread Matthias Klose
won't fix in gcc-4.8. Please recheck with GCC 4.9

** Changed in: gcc-4.8 (Ubuntu)
   Status: Confirmed = Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2014-05-03 Thread Christian Prochaska
It seems the same problem also applies to the 3.4.0-5 kernel in the
Ubuntu repository. The kernel image in the 13.04 release
(https://launchpad.net/ubuntu/+source/linux-
chromebook/3.4.0-5/+build/4314955) works for me, but the one in the
13.10 and 14.04 releases (https://launchpad.net/ubuntu/+source/linux-
chromebook/3.4.0-5.1/+build/4575433) does not. According to the build
log, the newer image was built with gcc 4.8.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-10-11 Thread Alberto Salvia Novella
** Changed in: gcc-4.8 (Ubuntu)
   Importance: Undecided = High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-05-14 Thread Marcin Juszkiewicz
I will take a look at it after 22nd May as my Chromebook goes back to
shop to get speakers fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-05-13 Thread Marcin Juszkiewicz
It is for #6 one.

Will try non-smp

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-05-13 Thread Marcin Juszkiewicz
no-smp boot failed

** Attachment added: dmesg-nosmp
   
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+attachment/3675099/+files/dmesg-nosmp

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-05-13 Thread Marcin Juszkiewicz
nosmp copy:

2fa8 kmem_cache_alloc_trace:
2fa8:   e1a0c00dmov ip, sp
2fac:   e92ddbf0push{r4, r5, r6, r7, r8, r9, fp, ip, lr, pc}
2fb0:   e24cb004sub fp, ip, #4
2fb4:   e24dd008sub sp, sp, #8
2fb8:   e52de004push{lr}; (str lr, [sp, #-4]!)
2fbc:   ebfebl  0 __gnu_mcount_nc
2fc0:   e59f3128ldr r3, [pc, #296]  ; 30f0 
kmem_cache_alloc_trace+0x148
2fc4:   e1a0700emov r7, lr
2fc8:   e1a05000mov r5, r0
2fcc:   e1a06001mov r6, r1
2fd0:   e1a08002mov r8, r2
2fd4:   e5933000ldr r3, [r3]
2fd8:   e2033010and r3, r3, #16
2fdc:   e1130001tst r3, r1
2fe0:   0a00beq 2fe8 kmem_cache_alloc_trace+0x40
2fe4:   ebfebl  0 _cond_resched
2fe8:   e5953000ldr r3, [r5]
2fec:   e593c004ldr ip, [r3, #4]
2ff0:   e5934000ldr r4, [r3]
2ff4:   e354cmp r4, #0
2ff8:   1a05bne 3014 kmem_cache_alloc_trace+0x6c
2ffc:   e1a5mov r0, r5
3000:   e1a01006mov r1, r6
3004:   e1a02007mov r2, r7
3008:   ebfebl  2f4 ksize+0xc0
300c:   e1a04000mov r4, r0
3010:   ea16b   3070 kmem_cache_alloc_trace+0xc8
3014:   e5953014ldr r3, [r5, #20]
3018:   e7942003ldr r2, [r4, r3]
301c:   e10fmrs r0, CPSR
3020:   f10c0080cpsid   i
3024:   e5953000ldr r3, [r5]
3028:   e5931000ldr r1, [r3]
302c:   e1510004cmp r1, r4
3030:   1a08bne 3058 kmem_cache_alloc_trace+0xb0
3034:   e5931004ldr r1, [r3, #4]
3038:   e151000ccmp r1, ip
303c:   1a05bne 3058 kmem_cache_alloc_trace+0xb0
3040:   e5832000str r2, [r3]
3044:   e2811001add r1, r1, #1
3048:   e5953000ldr r3, [r5]
304c:   e5831004str r1, [r3, #4]
3050:   e3a03001mov r3, #1
3054:   ea00b   305c kmem_cache_alloc_trace+0xb4
3058:   e3a03000mov r3, #0
305c:   e121f000msr CPSR_c, r0
3060:   e353cmp r3, #0
3064:   0adfbeq 2fe8 kmem_cache_alloc_trace+0x40
3068:   e5953014ldr r3, [r5, #20]
306c:   f7d2f003pld [r2, r3]
3070:   e3160902tst r6, #32768  ; 0x8000
3074:   0a06beq 3094 kmem_cache_alloc_trace+0xec
3078:   e354cmp r4, #0
307c:   0a04beq 3094 kmem_cache_alloc_trace+0xec
3080:   e5951010ldr r1, [r5, #16]
3084:   e351cmp r1, #0
3088:   0a01beq 3094 kmem_cache_alloc_trace+0xec
308c:   e1a4mov r0, r4
3090:   ebfebl  0 __memzero
3094:   e59f3058ldr r3, [pc, #88]   ; 30f4 
kmem_cache_alloc_trace+0x14c
3098:   e595900cldr r9, [r5, #12]
309c:   e5932004ldr r2, [r3, #4]
30a0:   e352cmp r2, #0
30a4:   0a0ebeq 30e4 kmem_cache_alloc_trace+0x13c
30a8:   e5935010ldr r5, [r3, #16]
30ac:   e355cmp r5, #0
30b0:   0a0bbeq 30e4 kmem_cache_alloc_trace+0x13c
30b4:   e2855008add r5, r5, #8
30b8:   e58d9000str r9, [sp]
30bc:   e1a03008mov r3, r8
30c0:   e58d6004str r6, [sp, #4]
30c4:   e1a01007mov r1, r7
30c8:   e515c008ldr ip, [r5, #-8]
30cc:   e1a02004mov r2, r4
30d0:   e5150004ldr r0, [r5, #-4]
30d4:   e12fff3cblx ip
30d8:   e4953008ldr r3, [r5], #8
30dc:   e353cmp r3, #0
30e0:   1af4bne 30b8 kmem_cache_alloc_trace+0x110
30e4:   e24bd024sub sp, fp, #36 ; 0x24
30e8:   e1a4mov r0, r4
30ec:   e89dabf0ldm sp, {r4, r5, r6, r7, r8, r9, fp, sp, pc}
...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 

[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-05-13 Thread David Hacker
I am pretty sure this is a GCC 4.8 issue I have almost identical log when 
compiling an msm-8960 kernel with GCC-4.8
[ 0.350923,0] Unable to handle kernel NULL pointer dereference at virtual 
address 0001
[ 0.351014,0] pgd = c0004000
[ 0.351136,0] [0001] *pgd=
[ 0.351258,0] Internal error: Oops: 5 [#1] PREEMPT SMP
[ 0.351350,0] Modules linked in:
[ 0.351533,0] CPU: 0 Not tainted (3.0.31-ge95971c #1)
[ 0.351594,0] PC is at kmem_cache_alloc_trace+0xa4/0x1a0
[ 0.351747,0] LR is at con_insert_unipair+0xa0/0xec
[ 0.351808,0] pc : [] lr : [] psr: 6093
[ 0.351808,0] sp : c8c45ef8 ip : c0c29d38 fp : 
[ 0.352021,0] r10: 2cf8 r9 : 0080 r8 : c0410a18
[ 0.352083,0] r7 : c8c44038 r6 : 00d0 r5 : c8c00200 r4 : 0001
[ 0.352205,0] r3 : c8c44000 r2 : 2013 r1 : 028ac000 r0 : c0053540
[ 0.352327,0] Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment kernel
[ 0.352418,0] Control: 10c5787d Table: 8020406a DAC: 0015

Kernel compiles and boots fine with GCC 4.7.
https://github.com/razrqcom-dev-team/android_kernel_motorola_msm8960-common/tree/cm-10.1-gcc47

I know this is off topic but hopefully it helps get to the bottom of the
root issue with GCC 4.8 and arm cross-compile

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-05-13 Thread Mans Rullgard
Looks like a SLUB freelist is being corrupted at some point prior to the
crash. Perhaps turning on CONFIG_SLUB_DEBUG (or some other memory
debugging option) will catch the fault sooner.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-05-12 Thread Mans Rullgard
Not exactly the same, the fault address is different.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-05-12 Thread Mans Rullgard
Could you post a disassembly of kmem_cache_alloc_trace?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-05-12 Thread Marcin Juszkiewicz
3404 kmem_cache_alloc_trace:
3404:   e1a0c00dmov ip, sp
3408:   e92ddff0push{r4, r5, r6, r7, r8, r9, sl, fp, ip, 
lr, pc}
340c:   e24cb004sub fp, ip, #4
3410:   e24dd00csub sp, sp, #12
3414:   e52de004push{lr}; (str lr, [sp, #-4]!)
3418:   ebfebl  0 __gnu_mcount_nc
341c:   e59f3140ldr r3, [pc, #320]  ; 3564 
kmem_cache_alloc_trace+0x160
3420:   e1a0700emov r7, lr
3424:   e1a04000mov r4, r0
3428:   e1a06001mov r6, r1
342c:   e1a08002mov r8, r2
3430:   e5933000ldr r3, [r3]
3434:   e2033010and r3, r3, #16
3438:   e1130001tst r3, r1
343c:   0a00beq 3444 kmem_cache_alloc_trace+0x40
3440:   ebfebl  0 _cond_resched
3444:   ee1d1f90mrc 15, 0, r1, cr13, cr0, {4}
3448:   e5942000ldr r2, [r4]
344c:   e0813002add r3, r1, r2
3450:   e593a004ldr sl, [r3, #4]
3454:   e7915002ldr r5, [r1, r2]
3458:   e355cmp r5, #0
345c:   1a05bne 3478 kmem_cache_alloc_trace+0x74
3460:   e1a4mov r0, r4
3464:   e1a01006mov r1, r6
3468:   e1a02007mov r2, r7
346c:   ebfebl  838 calculate_sizes+0x328
3470:   e1a05000mov r5, r0
3474:   ea1ab   34e4 kmem_cache_alloc_trace+0xe0
3478:   e5943014ldr r3, [r4, #20]
347c:   e7952003ldr r2, [r5, r3]
3480:   e10f9000mrs r9, CPSR
3484:   f10c0080cpsid   i
3488:   e5943000ldr r3, [r4]
348c:   ee1d0f90mrc 15, 0, r0, cr13, cr0, {4}
3490:   e7903003ldr r3, [r0, r3]
3494:   e1530005cmp r3, r5
3498:   0a01beq 34a4 kmem_cache_alloc_trace+0xa0
349c:   e3a03000mov r3, #0
34a0:   ea0ab   34d0 kmem_cache_alloc_trace+0xcc
34a4:   e5943000ldr r3, [r4]
34a8:   e283c004add ip, r3, #4
34ac:   e790c00cldr ip, [r0, ip]
34b0:   e15c000acmp ip, sl
34b4:   1af8bne 349c kmem_cache_alloc_trace+0x98
34b8:   e7802003str r2, [r0, r3]
34bc:   e28cc001add ip, ip, #1
34c0:   e5943000ldr r3, [r4]
34c4:   e2833004add r3, r3, #4
34c8:   e780c003str ip, [r0, r3]
34cc:   e3a03001mov r3, #1
34d0:   e121f009msr CPSR_c, r9
34d4:   e353cmp r3, #0
34d8:   0adabeq 3448 kmem_cache_alloc_trace+0x44
34dc:   e5943014ldr r3, [r4, #20]
34e0:   f7d2f003pld [r2, r3]
34e4:   e3160902tst r6, #32768  ; 0x8000
34e8:   0a06beq 3508 kmem_cache_alloc_trace+0x104
34ec:   e355cmp r5, #0
34f0:   0a04beq 3508 kmem_cache_alloc_trace+0x104
34f4:   e5941010ldr r1, [r4, #16]
34f8:   e351cmp r1, #0
34fc:   0a01beq 3508 kmem_cache_alloc_trace+0x104
3500:   e1a5mov r0, r5
3504:   ebfebl  0 __memzero
3508:   e59f3058ldr r3, [pc, #88]   ; 3568 
kmem_cache_alloc_trace+0x164
350c:   e594900cldr r9, [r4, #12]
3510:   e5932004ldr r2, [r3, #4]
3514:   e352cmp r2, #0
3518:   0a0ebeq 3558 kmem_cache_alloc_trace+0x154
351c:   e5934010ldr r4, [r3, #16]
3520:   e354cmp r4, #0
3524:   0a0bbeq 3558 kmem_cache_alloc_trace+0x154
3528:   e2844008add r4, r4, #8
352c:   e58d9000str r9, [sp]
3530:   e1a03008mov r3, r8
3534:   e58d6004str r6, [sp, #4]
3538:   e1a01007mov r1, r7
353c:   e514c008ldr ip, [r4, #-8]
3540:   e1a02005mov r2, r5
3544:   e5140004ldr r0, [r4, #-4]
3548:   e12fff3cblx ip
354c:   e4943008ldr r3, [r4], #8
3550:   e353cmp r3, #0
3554:   1af4bne 352c kmem_cache_alloc_trace+0x128
3558:   e24bd028sub sp, fp, #40 ; 0x28
355c:   e1a5mov r0, r5
3560:   e89daff0ldm sp, {r4, r5, r6, r7, r8, r9, sl, fp, 
sp, pc}
...


[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-05-12 Thread Mans Rullgard
Which log does that match?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-05-12 Thread Mans Rullgard
Could you try a non-smp build?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-05-11 Thread Mans Rullgard
How far into the boot process does the bad build fail? Do you get any
output at all on the serial console (with earlyprintk)?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-05-11 Thread Marcin Juszkiewicz
It does not display anything on screen. But combination of Power+Refresh
(F3) keys == hard reset and then mount pstore somewhere and it should
have console log of failed kernel.

Attached is log from failed build (done with older gcc-4.8).

** Attachment added: failed-dmesg
   
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+attachment/3674120/+files/failed-dmesg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-05-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gcc-4.8 (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-05-11 Thread Marcin Juszkiewicz
Used 4.8.0 from OpenEmbedded - failed same way:

[0.153366] Switching to clocksource mct-frc
[0.168712] AppArmor: AppArmor Filesystem Enabled
[0.173472] Unable to handle kernel NULL pointer dereference at virtual 
address 0001
[0.173491] pgd = 80004000
[0.173500] [0001] *pgd=
[0.173515] Internal error: Oops: 5 [#1] SMP ARM
[0.173525] Modules linked in:
[0.173539] CPU: 0Not tainted  (3.8.0 #1)
[0.173554] PC is at kmem_cache_alloc_trace+0x78/0x168
[0.173566] LR is at kmem_cache_alloc_trace+0x40/0x168
[0.173577] pc : [800f43d4]lr : [800f439c]psr: 2113
[0.173577] sp : ef0bfe00  ip : ef0bfe00  fp : ef0bfe34
[0.173591] r10: 13b7  r9 :   r8 : 0080
[0.173601] r7 : 802a614c  r6 : 00d0  r5 : 0001  r4 : ef001200
[0.173611] r3 :   r2 : 80795640  r1 : 0112b000  r0 : 
[0.173622] Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment 
kernel
[0.173635] Control: 10c5387d  Table: 4000406a  DAC: 0015
[0.173645] Process swapper/0 (pid: 1, stack limit = 0xef0be240)
[0.173655] Stack: (0xef0bfe00 to 0xef0c)
[0.173667] fe00: 8052df44 80261980 0110 2665 ef2df9c0 0003 
ef33a664 807e29d2
[0.173681] fe20:  807e29d4 ef0bfe54 ef0bfe38 802a614c 800f4368 
ef008400 ef2df9c0
[0.173695] fe40: 0003 0001 ef0bfe94 ef0bfe58 802a6ec8 802a60a8 
0001 0003
[0.173708] fe60: 0001 ef008654 80030328  0014 80891614 
80766b3c 80808ac0
[0.173722] fe80:  ef0be020 ef0bfeb4 ef0bfe98 80766330 802a6df0 
0001 
[0.173735] fea0: 808914f0 8055b1ec ef0bfed4 ef0bfeb8 80766800 807662f8 
80662b8b ef0bfec8
[0.173749] fec0: 80891048  ef0bfef4 ef0bfed8 80765e08 807666a8 
80664023 ef0bfefc
[0.173762] fee0: 000e 80892200 ef0bff1c ef0bfef8 80766bf4 80765d0c 
8066309b ef0bff08
[0.173776] ff00: 80762db0 0005 80773f48 8078efd0 ef0bff5c ef0bff20 
80008758 80766b48
[0.173789] ff20: 0005 0005 00ae 806cd10c 8004ea48 0005 
80773f48 8078efd0
[0.173803] ff40: 80808ac0 80808ac0 00ae  ef0bff94 ef0bff60 
8074ba78 800086c4
[0.173816] ff60: 0005 0005 8074b2c0 8052df58 80808ac0 80522608 
 
[0.173830] ff80:   ef0bffac ef0bff98 80522624 8074b974 
 
[0.173843] ffa0:  ef0bffb0 8000e118 80522614   
 
[0.173856] ffc0:       
 
[0.173869] ffe0:     0013  
 
[0.173895] [800f43d4] (kmem_cache_alloc_trace+0x78/0x168) from 
[802a614c] (con_insert_unipair+0xb0/0xfc)
[0.173916] [802a614c] (con_insert_unipair+0xb0/0xfc) from [802a6ec8] 
(con_set_default_unimap+0xe4/0x174)
[0.173936] [802a6ec8] (con_set_default_unimap+0xe4/0x174) from 
[80766330] (console_map_init+0x44/0x58)
[0.173953] [80766330] (console_map_init+0x44/0x58) from [80766800] 
(vty_init+0x164/0x1a8)
[0.173969] [80766800] (vty_init+0x164/0x1a8) from [80765e08] 
(tty_init+0x108/0x144)
[0.173984] [80765e08] (tty_init+0x108/0x144) from [80766bf4] 
(chr_dev_init+0xb8/0xdc)
[0.174000] [80766bf4] (chr_dev_init+0xb8/0xdc) from [80008758] 
(do_one_initcall+0xa0/0x164)
[0.174020] [80008758] (do_one_initcall+0xa0/0x164) from [8074ba78] 
(kernel_init_freeable+0x110/0x1d0)
[0.174042] [8074ba78] (kernel_init_freeable+0x110/0x1d0) from 
[80522624] (kernel_init+0x1c/0xf4)
[0.174061] [80522624] (kernel_init+0x1c/0xf4) from [8000e118] 
(ret_from_fork+0x14/0x20)
[0.174076] Code: eb10d1fe e1a05000 ea1a e5943014 (e7952003) 
[0.174099] ---[ end trace 44cecb92193a0840 ]---
[0.174624] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
[0.174624] 
[0.174643] CPU1: stopping
[0.174665] [80015f44] (unwind_backtrace+0x0/0xec) from [80526bc0] 
(dump_stack+0x20/0x24)
[0.174684] [80526bc0] (dump_stack+0x20/0x24) from [8001402c] 
(handle_IPI+0xf0/0x148)
[0.174701] [8001402c] (handle_IPI+0xf0/0x148) from [80008610] 
(gic_handle_irq+0x68/0x70)
[0.174717] [80008610] (gic_handle_irq+0x68/0x70) from [8000dc80] 
(__irq_svc+0x40/0x50)
[0.174730] Exception stack(0xef0e3f68 to 0xef0e3fb0)
[0.174742] 3f60:   ffed  01134000  
ef0e2000 ef0e2000
[0.174756] 3f80: ef0e2000 80808e5c 4000406a 410fc0f4  ef0e3fbc 
ef0e3fc0 ef0e3fb0
[0.174769] 3fa0: 8000f330 8000f334 6113 
[0.174783] [8000dc80] (__irq_svc+0x40/0x50) from [8000f334] 
(default_idle+0x34/0x3c)
[0.174799] [8000f334] (default_idle+0x34/0x3c) from [8000f4cc] 
(cpu_idle+0xb8/0x104)
[0.174817] [8000f4cc] (cpu_idle+0xb8/0x104) from [80523ee4] 
(secondary_start_kernel+0xf4/0x10c)
[0.174834] [80523ee4] (secondary_start_kernel+0xf4/0x10c) from 
[40523488] (0x40523488)

-- 
You received this bug 

[Bug 1178847] Re: chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

2013-05-10 Thread Marcin Juszkiewicz
I did builds on Chromebook running armhf/saucy:

hrw@krolik:~$ gcc --version
gcc (Ubuntu/Linaro 4.8.0-6ubuntu1) 4.8.0
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


** Attachment removed: Dependencies.txt
   
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+attachment/3673053/+files/Dependencies.txt

** Tags removed: amd64 apport-bug
** Tags added: armhf

** Description changed:

  I wanted to check newer kernel for Samsung ARM Chromebook. So I grabbed
  http://git.chromium.org/chromiumos/third_party/kernel-next.git, updated
  config and started building.
  
  Everything built fine (with lot of warnings) but kernel failed to boot.
  So I tried to build it under 'raring' and it booted fine...
  
  OK, so maybe it is gcc fault I though. And did build with gcc-4.7
  instead. This time kernel built and booted fine:
  
  hrw@krolik:~$ uname -a;cat /proc/device-tree/model ;echo
  Linux krolik 3.8.0-saucy4.7 #9 SMP Fri May 10 22:48:02 CEST 2013 armv7l 
armv7l armv7l GNU/Linux
  Google Snow
  
  So I think that this is gcc-4.8 fault.
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 13.10
- Package: gcc-4.8 4.8.0-4ubuntu4
- ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
- Uname: Linux 3.8.0-17-generic x86_64
- ApportVersion: 2.10-0ubuntu1
- Architecture: amd64
- Date: Sat May 11 00:11:48 2013
- MarkForUpload: True
- ProcEnviron:
-  TERM=xterm
-  SHELL=/bin/bash
-  PATH=(custom, no user)
-  LANG=pl_PL.UTF-8
-  LANGUAGE=pl:en
- SourcePackage: gcc-4.8
- UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178847

Title:
  chromeos 3.8 kernel fails to boot when compiled with gcc-4.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs