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
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
** 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
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
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
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.
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:
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]
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.
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
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
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: e52de004
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:
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
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
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
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:
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]
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
19 matches
Mail list logo
