[beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Searching for text messages from 2014 to 2016 from 810-399-9069 -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/321a4f68-557b-4052-80db-1460cf1a7eac%40googlegroups.com.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
I'm sorry to say, but now I confirmed my assumption. In my application I am heavily using /dev/ttyO5 and moderatly using /dev/ttyO2. One of my BB-White is stable on 4.1.0-rc8-bone9 since 38 days now. I don't want to touch this. I was running a BB-White (bb589b) with 4.1.0-rc8-bone9 for 2 days without problems. I then updated bb589b to 4.1.5-ti-r10 and am getting a crash *unexpected IRQ trap at vector 00* after just a few hours, same happend with 4.1.4-ti-r9. I'll now look for some more BB-White in order to get more information. -- Günter -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Now 4 days on r9 and 3 days on r10, without any reboots. --- Graham == On Friday, August 14, 2015 at 11:03:20 AM UTC-5, Graham wrote: Things are looking pretty good, now. I am running 4.1.4-ti-r9 on one BBB Rev C. and 4.1.5-ti-r10 on another. No reboots on either. Two days uptime on r9 and one day uptime on r10. I will let them run a few more days, at least. r8 set a new record of only 2 minutes between one set of reboots, then it waited a full day until the next. :-) Any idea what was the root cause, yet? --- Graham == -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
I don't want to say that I am 100% sure with my findings, as I need some more testing done before, but it might be that they suffer from a problem on BB-White. Together with my application, which heavily uses the ttyO5 and moderately uses ttyO2, I have one BB-White up running 4.1.0-rc8-bone9 since 34 days now I have another BB-White with 4.1.2-ti-r4 also tried 4.1.4-ti-r9, and both times after a few hours of operation am getting on the console unexpected IRQ trap at vector 00 Before ringing any bells, I want to ensure that those boards showing this error are stable with the 4.1.0-rc8-bone9. -- Günter (dl4mea) -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Things are looking pretty good, now. I am running 4.1.4-ti-r9 on one BBB Rev C. and 4.1.5-ti-r10 on another. No reboots on either. Two days uptime on r9 and one day uptime on r10. I will let them run a few more days, at least. r8 set a new record of only 2 minutes between one set of reboots, then it waited a full day until the next. :-) Any idea what was the root cause, yet? --- Graham == -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
What is the best way to get this applied to the last snapshot 2015-08-09 Is there a download of a .deb? For other units, will they pick this up using apt-get when this gets published? On Wednesday, August 12, 2015 at 9:27:15 PM UTC+1, Felipe Balbi wrote: On Wed, Aug 12, 2015 at 03:23:03PM -0500, Robert Nelson wrote: all right, but if you reproduced without PM, I'll stick my tests to vanilla kernels. 2 days and still nothing. unfortunately gotta reboot though, need to test some other bug on MUSB. Thanks for testing Felipe. We might have a weird config setting that's causing it.. Can you attache your .config that lasted for 2 days and i'll start running comparisons of that against our kitchen sink config on my bbb farm.. I'm using omap2plus_defconfig. Also, please leave a few boards running a vanilla kernel, a tag from Linus, then we can compare bb.org vs vanilla. -- balbi -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Thu, Aug 13, 2015 at 1:50 AM, Lee Armstrong lesm...@gmail.com wrote: What is the best way to get this applied to the last snapshot 2015-08-09 Is there a download of a .deb? For other units, will they pick this up using apt-get when this gets published? The way the apt repo is setup, kernel updates are not automatic.. (that way you can safely upgrade user-space without worrying about a random kernel upgrade happening..) sudo apt-get update sudo apt-get install linux-image-4.1.4-ti-r9 sudo reboot or: cd /opt/scripts/tools/ git pull sudo ./update_kernel.sh --ti-channel --testing via: https://rcn-ee.com/repos/latest/jessie-armhf/LATEST-ti Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Perfect thanks. Running r9 and no reboots yet although my 8 would take around 14 hours. On Thursday, August 13, 2015 at 2:43:48 PM UTC+1, RobertCNelson wrote: On Thu, Aug 13, 2015 at 1:50 AM, Lee Armstrong les...@gmail.com javascript: wrote: What is the best way to get this applied to the last snapshot 2015-08-09 Is there a download of a .deb? For other units, will they pick this up using apt-get when this gets published? The way the apt repo is setup, kernel updates are not automatic.. (that way you can safely upgrade user-space without worrying about a random kernel upgrade happening..) sudo apt-get update sudo apt-get install linux-image-4.1.4-ti-r9 sudo reboot or: cd /opt/scripts/tools/ git pull sudo ./update_kernel.sh --ti-channel --testing via: https://rcn-ee.com/repos/latest/jessie-armhf/LATEST-ti Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
I have version 4.1.4-ti-r8.1 operating on a total of 21 boards now. Uptime 18h for most of them, one even 1 day 20h, without any reboot. Good work! I understand this is a development build from Robert, is there a planning for something that is released more officially? Thanks a lot for all effort! -- Günter (dl4mea) -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Hi Günter, On Wed, Aug 12, 2015 at 10:22 AM, Koellner Guenter dl4...@yahoo.de wrote: I have version 4.1.4-ti-r8.1 operating on a total of 21 boards now. Uptime 18h for most of them, one even 1 day 20h, without any reboot. Good work! I understand this is a development build from Robert, is there a planning for something that is released more officially? So r8.1 was just r8 with the one revert for testing. On 4 of my test boxes running that revert, 4 have reached an uptime of over 5 days. To date, I've enabled that revert in my scripts for all these kernels.. 4.1.4-ti-r9 4.1.5-bone15 4.2.0-rc6-bone2 Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Hello Robert, what is the difference between 4.1.4-ti-r9 and 4.1.5-bone15 and which one is the one recommended for future use? Cheers, Günter Am 12.08.2015 um 17:38 schrieb Robert Nelson: Hi Günter, On Wed, Aug 12, 2015 at 10:22 AM, Koellner Guenter dl4...@yahoo.de wrote: I have version 4.1.4-ti-r8.1 operating on a total of 21 boards now. Uptime 18h for most of them, one even 1 day 20h, without any reboot. Good work! I understand this is a development build from Robert, is there a planning for something that is released more officially? So r8.1 was just r8 with the one revert for testing. On 4 of my test boxes running that revert, 4 have reached an uptime of over 5 days. To date, I've enabled that revert in my scripts for all these kernels.. 4.1.4-ti-r9 4.1.5-bone15 4.2.0-rc6-bone2 Regards, -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
all right, but if you reproduced without PM, I'll stick my tests to vanilla kernels. 2 days and still nothing. unfortunately gotta reboot though, need to test some other bug on MUSB. Thanks for testing Felipe. We might have a weird config setting that's causing it.. Can you attache your .config that lasted for 2 days and i'll start running comparisons of that against our kitchen sink config on my bbb farm.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Wed, Aug 12, 2015 at 03:23:03PM -0500, Robert Nelson wrote: all right, but if you reproduced without PM, I'll stick my tests to vanilla kernels. 2 days and still nothing. unfortunately gotta reboot though, need to test some other bug on MUSB. Thanks for testing Felipe. We might have a weird config setting that's causing it.. Can you attache your .config that lasted for 2 days and i'll start running comparisons of that against our kitchen sink config on my bbb farm.. I'm using omap2plus_defconfig. Also, please leave a few boards running a vanilla kernel, a tag from Linus, then we can compare bb.org vs vanilla. -- balbi -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Wed, Aug 12, 2015 at 10:54 AM, Koellner Guenter dl4...@yahoo.de wrote: Hello Robert, what is the difference between 4.1.4-ti-r9 and 4.1.5-bone15 and which one is the one recommended for future use? Stick with 4.1.4-ti-r9, while i'm planning to push out 4.1.Y-boneX for the life of lts, the ti branch has more am335x enable-ment and testing.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Mon, Aug 10, 2015 at 08:27:05PM -0500, Felipe Balbi wrote: On Mon, Aug 10, 2015 at 03:04:52PM -0500, Robert Nelson wrote: On Mon, Aug 10, 2015 at 2:59 PM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Aug 10, 2015 at 2:55 PM, Felipe Balbi ba...@ti.com wrote: Hi again, On Mon, Aug 10, 2015 at 02:48:11PM -0500, Felipe Balbi wrote: Hi, I'll leave my BBB running with v4.1.0 vanilla, with Debian unstable userland. are you guys running with or without wkup_m3 firmware ? Is PM enabled at all ? The v4.1.x-ti-rX have pm enabled and wkup_m3 firmware.. m3: 0x191: 277eef8611e260a5d73a9e3773fff8f767fe2b01 head of next-upstream http://git.ti.com/gitweb/?p=ti-cm3-pm-firmware/amx3-cm3.git;a=shortlog;h=refs/heads/next-upstream all right, but if you reproduced without PM, I'll stick my tests to vanilla kernels. 2 days and still nothing. -- balbi -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Wed, Aug 12, 2015 at 03:08:33PM -0500, Felipe Balbi wrote: On Mon, Aug 10, 2015 at 08:27:05PM -0500, Felipe Balbi wrote: On Mon, Aug 10, 2015 at 03:04:52PM -0500, Robert Nelson wrote: On Mon, Aug 10, 2015 at 2:59 PM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Aug 10, 2015 at 2:55 PM, Felipe Balbi ba...@ti.com wrote: Hi again, On Mon, Aug 10, 2015 at 02:48:11PM -0500, Felipe Balbi wrote: Hi, I'll leave my BBB running with v4.1.0 vanilla, with Debian unstable userland. are you guys running with or without wkup_m3 firmware ? Is PM enabled at all ? The v4.1.x-ti-rX have pm enabled and wkup_m3 firmware.. m3: 0x191: 277eef8611e260a5d73a9e3773fff8f767fe2b01 head of next-upstream http://git.ti.com/gitweb/?p=ti-cm3-pm-firmware/amx3-cm3.git;a=shortlog;h=refs/heads/next-upstream all right, but if you reproduced without PM, I'll stick my tests to vanilla kernels. 2 days and still nothing. unfortunately gotta reboot though, need to test some other bug on MUSB. -- balbi -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Mon, Aug 10, 2015 at 11:09 AM, Nuno Gonçalves nuno...@gmail.com wrote: On Mon, Aug 10, 2015 at 5:04 PM, Robert Nelson robertcnel...@gmail.com wrote: PS, i'm working on adding a PRM_RSTST check to u-boot so i can catch the reboot reason.. That's really great Robert. Thanks! Felipe actually pointed me to it. ;) It'll give us something: Table 8-197. PRM_RSTST Register Field Descriptions Bit Field Type Reset Description 31-10 RESERVED Rreturns0s 0h 9 ICEPICK_RST R/W1toClr 0h IcePick reset event. This is a source of global warm reset initiated by the emulation. [warm reset insensitive] 0h = 0x0 : No ICEPICK reset. 1h = 0x1 : IcePick reset has occurred. 8-6 RESERVED Rreturns0s 0h 5 EXTERNAL_WARM_RST R/W1toClr 0h External warm reset event [warm reset insensitive] 0h = 0x0 : No global warm reset. 1h = 0x1 : Global external warm reset has occurred. 4 WDT1_RST R/W1toClr 0h Watchdog1 timer reset event. This is a source of global WARM reset. [warm reset insensitive] 0h = 0x0 : No watchdog reset. 1h = 0x1 : watchdog reset has occurred. 3 RESERVED R/W1toClr 0h Reserved. 2 RESERVED R/W1toClr 0h Reserved. 1 GLOBAL_WARM_SW_RS R/W1toClr 0h Global warm software reset event [warm reset insensitive] T 0h = 0x0 : No global warm SW reset 1h = 0x1 : Global warm SW reset has occurred. 0 GLOBAL_COLD_RST R/W1toClr 1h Power-on (cold) reset event [warm reset insensitive] 0h = 0x0 : No power-on reset. 1h = 0x1 : Power-on reset has occurred. 1338 Power, Reset, and Clock Management (PRCM) Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Sun, Aug 09, 2015 at 05:59:09PM -0500, Robert Nelson wrote: Update: Last friday i built v4.1-rc1 and 4.1.4-ti-r8 with the commit Nuno found and reverted it.. [test-bbb-1: 4.1.4-ti-r8.1 (up 2 days, 10 hours, 3 minutes)] [test-bbb-2: 4.1.4-ti-r8.1 (up 2 days, 9 hours, 58 minutes)] [test-bbb-5: 4.1.0-rc1-x0-2-gf38e145-dirty (up 2 days, 10 hours, 45 minutes)] [test-bbb-6: 4.1.0-rc1-x0-2-gf38e145-dirty (up 2 days, 10 hours, 40 minutes)] what does this mean ? vanilla v4.1-rc1 + 2 MUSB commits still hasn't crashed ? -- balbi -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Mon, Aug 10, 2015 at 10:57 AM, Felipe Balbi ba...@ti.com wrote: On Sun, Aug 09, 2015 at 05:59:09PM -0500, Robert Nelson wrote: Update: Last friday i built v4.1-rc1 and 4.1.4-ti-r8 with the commit Nuno found and reverted it.. [test-bbb-1: 4.1.4-ti-r8.1 (up 2 days, 10 hours, 3 minutes)] [test-bbb-2: 4.1.4-ti-r8.1 (up 2 days, 9 hours, 58 minutes)] [test-bbb-5: 4.1.0-rc1-x0-2-gf38e145-dirty (up 2 days, 10 hours, 45 minutes)] [test-bbb-6: 4.1.0-rc1-x0-2-gf38e145-dirty (up 2 days, 10 hours, 40 minutes)] what does this mean ? vanilla v4.1-rc1 + 2 MUSB commits still hasn't crashed ? It's rc1 + the musb revert: ad78c918602cb7cce0fab5d5813213853a6f351d + deb-pkg resync: (so the *.dtb are part of my linux-image*.deb build) https://github.com/RobertCNelson/bisector/blob/master/3rdparty/packaging/builddeb + phy search fix: (beaglebone/beaglebone black's phy doesn't come up 100% of the time on mdio[0]...) https://github.com/RobertCNelson/bisector/blob/master/patches/beaglebone/phy/0003-cpsw-search-for-phy.patch cron job runs every 5 minutes with uptime info sent over nfs.. http://rcn-ee.homeip.net:81/farm/uptime/ [test-bbb-1: 4.1.4-ti-r8.1 (up 3 days, 3 hours, 8 minutes)] [test-bbb-2: 4.1.4-ti-r8.1 (up 3 days, 3 hours, 3 minutes)] [test-bbb-5: 4.1.0-rc1-x0-2-gf38e145-dirty (up 3 days, 3 hours, 50 minutes)] [test-bbb-6: 4.1.0-rc1-x0-2-gf38e145-dirty (up 3 days, 3 hours, 45 minutes)] PS, i'm working on adding a PRM_RSTST check to u-boot so i can catch the reboot reason.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
3 weeks ago I asked for it For what is worth I believe the OMAP and PMIC reset reason registers should be part of the boot log so future reboot problems can be sorted.. But I just asked, I didn't actually code! Not sure if it is easy to retrieve both, or if PMIC is that much relevant for this issues. Anyway, this will surely take out black magic from the equation when debugging this problems. Nuno On Mon, Aug 10, 2015 at 5:12 PM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Aug 10, 2015 at 11:09 AM, Nuno Gonçalves nuno...@gmail.com wrote: On Mon, Aug 10, 2015 at 5:04 PM, Robert Nelson robertcnel...@gmail.com wrote: PS, i'm working on adding a PRM_RSTST check to u-boot so i can catch the reboot reason.. That's really great Robert. Thanks! Felipe actually pointed me to it. ;) It'll give us something: Table 8-197. PRM_RSTST Register Field Descriptions Bit Field Type Reset Description 31-10 RESERVED Rreturns0s 0h 9 ICEPICK_RST R/W1toClr 0h IcePick reset event. This is a source of global warm reset initiated by the emulation. [warm reset insensitive] 0h = 0x0 : No ICEPICK reset. 1h = 0x1 : IcePick reset has occurred. 8-6 RESERVED Rreturns0s 0h 5 EXTERNAL_WARM_RST R/W1toClr 0h External warm reset event [warm reset insensitive] 0h = 0x0 : No global warm reset. 1h = 0x1 : Global external warm reset has occurred. 4 WDT1_RST R/W1toClr 0h Watchdog1 timer reset event. This is a source of global WARM reset. [warm reset insensitive] 0h = 0x0 : No watchdog reset. 1h = 0x1 : watchdog reset has occurred. 3 RESERVED R/W1toClr 0h Reserved. 2 RESERVED R/W1toClr 0h Reserved. 1 GLOBAL_WARM_SW_RS R/W1toClr 0h Global warm software reset event [warm reset insensitive] T 0h = 0x0 : No global warm SW reset 1h = 0x1 : Global warm SW reset has occurred. 0 GLOBAL_COLD_RST R/W1toClr 1h Power-on (cold) reset event [warm reset insensitive] 0h = 0x0 : No power-on reset. 1h = 0x1 : Power-on reset has occurred. 1338 Power, Reset, and Clock Management (PRCM) Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Mon, Aug 10, 2015 at 1:05 PM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Aug 10, 2015 at 11:23 AM, Nuno Gonçalves nuno...@gmail.com wrote: 3 weeks ago I asked for it For what is worth I believe the OMAP and PMIC reset reason registers should be part of the boot log so future reboot problems can be sorted.. But I just asked, I didn't actually code! Not sure if it is easy to retrieve both, or if PMIC is that much relevant for this issues. Anyway, this will surely take out black magic from the equation when debugging this problems. Okay here's something quick/dirty... http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/MLO-am335x_evm-v2015.07-r3 http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/u-boot-am335x_evm-v2015.07-r3.img #patch: https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2015.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch#L21 make sure the eMMC doesn't have it's own bootloader: U-Boot 2015.07-1-gd8d32cf (Aug 10 2015 - 12:54:52 -0500) Watchdog enabled I2C: ready DRAM: 512 MiB Reset Source: Global external warm reset has occurred. Reset Source: Power-on reset has occurred. MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Using default environment dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10 sudo dd if=MLO-am335x_evm-v2015.07-r3 of=/dev/sde count=1 seek=1 bs=128k sudo dd if=u-boot-am335x_evm-v2015.07-r3.img of=/dev/sde count=2 seek=1 bs=384k I need to fire up x86, that's attached to the bbb's (right now i can't log serial) Okay within a few minutes the first board rebooted... Reset Source: Power-on reset has occurred. bbb-4 is an A6 model.. I have 3 others still running, so i'll keep track of those too... root@test-bbb-4:~# U-Boot SPL 2015.07-1-gd8d32cf (Aug 10 2015 - 12:54:52) U-Boot 2015.07-1-gd8d32cf (Aug 10 2015 - 12:54:52 -0500) Watchdog enabled I2C: ready DRAM: 512 MiB Reset Source: Power-on reset has occurred. MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Using default environment Net: ethaddr not set. Validating first E-fuse MAC cpsw Hit any key to stop autoboot: 0 gpio: pin 53 (gpio 53) value is 1 switch to partitions #0, OK mmc0 is current device gpio: pin 54 (gpio 54) value is 1 Checking for: /uEnv.txt ... Checking for: /boot.scr ... Checking for: /boot/boot.scr ... Checking for: /boot/uEnv.txt ... gpio: pin 55 (gpio 55) value is 1 1550 bytes read in 31 ms (48.8 KiB/s) Loaded environment from /boot/uEnv.txt Checking if uname_r is set in /boot/uEnv.txt... gpio: pin 56 (gpio 56) value is 1 Running uname_boot ... loading /boot/vmlinuz-4.1.4-ti-r8 ... Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Mon, Aug 10, 2015 at 11:23 AM, Nuno Gonçalves nuno...@gmail.com wrote: 3 weeks ago I asked for it For what is worth I believe the OMAP and PMIC reset reason registers should be part of the boot log so future reboot problems can be sorted.. But I just asked, I didn't actually code! Not sure if it is easy to retrieve both, or if PMIC is that much relevant for this issues. Anyway, this will surely take out black magic from the equation when debugging this problems. Okay here's something quick/dirty... http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/MLO-am335x_evm-v2015.07-r3 http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/u-boot-am335x_evm-v2015.07-r3.img #patch: https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2015.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch#L21 make sure the eMMC doesn't have it's own bootloader: U-Boot 2015.07-1-gd8d32cf (Aug 10 2015 - 12:54:52 -0500) Watchdog enabled I2C: ready DRAM: 512 MiB Reset Source: Global external warm reset has occurred. Reset Source: Power-on reset has occurred. MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Using default environment dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10 sudo dd if=MLO-am335x_evm-v2015.07-r3 of=/dev/sde count=1 seek=1 bs=128k sudo dd if=u-boot-am335x_evm-v2015.07-r3.img of=/dev/sde count=2 seek=1 bs=384k I need to fire up x86, that's attached to the bbb's (right now i can't log serial) Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Hi again, On Mon, Aug 10, 2015 at 02:48:11PM -0500, Felipe Balbi wrote: Hi, I'll leave my BBB running with v4.1.0 vanilla, with Debian unstable userland. are you guys running with or without wkup_m3 firmware ? Is PM enabled at all ? [ trim ] -- balbi -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Mon, Aug 10, 2015 at 5:04 PM, Robert Nelson robertcnel...@gmail.com wrote: PS, i'm working on adding a PRM_RSTST check to u-boot so i can catch the reboot reason.. That's really great Robert. Thanks! Nuno -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
It is not a flakey DC jack. But yes the symptoms do mimic that kind of failure. Same hardware works fine with Debian 8.1/kernel 3.14 and prior. It happens under all loading /activity, but easy to reproduce with the board idling, minimum console software load. It does not happen with the board powered by the USB port. It only happens when powered by the +5V barrel jack. No indication in syslog as to what happened. == I note that you were working in area changing ticks to jiffies or something like that. I personally suspect that there was some code dependent on the previous timing system that was used to time some of the USB power switch over mechanisms, that was not updated to deal with the timing system changes you made. For instance, the On-the-Go USB system periodically pushes power out the USB port to see if someone has connected a USB device. The PMIC sees this and can interpret this as power has appeared on the USB connector and to attempt a switchover. It really needs to wait some time period to see that it is stable input power rather than a power probe pulse generated by the BBB itself. If your timing system changes modified this switchover timing, the system could attempt to switch to a non-existant power source and die, causing a power-on reboot. This theory is supported by experimental tests run by William that says if the USB power line is shorted to ground, then the unit does not reboot. I am just summarizing several weeks of observations by all the guys on this thread. --- Graham On Mon, Aug 10, 2015 at 2:00 PM, Felipe Balbi ba...@ti.com wrote: Hi, On Mon, Aug 10, 2015 at 01:56:04PM -0500, Robert Nelson wrote: On Mon, Aug 10, 2015 at 1:05 PM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Aug 10, 2015 at 11:23 AM, Nuno Gonçalves nuno...@gmail.com wrote: 3 weeks ago I asked for it For what is worth I believe the OMAP and PMIC reset reason registers should be part of the boot log so future reboot problems can be sorted.. But I just asked, I didn't actually code! Not sure if it is easy to retrieve both, or if PMIC is that much relevant for this issues. Anyway, this will surely take out black magic from the equation when debugging this problems. Okay here's something quick/dirty... http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/MLO-am335x_evm-v2015.07-r3 http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/u-boot-am335x_evm-v2015.07-r3.img #patch: https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2015.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch#L21 make sure the eMMC doesn't have it's own bootloader: U-Boot 2015.07-1-gd8d32cf (Aug 10 2015 - 12:54:52 -0500) Watchdog enabled I2C: ready DRAM: 512 MiB Reset Source: Global external warm reset has occurred. Reset Source: Power-on reset has occurred. MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Using default environment dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10 sudo dd if=MLO-am335x_evm-v2015.07-r3 of=/dev/sde count=1 seek=1 bs=128k sudo dd if=u-boot-am335x_evm-v2015.07-r3.img of=/dev/sde count=2 seek=1 bs=384k I need to fire up x86, that's attached to the bbb's (right now i can't log serial) Okay within a few minutes the first board rebooted... Reset Source: Power-on reset has occurred. weird, this is likely either flakey DC Jack connection, or PMIC going bonkers. How do you guys reproduce this ? Is the board idle or is it running ? Which gadget driver ? Is USB cable connected to a host ? A desktop host or wired back into the host port of BBB itself ? I wanna try to reproduce it here. -- balbi -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Hi, On Mon, Aug 10, 2015 at 01:56:04PM -0500, Robert Nelson wrote: On Mon, Aug 10, 2015 at 1:05 PM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Aug 10, 2015 at 11:23 AM, Nuno Gonçalves nuno...@gmail.com wrote: 3 weeks ago I asked for it For what is worth I believe the OMAP and PMIC reset reason registers should be part of the boot log so future reboot problems can be sorted.. But I just asked, I didn't actually code! Not sure if it is easy to retrieve both, or if PMIC is that much relevant for this issues. Anyway, this will surely take out black magic from the equation when debugging this problems. Okay here's something quick/dirty... http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/MLO-am335x_evm-v2015.07-r3 http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/u-boot-am335x_evm-v2015.07-r3.img #patch: https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2015.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch#L21 make sure the eMMC doesn't have it's own bootloader: U-Boot 2015.07-1-gd8d32cf (Aug 10 2015 - 12:54:52 -0500) Watchdog enabled I2C: ready DRAM: 512 MiB Reset Source: Global external warm reset has occurred. Reset Source: Power-on reset has occurred. MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Using default environment dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10 sudo dd if=MLO-am335x_evm-v2015.07-r3 of=/dev/sde count=1 seek=1 bs=128k sudo dd if=u-boot-am335x_evm-v2015.07-r3.img of=/dev/sde count=2 seek=1 bs=384k I need to fire up x86, that's attached to the bbb's (right now i can't log serial) Okay within a few minutes the first board rebooted... Reset Source: Power-on reset has occurred. weird, this is likely either flakey DC Jack connection, or PMIC going bonkers. How do you guys reproduce this ? Is the board idle or is it running ? Which gadget driver ? Is USB cable connected to a host ? A desktop host or wired back into the host port of BBB itself ? I wanna try to reproduce it here. -- balbi -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Mon, Aug 10, 2015 at 2:00 PM, Felipe Balbi ba...@ti.com wrote: Hi, On Mon, Aug 10, 2015 at 01:56:04PM -0500, Robert Nelson wrote: On Mon, Aug 10, 2015 at 1:05 PM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Aug 10, 2015 at 11:23 AM, Nuno Gonçalves nuno...@gmail.com wrote: 3 weeks ago I asked for it For what is worth I believe the OMAP and PMIC reset reason registers should be part of the boot log so future reboot problems can be sorted.. But I just asked, I didn't actually code! Not sure if it is easy to retrieve both, or if PMIC is that much relevant for this issues. Anyway, this will surely take out black magic from the equation when debugging this problems. Okay here's something quick/dirty... http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/MLO-am335x_evm-v2015.07-r3 http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/u-boot-am335x_evm-v2015.07-r3.img #patch: https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2015.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch#L21 make sure the eMMC doesn't have it's own bootloader: U-Boot 2015.07-1-gd8d32cf (Aug 10 2015 - 12:54:52 -0500) Watchdog enabled I2C: ready DRAM: 512 MiB Reset Source: Global external warm reset has occurred. Reset Source: Power-on reset has occurred. MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Using default environment dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10 sudo dd if=MLO-am335x_evm-v2015.07-r3 of=/dev/sde count=1 seek=1 bs=128k sudo dd if=u-boot-am335x_evm-v2015.07-r3.img of=/dev/sde count=2 seek=1 bs=384k I need to fire up x86, that's attached to the bbb's (right now i can't log serial) Okay within a few minutes the first board rebooted... Reset Source: Power-on reset has occurred. weird, this is likely either flakey DC Jack connection, or PMIC going bonkers. How do you guys reproduce this ? Is the board idle or is it running ? Which gadget driver ? Is USB cable connected to a host ? A desktop host or wired back into the host port of BBB itself ? I wanna try to reproduce it here. Pretty much just grab: http://rcn-ee.com/rootfs/bb.org/testing/2015-08-09/console/bb-debian-8.1-console-armhf-2015-08-09-2gb.img.xz dd it to a microSD card and just let it idle.. powered via DC ethernet connected (i was echoing uptime -p to a file on nfs) serial debug attached usb otg = not connected.. (if you connect this it'll stay ON and won't reset) usb host = not connected hdmi = not connected no capes plugged in gadget drivers: 4.1.4-ti-rt-r8 CONFIG_USB_MUSB_HDRC=y # CONFIG_USB_MUSB_HOST is not set # CONFIG_USB_MUSB_GADGET is not set CONFIG_USB_MUSB_DUAL_ROLE=y CONFIG_USB_MUSB_DSPS=y CONFIG_USB_MUSB_AM335X_CHILD=y # CONFIG_USB_TI_CPPI41_DMA is not set CONFIG_MUSB_PIO_ONLY=y CONFIG_USB_LIBCOMPOSITE=y CONFIG_USB_U_ETHER=y CONFIG_USB_F_ECM=y CONFIG_USB_F_SUBSET=y CONFIG_USB_F_RNDIS=y # CONFIG_USB_CONFIGFS is not set # CONFIG_USB_ZERO is not set # CONFIG_USB_AUDIO is not set CONFIG_USB_ETH=y CONFIG_USB_ETH_RNDIS=y https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/4.1.4-ti-rt-r8/patches/defconfig#L4804-L4813 Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Mon, Aug 10, 2015 at 2:16 PM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Aug 10, 2015 at 2:00 PM, Felipe Balbi ba...@ti.com wrote: Hi, On Mon, Aug 10, 2015 at 01:56:04PM -0500, Robert Nelson wrote: On Mon, Aug 10, 2015 at 1:05 PM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Aug 10, 2015 at 11:23 AM, Nuno Gonçalves nuno...@gmail.com wrote: 3 weeks ago I asked for it For what is worth I believe the OMAP and PMIC reset reason registers should be part of the boot log so future reboot problems can be sorted.. But I just asked, I didn't actually code! Not sure if it is easy to retrieve both, or if PMIC is that much relevant for this issues. Anyway, this will surely take out black magic from the equation when debugging this problems. Okay here's something quick/dirty... http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/MLO-am335x_evm-v2015.07-r3 http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/u-boot-am335x_evm-v2015.07-r3.img #patch: https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2015.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch#L21 make sure the eMMC doesn't have it's own bootloader: U-Boot 2015.07-1-gd8d32cf (Aug 10 2015 - 12:54:52 -0500) Watchdog enabled I2C: ready DRAM: 512 MiB Reset Source: Global external warm reset has occurred. Reset Source: Power-on reset has occurred. MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Using default environment dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10 sudo dd if=MLO-am335x_evm-v2015.07-r3 of=/dev/sde count=1 seek=1 bs=128k sudo dd if=u-boot-am335x_evm-v2015.07-r3.img of=/dev/sde count=2 seek=1 bs=384k I need to fire up x86, that's attached to the bbb's (right now i can't log serial) Okay within a few minutes the first board rebooted... Reset Source: Power-on reset has occurred. weird, this is likely either flakey DC Jack connection, or PMIC going bonkers. How do you guys reproduce this ? Is the board idle or is it running ? Which gadget driver ? Is USB cable connected to a host ? A desktop host or wired back into the host port of BBB itself ? I wanna try to reproduce it here. Pretty much just grab: http://rcn-ee.com/rootfs/bb.org/testing/2015-08-09/console/bb-debian-8.1-console-armhf-2015-08-09-2gb.img.xz dd it to a microSD card and just let it idle.. powered via DC ethernet connected (i was echoing uptime -p to a file on nfs) serial debug attached usb otg = not connected.. (if you connect this it'll stay ON and won't reset) usb host = not connected hdmi = not connected no capes plugged in gadget drivers: 4.1.4-ti-rt-r8 CONFIG_USB_MUSB_HDRC=y # CONFIG_USB_MUSB_HOST is not set # CONFIG_USB_MUSB_GADGET is not set CONFIG_USB_MUSB_DUAL_ROLE=y CONFIG_USB_MUSB_DSPS=y CONFIG_USB_MUSB_AM335X_CHILD=y # CONFIG_USB_TI_CPPI41_DMA is not set CONFIG_MUSB_PIO_ONLY=y CONFIG_USB_LIBCOMPOSITE=y CONFIG_USB_U_ETHER=y CONFIG_USB_F_ECM=y CONFIG_USB_F_SUBSET=y CONFIG_USB_F_RNDIS=y # CONFIG_USB_CONFIGFS is not set # CONFIG_USB_ZERO is not set # CONFIG_USB_AUDIO is not set CONFIG_USB_ETH=y CONFIG_USB_ETH_RNDIS=y https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/4.1.4-ti-rt-r8/patches/defconfig#L4804-L4813 Opps that's the rt variant.. https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/4.1.4-ti-r8/patches/defconfig#L4810-L4819 (that section is the same, but to dot the i's) Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Hi, I'll leave my BBB running with v4.1.0 vanilla, with Debian unstable userland. On Mon, Aug 10, 2015 at 02:20:22PM -0500, Robert Nelson wrote: On Mon, Aug 10, 2015 at 2:16 PM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Aug 10, 2015 at 2:00 PM, Felipe Balbi ba...@ti.com wrote: Hi, On Mon, Aug 10, 2015 at 01:56:04PM -0500, Robert Nelson wrote: On Mon, Aug 10, 2015 at 1:05 PM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Aug 10, 2015 at 11:23 AM, Nuno Gonçalves nuno...@gmail.com wrote: 3 weeks ago I asked for it For what is worth I believe the OMAP and PMIC reset reason registers should be part of the boot log so future reboot problems can be sorted.. But I just asked, I didn't actually code! Not sure if it is easy to retrieve both, or if PMIC is that much relevant for this issues. Anyway, this will surely take out black magic from the equation when debugging this problems. Okay here's something quick/dirty... http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/MLO-am335x_evm-v2015.07-r3 http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/u-boot-am335x_evm-v2015.07-r3.img #patch: https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2015.07/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch#L21 make sure the eMMC doesn't have it's own bootloader: U-Boot 2015.07-1-gd8d32cf (Aug 10 2015 - 12:54:52 -0500) Watchdog enabled I2C: ready DRAM: 512 MiB Reset Source: Global external warm reset has occurred. Reset Source: Power-on reset has occurred. MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Using default environment dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10 sudo dd if=MLO-am335x_evm-v2015.07-r3 of=/dev/sde count=1 seek=1 bs=128k sudo dd if=u-boot-am335x_evm-v2015.07-r3.img of=/dev/sde count=2 seek=1 bs=384k I need to fire up x86, that's attached to the bbb's (right now i can't log serial) Okay within a few minutes the first board rebooted... Reset Source: Power-on reset has occurred. weird, this is likely either flakey DC Jack connection, or PMIC going bonkers. How do you guys reproduce this ? Is the board idle or is it running ? Which gadget driver ? Is USB cable connected to a host ? A desktop host or wired back into the host port of BBB itself ? I wanna try to reproduce it here. Pretty much just grab: http://rcn-ee.com/rootfs/bb.org/testing/2015-08-09/console/bb-debian-8.1-console-armhf-2015-08-09-2gb.img.xz dd it to a microSD card and just let it idle.. powered via DC ethernet connected (i was echoing uptime -p to a file on nfs) serial debug attached usb otg = not connected.. (if you connect this it'll stay ON and won't reset) usb host = not connected hdmi = not connected no capes plugged in gadget drivers: 4.1.4-ti-rt-r8 CONFIG_USB_MUSB_HDRC=y # CONFIG_USB_MUSB_HOST is not set # CONFIG_USB_MUSB_GADGET is not set CONFIG_USB_MUSB_DUAL_ROLE=y CONFIG_USB_MUSB_DSPS=y CONFIG_USB_MUSB_AM335X_CHILD=y # CONFIG_USB_TI_CPPI41_DMA is not set CONFIG_MUSB_PIO_ONLY=y CONFIG_USB_LIBCOMPOSITE=y CONFIG_USB_U_ETHER=y CONFIG_USB_F_ECM=y CONFIG_USB_F_SUBSET=y CONFIG_USB_F_RNDIS=y # CONFIG_USB_CONFIGFS is not set # CONFIG_USB_ZERO is not set # CONFIG_USB_AUDIO is not set CONFIG_USB_ETH=y CONFIG_USB_ETH_RNDIS=y https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/4.1.4-ti-rt-r8/patches/defconfig#L4804-L4813 Opps that's the rt variant.. https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/4.1.4-ti-r8/patches/defconfig#L4810-L4819 (that section is the same, but to dot the i's) Regards, -- Robert Nelson https://rcn-ee.com/ -- balbi -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Mon, Aug 10, 2015 at 2:55 PM, Felipe Balbi ba...@ti.com wrote: Hi again, On Mon, Aug 10, 2015 at 02:48:11PM -0500, Felipe Balbi wrote: Hi, I'll leave my BBB running with v4.1.0 vanilla, with Debian unstable userland. are you guys running with or without wkup_m3 firmware ? Is PM enabled at all ? The v4.1.x-ti-rX have pm enabled and wkup_m3 firmware.. It's using ti's 4.1.y as base: http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-4.1.y BUT.. When doing the v4.0.0 - v4.1.0-rc1 bisect the wkup firmware wasn't used. (this why it took a couple of days to factor out our local ti patchset against v4.1.0-rc1) Here's the config I used during the bisect: https://github.com/RobertCNelson/bisector/blob/master/patches/defconfig Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Mon, Aug 10, 2015 at 2:59 PM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Aug 10, 2015 at 2:55 PM, Felipe Balbi ba...@ti.com wrote: Hi again, On Mon, Aug 10, 2015 at 02:48:11PM -0500, Felipe Balbi wrote: Hi, I'll leave my BBB running with v4.1.0 vanilla, with Debian unstable userland. are you guys running with or without wkup_m3 firmware ? Is PM enabled at all ? The v4.1.x-ti-rX have pm enabled and wkup_m3 firmware.. m3: 0x191: 277eef8611e260a5d73a9e3773fff8f767fe2b01 head of next-upstream http://git.ti.com/gitweb/?p=ti-cm3-pm-firmware/amx3-cm3.git;a=shortlog;h=refs/heads/next-upstream Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Mon, Aug 10, 2015 at 03:04:52PM -0500, Robert Nelson wrote: On Mon, Aug 10, 2015 at 2:59 PM, Robert Nelson robertcnel...@gmail.com wrote: On Mon, Aug 10, 2015 at 2:55 PM, Felipe Balbi ba...@ti.com wrote: Hi again, On Mon, Aug 10, 2015 at 02:48:11PM -0500, Felipe Balbi wrote: Hi, I'll leave my BBB running with v4.1.0 vanilla, with Debian unstable userland. are you guys running with or without wkup_m3 firmware ? Is PM enabled at all ? The v4.1.x-ti-rX have pm enabled and wkup_m3 firmware.. m3: 0x191: 277eef8611e260a5d73a9e3773fff8f767fe2b01 head of next-upstream http://git.ti.com/gitweb/?p=ti-cm3-pm-firmware/amx3-cm3.git;a=shortlog;h=refs/heads/next-upstream all right, but if you reproduced without PM, I'll stick my tests to vanilla kernels. -- balbi -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Digital signature
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Hi, last Friday I got two bisecting builds from Nuno, which I have tested on my pool of BB-Black. The current pool consists of two BB-Black which are from one of the first BB-Black productions done by Embest around 2014. These boards are named old Plus there are 4+1 new BB-Black from Embest manufactured around April/May 2015, named new Prior to testing Nuno's builds, I had installed 4.0.4-bone4 on them for more than 36h without a reboot, concluding that 4.0.4-bone4 is stable on all. *Results:** *_ Nuno's bisecting build #40:__ _bbde39 (old): stable - uptime 1 day 1 hour bbe0ae + bb77e6 (new): stable - uptime 1 day 1 hour _ Nuno's bisecting build #41:__ ___bbc1a1 (old): stable - uptime 1 day 1 hour bb6bce + bb6a6f: *unstable*: both boards had 5 reboots over the last 25h I addition I left one new board bbd14b run with 4.0.4-bone4 which meanwhile has an uptime of 2 days 22 hours It much seems to be as not all of the hardware of BB-Black is suffering from this problem. -- Günter (dl4mea) Am 31.07.2015 um 16:40 schrieb Robert Nelson: On Fri, Jul 31, 2015 at 9:19 AM, Graham gra...@flex-radio.com wrote: Well, that is progress. I don't think I have ever done a git bisect where it takes one or two days to tell good from bad. I know this is painful for you. Thanks for grinding on it. --- Graham When we get down to a kernel git bisect i have a script ready that'll take all the pain out of it.. ;) and right now it's looking v4.0.0 - v4.1.0... I'm current keeping track of things here: https://gist.github.com/RobertCNelson/b52f8318e9798625b655 I'm helping out grandma this weekend, so i'll be updating that gist when i can. (As long as the boards don't need a hard power reset) Regards, -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
So, this build works fine for all boards: 9e204d885a6d0ae3696284bacd86e2b94dd936c8 # v4.0-rc3-40-g9e204d8 usb: musb: dsps: use msecs_to_jiffies instead This commit is the first introducing the reboot problem. The problem is also confirmed to only happen in some board versions: ad78c918602cb7cce0fab5d5813213853a6f351d # v4.0-rc3-41-gad78c91 usb: musb: dsps: just start polling already We can't discard a silicon problem, but this is way over my pay grade. Hope Balbi can give us any hint about any possible reasons this commit is creating this issue, since the code doesn't appear to have any evident problem... Thanks, Nuno On Sat, Aug 8, 2015 at 6:08 PM, Koellner Guenter dl4...@yahoo.de wrote: Hi, last Friday I got two bisecting builds from Nuno, which I have tested on my pool of BB-Black. The current pool consists of two BB-Black which are from one of the first BB-Black productions done by Embest around 2014. These boards are named old Plus there are 4+1 new BB-Black from Embest manufactured around April/May 2015, named new Prior to testing Nuno's builds, I had installed 4.0.4-bone4 on them for more than 36h without a reboot, concluding that 4.0.4-bone4 is stable on all. Results: Nuno's bisecting build #40: bbde39 (old): stable - uptime 1 day 1 hour bbe0ae + bb77e6 (new): stable - uptime 1 day 1 hour Nuno's bisecting build #41: bbc1a1 (old): stable - uptime 1 day 1 hour bb6bce + bb6a6f: unstable: both boards had 5 reboots over the last 25h I addition I left one new board bbd14b run with 4.0.4-bone4 which meanwhile has an uptime of 2 days 22 hours It much seems to be as not all of the hardware of BB-Black is suffering from this problem. -- Günter (dl4mea) Am 31.07.2015 um 16:40 schrieb Robert Nelson: On Fri, Jul 31, 2015 at 9:19 AM, Graham gra...@flex-radio.com wrote: Well, that is progress. I don't think I have ever done a git bisect where it takes one or two days to tell good from bad. I know this is painful for you. Thanks for grinding on it. --- Graham When we get down to a kernel git bisect i have a script ready that'll take all the pain out of it.. ;) and right now it's looking v4.0.0 - v4.1.0... I'm current keeping track of things here: https://gist.github.com/RobertCNelson/b52f8318e9798625b655 I'm helping out grandma this weekend, so i'll be updating that gist when i can. (As long as the boards don't need a hard power reset) Regards, -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Update: also the old board with Nuno's #41 has rebooted. Hard to make a statistic from this, but it means that new boards are booting 5 times more often then old ones -- Günter Am 08.08.2015 um 19:16 schrieb Nuno Gonçalves: So, this build works fine for all boards: 9e204d885a6d0ae3696284bacd86e2b94dd936c8 # v4.0-rc3-40-g9e204d8 usb: musb: dsps: use msecs_to_jiffies instead This commit is the first introducing the reboot problem. The problem is also confirmed to only happen in some board versions: ad78c918602cb7cce0fab5d5813213853a6f351d # v4.0-rc3-41-gad78c91 usb: musb: dsps: just start polling already We can't discard a silicon problem, but this is way over my pay grade. Hope Balbi can give us any hint about any possible reasons this commit is creating this issue, since the code doesn't appear to have any evident problem... Thanks, Nuno On Sat, Aug 8, 2015 at 6:08 PM, Koellner Guenter dl4...@yahoo.de wrote: Hi, last Friday I got two bisecting builds from Nuno, which I have tested on my pool of BB-Black. The current pool consists of two BB-Black which are from one of the first BB-Black productions done by Embest around 2014. These boards are named old Plus there are 4+1 new BB-Black from Embest manufactured around April/May 2015, named new Prior to testing Nuno's builds, I had installed 4.0.4-bone4 on them for more than 36h without a reboot, concluding that 4.0.4-bone4 is stable on all. Results: Nuno's bisecting build #40: bbde39 (old): stable - uptime 1 day 1 hour bbe0ae + bb77e6 (new): stable - uptime 1 day 1 hour Nuno's bisecting build #41: bbc1a1 (old): stable - uptime 1 day 1 hour bb6bce + bb6a6f: unstable: both boards had 5 reboots over the last 25h I addition I left one new board bbd14b run with 4.0.4-bone4 which meanwhile has an uptime of 2 days 22 hours It much seems to be as not all of the hardware of BB-Black is suffering from this problem. -- Günter (dl4mea) Am 31.07.2015 um 16:40 schrieb Robert Nelson: On Fri, Jul 31, 2015 at 9:19 AM, Graham gra...@flex-radio.com wrote: Well, that is progress. I don't think I have ever done a git bisect where it takes one or two days to tell good from bad. I know this is painful for you. Thanks for grinding on it. --- Graham When we get down to a kernel git bisect i have a script ready that'll take all the pain out of it.. ;) and right now it's looking v4.0.0 - v4.1.0... I'm current keeping track of things here: https://gist.github.com/RobertCNelson/b52f8318e9798625b655 I'm helping out grandma this weekend, so i'll be updating that gist when i can. (As long as the boards don't need a hard power reset) Regards, -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
git bisect start git bisect good v4.0 git bisect bad v4.1-rc1 git bisect bad 6c373ca89399c5a3f7ef210ad8f63dc3437da345 # v4.0-5833-g6c373ca git bisect bad e95e7f627062be5e6ce971ce873e6234c91ffc50 # v4.0-2825-ge95e7f6 git bisect bad c4be50eee2bd4d50e0f0ca58776f685c08de69c3 # v4.0-1399-gc4be50e git bisect goo 1a370f4cd95e056d55ef5bf1a183880e70195e59 # v4.0-682-g1a370f4 git bisect good 3be1b98e073bdd4c1bb3144201a927c4a21330ba # v4.0-1013-g3be1b98 git bisect bad c6ab3aec4bc4beda2d6eb8ea43c6f5be3b215d3f # v4.0-rc5-193-gc6ab3ae git bisect bad ab330cf3888d8e0779fa05a243d53ba9f53a7ba9 # v4.0-rc3-96-gab330cf git bisect bad 44b316525986252bb95d356419fc9e75f0532112 # v4.0-rc3-48-g44b3165 git bisect good d5fa3e9f7398adf337f03fa3257d5e9b214078ee # v4.0-rc3-24-gd5fa3e9 git bisect good ccf5fb698155ee289b9257b0f1d6be3c7900ba0a # v4.0-rc3-36-gccf5fb6 git bisect bad eac68e8f979b82d257eea0a4bbcda7b169d330bf # v4.0-rc3-42-geac68e8 git bisect good 043f5b75dd2b1fbd45d5f367d50e5ae5b4afa955 # v4.0-rc3-39-g043f5b7 git bisect bad ad78c918602cb7cce0fab5d5813213853a6f351d # v4.0-rc3-41-gad78c91 https://lh3.googleusercontent.com/-9xfbLOnnuQQ/VcRl-cCZnJI/AAADD4c/tl9Z8HJGnaA/s1600/Screenshot%2Bfrom%2B2015-08-07%2B08%253A59%253A15.png This means it is down to this two: 9e204d885a6d0ae3696284bacd86e2b94dd936c8 # v4.0-rc3-40-g9e204d8 usb: musb: dsps: use msecs_to_jiffies instead ad78c918602cb7cce0fab5d5813213853a6f351d # v4.0-rc3-41-gad78c91 usb: musb: dsps: just start polling already Guess I'm giving a look at the code... Nuno -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Just a quick update. If I didn't get it wrong so far: git bisect start git bisect good v4.0 git bisect bad v4.1-rc1 git bisect bad 6c373ca89399c5a3f7ef210ad8f63dc3437da345 # v4.0-5833-g6c373ca git bisect bad e95e7f627062be5e6ce971ce873e6234c91ffc50 # v4.0-2825-ge95e7f6 git bisect bad c4be50eee2bd4d50e0f0ca58776f685c08de69c3 # v4.0-1399-gc4be50e git bisect good1a370f4cd95e056d55ef5bf1a183880e70195e59 # v4.0-682-g1a370f4 git bisect good 3be1b98e073bdd4c1bb3144201a927c4a21330ba # v4.0-1013-g3be1b98 git bisect bad c6ab3aec4bc4beda2d6eb8ea43c6f5be3b215d3f # v4.0-rc5-193-gc6ab3ae git bisect bad ab330cf3888d8e0779fa05a243d53ba9f53a7ba9 # v4.0-rc3-96-gab330cf This results in the following suspects: https://lh3.googleusercontent.com/-YNwUnIaBp7I/VcG7DM0ugXI/AAADD34/yksejFzmH-s/s1600/bisect_visualize.png It will still take up to 3 days to pinpoint the evil commit... Thanks, Nuno -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Hi, all I can add at this time is that I have a strong feeling that there is a hardware dependency as well.1) I ran linux-image-4.0.4-bone4 stable on two boards (Embest March 2014) for 2 days 2) After updating to some 4.1.x or 4.2.x one was stable, the other one showed the effect. I got 32 BBB (Embest March/April 2015) production yesterday and will insert minimum 10 of them into the test bed tonight. Then I let linux-image-4.0.4-bone4 run for at least 24h and we see how it behaves. -- Günter (dl4mea) -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Nice Job Nuno! Right now I can confirm up to 1a370f4cd95e056d55ef5bf1a183880e70195e59 I have 5/5 boards running for 21 hours.. The worst delay I've seen between reboots has been around 2.5 days.. On Wed, Aug 5, 2015 at 2:31 AM, Nuno Gonçalves nuno...@gmail.com wrote: Just a quick update. If I didn't get it wrong so far: git bisect start git bisect good v4.0 git bisect bad v4.1-rc1 git bisect bad 6c373ca89399c5a3f7ef210ad8f63dc3437da345 # v4.0-5833-g6c373ca git bisect bad e95e7f627062be5e6ce971ce873e6234c91ffc50 # v4.0-2825-ge95e7f6 git bisect bad c4be50eee2bd4d50e0f0ca58776f685c08de69c3 # v4.0-1399-gc4be50e git bisect good1a370f4cd95e056d55ef5bf1a183880e70195e59 # v4.0-682-g1a370f4 git bisect good 3be1b98e073bdd4c1bb3144201a927c4a21330ba # v4.0-1013-g3be1b98 git bisect bad c6ab3aec4bc4beda2d6eb8ea43c6f5be3b215d3f # v4.0-rc5-193-gc6ab3ae git bisect bad ab330cf3888d8e0779fa05a243d53ba9f53a7ba9 # v4.0-rc3-96-gab330cf This results in the following suspects: https://lh3.googleusercontent.com/-YNwUnIaBp7I/VcG7DM0ugXI/AAADD34/yksejFzmH-s/s1600/bisect_visualize.png It will still take up to 3 days to pinpoint the evil commit... Thanks, Nuno -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
I will add anecdotal comment in support of Guenter's comment about a serial port problem. Three times, I have had the ttyS0 port hardware serial console port stop working in advance of the reboot, while I could still sign in on SSH via Ethernet, and the BBB seemed to be otherwise still working. It may be the same problem, or it may be a different problem, but I suspect that the serial port is involved. --- Graham == On Wed, Aug 5, 2015 at 7:03 AM, Robert Nelson robertcnel...@gmail.com wrote: Nice Job Nuno! Right now I can confirm up to 1a370f4cd95e056d55ef5bf1a183880e70195e59 I have 5/5 boards running for 21 hours.. The worst delay I've seen between reboots has been around 2.5 days.. On Wed, Aug 5, 2015 at 2:31 AM, Nuno Gonçalves nuno...@gmail.com wrote: Just a quick update. If I didn't get it wrong so far: git bisect start git bisect good v4.0 git bisect bad v4.1-rc1 git bisect bad 6c373ca89399c5a3f7ef210ad8f63dc3437da345 # v4.0-5833-g6c373ca git bisect bad e95e7f627062be5e6ce971ce873e6234c91ffc50 # v4.0-2825-ge95e7f6 git bisect bad c4be50eee2bd4d50e0f0ca58776f685c08de69c3 # v4.0-1399-gc4be50e git bisect good1a370f4cd95e056d55ef5bf1a183880e70195e59 # v4.0-682-g1a370f4 git bisect good 3be1b98e073bdd4c1bb3144201a927c4a21330ba # v4.0-1013-g3be1b98 git bisect bad c6ab3aec4bc4beda2d6eb8ea43c6f5be3b215d3f # v4.0-rc5-193-gc6ab3ae git bisect bad ab330cf3888d8e0779fa05a243d53ba9f53a7ba9 # v4.0-rc3-96-gab330cf This results in the following suspects: https://lh3.googleusercontent.com/-YNwUnIaBp7I/VcG7DM0ugXI/AAADD34/yksejFzmH-s/s1600/bisect_visualize.png It will still take up to 3 days to pinpoint the evil commit... Thanks, Nuno -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Sun, Aug 2, 2015 at 7:27 AM, 'dl4mea' via BeagleBoard beagleboard@googlegroups.com wrote: Hi, after 36h the two clients bbde39 and bbc1a1 are still operating without a reboot, same bb1cf1. Remember, these are from very first Embest production, pretty old ones. I also installed the version 4.0.4-bone4 on the other 13 BB-Black on my table, 4 of them are stable since power up, the other 9 pieces are rebooting up to every 2-4 hours. Thanks for testing! That's not good news, 4.0.4 is 4/13.. How about: linux-image-3.19.3-bone4 From my experience it looks much as if just newer BB-Black are concerned by this problem. I am waiting for a parcel with 16 pieces from an April/May 2015 production lot, and will then put them into the test bed. Last night 2 boards running just mainline 4.0-rc1 failed... So atleast it's not the ti patchset or bone patchset.. but we might have two issues going on.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
I already did a test with linux-image-3.19.3-bone4 but after a while, I got unexpected IRQ trap at vector 00 However, at this time my application was intensivly working with the serial port, causing a lot of interrupts, but I will retest again without running data through my application. -- Günter (dl4mea) -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
This is what I can add for now, please note the uptime of the first, which is up since 8 days. These are 3 BB-Black from the very first production of Embest, probably there was a different PMIC? I should get 16 out of the April Embest production (which were stored at a different location) today and I will include them afterwards. # dmesg | grep phy mask [3.687140] davinci_mdio 4a101000.mdio: detected phy mask fffe # cat /proc/device-tree/model TI AM335x BeagleBone Black # uname -a Linux bb1cf1 4.1.2-ti-r4.6 #1 SMP PREEMPT Tue Jul 21 08:24:37 CDT 2015 armv7l GNU/Linux # uptime 07:15:08 up 8 days, 11:13, 1 user, load average: 0.00, 0.01, 0.05 # dmesg | grep phy mask [2.722583] davinci_mdio 4a101000.mdio: detected phy mask fffe # cat /proc/device-tree/model TI AM335x BeagleBone Black # uname -a Linux bbc1a1 4.0.4-bone4 #1 Mon May 18 05:59:35 UTC 2015 armv7l GNU/Linux # uptime 07:17:40 up 9:26, 1 user, load average: 0.00, 0.01, 0.04 # dmesg | grep phy mask [2.722541] davinci_mdio 4a101000.mdio: detected phy mask fffe # cat /proc/device-tree/model TI AM335x BeagleBone Black # uname -a Linux bbde39 4.0.4-bone4 #1 Mon May 18 05:59:35 UTC 2015 armv7l GNU/Linux # uptime 07:18:55 up 9:28, 1 user, load average: 0.00, 0.01, 0.05 for you all to enjoy, one of the BB-White: # dmesg | grep phy mask [3.676818] davinci_mdio 4a101000.mdio: detected phy mask fffe # cat /proc/device-tree/model TI AM335x BeagleBone # uname -a Linux rc22 4.1.0-rc8-bone9 #1 Wed Jun 17 00:05:43 UTC 2015 armv7l GNU/Linux # uptime 07:20:25 up 22 days, 2:36, 2 users, load average: 0.24, 0.20, 0.18 -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Fri, Jul 31, 2015 at 10:59 PM, Robert Nelson robertcnel...@gmail.com wrote: On Fri, Jul 31, 2015 at 8:42 PM, Robert Nelson robertcnel...@gmail.com wrote: mid-day update, 9 boards now running.. linux-image-4.1.0-rc4-bone2 just rebooted on me.. so, current kernel bisect: v4.0.0 - v4.1.0-rc4 just waiting on rc1/rc2/rc3 to fail next.. ;) rc3 just rebooted v4.0.0 - v4.1.0-rc3 and after 14 hours, rc1 just rebooted... I'm going to quickly rebuild rc1 without my bone0 patchset.. v4.0.0 - v4.1.0-rc1 okay first one up: http://rcn-ee.homeip.net:81/farm/testing/v4.1.x/just-rc1/linux-image-4.1.0-rc1-x0-dirty_1cross_armhf.deb NOTE... any boards without a phy mask of fffe should not be used for the testing going forward.. root@test-bbb-3:~# dmesg | grep mdio [3.432508] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [3.432526] davinci_mdio 4a101000.mdio: detected phy mask fffe as ethernet will be broken.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
mid-day update, 9 boards now running.. linux-image-4.1.0-rc4-bone2 just rebooted on me.. so, current kernel bisect: v4.0.0 - v4.1.0-rc4 just waiting on rc1/rc2/rc3 to fail next.. ;) rc3 just rebooted v4.0.0 - v4.1.0-rc3 Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Well, that is progress. I don't think I have ever done a git bisect where it takes one or two days to tell good from bad. I know this is painful for you. Thanks for grinding on it. --- Graham == On Friday, July 31, 2015 at 8:05:24 AM UTC-5, RobertCNelson wrote: Just a quick update.. verfied a non v4.1.x-ti kernel failed last night.. Right now i'm looking between: linux-image-4.0.4-bone4 linux-image-4.1.2-bone12 usb: apt-get install linux-image-4.0.4-bone4 (up 1 day, 9 hours, 56 minutes) dc: apt-get install linux-image-4.0.4-bone4 (up 1 day, 9 hours, 56 minutes) 3: apt-get install linux-image-4.1.1-bone10 (up 1 hour, 15 minutes) Ran out of power supplies, so i'm going to get another 3 boards running tonight.. So i'll have 9 running in total.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Fri, Jul 31, 2015 at 9:19 AM, Graham gra...@flex-radio.com wrote: Well, that is progress. I don't think I have ever done a git bisect where it takes one or two days to tell good from bad. I know this is painful for you. Thanks for grinding on it. --- Graham When we get down to a kernel git bisect i have a script ready that'll take all the pain out of it.. ;) and right now it's looking v4.0.0 - v4.1.0... I'm current keeping track of things here: https://gist.github.com/RobertCNelson/b52f8318e9798625b655 I'm helping out grandma this weekend, so i'll be updating that gist when i can. (As long as the boards don't need a hard power reset) Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Just a quick update.. verfied a non v4.1.x-ti kernel failed last night.. Right now i'm looking between: linux-image-4.0.4-bone4 linux-image-4.1.2-bone12 usb: apt-get install linux-image-4.0.4-bone4 (up 1 day, 9 hours, 56 minutes) dc: apt-get install linux-image-4.0.4-bone4 (up 1 day, 9 hours, 56 minutes) 3: apt-get install linux-image-4.1.1-bone10 (up 1 hour, 15 minutes) Ran out of power supplies, so i'm going to get another 3 boards running tonight.. So i'll have 9 running in total.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Fri, Jul 31, 2015 at 9:40 AM, Robert Nelson robertcnel...@gmail.com wrote: On Fri, Jul 31, 2015 at 9:19 AM, Graham gra...@flex-radio.com wrote: Well, that is progress. I don't think I have ever done a git bisect where it takes one or two days to tell good from bad. I know this is painful for you. Thanks for grinding on it. --- Graham When we get down to a kernel git bisect i have a script ready that'll take all the pain out of it.. ;) and right now it's looking v4.0.0 - v4.1.0... I'm current keeping track of things here: https://gist.github.com/RobertCNelson/b52f8318e9798625b655 I'm helping out grandma this weekend, so i'll be updating that gist when i can. (As long as the boards don't need a hard power reset) mid-day update, 9 boards now running.. linux-image-4.1.0-rc4-bone2 just rebooted on me.. so, current kernel bisect: v4.0.0 - v4.1.0-rc4 just waiting on rc1/rc2/rc3 to fail next.. ;) Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Fri, Jul 31, 2015 at 8:42 PM, Robert Nelson robertcnel...@gmail.com wrote: mid-day update, 9 boards now running.. linux-image-4.1.0-rc4-bone2 just rebooted on me.. so, current kernel bisect: v4.0.0 - v4.1.0-rc4 just waiting on rc1/rc2/rc3 to fail next.. ;) rc3 just rebooted v4.0.0 - v4.1.0-rc3 and after 14 hours, rc1 just rebooted... I'm going to quickly rebuild rc1 without my bone0 patchset.. v4.0.0 - v4.1.0-rc1 Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
I believe is better to run several boards with the same kernel to reduce the mean time to a BAD evidence. Otherwise we have seen already times up to 3 days for a single board to reboot. So I would suggest to try instead only 2 levels at once, so 3 kernel revisions, with 8 boards running at the same time each revision for a total of 24 boards, hopping that we can advance 2 bisect levels / day. Your git repo will be much appreciated. Thanks. Nuno On Thursday, July 30, 2015 at 8:23:26 PM UTC+1, RobertCNelson wrote: On Thu, Jul 30, 2015 at 12:05 PM, dl4mea dl4...@yahoo.de javascript: wrote: I can set up easily 24 boards, and with some additional work even 48, if that helps. Günter (dl4mea) Thanks Günter, right now i'm trying to get it between two pure mainline good/bad commits.. Then we can start a distributed git bisect. I'll setup a git repo, to help automate it.. With a 24-36 hour test, each git bisect step is x^2 C B G B G B G So with 7 boards you can quickly do the first 4 steps.. At-least the fails are quick. ;) Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Thu, Jul 30, 2015 at 12:05 PM, dl4mea dl4...@yahoo.de wrote: I can set up easily 24 boards, and with some additional work even 48, if that helps. Günter (dl4mea) Thanks Günter, right now i'm trying to get it between two pure mainline good/bad commits.. Then we can start a distributed git bisect. I'll setup a git repo, to help automate it.. With a 24-36 hour test, each git bisect step is x^2 C B G B G B G So with 7 boards you can quickly do the first 4 steps.. At-least the fails are quick. ;) Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
I can set up easily 24 boards, and with some additional work even 48, if that helps. Günter (dl4mea) -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Robert: I know you are not looking for a hardware modification as a solution, but if hardware modifications would help diagnose and debug the problem, I have the capability to do blue wires or change parts, for about anything other than a BGA. The trick is to get the BBB to tell you what is triggering the reboot. The USB power feed does not do it, the +5 V barrel power input does. Kernel 3.xx does not do it, kernel 4.x.x does. I suspect some code changes from the USB main line code has changed the way the power source/direction sniffing works. For instance, the USB connectors on tablets, which is probably inside kernel 4, can accept power for charging tablet batteries, or supply power for running thumb-drives or other USB accessories. How they do this would change code in this exact area. If the PMIC is allowed to autonomously make power source switch-overs, without permission from the Sitara, and it is making bad decisions, as others have suggested, then I am not sure how to approach it. --- Graham == -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
I can also probe the board with a logic analyzer, wait to the event to occur and figure where in the hardware it started. Just don't want to be doing something that have already been discarded. Robert: could you please put us in the loop about your investigation so we can team efforts? Thanks, Nuno On Wednesday, July 29, 2015 at 4:42:20 PM UTC+1, Graham wrote: Robert: I know you are not looking for a hardware modification as a solution, but if hardware modifications would help diagnose and debug the problem, I have the capability to do blue wires or change parts, for about anything other than a BGA. The trick is to get the BBB to tell you what is triggering the reboot. The USB power feed does not do it, the +5 V barrel power input does. Kernel 3.xx does not do it, kernel 4.x.x does. I suspect some code changes from the USB main line code has changed the way the power source/direction sniffing works. For instance, the USB connectors on tablets, which is probably inside kernel 4, can accept power for charging tablet batteries, or supply power for running thumb-drives or other USB accessories. How they do this would change code in this exact area. If the PMIC is allowed to autonomously make power source switch-overs, without permission from the Sitara, and it is making bad decisions, as others have suggested, then I am not sure how to approach it. --- Graham == -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Has anyone done a control register dump of the PMIC under kernel 4 and compared it to a register dump under kernel 3 to see if anything has changed? --- Graham == On Wednesday, July 29, 2015 at 10:42:20 AM UTC-5, Graham wrote: Robert: I know you are not looking for a hardware modification as a solution, but if hardware modifications would help diagnose and debug the problem, I have the capability to do blue wires or change parts, for about anything other than a BGA. The trick is to get the BBB to tell you what is triggering the reboot. The USB power feed does not do it, the +5 V barrel power input does. Kernel 3.xx does not do it, kernel 4.x.x does. I suspect some code changes from the USB main line code has changed the way the power source/direction sniffing works. For instance, the USB connectors on tablets, which is probably inside kernel 4, can accept power for charging tablet batteries, or supply power for running thumb-drives or other USB accessories. How they do this would change code in this exact area. If the PMIC is allowed to autonomously make power source switch-overs, without permission from the Sitara, and it is making bad decisions, as others have suggested, then I am not sure how to approach it. --- Graham == -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
On Wed, Jul 29, 2015 at 11:05 AM, Nuno Gonçalves nuno...@gmail.com wrote: I can also probe the board with a logic analyzer, wait to the event to occur and figure where in the hardware it started. Just don't want to be doing something that have already been discarded. Robert: could you please put us in the loop about your investigation so we can team efforts? Well right now it's.. git bisect start git bisect good v3.14 git bisect bad v4.12-rc4 rebuild... run for 24 hours (or if it resets earlier)... retest.. Wish we could trigger it faster.. but it's going to take awhile.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
I have seen some releases take more than 24 hours to fail. If it fails, then it does, but if it doesn't, you may have to go two full days before you can start thinking that you found it. --- Graham == On Wednesday, July 29, 2015 at 1:44:08 PM UTC-5, Graham wrote: OK. Understand. If you need help testing a version, send me a note. --- Graham == On Wednesday, July 29, 2015 at 12:33:10 PM UTC-5, RobertCNelson wrote: On Wed, Jul 29, 2015 at 11:05 AM, Nuno Gonçalves nun...@gmail.com wrote: I can also probe the board with a logic analyzer, wait to the event to occur and figure where in the hardware it started. Just don't want to be doing something that have already been discarded. Robert: could you please put us in the loop about your investigation so we can team efforts? Well right now it's.. git bisect start git bisect good v3.14 git bisect bad v4.12-rc4 rebuild... run for 24 hours (or if it resets earlier)... retest.. Wish we could trigger it faster.. but it's going to take awhile.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
OK. Understand. If you need help testing a version, send me a note. --- Graham == On Wednesday, July 29, 2015 at 12:33:10 PM UTC-5, RobertCNelson wrote: On Wed, Jul 29, 2015 at 11:05 AM, Nuno Gonçalves nun...@gmail.com javascript: wrote: I can also probe the board with a logic analyzer, wait to the event to occur and figure where in the hardware it started. Just don't want to be doing something that have already been discarded. Robert: could you please put us in the loop about your investigation so we can team efforts? Well right now it's.. git bisect start git bisect good v3.14 git bisect bad v4.12-rc4 rebuild... run for 24 hours (or if it resets earlier)... retest.. Wish we could trigger it faster.. but it's going to take awhile.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Downloaded and installed bone-debian-8.1-console-armhf-2015-07-26-2gb.img No modifications or updates. Trusted BBB Rev.C powered with Adafruit 2A wallwart via +5V barrel connector. No capes. Just power and Ethernet connected. Times and dates are UTC. BeagleBoard.org Debian Image 2015-07-26 Linux beaglebone 4.1.3-ti-r6 #1 SMP PREEMPT Fri Jul 24 23:16:27 UTC 2015 armv7l GNU/Linux Jul 28 04:38:27Initial Boot after download and install Jul 28 23:15:41Autonomous Reboot Wed Jul 29 01:00:53 UTC 2015 -- Current time of report == -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
debian@beaglebone:~$ uptime 19:48:12 up 14 days, 5:49, 1 user, load average: 0.00, 0.01, 0.05 *runs and hides* On Tue, Jul 28, 2015 at 7:00 PM, Robert Nelson robertcnel...@gmail.com wrote: Thanks for testing Graham! On Tue, Jul 28, 2015 at 8:54 PM, Graham gra...@flex-radio.com wrote: Downloaded and installed bone-debian-8.1-console-armhf-2015-07-26-2gb.img No modifications or updates. Trusted BBB Rev.C powered with Adafruit 2A wallwart via +5V barrel connector. No capes. Just power and Ethernet connected. Times and dates are UTC. BeagleBoard.org Debian Image 2015-07-26 Linux beaglebone 4.1.3-ti-r6 #1 SMP PREEMPT Fri Jul 24 23:16:27 UTC 2015 armv7l GNU/Linux Jul 28 04:38:27Initial Boot after download and install Jul 28 23:15:41Autonomous Reboot Wed Jul 29 01:00:53 UTC 2015 -- Current time of report Darn, I was hoping by having the correct cpufreq opp tables that would mitigate the reboot.. Mine only rebooted once on me today, with no details.. This is one strange bug.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6
Thanks for testing Graham! On Tue, Jul 28, 2015 at 8:54 PM, Graham gra...@flex-radio.com wrote: Downloaded and installed bone-debian-8.1-console-armhf-2015-07-26-2gb.img No modifications or updates. Trusted BBB Rev.C powered with Adafruit 2A wallwart via +5V barrel connector. No capes. Just power and Ethernet connected. Times and dates are UTC. BeagleBoard.org Debian Image 2015-07-26 Linux beaglebone 4.1.3-ti-r6 #1 SMP PREEMPT Fri Jul 24 23:16:27 UTC 2015 armv7l GNU/Linux Jul 28 04:38:27Initial Boot after download and install Jul 28 23:15:41Autonomous Reboot Wed Jul 29 01:00:53 UTC 2015 -- Current time of report Darn, I was hoping by having the correct cpufreq opp tables that would mitigate the reboot.. Mine only rebooted once on me today, with no details.. This is one strange bug.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
