| Message ID | 5A47E75E594F054BAF48C5E4FC4B92AB030A09B280@dbde02.ent.ti.com (mailing list archive) |
|---|---|
| State | Superseded, archived |
| Headers | show |
Anand, > -----Original Message----- > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap- > owner@vger.kernel.org] On Behalf Of Gadiyar, Anand > Sent: Friday, September 11, 2009 2:55 PM > To: Gadiyar, Anand; linux-omap@vger.kernel.org > Subject: RE: 3430SDP: Crash on first UART keypress after boot > > > Current linux-omap kernel boots up fine on 3430 SDP after > > adding Sergio's patch [1], but then I get the following crash > > on the first UART keypress. > > > > This is new, it used to work okay a little while ago. > > > > Regards, > > Anand > > The crash still exists with current linux-omap kernel. > > Disabling CONFIG_FB_OMAP makes the issue go away. > > (Only disabled this one option - see diff between .config.old > and .config below) > I don't see this issue on my SDP even with OMAP_FB enabled. May be we have different ES versions -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
> > > > > Current linux-omap kernel boots up fine on 3430 SDP after > > > adding Sergio's patch [1], but then I get the following crash > > > on the first UART keypress. > > > > > > This is new, it used to work okay a little while ago. > > > > > > Regards, > > > Anand > > > > The crash still exists with current linux-omap kernel. > > > > Disabling CONFIG_FB_OMAP makes the issue go away. > > > > (Only disabled this one option - see diff between .config.old > > and .config below) > > > > I don't see this issue on my SDP even with OMAP_FB enabled. > May be we have different ES versions Thanks for testing - switching to a different filesystem, the crash goes away. But I'm still not sure what caused the crash to disappear with the old filesystem but with CONFIG_FB_OMAP removed. Confused, Anand -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
====CUT HERE==== --- .config.old 2009-09-11 14:54:57.000000000 +0530 +++ .config 2009-09-11 14:55:08.000000000 +0530 @@ -1,7 +1,7 @@ # # Automatically generated make config: don't edit # Linux kernel version: 2.6.31-rc9-omap1 -# Fri Sep 11 14:54:57 2009 +# Fri Sep 11 14:55:08 2009 # CONFIG_ARM=y CONFIG_SYS_SUPPORTS_APM_EMULATION=y @@ -1154,9 +1154,9 @@ CONFIG_FB=y # CONFIG_FIRMWARE_EDID is not set # CONFIG_FB_DDC is not set # CONFIG_FB_BOOT_VESA_SUPPORT is not set -CONFIG_FB_CFB_FILLRECT=y -CONFIG_FB_CFB_COPYAREA=y -CONFIG_FB_CFB_IMAGEBLIT=y +# CONFIG_FB_CFB_FILLRECT is not set +# CONFIG_FB_CFB_COPYAREA is not set +# CONFIG_FB_CFB_IMAGEBLIT is not set # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set # CONFIG_FB_SYS_FILLRECT is not set # CONFIG_FB_SYS_COPYAREA is not set @@ -1177,12 +1177,8 @@ CONFIG_FB_CFB_IMAGEBLIT=y # CONFIG_FB_METRONOME is not set # CONFIG_FB_MB862XX is not set # CONFIG_FB_BROADSHEET is not set -CONFIG_FB_OMAP=y +# CONFIG_FB_OMAP is not set # CONFIG_FB_OMAP_LCD_VGA is not set -# CONFIG_FB_OMAP_LCDC_EXTERNAL is not set -# CONFIG_FB_OMAP_LCD_MIPID is not set -# CONFIG_FB_OMAP_BOOTLOADER_INIT is not set -CONFIG_FB_OMAP_CONSISTENT_DMA_SIZE=2 # CONFIG_BACKLIGHT_LCD_SUPPORT is not set #