BB xM freezes after clean install

[ciofeca]

A few days ago I downloaded the latest install packages (ArchLinuxARM-armv7-latest.tar.gz and BeagleBoard-bootloader.tar.gz).

I installed on a microSD and booted it on a Beagleboard xM revB. Everything went fine. I was able to login as root, configure stuff (resolvconf.conf, systemd/network/eth0.conf, and so on).Then updated packages (pacman -Syu) and booted again and... it freezes after boot, at about 5 seconds, while the kernel is checking for USB stuff (note that no USB peripherals were fitted in). I forgot Arch and went for Angstrom.


One hour ago I download the latest install packages again (the ArchLinuxARM-armv7-latest.tar.gz grew from 190 to 195Mb), wiped out the microSD, installed it and booted the same xM. It freezes at the same time.

$this->bbcode_second_pass_code('', '[ 4.550781] ALSA device list:
[ 4.553955] No soundcards found.
[ 4.558715] Waiting for root device /dev/mmcblk0p2...
[ 4.853790] usb 3-2: new high-speed USB device number 2 using ehci-omap
[ 4.873809] mmc0: card never left busy state
[ 4.878265] mmc0: error -110 whilst initialising SD card
[ 4.989715] usb 3-2: New USB device found, idVendor=0424, idProduct=9514
[ 4.996765] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 5.005523] hub 3-2:1.0: USB hub found
[ 5.009796] hub 3-2:1.0: 5 ports detected
[ 5.299041] usb 3-2.1: new high-speed USB device number 3 using ehci-omap
[ 5.409698] usb 3-2.1: New USB device found, idVendor=0424, idProduct=ec00
[ 5.416931] usb 3-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 98.788177] random: nonblocking pool is initialized
')

I cannot figure out why it happens. Am I the only one unable to boot a clean install of ArchLinuxArm on a BBxM ?
Do ArchLinuxArm guys release kernels only after checking them on actual hardware?

[WarheadsSE]

Well, sadly, our BBxM bit the electronic dust a while back, in that a regulator blew out.

IIRC, we're no longer in possession of a working unit

EDIT:

[kmihelich]

I've replaced the burned out xM, and the latest tarball is confirmed working just fine.

The error messages clearly state it's having problems with the SD card. Try using a different one.

[ciofeca]

Tried two other different microSD cards with the same result (another Kingston and a Verbatim, both class 4): it always stops there.

Note that I format the root partition using mkfs.ext4 -c (full badblocks scan before formatting) and I also tried dd if=/dev/sdb of=/dev/null to be sure. Anyway, Arch kernel console messages do not show any memorycard read error, with the exception of the "busy state":
$this->bbcode_second_pass_code('', '[ 4.863800] mmc0: card never left busy state
[ 4.868255] mmc0: error -110 whilst initialising SD card')

Reformatting the same microSD with Angstrom, just works.

I bet there is a problem in the latest Linux 3.17.2-1-ARCH kernel but at this point I am unable to diagnose anything other.

[kmihelich]

The kernel works just fine.

[ciofeca]

New microSD, same problem.

Maybe this is related to recent kernel updates (namely "twl4030-power: Add a configuration to turn off oscillator during off-idle"):

http://permalink.gmane.org/gmane.linux. ... map/118064