From: Manish S. <man...@gm...> - 2011-11-14 21:07:28
|
Hi , I am using linux 2.6.32 and gb 2.6.4 in overo module. When I turn on device for 2/3 days, I see following error sometimes.It seems like I2C for Power management IC got stuck. What might cause this kind of problem? Pid: 326, comm: twl4030-irq CPU: 0 Tainted: P (2.6.32 #11) PC is at omap_i2c_isr+0x280/0x350 LR is at handle_IRQ_event+0xa8/0x1ec pc : [<c035ab74>] lr : [<c009efd8>] psr: 40000113 sp : cf8ebda0 ip : 0000003c fp : c0700b20 r10: 00000002 r9 : c0700b00 r8 : 0000601f r7 : 00000001 r6 : 00000000 r5 : 00004000 r4 : cf884e00 r3 : 00000001 r2 : fa070000 r1 : 00000000 r0 : 0000002e Flags: nZcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel Control: 10c5387d Table: 87214019 DAC: 00000017 PC: 0xc035aaf4: aaf4 e5842034 9a00001d ea00001e e3150010 0a000006 e5940000 ebfca271 e5943000 ab14 e5932008 e1a01000 e59f0110 eb065978 e3150901 0a000019 e5940000 ebfca268 ab34 e5943000 e5932008 e1a01000 e59f00f0 eb06596f ea000011 e3150003 0a000005 ab54 e5942004 e3043010 e0053003 e3866b01 e1c230b8 eaffff78 e5942004 e1d250b8 ab74 e3150b01 0afffff3 e2433001 e5942004 e6ef3073 e1c201bc e3530000 1affffce ab94 e5942004 e3043010 e0053003 e1c230b8 ea000017 e3150b02 0a000009 e5940000 abb4 ebfca247 e5943000 e5932008 e1a01000 e59f0070 eb06594e e1d433b0 e3833b02 abd4 e1c433b0 e3150b01 0a000009 e5940000 ebfca23b e5943000 e5932008 e1a01000 -- Manish Shakya http://www.manishshakya.com.np <http://secs.oakland.edu/%7Eganesan/iMX/> |
From: Saravanakrishnan <kri...@gm...> - 2011-11-17 00:30:20
|
I am also facing the same issue. Does anyone have some pointers? On Mon, Nov 14, 2011 at 2:07 PM, Manish Shakya <man...@gm...>wrote: > Hi , > > I am using linux 2.6.32 and gb 2.6.4 in overo module. When I turn on > device for 2/3 days, I see following error sometimes.It seems like I2C for > Power management IC got stuck. What might cause this kind of problem? > > Pid: 326, comm: twl4030-irq > CPU: 0 Tainted: P (2.6.32 #11) > PC is at omap_i2c_isr+0x280/0x350 > LR is at handle_IRQ_event+0xa8/0x1ec > pc : [<c035ab74>] lr : [<c009efd8>] psr: 40000113 > sp : cf8ebda0 ip : 0000003c fp : c0700b20 > r10: 00000002 r9 : c0700b00 r8 : 0000601f > r7 : 00000001 r6 : 00000000 r5 : 00004000 r4 : cf884e00 > r3 : 00000001 r2 : fa070000 r1 : 00000000 r0 : 0000002e > Flags: nZcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel > Control: 10c5387d Table: 87214019 DAC: 00000017 > > PC: 0xc035aaf4: > aaf4 e5842034 9a00001d ea00001e e3150010 0a000006 e5940000 ebfca271 > e5943000 > ab14 e5932008 e1a01000 e59f0110 eb065978 e3150901 0a000019 e5940000 > ebfca268 > ab34 e5943000 e5932008 e1a01000 e59f00f0 eb06596f ea000011 e3150003 > 0a000005 > ab54 e5942004 e3043010 e0053003 e3866b01 e1c230b8 eaffff78 e5942004 > e1d250b8 > ab74 e3150b01 0afffff3 e2433001 e5942004 e6ef3073 e1c201bc e3530000 > 1affffce > ab94 e5942004 e3043010 e0053003 e1c230b8 ea000017 e3150b02 0a000009 > e5940000 > abb4 ebfca247 e5943000 e5932008 e1a01000 e59f0070 eb06594e e1d433b0 > e3833b02 > abd4 e1c433b0 e3150b01 0a000009 e5940000 ebfca23b e5943000 e5932008 > e1a01000 > > > > -- > Manish Shakya > http://www.manishshakya.com.np > <http://secs.oakland.edu/%7Eganesan/iMX/> > > -- > You received this message because you are subscribed to the Google Groups > "rowboat" group. > To post to this group, send email to ro...@go.... > To unsubscribe from this group, send email to > row...@go.... > For more options, visit this group at > http://groups.google.com/group/rowboat?hl=en. > |
From: Manish S. <man...@gm...> - 2011-11-17 14:28:50
|
Hi Saravanakrishnan, How often do you see this problem? Are you also using 2.6.32 kernel? On Wed, Nov 16, 2011 at 7:29 PM, Saravanakrishnan < kri...@gm...> wrote: > I am also facing the same issue. Does anyone have some pointers? > > On Mon, Nov 14, 2011 at 2:07 PM, Manish Shakya <man...@gm...>wrote: > >> Hi , >> >> I am using linux 2.6.32 and gb 2.6.4 in overo module. When I turn on >> device for 2/3 days, I see following error sometimes.It seems like I2C for >> Power management IC got stuck. What might cause this kind of problem? >> >> Pid: 326, comm: twl4030-irq >> CPU: 0 Tainted: P (2.6.32 #11) >> PC is at omap_i2c_isr+0x280/0x350 >> LR is at handle_IRQ_event+0xa8/0x1ec >> pc : [<c035ab74>] lr : [<c009efd8>] psr: 40000113 >> sp : cf8ebda0 ip : 0000003c fp : c0700b20 >> r10: 00000002 r9 : c0700b00 r8 : 0000601f >> r7 : 00000001 r6 : 00000000 r5 : 00004000 r4 : cf884e00 >> r3 : 00000001 r2 : fa070000 r1 : 00000000 r0 : 0000002e >> Flags: nZcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel >> Control: 10c5387d Table: 87214019 DAC: 00000017 >> >> PC: 0xc035aaf4: >> aaf4 e5842034 9a00001d ea00001e e3150010 0a000006 e5940000 ebfca271 >> e5943000 >> ab14 e5932008 e1a01000 e59f0110 eb065978 e3150901 0a000019 e5940000 >> ebfca268 >> ab34 e5943000 e5932008 e1a01000 e59f00f0 eb06596f ea000011 e3150003 >> 0a000005 >> ab54 e5942004 e3043010 e0053003 e3866b01 e1c230b8 eaffff78 e5942004 >> e1d250b8 >> ab74 e3150b01 0afffff3 e2433001 e5942004 e6ef3073 e1c201bc e3530000 >> 1affffce >> ab94 e5942004 e3043010 e0053003 e1c230b8 ea000017 e3150b02 0a000009 >> e5940000 >> abb4 ebfca247 e5943000 e5932008 e1a01000 e59f0070 eb06594e e1d433b0 >> e3833b02 >> abd4 e1c433b0 e3150b01 0a000009 e5940000 ebfca23b e5943000 e5932008 >> e1a01000 >> >> >> >> >> -- >> Manish Shakya >> http://www.manishshakya.com.np >> <http://secs.oakland.edu/%7Eganesan/iMX/> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "rowboat" group. >> To post to this group, send email to ro...@go.... >> To unsubscribe from this group, send email to >> row...@go.... >> For more options, visit this group at >> http://groups.google.com/group/rowboat?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "rowboat" group. > To post to this group, send email to ro...@go.... > To unsubscribe from this group, send email to > row...@go.... > For more options, visit this group at > http://groups.google.com/group/rowboat?hl=en. > -- Manish Shakya http://www.manishshakya.com.np http://secs.oakland.edu/~ganesan/iMX/ |
From: Ash C. <ash...@gm...> - 2011-11-22 03:28:35
|
Hi Manish, On Thu, Nov 17, 2011 at 6:28 AM, Manish Shakya <man...@gm...> wrote: > How often do you see this problem? Are you also using 2.6.32 kernel? I've also seen this problem on Overo with the 2.6.32 android kernel. Does it get better if you turn off any watchdogs provided by the PMIC? Also, the linaro-android kernel has some recent patches for OMAP3---I just did a build here: https://android-build.linaro.org/builds/~ashcharles/test-gumstix/ -Ash |
From: Manish S. <man...@gm...> - 2011-11-22 04:15:19
|
It seems like when TWL ADC (MADC) is turned on, the problem shows up. Since, there is no deterministic way to regenerate the problem, so cann't say disabling TWL ADC fix the problem. I am testing it with disabling TWL ADC. In kernel 2.6.38, I haven't seen the problem till now.Need to do more testing. Do you know what is the root causes iof the problem? I will try linaro-android kernel build. Do you what kind of patches has been applied? Thanks. On Mon, Nov 21, 2011 at 10:27 PM, Ash Charles <ash...@gm...> wrote: > Hi Manish, > > On Thu, Nov 17, 2011 at 6:28 AM, Manish Shakya > <man...@gm...> wrote: > > How often do you see this problem? Are you also using 2.6.32 kernel? > I've also seen this problem on Overo with the 2.6.32 android kernel. > Does it get better if you turn off any watchdogs provided by the PMIC? > Also, the linaro-android kernel has some recent patches for OMAP3---I > just did a build here: > https://android-build.linaro.org/builds/~ashcharles/test-gumstix/ > > -Ash > > -- > You received this message because you are subscribed to the Google Groups > "rowboat" group. > To post to this group, send email to ro...@go.... > To unsubscribe from this group, send email to > row...@go.... > For more options, visit this group at > http://groups.google.com/group/rowboat?hl=en. > > -- Manish Shakya http://www.manishshakya.com.np http://secs.oakland.edu/~ganesan/iMX/ |
From: Ash C. <ash...@gm...> - 2011-12-02 06:37:59
|
Hi Manish, On Mon, Nov 21, 2011 at 8:15 PM, Manish Shakya <man...@gm...> wrote: > Do you know what is the root causes iof the problem? I've not dug into it at all---I noticed the issue and reacted to get rid of the warning message only ;-) > > I will try linaro-android kernel build. Do you what kind of patches has been > applied? I'm essentially using the linaro-android build for Beagle. The Linaro guys have put lots of work into support for OMAP3 and have a nice 4.6 toolchain. The build uses a >3.0 kernel and is for Android 2.3.7. -Ash |
From: Manish S. <man...@gm...> - 2011-12-02 17:48:00
|
Hi Ash, I tried your linaro it works but it does not have sgx and need to fix touchscreen too.I also had to modify pthyon script to generate boot script. I seems like linaro is going to stop beagle board support. I guess it not good idea to use it. What you say? On Fri, Dec 2, 2011 at 1:37 AM, Ash Charles <ash...@gm...> wrote: > Hi Manish, > > On Mon, Nov 21, 2011 at 8:15 PM, Manish Shakya > <man...@gm...> wrote: > > Do you know what is the root causes iof the problem? > I've not dug into it at all---I noticed the issue and reacted to get > rid of the warning message only ;-) > > > > I will try linaro-android kernel build. Do you what kind of patches has > been > > applied? > I'm essentially using the linaro-android build for Beagle. The Linaro > guys have put lots of work into support for OMAP3 and have a nice 4.6 > toolchain. The build uses a >3.0 kernel and is for Android 2.3.7. > > -Ash > -- Manish Shakya http://www.manishshakya.com.np http://secs.oakland.edu/~ganesan/iMX/ |
From: Ash C. <ash...@gm...> - 2011-12-06 17:06:34
|
Hi Manish, On Fri, Dec 2, 2011 at 9:47 AM, Manish Shakya <man...@gm...> wrote: > I tried your linaro it works but it does not have sgx and need to fix > touchscreen too.I also had to modify pthyon script to generate boot script. > I seems like linaro is going to stop beagle board support. I guess it not > good idea to use it. What you say? I need to look through the Linaro kernel and check what support is missing. It looks like Linaro is not in fact EOLing Beagle. I think the discussion on their list was a little premature. -Ash |
From: Manish S. <man...@gm...> - 2011-12-06 18:10:17
|
Yes I agree both of build have advantages. I can't say much about linaro. It would be better if I also could contribute to the Overo Support for Android. On Tue, Dec 6, 2011 at 12:43 PM, Ash Charles <ash...@gm...> wrote: > On Tue, Dec 6, 2011 at 9:39 AM, Manish Shakya <man...@gm...> > wrote: > > Okay.. it would better if you could update your wiki for linaro build > Fair enough---I've got to try both rowboat and Linaro side-by-side as > I think both builds have their advantages. Do you have a strong > argument either way as the best way for Gumstix to support Android? > -Ash > -- Manish Shakya http://www.manishshakya.com.np http://secs.oakland.edu/~ganesan/iMX/ |
From: Keane, B. (STRX) <ben...@ka...> - 2012-03-30 00:24:33
|
Hi, Sorry to dig up an old thread - But I was hoping for an update. I am having the same issue. I am using Kernel 2.6.32 from the gumdroid project. I am wondering if the testing showed that it was the MADC? Did going to the linaro-android kernel 2.6.38 fix this problem? Your update and help is much appreciated. Ben ________________________________ From: Manish Shakya [mailto:man...@gm...] Sent: Tuesday, 22 November 2011 2:15 PM To: ro...@go...; ash...@gm... Cc: General mailing list for gumstix users. Subject: Re: [Gumstix-users] [rowboat] BUG: soft lockup - CPU#0 stuck for 61s! [twl4030-irq:326] It seems like when TWL ADC (MADC) is turned on, the problem shows up. Since, there is no deterministic way to regenerate the problem, so cann't say disabling TWL ADC fix the problem. I am testing it with disabling TWL ADC. In kernel 2.6.38, I haven't seen the problem till now.Need to do more testing. Do you know what is the root causes iof the problem? I will try linaro-android kernel build. Do you what kind of patches has been applied? Thanks. On Mon, Nov 21, 2011 at 10:27 PM, Ash Charles <ash...@gm...<mailto:ash...@gm...>> wrote: Hi Manish, On Thu, Nov 17, 2011 at 6:28 AM, Manish Shakya <man...@gm...<mailto:man...@gm...>> wrote: > How often do you see this problem? Are you also using 2.6.32 kernel? I've also seen this problem on Overo with the 2.6.32 android kernel. Does it get better if you turn off any watchdogs provided by the PMIC? Also, the linaro-android kernel has some recent patches for OMAP3---I just did a build here: https://android-build.linaro.org/builds/~ashcharles/test-gumstix/ -Ash -- You received this message because you are subscribed to the Google Groups "rowboat" group. To post to this group, send email to ro...@go...<mailto:ro...@go...>. To unsubscribe from this group, send email to row...@go...<mailto:rowboat%2Bu...@go...>. For more options, visit this group at http://groups.google.com/group/rowboat?hl=en. -- Manish Shakya http://www.manishshakya.com.np http://secs.oakland.edu/~ganesan/iMX/ ______________________________________________________________________ CAUTION: This message was sent via the Public Internet and its authenticity cannot be guaranteed. PROPRIETARY: This e-mail contains proprietary information some or all of which may be legally privileged. It is intended for the recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the authority by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or rely on this e-mail. |
From: Manish S. <man...@gm...> - 2012-03-30 01:11:56
|
I am sure that even if you remove MADC , problem won't go away. On Thu, Mar 29, 2012 at 8:24 PM, Keane, Ben (STRX) <ben...@ka...> wrote: > Hi, > > Sorry to dig up an old thread - But I was hoping for an update. > > I am having the same issue. I am using Kernel 2.6.32 from the gumdroid > project. I am wondering if the testing showed that it was the MADC? Did > going to the linaro-android kernel 2.6.38 fix this problem? > > Your update and help is much appreciated. > > Ben > > ________________________________ > From: Manish Shakya [mailto:man...@gm...] > Sent: Tuesday, 22 November 2011 2:15 PM > To: ro...@go...; ash...@gm... > Cc: General mailing list for gumstix users. > Subject: Re: [Gumstix-users] [rowboat] BUG: soft lockup - CPU#0 stuck for > 61s! [twl4030-irq:326] > > It seems like when TWL ADC (MADC) is turned on, the problem shows up. > Since, there is no deterministic way to regenerate the problem, so cann't > say disabling TWL ADC fix the problem. I am testing it with disabling TWL > ADC. > > In kernel 2.6.38, I haven't seen the problem till now.Need to do more > testing. > > Do you know what is the root causes iof the problem? > > I will try linaro-android kernel build. Do you what kind of patches has been > applied? > > Thanks. > On Mon, Nov 21, 2011 at 10:27 PM, Ash Charles <ash...@gm...> wrote: >> >> Hi Manish, >> >> On Thu, Nov 17, 2011 at 6:28 AM, Manish Shakya >> <man...@gm...> wrote: >> > How often do you see this problem? Are you also using 2.6.32 kernel? >> I've also seen this problem on Overo with the 2.6.32 android kernel. >> Does it get better if you turn off any watchdogs provided by the PMIC? >> Also, the linaro-android kernel has some recent patches for OMAP3---I >> just did a build here: >> https://android-build.linaro.org/builds/~ashcharles/test-gumstix/ >> >> -Ash >> >> -- >> You received this message because you are subscribed to the Google Groups >> "rowboat" group. >> To post to this group, send email to ro...@go.... >> To unsubscribe from this group, send email to >> row...@go.... >> For more options, visit this group at >> http://groups.google.com/group/rowboat?hl=en. >> > > > > -- > Manish Shakya > http://www.manishshakya.com.np > http://secs.oakland.edu/~ganesan/iMX/ > > ______________________________________________________________________ > CAUTION: This message was sent via the Public Internet and its authenticity > cannot be guaranteed. > > > PROPRIETARY: This e-mail contains proprietary information some or all of > which may be legally privileged. It is intended for the recipient only. If > an addressing or transmission error has misdirected this e-mail, please > notify the authority by replying to this e-mail. If you are not the intended > recipient you must not use, disclose, distribute, copy, print, or rely on > this e-mail. -- Manish Shakya http://www.manishshakya.com.np |
From: Keane, B. (STRX) <ben...@ka...> - 2012-03-30 01:14:14
|
Do you still have the problem? What Android kernel version are you using now? >-----Original Message----- >From: Manish Shakya [mailto:man...@gm...] >Sent: Friday, 30 March 2012 11:12 AM >To: Keane, Ben (STRX) >Cc: General mailing list for gumstix users.; >ro...@go...; ash...@gm... >Subject: Re: [Gumstix-users] [rowboat] BUG: soft lockup - >CPU#0 stuck for 61s! [twl4030-irq:326] > >I am sure that even if you remove MADC , problem won't go away. > >On Thu, Mar 29, 2012 at 8:24 PM, Keane, Ben (STRX) ><ben...@ka...> wrote: >> Hi, >> >> Sorry to dig up an old thread - But I was hoping for an update. >> >> I am having the same issue. I am using Kernel 2.6.32 from >the gumdroid >> project. I am wondering if the testing showed that it was >the MADC? >> Did going to the linaro-android kernel 2.6.38 fix this problem? >> >> Your update and help is much appreciated. >> >> Ben >> >> ________________________________ >> From: Manish Shakya [mailto:man...@gm...] >> Sent: Tuesday, 22 November 2011 2:15 PM >> To: ro...@go...; ash...@gm... >> Cc: General mailing list for gumstix users. >> Subject: Re: [Gumstix-users] [rowboat] BUG: soft lockup - >CPU#0 stuck >> for 61s! [twl4030-irq:326] >> >> It seems like when TWL ADC (MADC) is turned on, the problem >shows up. >> Since, there is no deterministic way to regenerate the problem, so >> cann't say disabling TWL ADC fix the problem. I am testing it with >> disabling TWL ADC. >> >> In kernel 2.6.38, I haven't seen the problem till now.Need >to do more >> testing. >> >> Do you know what is the root causes iof the problem? >> >> I will try linaro-android kernel build. Do you what kind of patches >> has been applied? >> >> Thanks. >> On Mon, Nov 21, 2011 at 10:27 PM, Ash Charles ><ash...@gm...> wrote: >>> >>> Hi Manish, >>> >>> On Thu, Nov 17, 2011 at 6:28 AM, Manish Shakya >>> <man...@gm...> wrote: >>> > How often do you see this problem? Are you also using >2.6.32 kernel? >>> I've also seen this problem on Overo with the 2.6.32 android kernel. >>> Does it get better if you turn off any watchdogs provided >by the PMIC? >>> Also, the linaro-android kernel has some recent patches for >OMAP3---I >>> just did a build here: >>> https://android-build.linaro.org/builds/~ashcharles/test-gumstix/ >>> >>> -Ash >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "rowboat" group. >>> To post to this group, send email to ro...@go.... >>> To unsubscribe from this group, send email to >>> row...@go.... >>> For more options, visit this group at >>> http://groups.google.com/group/rowboat?hl=en. >>> >> >> >> >> -- >> Manish Shakya >> http://www.manishshakya.com.np >> http://secs.oakland.edu/~ganesan/iMX/ >> >> >______________________________________________________________________ >> CAUTION: This message was sent via the Public Internet and its >> authenticity cannot be guaranteed. >> >> >> PROPRIETARY: This e-mail contains proprietary information >some or all >> of which may be legally privileged. It is intended for the recipient >> only. If an addressing or transmission error has misdirected this >> e-mail, please notify the authority by replying to this >e-mail. If you >> are not the intended recipient you must not use, disclose, >distribute, >> copy, print, or rely on this e-mail. > > > >-- >Manish Shakya >http://www.manishshakya.com.np > >______________________________________________________________________ >CAUTION: This message was sent via the Public Internet and its >authenticity cannot be guaranteed. > PROPRIETARY: This e-mail contains proprietary information some or all of which may be legally privileged. It is intended for the recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the authority by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or rely on this e-mail. |
From: Manish S. <man...@gm...> - 2012-03-30 01:15:59
|
If you use 2.6.32 there is a problem. I am trying to move to 2.6.37 On Thu, Mar 29, 2012 at 9:14 PM, Keane, Ben (STRX) <ben...@ka...> wrote: > Do you still have the problem? > > What Android kernel version are you using now? > >>-----Original Message----- >>From: Manish Shakya [mailto:man...@gm...] >>Sent: Friday, 30 March 2012 11:12 AM >>To: Keane, Ben (STRX) >>Cc: General mailing list for gumstix users.; >>ro...@go...; ash...@gm... >>Subject: Re: [Gumstix-users] [rowboat] BUG: soft lockup - >>CPU#0 stuck for 61s! [twl4030-irq:326] >> >>I am sure that even if you remove MADC , problem won't go away. >> >>On Thu, Mar 29, 2012 at 8:24 PM, Keane, Ben (STRX) >><ben...@ka...> wrote: >>> Hi, >>> >>> Sorry to dig up an old thread - But I was hoping for an update. >>> >>> I am having the same issue. I am using Kernel 2.6.32 from >>the gumdroid >>> project. I am wondering if the testing showed that it was >>the MADC? >>> Did going to the linaro-android kernel 2.6.38 fix this problem? >>> >>> Your update and help is much appreciated. >>> >>> Ben >>> >>> ________________________________ >>> From: Manish Shakya [mailto:man...@gm...] >>> Sent: Tuesday, 22 November 2011 2:15 PM >>> To: ro...@go...; ash...@gm... >>> Cc: General mailing list for gumstix users. >>> Subject: Re: [Gumstix-users] [rowboat] BUG: soft lockup - >>CPU#0 stuck >>> for 61s! [twl4030-irq:326] >>> >>> It seems like when TWL ADC (MADC) is turned on, the problem >>shows up. >>> Since, there is no deterministic way to regenerate the problem, so >>> cann't say disabling TWL ADC fix the problem. I am testing it with >>> disabling TWL ADC. >>> >>> In kernel 2.6.38, I haven't seen the problem till now.Need >>to do more >>> testing. >>> >>> Do you know what is the root causes iof the problem? >>> >>> I will try linaro-android kernel build. Do you what kind of patches >>> has been applied? >>> >>> Thanks. >>> On Mon, Nov 21, 2011 at 10:27 PM, Ash Charles >><ash...@gm...> wrote: >>>> >>>> Hi Manish, >>>> >>>> On Thu, Nov 17, 2011 at 6:28 AM, Manish Shakya >>>> <man...@gm...> wrote: >>>> > How often do you see this problem? Are you also using >>2.6.32 kernel? >>>> I've also seen this problem on Overo with the 2.6.32 android kernel. >>>> Does it get better if you turn off any watchdogs provided >>by the PMIC? >>>> Also, the linaro-android kernel has some recent patches for >>OMAP3---I >>>> just did a build here: >>>> https://android-build.linaro.org/builds/~ashcharles/test-gumstix/ >>>> >>>> -Ash >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "rowboat" group. >>>> To post to this group, send email to ro...@go.... >>>> To unsubscribe from this group, send email to >>>> row...@go.... >>>> For more options, visit this group at >>>> http://groups.google.com/group/rowboat?hl=en. >>>> >>> >>> >>> >>> -- >>> Manish Shakya >>> http://www.manishshakya.com.np >>> http://secs.oakland.edu/~ganesan/iMX/ >>> >>> >>______________________________________________________________________ >>> CAUTION: This message was sent via the Public Internet and its >>> authenticity cannot be guaranteed. >>> >>> >>> PROPRIETARY: This e-mail contains proprietary information >>some or all >>> of which may be legally privileged. It is intended for the recipient >>> only. If an addressing or transmission error has misdirected this >>> e-mail, please notify the authority by replying to this >>e-mail. If you >>> are not the intended recipient you must not use, disclose, >>distribute, >>> copy, print, or rely on this e-mail. >> >> >> >>-- >>Manish Shakya >>http://www.manishshakya.com.np >> >>______________________________________________________________________ >>CAUTION: This message was sent via the Public Internet and its >>authenticity cannot be guaranteed. >> > > PROPRIETARY: This e-mail contains proprietary information some or all of which may be legally privileged. It is intended for the recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the authority by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or rely on this e-mail. > > -- > You received this message because you are subscribed to the Google Groups "rowboat" group. > To post to this group, send email to ro...@go.... > To unsubscribe from this group, send email to row...@go.... > For more options, visit this group at http://groups.google.com/group/rowboat?hl=en. > -- Manish Shakya http://www.manishshakya.com.np |
From: Keane, B. (STRX) <ben...@ka...> - 2012-03-30 01:51:19
|
Where are you getting the source from? Why did you choose 2.6.37? Previously you mentioned 2.6.38 - did that not work? >-----Original Message----- >From: Manish Shakya [mailto:man...@gm...] >Sent: Friday, 30 March 2012 11:16 AM >To: ro...@go... >Cc: General mailing list for gumstix users. >Subject: Re: [Gumstix-users] [rowboat] BUG: soft lockup - >CPU#0 stuck for 61s! [twl4030-irq:326] > >If you use 2.6.32 there is a problem. I am trying to move to 2.6.37 > >On Thu, Mar 29, 2012 at 9:14 PM, Keane, Ben (STRX) ><ben...@ka...> wrote: >> Do you still have the problem? >> >> What Android kernel version are you using now? >> >>>-----Original Message----- >>>From: Manish Shakya [mailto:man...@gm...] >>>Sent: Friday, 30 March 2012 11:12 AM >>>To: Keane, Ben (STRX) >>>Cc: General mailing list for gumstix users.; >ro...@go...; >>>ash...@gm... >>>Subject: Re: [Gumstix-users] [rowboat] BUG: soft lockup - >CPU#0 stuck >>>for 61s! [twl4030-irq:326] >>> >>>I am sure that even if you remove MADC , problem won't go away. >>> >>>On Thu, Mar 29, 2012 at 8:24 PM, Keane, Ben (STRX) >>><ben...@ka...> wrote: >>>> Hi, >>>> >>>> Sorry to dig up an old thread - But I was hoping for an update. >>>> >>>> I am having the same issue. I am using Kernel 2.6.32 from >>>the gumdroid >>>> project. I am wondering if the testing showed that it was >>>the MADC? >>>> Did going to the linaro-android kernel 2.6.38 fix this problem? >>>> >>>> Your update and help is much appreciated. >>>> >>>> Ben >>>> >>>> ________________________________ >>>> From: Manish Shakya [mailto:man...@gm...] >>>> Sent: Tuesday, 22 November 2011 2:15 PM >>>> To: ro...@go...; ash...@gm... >>>> Cc: General mailing list for gumstix users. >>>> Subject: Re: [Gumstix-users] [rowboat] BUG: soft lockup - >>>CPU#0 stuck >>>> for 61s! [twl4030-irq:326] >>>> >>>> It seems like when TWL ADC (MADC) is turned on, the problem >>>shows up. >>>> Since, there is no deterministic way to regenerate the problem, so >>>> cann't say disabling TWL ADC fix the problem. I am testing >it with >>>> disabling TWL ADC. >>>> >>>> In kernel 2.6.38, I haven't seen the problem till now.Need >>>to do more >>>> testing. >>>> >>>> Do you know what is the root causes iof the problem? >>>> >>>> I will try linaro-android kernel build. Do you what kind >of patches >>>> has been applied? >>>> >>>> Thanks. >>>> On Mon, Nov 21, 2011 at 10:27 PM, Ash Charles >>><ash...@gm...> wrote: >>>>> >>>>> Hi Manish, >>>>> >>>>> On Thu, Nov 17, 2011 at 6:28 AM, Manish Shakya >>>>> <man...@gm...> wrote: >>>>> > How often do you see this problem? Are you also using >>>2.6.32 kernel? >>>>> I've also seen this problem on Overo with the 2.6.32 >android kernel. >>>>> Does it get better if you turn off any watchdogs provided >>>by the PMIC? >>>>> Also, the linaro-android kernel has some recent patches for >>>OMAP3---I >>>>> just did a build here: >>>>> https://android-build.linaro.org/builds/~ashcharles/test-gumstix/ >>>>> >>>>> -Ash >>>>> >>>>> -- >>>>> You received this message because you are subscribed to >the Google >>>>> Groups "rowboat" group. >>>>> To post to this group, send email to ro...@go.... >>>>> To unsubscribe from this group, send email to >>>>> row...@go.... >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/rowboat?hl=en. >>>>> >>>> >>>> >>>> >>>> -- >>>> Manish Shakya >>>> http://www.manishshakya.com.np >>>> http://secs.oakland.edu/~ganesan/iMX/ >>>> >>>> >>>_____________________________________________________________ >_________ >>>> CAUTION: This message was sent via the Public Internet and its >>>> authenticity cannot be guaranteed. >>>> >>>> >>>> PROPRIETARY: This e-mail contains proprietary information >>>some or all >>>> of which may be legally privileged. It is intended for the >recipient >>>> only. If an addressing or transmission error has misdirected this >>>> e-mail, please notify the authority by replying to this >>>e-mail. If you >>>> are not the intended recipient you must not use, disclose, >>>distribute, >>>> copy, print, or rely on this e-mail. >>> >>> >>> >>>-- >>>Manish Shakya >>>http://www.manishshakya.com.np >>> >>>_____________________________________________________________ >_________ >>>CAUTION: This message was sent via the Public Internet and its >>>authenticity cannot be guaranteed. >>> >> >> PROPRIETARY: This e-mail contains proprietary information >some or all of which may be legally privileged. It is >intended for the recipient only. If an addressing or >transmission error has misdirected this e-mail, please notify >the authority by replying to this e-mail. If you are not the >intended recipient you must not use, disclose, distribute, >copy, print, or rely on this e-mail. >> >> -- >> You received this message because you are subscribed to the >Google Groups "rowboat" group. >> To post to this group, send email to ro...@go.... >> To unsubscribe from this group, send email to >row...@go.... >> For more options, visit this group at >http://groups.google.com/group/rowboat?hl=en. >> > > > >-- >Manish Shakya >http://www.manishshakya.com.np > >--------------------------------------------------------------- >--------------- >This SF email is sponsosred by: >Try Windows Azure free for 90 days Click Here >http://p.sf.net/sfu/sfd2d-msazure >_______________________________________________ >gumstix-users mailing list >gum...@li... >https://lists.sourceforge.net/lists/listinfo/gumstix-users > >______________________________________________________________________ >CAUTION: This message was sent via the Public Internet and its >authenticity cannot be guaranteed. > PROPRIETARY: This e-mail contains proprietary information some or all of which may be legally privileged. It is intended for the recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the authority by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or rely on this e-mail. |