On Tue, May 18, 2010 at 3:34 PM, Robert Nelson <[email protected]> wrote: > On Tue, May 18, 2010 at 2:55 AM, Tomi Valkeinen > <[email protected]> wrote: >> On Mon, 2010-05-17 at 16:30 +0200, ext Robert Nelson wrote: >>> Hi Tomi, >>> >>> I've been using your dss2 branch with much success. >>> >>> http://gitorious.org/linux-omap-dss2/linux/commits/for-next >>> >>> I've just ran into a weird BUG that occurs on reboot on my headless >>> beagles and wondering if you've ran into it too... >>> >>> The kernel I'm currently testing is 2.6.34-rc7 plus the 2.6.35 dss2 >>> for-next commits.. >>> >>> I was assuming >>> http://gitorious.org/linux-omap-dss2/linux/commit/89627989c6b4408c4578a41bcd5f9d04545797ad >>> would fix it, but it hasn't fixed the Opps'ing... >>> >>> log on attempt to reboot: >>> >>> http://pastebin.com/iqAHMVD4 >> >> It looks like there's a mismatch with clock enables and disables >> somewhere... I haven't seen that. >> >> Can you tell me more details of your beagle? Does "headless" mean that >> it's standard beagle board, but no display is connected to it? > > Correct, just a beagle with no display connected.. > > I upgraded to 2.6.34 final plus dss2 for-next and enabled omapfb.debug > and a generic modesetting to see if would make any difference in the > bootargs. Same result.. > > http://www.pastie.org/965380 > > I should also mention, this only occurs after a small length of time > (about 10 minutes).. I can't seem to trigger it after a frresh reboot > (1-2 minutes).. > > config for reference: > http://bazaar.launchpad.net/~beagleboard-kernel/+junk/2.6.34-devel/annotate/head:/patches/lucid-defconfig
I think I saw this bug yesterday, but didn't paid much attention. CC'ing Ville who might have fixed this already. -- Felipe Contreras -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
