On 06/27/12 18:24, the mail apparently from Ramakrishnan Muthukrishnan included:
Hi,
With the latest tilt-3.4 branch, I see these messages in the kernel while booting up:
[ 3.176330] twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) [ 3.185882] omap_vout omap_vout: 'hdmi' Display already enabled [ 3.192138] omap_vout omap_vout: 'hdmi' Display already enabled [ 3.198425] omap_vout omap_vout: Buffer Size = 3686400 [ 3.204925] omapdss OVERLAY error: check_overlay: paddr cannot be 0
Hum
[ 3.211578] omap_vout omap_vout: setup_overlay failed [ 3.216949] omap_vout omap_vout: apply_changes failed [ 3.235626] omap_vout: probe of omap_vout failed with error -22 [ 3.242187] omap_vout:Could not register Video driver
After that....
[ 3.253204] dmm dmm: initialized all PAT entries [ 3.414428] [drm] Enabling DMM ywrap scrolling [ 3.486267] Console: switching to colour frame buffer device 240x67 [ 3.517700] fb0: omapdrm frame buffer device [ 3.522308] drm: registered panic notifier [ 3.526733] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 3.533843] [drm] No driver support for vblank timestamp query. [ 3.540252] [drm] Initialized omapdrm 1.0.0 20110917 on minor 0 [ 3.546905] ALSA device list: [ 3.550079] #0: PandaBoard [ 3.553222] #1: OMAPHDMI [ 3.793914] kjournald starting. Commit interval 5 seconds [ 3.796417] EXT3-fs (mmcblk0p2): using internal journal [ 3.798736] EXT3-fs (mmcblk0p2): recovery complete [ 3.798736] EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode [ 3.798767] VFS: Mounted root (ext3 filesystem) on device 179:2. [ 3.803009] devtmpfs: mounted [ 3.803314] Freeing init memory: 360K INIT: version 2.86 booting
...it all seems pretty nice.
I don't see any /dev/video* devices listed as expected.
Another observation is that, I see random kernel oops messages (they are totally random and I don't see them on reboot in some occasions). Here is the log when I see the crash:
Like it says these are warnings
[ 4.535278] WARNING: at fs/sysfs/file.c:343
sysfs_open_file+0x7c/0x238()
they are not OOPSes or crashes.
Error opening /dev/fb0: No such file or directory Starting udev [ 4.311767] udevd (797): /proc/797/oom_adj is deprecated, please use /proc/797/oom_score_adj instead. [ 4.463073] ------------[ cut here ]------------ [ 4.535278] WARNING: at fs/sysfs/file.c:343 sysfs_open_file+0x7c/0x238() [ 4.692840] missing sysfs attribute operations for kobject:
This is meant to tell the name of the kobject which has no attribute operations, apparently ''. I guess udev touched everything in sight and provoked this warning, possibly as a consequence of the first problem about paddr being 0 killing registration of something. But the warning itself isn't fatal.
[ 0.000000] Kernel command line: console=tty0 console=ttyO2,115200n8 earlycon=ttyO2,115200n8 earlyprintk=1 root=/dev/mmcblk0p2 rootwait rw vram=32M omapfb.vram=0:16M,1:16M omapdss.def_disp=hdmi
I doubt it's the source of the problem but you shouldn't need any of that stuff about vram, omapfb, omapdss.
-Andy