Humm, so it took awhile to finally trigger one, but then it only
occurred since my nfs server had been rebooted...
[ 28.945678] eth0: no IPv6 routers present
[87216.428833] nfs: server 192.168.1.95 not responding, timed out
[87360.618927] INFO: task expect:27318 blocked for more than 120 seconds.
[87360.625885] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[87360.634246] expect D c04e4c50 0 27318 21265 0x00000000
[87360.641052] Backtrace:
[87360.643707] [<c04e4864>] (__schedule+0x0/0x43c) from [<c04e4dbc>]
(schedule+0x78/0x7c)
[87360.652160] [<c04e4d44>] (schedule+0x0/0x7c) from [<c04e4e58>]
(io_schedule+0x98/0x108)
[87360.660736] [<c04e4dc0>] (io_schedule+0x0/0x108) from [<c0089660>]
(sleep_on_page+0x10/0x18)
[87360.669738] r4:cec89dec r3:0000000d
[87360.673583] [<c0089650>] (sleep_on_page+0x0/0x18) from [<c04e5328>]
(__wait_on_bit+0x5c/0xa8)
[87360.682678] [<c04e52cc>] (__wait_on_bit+0x0/0xa8) from [<c00897fc>]
(wait_on_page_bit+0x98/0xa8)
[87360.692047] [<c0089764>] (wait_on_page_bit+0x0/0xa8) from
[<c00898cc>] (filemap_fdatawait_range+0x70/0x148)
[87360.702423] r5:ffffffff r4:c14624b0
[87360.706268] [<c008985c>] (filemap_fdatawait_range+0x0/0x148) from
[<c008a7c4>] (filemap_write_and_wait_range+0x5c/0x70)
[87360.717773] [<c008a768>] (filemap_write_and_wait_range+0x0/0x70)
from [<c0189e64>] (nfs_file_fsync+0x68/0x13c)
[87360.728424] r9:00000000 r8:00000000 r7:00000006 r6:00000000 r5:c5d67900
Regards,
Images to test…
http://rcn-ee.homeip.net:81/testing/beaglebone/3.2-cpufreq-more/
I have tested this image on my BeagleBone now, using the same memory cards as earlier. The device crashes during boot, seemingly right before the loging prompt would be shown. There is unfortunatly no crash report written to the serial port.
Wrt. applications, the crash seems mostly to occur when I log in. It does not matter if I log in through SSH or the serial port. What is strange is that my start-up scripts most of the time run correctly, the crash seems to be triggered by me logging in to the device.
-Kristian
I have experimented with the Angstrom kernel now, and I see the same behavior. I replaced uImage and modules with the ones from here [1], and after a seemingly successful boot, the device crashes.
-Kristian
[1] - http://downloads.angstrom-distribution.org/demo/beaglebone/
I tried this /3.2-cpufreq-more/ version and have the same crash but now I am looking at the backtrace it is different to yours at the top but still ends up stalling when it 's attempting to schedule io. Mine seems to be locking up scheduling tty io which I assume is eventually going into the USB serial device.
Does anyone know if the wait for completion and schedule encapsulates some sort of interrupt setup and callback? Interrupts not working maybe?
I did some more experimentation, with a new kernel built today (git describe gives 3.2-psp9-2-gd2cef3a). I thought I had tried the different power inputs before, but maybe I remember wrong.
If I boot using USB, then everything works and the device seems stable. I am not sure that the crash will not occur, but the machine has been up for the last couple of hours. On a second machine where the crash-problem also occurs, I have tried multiple reboots (USB-powered) and I have been able to log in every time (both SSH and serial).
If I, on the other hand, boot using the 5V, then the machine crashes as described earlier. The crash either happens during the boot sequence or when I try to log in. This also happens on the other machine with the crash-problem.
-Kristian
A curious thing happened tonight.
I had to power off the PC so there was no serial console connection and suddenly I noticed the BeagleBone had booted and there was a login prompt on the 7" Liliput USB screen.
I am logged in and installing packages.
tindog:/home/lancelot # ssh -X bone
The authenticity of host 'bone (192.168.10.19)' can't be established.
ECDSA key fingerprint is 0b:d0:ca:10:2c:26:9e:36:bc:02:ce:e1:b7:54:0a:3f.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'bone,192.168.10.19' (ECDSA) to the list of known hosts.
root@bone's password:
Welcome to Ubuntu 11.10 (GNU/Linux 3.2.17-psp10.1 armv7l)
* Documentation: https://help.ubuntu.com/
Last login: Sat May 19 17:41:36 2012
/usr/bin/xauth: file /root/.Xauthority does not exist
root@omap:~# uname -r
3.2.17-psp10.1
root@omap:~#
Regards
Sid.
I have now tried every ubuntu version and release from this page http://elinux.org/BeagleBoardUbuntu since may and all of them have the hung timeout message. Does anyone want to buy a revision A4 that seems to boot fine with the stock angstrom build that comes with the board but won’t run debian? I am in Australia but can mail it anywhere.