followup to: http://groups.google.com/group/beagleboard/browse_thread/thread/cd8ea1b8c7518c9f/d55ad4bfc0ac95e8
this problem is still happening sometimes
under low load i can get weeks of uptime, but when copying large files
over the network the crash is quite common. i have been using watchdog
to reboot the board when it does crash (by checking if it can ping the
router),
i have updated to 2.6.32.7-x7.0, and swapped the usb-ide adapter for a
WD usb drive.
this makes the board unusable as a network backup server, though it is
fine as a MPD player.
I am wondering about getting a C4, but i'm not sure that will help
with the OTG port
sam
Hi Sam,
followup to: http://groups.google.com/group/beagleboard/browse_thread/thread/cd8ea1b8c7518c9f/d55ad4bfc0ac95e8
this problem is still happening sometimes
under low load i can get weeks of uptime, but when copying large files
over the network the crash is quite common. i have been using watchdog
to reboot the board when it does crash (by checking if it can ping the
router),
I'm not sure on your setup, but one thing I've done while running
stress testing the musb otg port. Move your rootfs to the SD card,
and using the external usb harddrive for mounted storage and swap..
i have updated to 2.6.32.7-x7.0, and swapped the usb-ide adapter for a
WD usb drive.
Give this build a try: (I've been testing musb patches headed for 2.6.33)
http://rcn-ee.homeip.net:81/dl/linux-image-2.6.32.7-x7.1_1.0cross_armel.deb
and make sure the fifo is mode 5: "dmesg | grep fifo"
this makes the board unusable as a network backup server, though it is
fine as a MPD player.
I am wondering about getting a C4, but i'm not sure that will help
with the OTG port
I'm in the process of testing that too, just waiting on two new usb
harddrives... I'm expecting the OTG port to ack exactly the same..
(knock on wood) The ehci should work great now, any issues should just
be bugs in the kernel ehci layer..
Regards,
thanks. i have run that for a few days
uname -a
Linux beagleboard 2.6.32.7-x7.1 #1 PREEMPT Wed Feb 3 18:45:18 CST 2010
armv7l GNU/Linux
(i basically followed the commands in one of your install scripts to
install it, i hope thats write)
dmesg | grep fifo
[71393.617248] musb_hdrc: setup fifo_mode 5
still get the crashes. it seems slightly better to start with, but its
hard to be objective.
my setup is a rev C3, power by the 5 volt from a USB hub. the hub is
connect to the OTG port. the hub has a hard disk, and an usb-ethernet
sam@beagleboard:/data/aarddict/201002$ mount
/dev/mmcblk0p2 on / type ext3 (rw,noatime,errors=remount-ro)
...
/dev/sda1 on /data type ext4 (rw)
sam@beagleboard:/data/aarddict/201002$ lsusb
Bus 002 Device 005: ID 1058:1010 Western Digital Technologies, Inc.
Bus 002 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port
HUB
Bus 002 Device 003: ID 0a46:9601 Davicom Semiconductor, Inc. DM9601
Fast Ethernet Adapter
Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port
HUB
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
sam@beagleboard:/data/aarddict/201002$
i am happy to experiment a bit. but i dont have a build environment
set up.
thanks
sam
i have tested with angstrom ( http://code.google.com/p/beagleboard/wiki/HowToGetAngstromRunning
)
root@beagleboard:~# uname -a
Linux beagleboard 2.6.29-omap1 #1 PREEMPT Wed Oct 21 13:11:52 CEST
2009 armv7l GNU/Linux
which seems to be stable.
also with one of the older ubuntu kernels http://rcn-ee.net/deb/kernel/beagle/karmic/v2.6.29-x45.2/
(the newest 2.6.29), which gave the crash.
sam