I have had similar experiences to you. I wanted the power management features so went with the 3.2 kernel from Ti. In the end I gave up and switched to a 3.8 kernel and for now will do without PM.
Even the default file image supplied with the SDK would reboot randomly. Nothing in the logs or on the serial console to indicate why. Initially I thought it was U-Boot and maybe it was setting up the memory timings too aggressively. I noticed the the Ti image gave me a higher BogoMips value than the Angstrom kernel that came pre-installed. Using the U-Boot from the Angstrom image and the kernel from Ti resulted in a lower Bogomips value, so there is certainly something going on there, but the Ti kernel still crashed randomly. My complied 3.8 kernel with the Ti U-Boot or the Angstorm U-Boot is fine though (again lower BogoMips on the Angstrom U-Boot). I also tried several different boards with the same result. I also can't get the accelerated graphics to work with my 3.8 kernel, but for now framebuffer support is OK I did find a git repository based on a 3.11 kernel ( git://github.com/dgerlach/linux-pm.git ) , with power management, but I could not get that to boot, it would just hang after U-Boot decompressed the kernel and given my schedule I was running out of time to try and figure out what I had done wrong. Given time I will go back to it and maybe see if I can get it working. On Wednesday, 30 October 2013 18:09:57 UTC, bko...@scanimetrics.com wrote: > > Hello all, > > Over the last few days I've been trying to get the 3.2 Linux Kernel > (AM335x-PSP_04.06.00.11) that comes with TI's 06.00.00.00 SDK to work on > the Beagle Bone Black with a Debian root file system. I compiled the kernel > from their source code myself along with a few extra modules that I need. > The end goal is to port a data logging application to the Beagle Bone > Black. The reason to use TI's kernel is that it is the only kernel that I > am aware of that supports power management functionality on the Beagle Bone > Black. The reason to use Debian is because the data logging application > currently runs on a Debian system; pre-built packages and experience with > Debian ought to make the port easier. > > I have managed to successfully bolt the 3.2 kernel into a Debian root file > system that runs off the emmc. Everything seems to work fine except that > the board reboots itself at random intervals (typically at least once every > 4 hours). At the time of the reboots I am not running any application and > am just letting Linux idle. > > The reboots are not accompanied by any suspicious messages in syslog or > dmesg (I also have an FTDI cable hooked up to capture messages from the > console and still see nothing). > > I am powering the board via the barrel connector and have tried multiple > power supplies but see no improvement. To further rule out power supply > issues, I have also tried the 3.8 kernel with the exact same root file > system with the same boot loader and have found that the reboots simply > disappear. > > At this point I am very stuck and am open to any ideas and will be very > thankful for any insights. > > I fear that in order to get up and running with a Kernel that supports > power management I may have to use TI's Arago distribution and compile all > needed packages from source which, although I've never done something like > that before, seems like it would take a whole lot of time and effort. > > Thanks! > > > -- 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/groups/opt_out.
