[overo] OTG broken? Udev issue?

[overoarm]

On a fresh install of alarm on my overo fire I ran into issues once I updated. It seems as though udev and my OTG are not playing nice. The OTG port is on my gumstix summit expansion board. Everything worked on the initial image downloaded
Boot error$this->bbcode_second_pass_code('', 'Uncompressing Linux... done, booting the kernel.
[ 0.119995] Could not look up mcpdm hw_mod
[ 1.851165] twl4030_wdt twl4030_wdt: Failed to register misc device
[ 2.084106] omap_hsmmc omap_hsmmc.1: could not set regulator OCR (-22)
[ 2.413665] omap_hsmmc omap_hsmmc.1: could not set regulator OCR (-22)
INIT: version 2.88 booting')
Udev error$this->bbcode_second_pass_code('', ':: Waiting for UDev uevents to be processed [BUSY]
udevd[85]: worker [88] timeout, kill it
udevd[85]: seq 1029 '/devices/platform/omap/omap_hsmmc.1/mmc_host/mmc1/mmc1:0001/mmc1:0001:1' killed')

I have tried searching for something relating and I am not having any luck as of yet. Does uImage need to be refreshed? Such as in the same manner as on Arch by running mkinitcpio -p kernelName , but no preset file for the kernel. Maybe I am confusing myself with Arch and alarm, I am new to the ARM world.

Other info$this->bbcode_second_pass_code('', 'Linux alarm 3.2.7-1-ARCH #1 SMP PREEMPT Sat Feb 25 23:37:27 UTC 2012 armv7l ARMv7 Processor rev 3 (v7l) Gumstix Overo GNU/Linux
console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext4 raid=noautodetect rootwait')
Everything is on a 16GB class 4 Kingston sdcard
My apologies if these are really basic issues but I feel lost on what to do. I appreciate any time and help on this, if more information about anything is needed please let me know and I will post. Thank you very much for helping me resolve my issue.

edited to fix typo's and remove something I was confusing myself over that was not an issue.

edit2:
Just noticed this as well $this->bbcode_second_pass_code('', 'hwclock
hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory
ls -la /dev/rtc
lrwxrwxrwx 1 root root 4 Dec 31 18:57 /dev/rtc -> rtc0
ls -la /dev/rtc0
crw------- 1 root root 254, 0 Dec 31 18:57 /dev/rtc0')
Not sure if this is related though, just another thing I just ran across.
Thanks

[overoarm]

Well I went back to 3.2.6 kernel and it got rid of my udev messages and that booted cleanly, brought back my USB keyboard mouse and monitor as well. OTG USB still does not work for me and I still get this on the boot up$this->bbcode_second_pass_code('', 'Uncompressing Linux... done, booting the kernel.
[ 1.851165] twl4030_wdt twl4030_wdt: Failed to register misc device
[ 2.084106] omap_hsmmc omap_hsmmc.1: could not set regulator OCR (-22)
INIT: version 2.88 booting')

I see that is set to be built into the kernel. I am going to try building it as a module instead and see if that solves that message. I will also go and diff the 2 version's config's and see what broke my usb keyboard, mouse, hub and monitor. Hopefully will find something that will help with OTG as well, as my expansion board really needs that to work properly. I will post back anything else I find out.

Though I understand some do not have a hwclock and maybe the step in the first steps guide is not relevant but I still get that error when I try and run hwclock --systohc as well.

Thanks

[overoarm]

Just updated again and udev spits this back out$this->bbcode_second_pass_code('', 'udevd[84]: worker [87] timeout, kill it
udevd[84]: seq 1001 '/devices/platform/omap/omap_hsmmc.1/mmc_host/mmc1/mmc1:0001/mmc1:0001:1' killed')

I recompiled 3.2.7 and was able to bring back all the USB devices I lost when upgrading through alarm. But I am getting mixed results in eliminating this error $this->bbcode_second_pass_code('', 'Uncompressing Linux... done, booting the kernel.
[ 1.836944] twl4030_wdt twl4030_wdt: Failed to register misc device
[ 2.179595] omap_hsmmc omap_hsmmc.1: could not set regulator OCR (-22)
INIT: version 2.88 booting')
Seems every couple boots it shows back up. I am not noticing anything and can not find anything online relating to this. Would really appreciate some help in figuring this out.

Is anyone else running overo? Has anyone else noticed the load address is different on the alarm bootcmd suggestions vs. the loadaddr that is stated on gumstix docs, is there a reason of the difference? I have booted with both loadaddr's and see nothing different other than my board on boot actually recognizes NAND.
$this->bbcode_second_pass_code('', 'setenv bootargs 'console=ttyO2,115200n8 mpurate=500 root=/dev/mmcblk0p2 rw root rootfstype=ext4 raid=noautodetect omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=dvi rootwait'
fatload mmc 0 0x82000000 uImage
bootm 0x82000000
boot')

Thanks for anyone offering suggestions links anything for me to try googlefu is failing me still at the moment.

[overoarm]

well bumped kernel to 3.2.9 used the x6 rcn patches and added a few more overo related patches and have been able to get OTG working again and everything on my gumstix overo expansion board. If anyone is actually interested in the overo stuff I can post my config changes and patches not in rcn. But seems to not be many using an overo on here.

Got DSP almost fully working as well.

[overoarm]

wow pretty shocked no one even chimed in to try and pass on tips, views anything.

Anyways, just imported more missing overo patches that rcn-ee patchset does not have, was kind of surprising how many functionality patches were missing past just the ability to boot and get internet. 3.2.9 Kernel works wonders for me, brought back all lost sensors and chips on my gumstix expansion board, also brought back functionality to my libertas_sdio chip. DSP has been tested fully and is working perfectly. Have written a few new recipes for things missing in alarm relating to DSP.

If anyone would like these as well I can post the PKGBUILDS. If no interest is expressed I will stop posting my further findings and what packages I have added PKGBUILDS for. I have a local repo setup that I can share as well if anyone does not want to compile a DSP kernel and the rest of the required packages.

edit:
and if you want DSP you need to pay attention to the boot args I posted above especially loadaddr. Then add in the missing parts for the DSP.

[ilikedarkbeer]

I guess the overo isn't a popular platform here...

I dunno if you're still around but I'm very much intersted in how you fixed the OTG port.
I've inherited an older overo with no bluetooth or wifi + summit expansion board so the ethernet over usb gadget is my only useful connection to the board. So far I've had no luck with any post 3.0 kernel from anywhere.