genpix, have you checked dmesg to see if anything shows up there ?
And yeah, I’ve noticed that Debian is really solid myself.
Yeah, I see a lot of mmcblk0 errors (sector #'s with the error are all different after each reboot).
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2013.07.10 18:58:23 =~=~=~=~=~=~=~=~=~=~=~=
U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
mmc_send_cmd : timeout: No status update
reading u-boot.img
reading u-boot.img
U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14)
I2C: ready
DRAM: 512 MiB
WARNING: Caches not enabled
NAND: No NAND device found!!!
0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net: not set. Validating first E-fuse MAC
Phy not found
PHY reset timed out
cpsw, usb_ether
Hit any key to stop autoboot: 1 0
gpio: pin 53 (gpio 53) value is 1
mmc_send_cmd : timeout: No status update
Card did not respond to voltage select!
mmc0(part 0) is current device
mmc_send_cmd : timeout: No status update
Card did not respond to voltage select!
No micro SD card found, setting mmcdev to 1
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 1
reading uEnv.txt
26 bytes read in 2 ms (12.7 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc …
gpio: pin 55 (gpio 55) value is 1
4270840 bytes read in 746 ms (5.5 MiB/s)
gpio: pin 56 (gpio 56) value is 1
24129 bytes read in 51 ms (461.9 KiB/s)
Booting from mmc …
Booting kernel from Legacy Image at 80007fc0 …
Image Name: Angstrom/3.8.13/beaglebone
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4270776 Bytes = 4.1 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum … OK
Flattened Device Tree blob at 80f80000
Booting using the fdt blob at 0x80f80000
XIP Kernel Image … OK
OK
Using Device Tree in place at 80f80000, end 80f88e40
Starting kernel …
Uncompressing Linux… done, booting the kernel.
[ 0.194190] omap2_mbox_probe: platform not supported
[ 0.204737] tps65217-bl tps65217-bl: no platform data provided
[ 0.304784] bone-capemgr bone_capemgr.8: slot #1: No cape found
[ 0.341892] bone-capemgr bone_capemgr.8: slot #2: No cape found
[ 0.379004] bone-capemgr bone_capemgr.8: slot #3: No cape found
[ 0.404710] bone-capemgr bone_capemgr.8: slot #5: BB-BONELT-HDMI conflict P8.45 (#0:BB-BONE-LCD7-01)
[ 0.414305] bone-capemgr bone_capemgr.8: slot #5: Failed verification
[ 0.421078] bone-capemgr bone_capemgr.8: loader: failed to load slot-5 BB-BONELT-HDMI:00A0 (prio 1)
[ 0.433560] bone-capemgr bone_capemgr.8: slot #6: BB-BONELT-HDMIN conflict P8.45 (#0:BB-BONE-LCD7-01)
[ 0.443293] bone-capemgr bone_capemgr.8: slot #6: Failed verification
[ 0.450073] bone-capemgr bone_capemgr.8: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 0.471908] omap_hsmmc mmc.4: of_parse_phandle_with_args of ‘reset’ failed
[ 0.535689] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.7
[ 0.547422] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.7) status -22
[ 0.554759] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
[ 0.714922] tilcdc 4830e000.fb: timeout waiting for framedone
[ 10.276986] mmcblk0: error -84 transferring data, sector 414513, nr 96, cmd response 0x900, card status 0xb00
[ 10.803959] mmcblk0: error -84 transferring data, sector 1787081, nr 88, cmd response 0x900, card status 0xb00
[ 13.438402] mmcblk0: error -84 transferring data, sector 1717969, nr 112, cmd response 0x900, card status 0xd00
[ 13.449021] end_request: I/O error, dev mmcblk0, sector 1717969
[ 13.455219] end_request: I/O error, dev mmcblk0, sector 1717977
[ 13.461402] end_request: I/O error, dev mmcblk0, sector 1717985
[ 13.467589] end_request: I/O error, dev mmcblk0, sector 1717993
[ 13.473786] end_request: I/O error, dev mmcblk0, sector 1718001
[ 13.479974] end_request: I/O error, dev mmcblk0, sector 1718009
[ 13.486160] end_request: I/O error, dev mmcblk0, sector 1718017
[ 13.492342] end_request: I/O error, dev mmcblk0, sector 1718025
[ 13.498523] end_request: I/O error, dev mmcblk0, sector 1718033
[ 13.504705] end_request: I/O error, dev mmcblk0, sector 1718041
[ 13.511263] Aborting journal on device mmcblk0p2-8.
[ 13.532973] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4688: Journal has aborted
[ 13.542585] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4688: Journal has aborted
[ 13.552110] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4688: Journal has aborted
[ 13.561890] mmcblk0: error -84 transferring data, sector 1702505, nr 128, cmd response 0x900, card status 0xb00
[ 13.574712] journal commit I/O error
[ 13.750598] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 13.759985] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
[ 13.815771] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 13.834230] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 13.857642] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 13.873239] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 13.897675] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 13.925212] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 13.956657] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 13.981615] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 14.007385] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 14.028575] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 14.038172] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 14.047677] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 14.058562] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
systemd-fsck[84]: Angstrom: clean, 50595/112672 files, 286738/449820 blocks
[ 16.379907] mmcblk0: error -84 transferring data, sector 1404313, nr 112, cmd response 0x900, card status 0xb00
[ 18.885538] mmcblk0: error -84 transferring data, sector 1689865, nr 128, cmd response 0x900, card status 0xb00
[ 19.116511] libphy: PHY 4a101000.mdio:00 not found
[ 19.121568] net eth0: phy 4a101000.mdio:00 not found on slave 0
[ 19.127769] libphy: PHY 4a101000.mdio:01 not found
[ 19.132783] net eth0: phy 4a101000.mdio:01 not found on slave 1
.—O—.
.-. o o
-----.-----.-----.| | .----…-----.-----.
__ | —'| ‘–.| .-’| | |
— || --‘| | | ’ | | | |
‘—’—’–‘–’–. |-----‘’----‘’–’ ‘-----’-‘-’-’
-’ |
‘—’
The Angstrom Distribution beaglebone ttyO0
Angstrom v2012.12 - Kernel 3.8.13
beaglebone login: