RE: OMAP 3630 random crashes
Hi You are right. I used a different bootloader for the newer kernels, because of another build system and did not think about it. The u-boot from github/gumstix sets the memory timings different than the u-boot directly from denx.de. I switched to the gumstix-uboot and i can now allocate all the memory in the system with all peripherals enabled, and i just get killed by the OOM a some point. But thanks for the help so far, even though it was not a kernel issue :-) Med venlig hilsen/Best regards Casper Mogensen From: Tony Lindgren Sent: Tuesday, July 01, 2014 09:54 To: Michael Trimarchi Cc: Casper Lyngesen Mogensen; Ash Charles; linux-omap@vger.kernel.org Subject: Re: OMAP 3630 random crashes * Michael Trimarchi [140630 06:49]: > > On Mon, Jun 30, 2014 at 3:43 PM, Casper Lyngesen Mogensen > wrote: > > > > I got two new Overo AirStorm today, and they have same behavior. I tried > > disabling > > the SMSC9xxx again and booted from MMC. This seems to make the backtrace a > > little more consistent(Tried on both new and old). There is (almost) always > > something > > about Alignment trap, the crash log itself differs every time. Also i get > > to allocate a lot > > more memory before crash with these settings. > > What kernel version are you using? We should have v3.15 working fine, but PM features are not merged in util for v3.16. I would try dding calls to omap_sdrc_init to pdata-quirks.c the same way board-over.c is doing: omap_sdrc_init(mt46h32m32lf6_sdrc_params, mt46h32m32lf6_sdrc_params); If the memory timings are not correctly set by the bootloader that could explain the issues. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP 3630 random crashes
* Michael Trimarchi [140630 06:49]: > > On Mon, Jun 30, 2014 at 3:43 PM, Casper Lyngesen Mogensen > wrote: > > > > I got two new Overo AirStorm today, and they have same behavior. I tried > > disabling > > the SMSC9xxx again and booted from MMC. This seems to make the backtrace a > > little more consistent(Tried on both new and old). There is (almost) always > > something > > about Alignment trap, the crash log itself differs every time. Also i get > > to allocate a lot > > more memory before crash with these settings. > > What kernel version are you using? We should have v3.15 working fine, but PM features are not merged in util for v3.16. I would try dding calls to omap_sdrc_init to pdata-quirks.c the same way board-over.c is doing: omap_sdrc_init(mt46h32m32lf6_sdrc_params, mt46h32m32lf6_sdrc_params); If the memory timings are not correctly set by the bootloader that could explain the issues. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: OMAP 3630 random crashes
Hi I use a 3.15.0 Med venlig hilsen/Best regards Casper Mogensen From: Michael Trimarchi Sent: Monday, June 30, 2014 15:47 To: Casper Lyngesen Mogensen Cc: Ash Charles; Tony Lindgren; linux-omap@vger.kernel.org Subject: Re: OMAP 3630 random crashes Hi On Mon, Jun 30, 2014 at 3:43 PM, Casper Lyngesen Mogensen wrote: > Hi > > I got two new Overo AirStorm today, and they have same behavior. I tried > disabling > the SMSC9xxx again and booted from MMC. This seems to make the backtrace a > little more consistent(Tried on both new and old). There is (almost) always > something > about Alignment trap, the crash log itself differs every time. Also i get to > allocate a lot > more memory before crash with these settings. > > What kernel version are you using? Michael > mallocsize = 3446 > mallocsize = 34464000 > mallocsize = 34468000 > [ 425.438629] Alignment trap: not handling instruction e1932f9f at > [] > [ 425.446136] Unhandled fault: alignment exception (0x001) at 0x7be3c202 > [ 425.453002] Internal error: : 1 [#1] SMP ARM > [ 425.457489] Modules linked in: snd_soc_omap_twl4030 libertas_sdio libertas > snd_soc_omap snd_pcm_dmaengine lib80211 cfg80211 snd_soc_twl4030 snd_soc_core > snd_compress snd_pcm snd_timer snd soundcore > [ 425.476226] CPU: 0 PID: 1582 Comm: kworker/u2:2 Not tainted 3.15.0-dirty > #14 > [ 425.483642] task: de062080 ti: dd1b8000 task.ti: dd1b8000 > [ 425.489349] PC is at __lock_acquire+0x160/0x1cb8 > [ 425.494232] LR is at lock_acquire+0xa0/0xfc > [ 425.498626] pc : []lr : []psr: 2193 > [ 425.498626] sp : dd1b9bb0 ip : 0001 fp : 7be3c0fe > [ 425.510681] r10: c0854c10 r9 : c0d7785c r8 : de062080 > [ 425.516174] r7 : r6 : dd1b8030 r5 : r4 : dfaef6d0 > [ 425.523010] r3 : 7be3c202 r2 : dfaef6d0 r1 : 28014a03 r0 : dfaef6d0 > [ 425.529876] Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment > kernel > [ 425.537628] Control: 10c5307d Table: 9e76c019 DAC: 0015 > [ 425.543670] Process kworker/u2:2 (pid: 1582, stack limit = 0xdd1b8248) > [ 425.550506] Stack: (0xdd1b9bb0 to 0xdd1ba000) > [ 425.555114] 9ba0: de062080 0004 > 0006 c07fb7e4 > [ 425.563720] 9bc0: 0008 c0081998 dd1b8020 de062080 0001 > c07ef168 c0081ab8 > [ 425.572296] 9be0: 1f2b8000 ddbe1780 ddbe65c0 dd1b8000 1f2b8000 c01486d4 > ddbd60f0 > [ 425.580902] 9c00: ddbe65c0 > > [ 425.589508] 9c20: dfaef6d0 0001 > c007914c c00843c4 > [ 425.598114] 9c40: 0001 0080 c007914c 0002 > dd1b8000 6193 > [ 425.606689] 9c60: c0854c10 dfaef6c0 0113 c007914c 0003 dd1b9cc8 > c0146d90 c0147b3c > [ 425.615295] 9c80: 0001 c054a808 0001 c007914c > dfaef6c0 > [ 425.623901] 9ca0: 0001 c007914c ddbe65c0 > dd1b9d30 0060 > [ 425.632507] 9cc0: 0001 c00791ac ddbe65c0 0002 c0149548 > 0001 > [ 425.641082] 9ce0: 0001 ddbd60f0 dd1b9d40 0001 dd1b9d2c c01b60a0 > dd1b9d2c 0001 > [ 425.649688] 9d00: de062080 0004 0006 0001 0001 > de1ff000 dde0a490 > [ 425.658294] 9d20: dd1b9d9c 0001 ddbe65c0 c00843c4 > 0001 > [ 425.666900] 9d40: ddbe65c0 c0130274 c007fa8c dd1b8038 6113 > de1ff000 ddbd22a0 > [ 425.675506] 9d60: dde0a468 dde0a468 ddbd60f0 ddbd2240 dd1b8000 de141015 > de141014 > [ 425.684082] 9d80: dd1b9eb8 c01b6534 dde0a468 c054a8d4 ddbd2240 c01302a8 > > [ 425.692687] 9da0: dde0a468 ddbd2240 ddbd2240 c0121cb4 0001 0011 > ddbd2240 c012297c > [ 425.701293] 9dc0: dd1b8000 01141015 de141014 dd1b9eb8 dd1b9e10 c0123344 > dd1b9e18 > [ 425.709899] 9de0: dd1b9e10 0003 dd1b8000 c0123c08 c0124b3c 0001 > c0081ab8 > [ 425.718505] 9e00: dd1b9eb8 dd1b8030 c01269a4 de086dc0 c0124b3c > 0001 > [ 425.727081] 9e20: 00727375 0003 de141011 de086e00 de11fb80 de11fb80 > dd1b9eb8 c0565f50 > [ 425.735687] 9e40: de141000 ff9c dd1b8000 c01269cc > dd1b9e70 > [ 425.744293] 9e60: dd1b8038 0002 de062080 c0d7785c > > [ 425.752899] 9e80: 00192082 c0926c08 000d c0565f50 0001 de141000 > ff9c de770500 > [ 425.761474] 9ea0: de062080 dd1b8000 c0127ed8 0041 0004 > de0361d0 ddbd2240 > [ 425.770080] 9ec0: 00727375 0003 de141011 de086e00 de0361d0 ddbd2240 > ddbd60f0 0011 >
Re: OMAP 3630 random crashes
> > [ 426.669921] 9fe0: 0013 > > [ 426.678558] [] (perf_event_task_tick) from [] > (scheduler_tick+0x70/0xd4) > [ 426.687469] [] (scheduler_tick) from [] > (update_process_times+0x54/0x60) > [ 426.696380] [] (update_process_times) from [] > (tick_sched_handle.isra.18+0x44/0x50) > [ 426.706298] [] (tick_sched_handle.isra.18) from [] > (tick_sched_timer+0x5c/0x90) > [ 426.715820] [] (tick_sched_timer) from [] > (__run_hrtimer+0x7c/0x1e0) > [ 426.724365] [] (__run_hrtimer) from [] > (hrtimer_interrupt+0x128/0x2b8) > [ 426.733093] [] (hrtimer_interrupt) from [] > (omap2_gp_timer_interrupt+0x24/0x34) > [ 426.742645] [] (omap2_gp_timer_interrupt) from [] > (handle_irq_event_percpu+0x40/0x1c4) > [ 426.752838] [] (handle_irq_event_percpu) from [] > (handle_irq_event+0x3c/0x5c) > [ 426.762176] [] (handle_irq_event) from [] > (handle_level_irq+0xac/0x154) > [ 426.770996] [] (handle_level_irq) from [] > (generic_handle_irq+0x28/0x3c) > [ 426.779907] [] (generic_handle_irq) from [] > (handle_IRQ+0x4c/0xb4) > [ 426.788269] [] (handle_IRQ) from [] > (omap3_intc_handle_irq+0x80/0x9c) > [ 426.796874] [] (omap3_intc_handle_irq) from [] > (__irq_svc+0x44/0x5c) > [ 426.805389] Exception stack(0xdd1b99b8 to 0xdd1b9a00) > [ 426.810729] 99a0: > c054a974 0001 > [ 426.819366] 99c0: 002a de24f284 000b c0082066 c07ff5c4 > c0082068 > [ 426.827972] 99e0: 0001 de062080 dd1b9a00 c054a974 c054a978 > 6113 > [ 426.836608] [] (__irq_svc) from [] > (_raw_spin_unlock_irq+0x28/0x2c) > [ 426.845092] [] (_raw_spin_unlock_irq) from [] > (do_exit+0x138/0x924) > [ 426.853546] [] (do_exit) from [] (die+0x1fc/0x3b8) > [ 426.860443] [] (die) from [] (do_DataAbort+0x88/0x98) > [ 426.867584] [] (do_DataAbort) from [] > (__dabt_svc+0x44/0x80) > [ 426.875366] Exception stack(0xdd1b9b68 to 0xdd1b9bb0) > [ 426.880706] 9b60: dfaef6d0 28014a03 dfaef6d0 7be3c202 > dfaef6d0 > [ 426.889343] 9b80: dd1b8030 de062080 c0d7785c c0854c10 7be3c0fe > 0001 dd1b9bb0 > [ 426.897949] 9ba0: c00843c4 c0082064 2193 > [ 426.903289] [] (__dabt_svc) from [] > (__lock_acquire+0x160/0x1cb8) > [ 426.911560] [] (__lock_acquire) from [] > (lock_acquire+0xa0/0xfc) > [ 426.919738] [] (lock_acquire) from [] > (_raw_spin_lock_irqsave+0x38/0x4c) > [ 426.928649] [] (_raw_spin_lock_irqsave) from [] > (__wake_up+0x1c/0x4c) > [ 426.937255] [] (__wake_up) from [] > (__wake_up_bit+0x30/0x38) > [ 426.945068] [] (__wake_up_bit) from [] > (ll_rw_block+0x2c/0xf4) > [ 426.953033] [] (ll_rw_block) from [] > (ext4_find_entry+0x190/0x5ec) > [ 426.961364] [] (ext4_find_entry) from [] > (ext4_lookup+0x38/0x164) > [ 426.969604] [] (ext4_lookup) from [] > (lookup_real+0x20/0x4c) > [ 426.977386] [] (lookup_real) from [] > (__lookup_hash+0x38/0x40) > [ 426.985351] [] (__lookup_hash) from [] > (lookup_slow+0x3c/0xa8) > [ 426.993286] [] (lookup_slow) from [] > (link_path_walk+0x404/0x85c) > [ 427.001525] [] (link_path_walk) from [] > (path_openat+0x8c/0x604) > [ 427.009674] [] (path_openat) from [] > (do_filp_open+0x2c/0x80) > [ 427.017547] [] (do_filp_open) from [] > (do_open_exec+0x18/0xf4) > [ 427.025512] [] (do_open_exec) from [] > (do_execve+0x1a8/0x5cc) > [ 427.033386] [] (do_execve) from [] > (call_usermodehelper+0x100/0x130) > [ 427.042266] [] (call_usermodehelper) from [] > (ret_from_fork+0x14/0x2c) > [ 427.051300] Code: e1973003 1a0b e1a03005 e1a5 (e5b35148) > [ 427.057708] ---[ end trace 713ce209622ee485 ]--- > [ 427.062561] Kernel panic - not syncing: Fatal exception in interrupt > [ 427.069244] ---[ end Kernel panic - not syncing: Fatal exception in > interrupt > > > > > Med venlig hilsen/Best regards > > Casper Mogensen > > > From: Casper Lyngesen Mogensen > Sent: Friday, June 20, 2014 16:26 > To: Ash Charles > Cc: Tony Lindgren; linux-omap@vger.kernel.org > Subject: RE: OMAP 3630 random crashes > > Hi > > The memory on the Overo, i have with me right now, is actually marked JW513, > and 18 months is also around the time, they were bought. Will check my other > modules, when i get back to the office. > However i have not been able to recreate the problem with the 3.5.0 kernel on > same Overo > > Med venlig hilsen/Best regards > > Casper Mogensen > > > From: ashchar...@gmail.c
RE: OMAP 3630 random crashes
[ 426.836608] [] (__irq_svc) from []
(_raw_spin_unlock_irq+0x28/0x2c)
[ 426.845092] [] (_raw_spin_unlock_irq) from []
(do_exit+0x138/0x924)
[ 426.853546] [] (do_exit) from [] (die+0x1fc/0x3b8)
[ 426.860443] [] (die) from [] (do_DataAbort+0x88/0x98)
[ 426.867584] [] (do_DataAbort) from []
(__dabt_svc+0x44/0x80)
[ 426.875366] Exception stack(0xdd1b9b68 to 0xdd1b9bb0)
[ 426.880706] 9b60: dfaef6d0 28014a03 dfaef6d0 7be3c202
dfaef6d0
[ 426.889343] 9b80: dd1b8030 de062080 c0d7785c c0854c10 7be3c0fe
0001 dd1b9bb0
[ 426.897949] 9ba0: c00843c4 c0082064 2193
[ 426.903289] [] (__dabt_svc) from []
(__lock_acquire+0x160/0x1cb8)
[ 426.911560] [] (__lock_acquire) from []
(lock_acquire+0xa0/0xfc)
[ 426.919738] [] (lock_acquire) from []
(_raw_spin_lock_irqsave+0x38/0x4c)
[ 426.928649] [] (_raw_spin_lock_irqsave) from []
(__wake_up+0x1c/0x4c)
[ 426.937255] [] (__wake_up) from []
(__wake_up_bit+0x30/0x38)
[ 426.945068] [] (__wake_up_bit) from []
(ll_rw_block+0x2c/0xf4)
[ 426.953033] [] (ll_rw_block) from []
(ext4_find_entry+0x190/0x5ec)
[ 426.961364] [] (ext4_find_entry) from []
(ext4_lookup+0x38/0x164)
[ 426.969604] [] (ext4_lookup) from []
(lookup_real+0x20/0x4c)
[ 426.977386] [] (lookup_real) from []
(__lookup_hash+0x38/0x40)
[ 426.985351] [] (__lookup_hash) from []
(lookup_slow+0x3c/0xa8)
[ 426.993286] [] (lookup_slow) from []
(link_path_walk+0x404/0x85c)
[ 427.001525] [] (link_path_walk) from []
(path_openat+0x8c/0x604)
[ 427.009674] [] (path_openat) from []
(do_filp_open+0x2c/0x80)
[ 427.017547] [] (do_filp_open) from []
(do_open_exec+0x18/0xf4)
[ 427.025512] [] (do_open_exec) from []
(do_execve+0x1a8/0x5cc)
[ 427.033386] [] (do_execve) from []
(call_usermodehelper+0x100/0x130)
[ 427.042266] [] (call_usermodehelper) from []
(ret_from_fork+0x14/0x2c)
[ 427.051300] Code: e1973003 1a0b e1a03005 e1a5 (e5b35148)
[ 427.057708] ---[ end trace 713ce209622ee485 ]---
[ 427.062561] Kernel panic - not syncing: Fatal exception in interrupt
[ 427.069244] ---[ end Kernel panic - not syncing: Fatal exception in interrupt
Med venlig hilsen/Best regards
Casper Mogensen
From: Casper Lyngesen Mogensen
Sent: Friday, June 20, 2014 16:26
To: Ash Charles
Cc: Tony Lindgren; linux-omap@vger.kernel.org
Subject: RE: OMAP 3630 random crashes
Hi
The memory on the Overo, i have with me right now, is actually marked JW513,
and 18 months is also around the time, they were bought. Will check my other
modules, when i get back to the office.
However i have not been able to recreate the problem with the 3.5.0 kernel on
same Overo
Med venlig hilsen/Best regards
Casper Mogensen
From: ashchar...@gmail.com on behalf of Ash Charles
Sent: Friday, June 20, 2014 16:17
To: Casper Lyngesen Mogensen
Cc: Tony Lindgren; linux-omap@vger.kernel.org
Subject: Re: OMAP 3630 random crashes
Hi Casper,
What is the top-side marking on the memory chip on your Overo? There
were some random faults due to poor memory chips marked 'JW513' from
about 18 months ago.
--Ash
On Fri, Jun 20, 2014 at 7:00 AM, Casper Lyngesen Mogensen
wrote:
> Hi
>
> U-boot seems to set the speed to 165 Mhz
> "OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz"
>
> I have a LAN9221, but tried the other timings, still same result.
>
> Also tried running the entire system from an MMC card, same result, but my
> test had
> to run a little longer.
>
> Found a quicker test to reproduce the error, a little C-program:
>
> #include
> #include
> #include
>
> int main(void){
> long long var=0;
>
> int *ptr=NULL;
>
> int run=1;
> while(run){
> ptr=malloc(sizeof(int)*1000);
> if(ptr==NULL){
> run=0;
> }
> var+=1000;
> printf("mallocsize = %lld\n",var*sizeof(int));
> }
> }
>
>
> Booting from NFS, the system crashes at ~40mb allocated
> On MMC at ~60MB
>
> Med venlig hilsen/Best regards
>
> Casper Mogensen
>
> ________
> From: Tony Lindgren
> Sent: Friday, June 20, 2014 11:14
> To: Casper Lyngesen Mogensen
> Cc: linux-omap@vger.kernel.org
> Subject: Re: OMAP 3630 random crashes
>
> Hi,
>
> * Casper Lyngesen Mogensen [140620 01:52]:
>> Hi
>>
>> I have custom board with a Gumstix Overo, my board is similar to a
>> Tobi board. Right now i have it running with a 3.5.0 kernel. I'm
>> trying to upgrade the kernel, and have tried several versions (3.10 ->
>> 3.15) and i seem to be hitting the same problem with all versions, i
>> get random crashes. Found a way to trigger the
Re: OMAP 3630 random crashes
* Casper Lyngesen Mogensen [140622 23:08]: > Hi again > > All my boards are marked "JW513". So the problem might be hardware related, i > will try to get some new Overo's and test on these instead. OK, please let us know how it goes. Also if using armhf based distro some omap3 SoCs need CONFIG_CPU_BPREDICT_DISABLE=y or CONFIG_ARM_ERRATA_430973=y or both. Sorry no idea yet which revisions, but I've seen some flakeyness with apt-get dist-upgrade occasionally failing on a 3630 with revision info: CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5307d Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: OMAP 3630 random crashes
Hi again
All my boards are marked "JW513". So the problem might be hardware related, i
will try to get some new Overo's and test on these instead.
Med venlig hilsen/Best regards
Casper Mogensen
From: linux-omap-ow...@vger.kernel.org on
behalf of Casper Lyngesen Mogensen
Sent: Friday, June 20, 2014 16:26
To: Ash Charles
Cc: Tony Lindgren; linux-omap@vger.kernel.org
Subject: RE: OMAP 3630 random crashes
Hi
The memory on the Overo, i have with me right now, is actually marked JW513,
and 18 months is also around the time, they were bought. Will check my other
modules, when i get back to the office.
However i have not been able to recreate the problem with the 3.5.0 kernel on
same Overo
Med venlig hilsen/Best regards
Casper Mogensen
From: ashchar...@gmail.com on behalf of Ash Charles
Sent: Friday, June 20, 2014 16:17
To: Casper Lyngesen Mogensen
Cc: Tony Lindgren; linux-omap@vger.kernel.org
Subject: Re: OMAP 3630 random crashes
Hi Casper,
What is the top-side marking on the memory chip on your Overo? There
were some random faults due to poor memory chips marked 'JW513' from
about 18 months ago.
--Ash
On Fri, Jun 20, 2014 at 7:00 AM, Casper Lyngesen Mogensen
wrote:
> Hi
>
> U-boot seems to set the speed to 165 Mhz
> "OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz"
>
> I have a LAN9221, but tried the other timings, still same result.
>
> Also tried running the entire system from an MMC card, same result, but my
> test had
> to run a little longer.
>
> Found a quicker test to reproduce the error, a little C-program:
>
> #include
> #include
> #include
>
> int main(void){
> long long var=0;
>
> int *ptr=NULL;
>
> int run=1;
> while(run){
> ptr=malloc(sizeof(int)*1000);
> if(ptr==NULL){
> run=0;
> }
> var+=1000;
> printf("mallocsize = %lld\n",var*sizeof(int));
> }
> }
>
>
> Booting from NFS, the system crashes at ~40mb allocated
> On MMC at ~60MB
>
> Med venlig hilsen/Best regards
>
> Casper Mogensen
>
> ________
> From: Tony Lindgren
> Sent: Friday, June 20, 2014 11:14
> To: Casper Lyngesen Mogensen
> Cc: linux-omap@vger.kernel.org
> Subject: Re: OMAP 3630 random crashes
>
> Hi,
>
> * Casper Lyngesen Mogensen [140620 01:52]:
>> Hi
>>
>> I have custom board with a Gumstix Overo, my board is similar to a
>> Tobi board. Right now i have it running with a 3.5.0 kernel. I'm
>> trying to upgrade the kernel, and have tried several versions (3.10 ->
>> 3.15) and i seem to be hitting the same problem with all versions, i
>> get random crashes. Found a way to trigger the crash within
>> minutes/seconds:
>>
>> # dd if=/dev/urandom of=/tmp/test.file bs=1024 count=10
>>
>> A count > 1 will at some point trigger the crash. The hang/crash
>> is repeatable everytime but the log is not, sometimes i do not get
>> any trace at all. I can provide more logs if necessary. Config and
>> crash log are below..
>>
>> Have tried disabling various peripherals, such as sound, usb,
>> ethernet, wifi, bluetooth, but with no luck. Also tried different Overo
>> boards.
>>
>> Hope someone can help me/point me in the right direction
>
> I was seeing similar issues with NFSroot until commit dcf21919
> (ARM: dts: Fix GPMC timings for LAN9220). Turns out LAN9220 has
> much slower timings compared to LAN9221. So you need to check that
> you're using right timings if you have LAN9220.
>
> Also, check what rate your bootloader is setting the L3 speed.
> If it's set to 200MHz, then LAN9220 timings seem to overflow the
> GPMC registers for the calculated values and bootloader timings
> are used instead.
>
>> Starting kernel ...
>>
>> [0.00] Booting Linux on physical CPU 0x0
>> [0.00] Linux version 3.15.0 (clmo@N66266) (gcc version 4.8.1
>> (crosstool-NG 1.19.0) ) #3 SMP Wed Jun 11 23:50:13 CEST 2014
>> [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7),
>> cr=10c5387d
>> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
>> instruction cache
>> [0.00] Machine model: OMAP36xx/AM37xx/DM37xx Gumstix Overo on Tobi
>> [0.00] cma: CMA: reserved 16 MiB at 8d80
>> [0.00] Memory policy: Data cache writeback
>> [0.00] CPU: All CPU(s) started in SVC mode.
>> [0.00] OMAP3630 ES1.2 (l2cache neon isp 192
RE: OMAP 3630 random crashes
Hi
The memory on the Overo, i have with me right now, is actually marked JW513,
and 18 months is also around the time, they were bought. Will check my other
modules, when i get back to the office.
However i have not been able to recreate the problem with the 3.5.0 kernel on
same Overo
Med venlig hilsen/Best regards
Casper Mogensen
From: ashchar...@gmail.com on behalf of Ash Charles
Sent: Friday, June 20, 2014 16:17
To: Casper Lyngesen Mogensen
Cc: Tony Lindgren; linux-omap@vger.kernel.org
Subject: Re: OMAP 3630 random crashes
Hi Casper,
What is the top-side marking on the memory chip on your Overo? There
were some random faults due to poor memory chips marked 'JW513' from
about 18 months ago.
--Ash
On Fri, Jun 20, 2014 at 7:00 AM, Casper Lyngesen Mogensen
wrote:
> Hi
>
> U-boot seems to set the speed to 165 Mhz
> "OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz"
>
> I have a LAN9221, but tried the other timings, still same result.
>
> Also tried running the entire system from an MMC card, same result, but my
> test had
> to run a little longer.
>
> Found a quicker test to reproduce the error, a little C-program:
>
> #include
> #include
> #include
>
> int main(void){
> long long var=0;
>
> int *ptr=NULL;
>
> int run=1;
> while(run){
> ptr=malloc(sizeof(int)*1000);
> if(ptr==NULL){
> run=0;
> }
> var+=1000;
> printf("mallocsize = %lld\n",var*sizeof(int));
> }
> }
>
>
> Booting from NFS, the system crashes at ~40mb allocated
> On MMC at ~60MB
>
> Med venlig hilsen/Best regards
>
> Casper Mogensen
>
> ________
> From: Tony Lindgren
> Sent: Friday, June 20, 2014 11:14
> To: Casper Lyngesen Mogensen
> Cc: linux-omap@vger.kernel.org
> Subject: Re: OMAP 3630 random crashes
>
> Hi,
>
> * Casper Lyngesen Mogensen [140620 01:52]:
>> Hi
>>
>> I have custom board with a Gumstix Overo, my board is similar to a
>> Tobi board. Right now i have it running with a 3.5.0 kernel. I'm
>> trying to upgrade the kernel, and have tried several versions (3.10 ->
>> 3.15) and i seem to be hitting the same problem with all versions, i
>> get random crashes. Found a way to trigger the crash within
>> minutes/seconds:
>>
>> # dd if=/dev/urandom of=/tmp/test.file bs=1024 count=10
>>
>> A count > 1 will at some point trigger the crash. The hang/crash
>> is repeatable everytime but the log is not, sometimes i do not get
>> any trace at all. I can provide more logs if necessary. Config and
>> crash log are below..
>>
>> Have tried disabling various peripherals, such as sound, usb,
>> ethernet, wifi, bluetooth, but with no luck. Also tried different Overo
>> boards.
>>
>> Hope someone can help me/point me in the right direction
>
> I was seeing similar issues with NFSroot until commit dcf21919
> (ARM: dts: Fix GPMC timings for LAN9220). Turns out LAN9220 has
> much slower timings compared to LAN9221. So you need to check that
> you're using right timings if you have LAN9220.
>
> Also, check what rate your bootloader is setting the L3 speed.
> If it's set to 200MHz, then LAN9220 timings seem to overflow the
> GPMC registers for the calculated values and bootloader timings
> are used instead.
>
>> Starting kernel ...
>>
>> [0.00] Booting Linux on physical CPU 0x0
>> [0.00] Linux version 3.15.0 (clmo@N66266) (gcc version 4.8.1
>> (crosstool-NG 1.19.0) ) #3 SMP Wed Jun 11 23:50:13 CEST 2014
>> [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7),
>> cr=10c5387d
>> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
>> instruction cache
>> [0.00] Machine model: OMAP36xx/AM37xx/DM37xx Gumstix Overo on Tobi
>> [0.00] cma: CMA: reserved 16 MiB at 8d80
>> [0.00] Memory policy: Data cache writeback
>> [0.00] CPU: All CPU(s) started in SVC mode.
>> [0.00] OMAP3630 ES1.2 (l2cache neon isp 192mhz_clk )
>> [0.00] PERCPU: Embedded 9 pages/cpu @cecc6000 s14080 r8192 d14592
>> u36864
>> [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total
>> pages: 60704
>> [0.00] Kernel command line: console=ttyO2,115200n8 root=/dev/nfs
>> nfsroot=192.168.100.1:/export/bbroot,nolock rw
>> ip=192.168.100.7::192.168.100.1:::eth0:off mem=240M
>
> Maybe also check if your test works with NFSroot idsabled.
>
> Regards,
>
> Tony
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP 3630 random crashes
Hi Casper,
What is the top-side marking on the memory chip on your Overo? There
were some random faults due to poor memory chips marked 'JW513' from
about 18 months ago.
--Ash
On Fri, Jun 20, 2014 at 7:00 AM, Casper Lyngesen Mogensen
wrote:
> Hi
>
> U-boot seems to set the speed to 165 Mhz
> "OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz"
>
> I have a LAN9221, but tried the other timings, still same result.
>
> Also tried running the entire system from an MMC card, same result, but my
> test had
> to run a little longer.
>
> Found a quicker test to reproduce the error, a little C-program:
>
> #include
> #include
> #include
>
> int main(void){
> long long var=0;
>
> int *ptr=NULL;
>
> int run=1;
> while(run){
> ptr=malloc(sizeof(int)*1000);
> if(ptr==NULL){
> run=0;
> }
> var+=1000;
> printf("mallocsize = %lld\n",var*sizeof(int));
> }
> }
>
>
> Booting from NFS, the system crashes at ~40mb allocated
> On MMC at ~60MB
>
> Med venlig hilsen/Best regards
>
> Casper Mogensen
>
> ________
> From: Tony Lindgren
> Sent: Friday, June 20, 2014 11:14
> To: Casper Lyngesen Mogensen
> Cc: linux-omap@vger.kernel.org
> Subject: Re: OMAP 3630 random crashes
>
> Hi,
>
> * Casper Lyngesen Mogensen [140620 01:52]:
>> Hi
>>
>> I have custom board with a Gumstix Overo, my board is similar to a
>> Tobi board. Right now i have it running with a 3.5.0 kernel. I'm
>> trying to upgrade the kernel, and have tried several versions (3.10 ->
>> 3.15) and i seem to be hitting the same problem with all versions, i
>> get random crashes. Found a way to trigger the crash within
>> minutes/seconds:
>>
>> # dd if=/dev/urandom of=/tmp/test.file bs=1024 count=10
>>
>> A count > 1 will at some point trigger the crash. The hang/crash
>> is repeatable everytime but the log is not, sometimes i do not get
>> any trace at all. I can provide more logs if necessary. Config and
>> crash log are below..
>>
>> Have tried disabling various peripherals, such as sound, usb,
>> ethernet, wifi, bluetooth, but with no luck. Also tried different Overo
>> boards.
>>
>> Hope someone can help me/point me in the right direction
>
> I was seeing similar issues with NFSroot until commit dcf21919
> (ARM: dts: Fix GPMC timings for LAN9220). Turns out LAN9220 has
> much slower timings compared to LAN9221. So you need to check that
> you're using right timings if you have LAN9220.
>
> Also, check what rate your bootloader is setting the L3 speed.
> If it's set to 200MHz, then LAN9220 timings seem to overflow the
> GPMC registers for the calculated values and bootloader timings
> are used instead.
>
>> Starting kernel ...
>>
>> [0.00] Booting Linux on physical CPU 0x0
>> [0.00] Linux version 3.15.0 (clmo@N66266) (gcc version 4.8.1
>> (crosstool-NG 1.19.0) ) #3 SMP Wed Jun 11 23:50:13 CEST 2014
>> [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7),
>> cr=10c5387d
>> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
>> instruction cache
>> [0.00] Machine model: OMAP36xx/AM37xx/DM37xx Gumstix Overo on Tobi
>> [0.00] cma: CMA: reserved 16 MiB at 8d80
>> [0.00] Memory policy: Data cache writeback
>> [0.00] CPU: All CPU(s) started in SVC mode.
>> [0.00] OMAP3630 ES1.2 (l2cache neon isp 192mhz_clk )
>> [0.00] PERCPU: Embedded 9 pages/cpu @cecc6000 s14080 r8192 d14592
>> u36864
>> [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total
>> pages: 60704
>> [0.00] Kernel command line: console=ttyO2,115200n8 root=/dev/nfs
>> nfsroot=192.168.100.1:/export/bbroot,nolock rw
>> ip=192.168.100.7::192.168.100.1:::eth0:off mem=240M
>
> Maybe also check if your test works with NFSroot idsabled.
>
> Regards,
>
> Tony
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: OMAP 3630 random crashes
Hi
U-boot seems to set the speed to 165 Mhz
"OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz"
I have a LAN9221, but tried the other timings, still same result.
Also tried running the entire system from an MMC card, same result, but my test
had
to run a little longer.
Found a quicker test to reproduce the error, a little C-program:
#include
#include
#include
int main(void){
long long var=0;
int *ptr=NULL;
int run=1;
while(run){
ptr=malloc(sizeof(int)*1000);
if(ptr==NULL){
run=0;
}
var+=1000;
printf("mallocsize = %lld\n",var*sizeof(int));
}
}
Booting from NFS, the system crashes at ~40mb allocated
On MMC at ~60MB
Med venlig hilsen/Best regards
Casper Mogensen
From: Tony Lindgren
Sent: Friday, June 20, 2014 11:14
To: Casper Lyngesen Mogensen
Cc: linux-omap@vger.kernel.org
Subject: Re: OMAP 3630 random crashes
Hi,
* Casper Lyngesen Mogensen [140620 01:52]:
> Hi
>
> I have custom board with a Gumstix Overo, my board is similar to a
> Tobi board. Right now i have it running with a 3.5.0 kernel. I'm
> trying to upgrade the kernel, and have tried several versions (3.10 ->
> 3.15) and i seem to be hitting the same problem with all versions, i
> get random crashes. Found a way to trigger the crash within
> minutes/seconds:
>
> # dd if=/dev/urandom of=/tmp/test.file bs=1024 count=10
>
> A count > 1 will at some point trigger the crash. The hang/crash
> is repeatable everytime but the log is not, sometimes i do not get
> any trace at all. I can provide more logs if necessary. Config and
> crash log are below..
>
> Have tried disabling various peripherals, such as sound, usb,
> ethernet, wifi, bluetooth, but with no luck. Also tried different Overo
> boards.
>
> Hope someone can help me/point me in the right direction
I was seeing similar issues with NFSroot until commit dcf21919
(ARM: dts: Fix GPMC timings for LAN9220). Turns out LAN9220 has
much slower timings compared to LAN9221. So you need to check that
you're using right timings if you have LAN9220.
Also, check what rate your bootloader is setting the L3 speed.
If it's set to 200MHz, then LAN9220 timings seem to overflow the
GPMC registers for the calculated values and bootloader timings
are used instead.
> Starting kernel ...
>
> [0.00] Booting Linux on physical CPU 0x0
> [0.00] Linux version 3.15.0 (clmo@N66266) (gcc version 4.8.1
> (crosstool-NG 1.19.0) ) #3 SMP Wed Jun 11 23:50:13 CEST 2014
> [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
> instruction cache
> [0.00] Machine model: OMAP36xx/AM37xx/DM37xx Gumstix Overo on Tobi
> [0.00] cma: CMA: reserved 16 MiB at 8d80
> [0.00] Memory policy: Data cache writeback
> [0.00] CPU: All CPU(s) started in SVC mode.
> [0.00] OMAP3630 ES1.2 (l2cache neon isp 192mhz_clk )
> [0.00] PERCPU: Embedded 9 pages/cpu @cecc6000 s14080 r8192 d14592
> u36864
> [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total
> pages: 60704
> [0.00] Kernel command line: console=ttyO2,115200n8 root=/dev/nfs
> nfsroot=192.168.100.1:/export/bbroot,nolock rw
> ip=192.168.100.7::192.168.100.1:::eth0:off mem=240M
Maybe also check if your test works with NFSroot idsabled.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: OMAP 3630 random crashes
Hi, * Casper Lyngesen Mogensen [140620 01:52]: > Hi > > I have custom board with a Gumstix Overo, my board is similar to a > Tobi board. Right now i have it running with a 3.5.0 kernel. I'm > trying to upgrade the kernel, and have tried several versions (3.10 -> > 3.15) and i seem to be hitting the same problem with all versions, i > get random crashes. Found a way to trigger the crash within > minutes/seconds: > > # dd if=/dev/urandom of=/tmp/test.file bs=1024 count=10 > > A count > 1 will at some point trigger the crash. The hang/crash > is repeatable everytime but the log is not, sometimes i do not get > any trace at all. I can provide more logs if necessary. Config and > crash log are below.. > > Have tried disabling various peripherals, such as sound, usb, > ethernet, wifi, bluetooth, but with no luck. Also tried different Overo > boards. > > Hope someone can help me/point me in the right direction I was seeing similar issues with NFSroot until commit dcf21919 (ARM: dts: Fix GPMC timings for LAN9220). Turns out LAN9220 has much slower timings compared to LAN9221. So you need to check that you're using right timings if you have LAN9220. Also, check what rate your bootloader is setting the L3 speed. If it's set to 200MHz, then LAN9220 timings seem to overflow the GPMC registers for the calculated values and bootloader timings are used instead. > Starting kernel ... > > [0.00] Booting Linux on physical CPU 0x0 > [0.00] Linux version 3.15.0 (clmo@N66266) (gcc version 4.8.1 > (crosstool-NG 1.19.0) ) #3 SMP Wed Jun 11 23:50:13 CEST 2014 > [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d > [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing > instruction cache > [0.00] Machine model: OMAP36xx/AM37xx/DM37xx Gumstix Overo on Tobi > [0.00] cma: CMA: reserved 16 MiB at 8d80 > [0.00] Memory policy: Data cache writeback > [0.00] CPU: All CPU(s) started in SVC mode. > [0.00] OMAP3630 ES1.2 (l2cache neon isp 192mhz_clk ) > [0.00] PERCPU: Embedded 9 pages/cpu @cecc6000 s14080 r8192 d14592 > u36864 > [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total > pages: 60704 > [0.00] Kernel command line: console=ttyO2,115200n8 root=/dev/nfs > nfsroot=192.168.100.1:/export/bbroot,nolock rw > ip=192.168.100.7::192.168.100.1:::eth0:off mem=240M Maybe also check if your test works with NFSroot idsabled. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
OMAP 3630 random crashes
Hi I have custom board with a Gumstix Overo, my board is similar to a Tobi board. Right now i have it running with a 3.5.0 kernel. I'm trying to upgrade the kernel, and have tried several versions (3.10 -> 3.15) and i seem to be hitting the same problem with all versions, i get random crashes. Found a way to trigger the crash within minutes/seconds: # dd if=/dev/urandom of=/tmp/test.file bs=1024 count=10 A count > 1 will at some point trigger the crash. The hang/crash is repeatable everytime but the log is not, sometimes i do not get any trace at all. I can provide more logs if necessary. Config and crash log are below.. Have tried disabling various peripherals, such as sound, usb, ethernet, wifi, bluetooth, but with no luck. Also tried different Overo boards. Hope someone can help me/point me in the right direction Starting kernel ... [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 3.15.0 (clmo@N66266) (gcc version 4.8.1 (crosstool-NG 1.19.0) ) #3 SMP Wed Jun 11 23:50:13 CEST 2014 [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [0.00] Machine model: OMAP36xx/AM37xx/DM37xx Gumstix Overo on Tobi [0.00] cma: CMA: reserved 16 MiB at 8d80 [0.00] Memory policy: Data cache writeback [0.00] CPU: All CPU(s) started in SVC mode. [0.00] OMAP3630 ES1.2 (l2cache neon isp 192mhz_clk ) [0.00] PERCPU: Embedded 9 pages/cpu @cecc6000 s14080 r8192 d14592 u36864 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60704 [0.00] Kernel command line: console=ttyO2,115200n8 root=/dev/nfs nfsroot=192.168.100.1:/export/bbroot,nolock rw ip=192.168.100.7::192.168.100.1:::eth0:off mem=240M [0.00] PID hash table entries: 1024 (order: 0, 4096 bytes) [0.00] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [0.00] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [0.00] Memory: 211448K/244736K available (5624K kernel code, 655K rwdata, 2148K rodata, 389K init, 5527K bss, 33288K reserved, 0K highmem) [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xfff0 - 0xfffe ( 896 kB) [0.00] vmalloc : 0xcf80 - 0xff00 ( 760 MB) [0.00] lowmem : 0xc000 - 0xcf00 ( 240 MB) [0.00] pkmap : 0xbfe0 - 0xc000 ( 2 MB) [0.00] modules : 0xbf00 - 0xbfe0 ( 14 MB) [0.00] .text : 0xc0008000 - 0xc079f520 (7774 kB) [0.00] .init : 0xc07a - 0xc0801700 ( 390 kB) [0.00] .data : 0xc0802000 - 0xc08a5e40 ( 656 kB) [0.00].bss : 0xc08a5e40 - 0xc0e0bdc8 (5528 kB) [0.00] Hierarchical RCU implementation. [0.00] RCU restricting CPUs from NR_CPUS=2 to nr_cpu_ids=1. [0.00] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 [0.00] NR_IRQS:16 nr_irqs:16 16 [0.00] IRQ: Found an INTC at 0xfa20 (revision 4.0) with 96 interrupts [0.00] Total of 96 interrupts on 1 active controller [0.00] Clocking rate (Crystal/Core/MPU): 26.0/400/600 MHz [0.00] OMAP clockevent source: timer1 at 32768 Hz [0.30] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 655360ns [0.30] OMAP clocksource: 32k_counter at 32768 Hz [0.001159] Console: colour dummy device 80x30 [0.001220] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar [0.001220] ... MAX_LOCKDEP_SUBCLASSES: 8 [0.001251] ... MAX_LOCK_DEPTH: 48 [0.001251] ... MAX_LOCKDEP_KEYS:8191 [0.001281] ... CLASSHASH_SIZE: 4096 [0.001281] ... MAX_LOCKDEP_ENTRIES: 16384 [0.001312] ... MAX_LOCKDEP_CHAINS: 32768 [0.001312] ... CHAINHASH_SIZE: 16384 [0.001312] memory used by lock dependency info: 3695 kB [0.001342] per task-struct memory footprint: 1152 bytes [0.001403] Calibrating delay loop... 594.73 BogoMIPS (lpj=2973696) [0.097656] pid_max: default: 32768 minimum: 301 [0.098266] Security Framework initialized [0.098449] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.098480] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.102508] CPU: Testing write buffer coherency: ok [0.104125] CPU0: thread -1, cpu 0, socket -1, mpidr 0 [0.104187] Setting up static identity map for 0x805568a8 - 0x80556918 [0.108673] Brought up 1 CPUs [0.108703] SMP: Total of 1 processors activated. [0.108703] CPU: All CPU(s) started in SVC mode. [0.112609] devtmpfs: initialized [0.123229] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3 [0.203124] omap_hwmod: mcbsp2_sidetone using br
