Kernel panicking with ALIP and NANO, 12.xx prebuilt images
I' getting this error during boot on a freshly dd'd image of alip or nano prebuilt images. [5.487091] generic-usb 0003:046D:C018.0003: input: USB HID v1.11 Mouse [Log0 [5.755706] udevd[733]: starting version 173 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. [7.124542] omap_device: omap_i2c.1: new worst case activate latency 0: 14406 Begin: Running /scripts/local-premount ... done. [8.234649] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. ) Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. *[ 14.322998] Kernel panic - not syncing: Attempted to kill init! * [ 14.336883] [<80010c9d>] (unwind_backtrace+0x1/0x90) from [<803e137d>] (pani) [ 14.353027] [<803e137d>] (panic+0x45/0x124) from [<80036fb1>] (forget_origin) [ 14.369812] [<80036fb1>] (forget_original_parent+0x65/0x14c) from [<800370a9) [ 14.387023] [<800370a9>] (exit_notify+0x11/0xe4) from [<80037573>] (do_exit+) [ 14.403015] [<80037573>] (do_exit+0x215/0x286) from [<8003774b>] (do_group_e) [ 14.419433] [<8003774b>] (do_group_exit+0x5f/0x80) from [<80041b8f>] (get_si) [ 14.436920] [<80041b8f>] (get_signal_to_deliver+0x27f/0x2bc) from [<8000e165) [ 14.454193] [<8000e165>] (do_signal+0x81/0x138) from [<8000e62d>] (do_notify) [ 14.470947] [<8000e62d>] (do_notify_resume+0x15/0x3c) from [<8000c059>] (wor) and struck here forever. Is this a mistake i'm doing or a bug..?? After trying to boot a number of times, finally succeeds. Not just this but also Seg faults like this during shutdown: umount: /run/lock: not mounted * Will now halt [ 9085.198303] Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa [ 9085.211364] Internal error: : 1028 [#1] PREEMPT SMP [ 9085.221252] Modules linked in: bluetooth mousedev snd_soc_overo libertas_sdic [ 9085.251281] CPU: 0Not tainted (3.1.1-21-linaro-omap #21~ci~201202260723) [ 9085.265747] PC is at musb_generic_disable+0x16/0x1e [ 9085.276214] LR is at musb_shutdown+0x33/0x6e [ 9085.286010] pc : [<802f238e>]lr : [<802f2639>]psr: 60b3 [ 9085.286010] sp : 8e083e58 ip : 0002ba34 fp : [ 9085.308715] r10: r9 : 8e082000 r8 : 8000c204 [ 9085.319458] r7 : 0003 r6 : 80c6aeec r5 : 4013 r4 : 8ed96128 [ 9085.331573] r3 : fa0ab000 r2 : r1 : 000c r0 : 8ed96128 [ 9085.343780] Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA Thumb Segment r [ 9085.356933] Control: 50c5387d Table: 8e330019 DAC: 0015 [ 9085.368377] Process halt (pid: 2541, stack limit = 0x8e0822f8) [ 9085.379913] Stack: (0x8e083e58 to 0x8e084000) [ 9085.389892] 3e40: 802f4 [ 9085.404022] 3e60: 8ed2c008 80282293 8028227f 80280499 806c2a7c cdef0123 2812b [ 9085.418090] 3e80: cdef0123 800431df 8e2c75c0 004ae036 8e2c75c0 0001 0 [ 9085.432281] 3ea0: 8e2c75c0 0001 0001 8e2c7a40 8e2c75c0 0034 0 [ 9085.446563] 3ec0: 0034 6013 80058f47 0034 0 [ 9085.460845] 3ee0: 8e01a440 800ae6c5 806c96f4 8e010 [ 9085.475219] 3f00: 6013 800593b7 0002 5 [ 9085.489685] 3f20: 8e01a444 8e2c75c0 0001 806c96e0 800a4 [ 9085.504211] 3f40: 8e01a440 8e083f9c 800c76d5 803f0feb 8e2c1 [ 9085.518707] 3f60: 8e2c75c0 0001 8000c167 0058 2030 3 [ 9085.533111] 3f80: 80059a63 0002 271aec19 0006 0002 7ef06 [ 9085.547454] 3fa0: 0058 8000bfe1 0002 7ef0fe44 fee1dead 28121969 43213 [ 9085.561828] 3fc0: 0002 7ef0fe44 0006 0058 76fc0 [ 9085.576171] 3fe0: 0058 7ef0fcb4 76f2a2ad 76eb6ed6 2030 fee1dead 0 [ 9085.590545] [<802f238e>] (musb_generic_disable+0x16/0x1e) from [<802f2639>] ) [ 9085.606140] [<802f2639>] (musb_shutdown+0x33/0x6e) from [<80282293>] (platfo) [ 9085.621917] [<80282293>] (platform_drv_shutdown+0x15/0x16) from [<80280499>]) [ 9085.637969] [<80280499>] (device_shutdown+0x49/0x70) from [<80042bbb>] (kern) [ 9085.653106] [<80042bbb>] (kernel_halt+0xf/0x2c) from [<800431df>] (sys_reboo) [ 9085.667968] [<800431df>] (sys_reboot+0xa7/0x158) from [<8000bfe1>] (ret_fast) [ 9085.683380] Code: 80da 811a f883 2060 (7a9a) 885a [ 9085.694732] [ cut here ] [ 9085.705871] WARNING: at /build/buildd/linux-linaro-omap-3.1-3.1.1/arch/arm/m) [ 9085.731658] In-band Error seen by MPU at address 0 [ 9085.743377] Modules linked in: bluetooth mousedev snd_soc_overo libertas_sdic [ 9085.777221] [<80010c9d>] (unwind_backtrace+0x1/0x90) from [<8003495d>] (warn) [ 9085.794372] [<8003495d>] (warn_slowpath_common+0x39/0x50) from [<800349d7>] ) [ 9085.811798] [<800349d7>] (warn_slowpath_fmt+0x21/0x2a) from [<80020109>] (om) [ 9085.829071] [<80020109>] (omap3_l3_app_irq+0xc9/0x118) from [<8006cca7>] (ha) [ 9085.847076] [<8006c
Re: Kernel panicking with ALIP and NANO, 12.xx prebuilt images
On 18 May 2012 10:51, Sudhangathan B S wrote: > I' getting this error during boot on a freshly dd'd image of alip or nano > prebuilt images. Please, could you add a link to the exact image you used? Latest pre-built images are available on http://snapshots.linaro.org/precise/pre-built/ ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Kernel panicking with ALIP and NANO, 12.xx prebuilt images
This is link from which I downloaded the image for nano.. I'm using a Summit-Fire combination.. http://releases.linaro.org/images/12.03/oneiric/nano/overo-nano.img.gz more info: root@linaro-nano:~# uname -a Linux linaro-nano 3.1.1-21-linaro-omap #21~ci~20120226072322~4f4a8a65-Ubuntu SMP PREEMPT Sun Feb 26 19: armv7l armv7l armv7l GNU/Linux and i'm not sure exactly which image i used for alip.. I'm sure it is the same link but can be any version from january to march. more info: root@linaro-alip:~# uname -a Linux linaro-alip 3.1.1-21-linaro-omap #21~ci~20120226072322~4f4a8a65-Ubuntu SMP PREEMPT Sun Feb 26 19: armv7l armv7l armv7l GNU/Linux Need more info..?? - Sudhangathan BS Ph:(+91) 9731-905-205 - On Fri, May 18, 2012 at 1:41 PM, Fathi Boudra wrote: > On 18 May 2012 10:51, Sudhangathan B S wrote: > > I' getting this error during boot on a freshly dd'd image of alip or nano > > prebuilt images. > > Please, could you add a link to the exact image you used? > Latest pre-built images are available on > http://snapshots.linaro.org/precise/pre-built/ > ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: 12.05 linux-linaro kernel tree
Hi Tushar, On 05/17/2012 01:06 PM, Tushar Behera wrote: On 05/11/2012 01:04 AM, Andrey Konovalov wrote: Samsung: topic/base topic/core topic/bl topic/dt topic/fb topic/pd topic/s2ram topic/asv_cpufreq topic/led topic/dummy_reg topic/gadget topic/touch topic/wlan topic/audio topic/hdmi topic/mali topic/cma_v24 topic/android_config Following topic branches are available to be pulled to linux-linaro tree. topic/base topic/core topic/bl topic/dt topic/fb topic/pd topic/s2ram topic/asv_cpufreq topic/led topic/dummy_reg topic/gadget topic/touch topic/wlan topic/audio topic/hdmi *topic/mfc* topic/mali *topic/cma_origen* topic/android_config *topic/ubuntu_config* These topics have been merged ok into the linux-linaro tree yesterday. Thanks! * topic/base is based on v3.4-rc7 and has config patches, both internal and from John's linaro-config-3.4 branch. All other topic branches are based on topic/base. * topic/cma_v24 has been dropped. Instead we have topic/cma_origen that has only Origen specific CMA patches. With this set of patches, I can boot-test Ubuntu and it fails for Android. I will update you if the Android related kernel panic is fixed before 2012.05 release. OK Please let me know if you run across any issues while merging these branches. There were two simple conflicts when merging the topic/mali. The solutions are attached for your reference. Thanks, Andrey --- /home/ynk/git.linaro.org/lin-lin-tra.lltconfigs/solutions/886efb590db144743c71795a2849d19c/arch-arm-mach-exynos-mach-origen.c.orig 2012-05-17 21:15:42.247953580 +0400 +++ arch/arm/mach-exynos/mach-origen.c 2012-05-17 21:16:22.411954955 +0400 @@ -22,12 +22,9 @@ #include #include #include -<<< HEAD #include #include -=== #include ->>> rebase-samslt-mali #include #include --- /home/ynk/git.linaro.org/lin-lin-tra.lltconfigs/solutions/886efb590db144743c71795a2849d19c/drivers-video-Kconfig.orig 2012-05-17 21:16:22.451954956 +0400 +++ drivers/video/Kconfig 2012-05-17 21:16:58.819956201 +0400 @@ -25,11 +25,8 @@ source "drivers/gpu/stub/Kconfig" source "drivers/gpu/ion/Kconfig" -<<< HEAD -=== source "drivers/gpu/arm/Kconfig" ->>> rebase-samslt-mali config VGASTATE tristate default n ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: android-3.4 or android-3.4-compat
On 17 May 2012 22:09, Zach Pfeffer wrote: > On 17 May 2012 20:49, John Stultz wrote: >> Hey Andrey, Zach, >> So I'm back from my vacation, and have found that the Android team has >> released a -compat tree for their 3.4 kernel. Basically this tree re-adds >> some items like earlysuspend and classic wakelocks in order to provide >> better compatibility with old (and by old, I really mean current as far as >> we see - so ICS and earlier) Android userland. >> >> Since we're still shipping ICS, and have no access to whatever the Android >> 5.0 userland will be, it seems merging in the -compat tree would make sense. >> >> However, I know Tixy and others have already tried to address the lack of >> earlysuspend in the android-3.3+ kernels, so I wanted to double check that >> this wouldn't cause additional pain (since those adjustments might need to >> be reverted). >> >> So I just wanted to check first with folks to make sure there are no >> objections to merging in the -compat changes, and that the timing of merging >> in these changes isn't problematic (I can happily hold off till this months >> release is done, so we don't risk any last minute gotchas). > > Yeah, lets hold off. I'll get it on the schedule for next month. Sound > good everyone? Put a meeting together next week to plan it. >> thanks >> -john >> >> > > > > -- > Zach Pfeffer > Android Platform Team Lead, Linaro Platform Teams > Linaro.org | Open source software for ARM SoCs > Follow Linaro: http://www.facebook.com/pages/Linaro > http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Kernel panicking with ALIP and NANO, 12.xx prebuilt images
Yeah---I'm also seeing this on Overo. I'm confused as to what exactly is causing the kernel panic but I suspect something in user space that is exercising some less-used aspect of the kernel. Yesterday I tried using a well tested kernel with a recent linaro rootfs and saw a similar panic as the display was coming up. No solutions at this point -Ash On Fri, May 18, 2012 at 3:17 AM, Sudhangathan B S wrote: > This is link from which I downloaded the image for nano.. I'm using a > Summit-Fire combination.. > http://releases.linaro.org/images/12.03/oneiric/nano/overo-nano.img.gz > more info: > root@linaro-nano:~# uname -a > Linux linaro-nano 3.1.1-21-linaro-omap #21~ci~20120226072322~4f4a8a65-Ubuntu > SMP PREEMPT Sun Feb 26 19: armv7l armv7l armv7l GNU/Linux > > and i'm not sure exactly which image i used for alip.. I'm sure it is the > same link but can be any version from january to march. > more info: > root@linaro-alip:~# uname -a > Linux linaro-alip 3.1.1-21-linaro-omap #21~ci~20120226072322~4f4a8a65-Ubuntu > SMP PREEMPT Sun Feb 26 19: armv7l armv7l armv7l GNU/Linux > > Need more info..?? > - > Sudhangathan BS > Ph:(+91) 9731-905-205 > - > > > On Fri, May 18, 2012 at 1:41 PM, Fathi Boudra > wrote: >> >> On 18 May 2012 10:51, Sudhangathan B S wrote: >> > I' getting this error during boot on a freshly dd'd image of alip or >> > nano >> > prebuilt images. >> >> Please, could you add a link to the exact image you used? >> Latest pre-built images are available on >> http://snapshots.linaro.org/precise/pre-built/ > > > > ___ > linaro-dev mailing list > linaro-dev@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev > ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Kernel panicking with ALIP and NANO, 12.xx prebuilt images
Hi, We've seen it on Fast Models as well, using developer.tar.gz from wednesday. Riku On 18 May 2012 17:08, Ash Charles wrote: > Yeah---I'm also seeing this on Overo. > > I'm confused as to what exactly is causing the kernel panic but I > suspect something in user space that is exercising some less-used > aspect of the kernel. Yesterday I tried using a well tested kernel > with a recent linaro rootfs and saw a similar panic as the display was > coming up. > No solutions at this point > -Ash > > On Fri, May 18, 2012 at 3:17 AM, Sudhangathan B S > wrote: >> This is link from which I downloaded the image for nano.. I'm using a >> Summit-Fire combination.. >> http://releases.linaro.org/images/12.03/oneiric/nano/overo-nano.img.gz >> more info: >> root@linaro-nano:~# uname -a >> Linux linaro-nano 3.1.1-21-linaro-omap #21~ci~20120226072322~4f4a8a65-Ubuntu >> SMP PREEMPT Sun Feb 26 19: armv7l armv7l armv7l GNU/Linux >> >> and i'm not sure exactly which image i used for alip.. I'm sure it is the >> same link but can be any version from january to march. >> more info: >> root@linaro-alip:~# uname -a >> Linux linaro-alip 3.1.1-21-linaro-omap #21~ci~20120226072322~4f4a8a65-Ubuntu >> SMP PREEMPT Sun Feb 26 19: armv7l armv7l armv7l GNU/Linux >> >> Need more info..?? >> - >> Sudhangathan BS >> Ph:(+91) 9731-905-205 >> - >> >> >> On Fri, May 18, 2012 at 1:41 PM, Fathi Boudra >> wrote: >>> >>> On 18 May 2012 10:51, Sudhangathan B S wrote: >>> > I' getting this error during boot on a freshly dd'd image of alip or >>> > nano >>> > prebuilt images. >>> >>> Please, could you add a link to the exact image you used? >>> Latest pre-built images are available on >>> http://snapshots.linaro.org/precise/pre-built/ >> >> >> >> ___ >> linaro-dev mailing list >> linaro-dev@lists.linaro.org >> http://lists.linaro.org/mailman/listinfo/linaro-dev >> > > ___ > linaro-dev mailing list > linaro-dev@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: 12.05 linux-linaro kernel tree
Greetings, Here is the list of the topics currently included into the 12.05 linux-linaro tree (v3.4-rc7 based): Generic topics: ufs (ufs-for-linux-linaro) emmc (emmc-for-linux-linaro) thermal_exynos4_imx6 (thermal_exynos4_imx6_work) linaro-android-3.4 armlt-gator (tracking-armlt-gator) umm-wip (umm-3.4rc4-wip) unsorted (tracking-orphan-unsorted branch from people/ynk/linux-linaro-tracking.git for the stuff that doesn't fit into any existing topics) linaro-configs-3.4 ARM LT's topics: tracking-armlt-hdlcd tracking-armlt-mmc tracking-armlt-arm-arch-fixes tracking-armlt-misc-fixes tracking-armlt-ubuntu-config tracking-armlt-android-config Samsung LT's topics: topic/base topic/core topic/bl topic/dt topic/fb topic/pd topic/s2ram topic/asv_cpufreq topic/led topic/dummy_reg topic/gadget topic/touch topic/wlan topic/audio topic/hdmi topic/mfc topic/mali topic/cma_origen topic/android_config topic/ubuntu_config Before the next Monday, May 21st, I could also get the ubuntu sauce topic (a new one). Not sure about updates to the umm-wip topic; most probably there will be no more updates for this 12.05 release. There is still linaro_cpuidle topic (people/rob_lee/linux.git, linaro_cpuidle) in my manifest (commented out), but it was last updated 2 months ago, and the contents seem to be included into the mainline. So it will be wiped out if there are no objections. Thanks, Andrey On 05/10/2012 11:34 PM, Andrey Konovalov wrote: Most probably it will be v3.4-rc7. The 12.05 linux-linaro tree will get the ARM and Samsung LTs topics plus the 7 generic topics currently included into the linux-linaro-core-tracking tree: ufs (ufs-for-linux-linaro) emmc (emmc-for-linux-linaro) thermal_exynos4_imx6 (thermal_exynos4_imx6_work) linaro-android-3.4 armlt-gator (tracking-armlt-gator) umm-wip (umm-3.4rc4-wip) linaro-configs-3.4 If you don't see your generic topic in this list, but you think it should be there, please let me know ASAP. If you have a new topic to add, please send me the request before the next Thursday, May 17; the sooner, the better. The requirements for a topic can be found here: https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelTreeProcess#Adding_a_topic_to_linux-linaro_kernel_and_maintaining_it The landing teams - please update your topic branches if needed: ARM: tracking-armlt-hdlcd tracking-armlt-mmc tracking-armlt-arm-arch-fixes tracking-armlt-misc-fixes tracking-armlt-ubuntu-config tracking-armlt-android-config Samsung: topic/base topic/core topic/bl topic/dt topic/fb topic/pd topic/s2ram topic/asv_cpufreq topic/led topic/dummy_reg topic/gadget topic/touch topic/wlan topic/audio topic/hdmi topic/mali topic/cma_v24 topic/android_config Thanks, Andrey ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: android-3.4 or android-3.4-compat
On 05/18/2012 06:57 AM, Zach Pfeffer wrote: On 17 May 2012 22:09, Zach Pfeffer wrote: On 17 May 2012 20:49, John Stultz wrote: Hey Andrey, Zach, So I'm back from my vacation, and have found that the Android team has released a -compat tree for their 3.4 kernel. Basically this tree re-adds some items like earlysuspend and classic wakelocks in order to provide better compatibility with old (and by old, I really mean current as far as we see - so ICS and earlier) Android userland. Since we're still shipping ICS, and have no access to whatever the Android 5.0 userland will be, it seems merging in the -compat tree would make sense. However, I know Tixy and others have already tried to address the lack of earlysuspend in the android-3.3+ kernels, so I wanted to double check that this wouldn't cause additional pain (since those adjustments might need to be reverted). So I just wanted to check first with folks to make sure there are no objections to merging in the -compat changes, and that the timing of merging in these changes isn't problematic (I can happily hold off till this months release is done, so we don't risk any last minute gotchas). Yeah, lets hold off. I'll get it on the schedule for next month. Sound good everyone? Put a meeting together next week to plan it. I won't be there, so I'd rather do it over email. I really don't think this will be a huge impact, but really just wanted to give a general heads up and get input from Tixy on how badly it might impact his fix (or any other userland changes we made to accommodate 3.3+ kernels that I'm unaware of) and Andrey on if he had any objections. thanks -john ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: android-3.4 or android-3.4-compat
On 05/18/2012 09:54 PM, John Stultz wrote: On 05/18/2012 06:57 AM, Zach Pfeffer wrote: On 17 May 2012 22:09, Zach Pfeffer wrote: On 17 May 2012 20:49, John Stultz wrote: Hey Andrey, Zach, So I'm back from my vacation, and have found that the Android team has released a -compat tree for their 3.4 kernel. Basically this tree re-adds some items like earlysuspend and classic wakelocks in order to provide better compatibility with old (and by old, I really mean current as far as we see - so ICS and earlier) Android userland. Since we're still shipping ICS, and have no access to whatever the Android 5.0 userland will be, it seems merging in the -compat tree would make sense. However, I know Tixy and others have already tried to address the lack of earlysuspend in the android-3.3+ kernels, so I wanted to double check that this wouldn't cause additional pain (since those adjustments might need to be reverted). So I just wanted to check first with folks to make sure there are no objections to merging in the -compat changes, and that the timing of merging in these changes isn't problematic (I can happily hold off till this months release is done, so we don't risk any last minute gotchas). Yeah, lets hold off. I'll get it on the schedule for next month. Sound good everyone? Works for me. Put a meeting together next week to plan it. I won't be there, so I'd rather do it over email. I really don't think this will be a huge impact, but really just wanted to give a general heads up and get input from Tixy on how badly it might impact his fix (or any other userland changes we made to accommodate 3.3+ kernels that I'm unaware of) and Andrey on if he had any objections. No particular objections from my side. Whatever decision is made. Thanks, Andrey ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
