On 4/21/2011 1:12 AM, Paul Walmsley wrote:
Hi Rajendra, Santosh, just FYI I just observed this happening without the clockdomain patch, and tracked this down. It seems that there is an intermittent problem with the OMAP L3 bus code. On the 35xx BeagleBoard here, it occasionally hangs after powerup: [ 0.810119] OMAP GPIO hardware version 2.5 [ 0.815368] OMAP GPIO hardware version 2.5 [ 0.820465] OMAP GPIO hardware version 2.5 [ 0.825531] OMAP GPIO hardware version 2.5 [ 0.830657] OMAP GPIO hardware version 2.5 [ 0.835784] OMAP GPIO hardware version 2.5 [ 0.840881] initcall omap_gpio_drv_reg+0x0/0xc returned 0 after 38146 usecs [ 0.848358] calling bdi_class_init+0x0/0x50 @ 1 [ 0.854003] initcall bdi_class_init+0x0/0x50 returned 0 after 0 usecs [ 0.860870] calling kobject_uevent_init+0x0/0x20 @ 1 [ 0.866363] initcall kobject_uevent_init+0x0/0x20 returned 0 after 0 usecs [ 0.873626] calling gpiolib_sysfs_init+0x0/0x98 @ 1 [ 0.885894] initcall gpiolib_sysfs_init+0x0/0x98 returned 0 after 0 usecs [ 0.893157] calling lcd_class_init+0x0/0x58 @ 1 [ 0.898742] initcall lcd_class_init+0x0/0x58 returned 0 after 0 usecs [ 0.905731] calling backlight_class_init+0x0/0x70 @ 1 [ 0.911834] initcall backlight_class_init+0x0/0x70 returned 0 after 0 usecs [ 0.919219] calling tty_class_init+0x0/0x3c @ 1 [ 0.924743] initcall tty_class_init+0x0/0x3c returned 0 after 0 usecs [ 0.931610] calling vtconsole_class_init+0x0/0xe4 @ 1 [ 0.938812] initcall vtconsole_class_init+0x0/0xe4 returned 0 after 7629 usecs [ 0.946472] calling wakeup_sources_debugfs_init+0x0/0x3c @ 1 [ 0.952606] initcall wakeup_sources_debugfs_init+0x0/0x3c returned 0 after 0 usecs [ 0.960571] calling spi_init+0x0/0x88 @ 1 [ 0.966247] initcall spi_init+0x0/0x88 returned 0 after 0 usecs [ 0.972564] calling i2c_init+0x0/0x70 @ 1 [ 0.978485] initcall i2c_init+0x0/0x70 returned 0 after 0 usecs [ 0.984832] calling omap3_l3_init+0x0/0x14 @ 1
Will have a look at it -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
