Beagleboard serial port crashing

My console connection to the beagleboard is dying after around 10 minutes of
uptime. This happens with 2.6.29 kernels (both standard and from the pm
branch). After it happens, the console does not produce any new characters,
and ignores all input.

It's not the host computer serial port, because if I reset the beagleboard I
get the boot messages immediately.

This is not the serial sleep-on-idle feature. That sleep manifests itself on
my beagle as corrupt characters as it comes out of sleep, but it *did* always
respond.

Any ideas? I'm happy to run diagnostic commands.

Cameron.

Specs:
Beagleboard: RevC3
Serial cable: Digikey Part BBC01-ND (recommended on bb.org)
serial program: minicom

Hardware mods:
Shorted OTG id pin (force host mode)
Installed Battery (BT1) - Removed R66

Kernel:
Custom linux-omap-pm 2.6.29 built using patches and defconfig from
http://rcn-ee.homeip.net:81/dl/omap/beagle/v2.6.29-e63cf07-pm42.1
More detail on kernel build process at:
http://bioacoustics.cse.unsw.edu.au/trac/core/wiki/BeagleBuildCustomKernel

My console connection to the beagleboard is dying after around 10 minutes of
uptime. This happens with 2.6.29 kernels (both standard and from the pm
branch). After it happens, the console does not produce any new characters,
and ignores all input.

It's not the host computer serial port, because if I reset the beagleboard I
get the boot messages immediately.

This is not the serial sleep-on-idle feature. That sleep manifests itself on
my beagle as corrupt characters as it comes out of sleep, but it *did* always
respond.

Any ideas? I'm happy to run diagnostic commands.

Cameron.

Specs:
Beagleboard: RevC3
Serial cable: Digikey Part BBC01-ND (recommended on bb.org)
serial program: minicom

Hardware mods:
Shorted OTG id pin (force host mode)
Installed Battery (BT1) - Removed R66

Kernel:
Custom linux-omap-pm 2.6.29 built using patches and defconfig from
http://rcn-ee.homeip.net:81/dl/omap/beagle/v2.6.29-e63cf07-pm42.1

Yeah, i couldn't get that 'pm' patchset kernel to work reliably...
What your seeing is what i saw..

I'd atleast try refreshing the patches from the latest angstrom
2.6.29-pm.. Or use the new mainline patches just submitted to the l-o
mailing list..

More detail on kernel build process at:
http://bioacoustics.cse.unsw.edu.au/trac/core/wiki/BeagleBuildCustomKernel

>

Regards,