If someone can capture a full backtrace then I will look. I will also aim to reproduce
myself a few more times. I am told there is a JTAG option but have not looked further
since the weekend yet.
--
Chief ARM Architect | Sent from my iPad
On Sep 14, 2013, at 11:04, Steven Falco <stevenfalco(a)gmail.com> wrote:
On 09/14/2013 03:48 AM, Matthias Runge wrote:
> On 09/13/2013 12:17 PM, Jon Masters wrote:
>> When it does crash (which is every so many boots), I briefly (on
>> occasion) see output about illegal/undefined instructions. There's
>> perhaps a multitplatform artifact in here. Some kind of errata or
>> other workaround might be enabled that triggers on some boots and
>> causes this.
> The sadly, there is no (real) output from the kernel, but
> "Wrong Image Format for"
>
> Matthias
I am seeing similar behavior. Sometimes I get a hang:
Enter choice: 1
1: Fedora (3.11.0-300.fc20.armv7hl) 20 (Null)
Retrieving file: /initramfs-3.11.0-300.fc20.armv7hl.img
10760171 bytes read in 600 ms (17.1 MiB/s)
Retrieving file: /vmlinuz-3.11.0-300.fc20.armv7hl
4748528 bytes read in 304 ms (14.9 MiB/s)
append: console=ttymxc0,115200 root=UUID=e72ec2c4-bd9e-4100-85be-df34e7f01e53 ro rhgb
quiet LANG=en_US.UTF-8
Retrieving file: /dtb/imx6q-wandboard.dtb
23567 bytes read in 160 ms (143.6 KiB/s)
(no more output after the above)
Another time I got:
Retrieving file: /dtb/imx6q-wandboard.dtb
23567 bytes read in 161 ms (142.6 KiB/s)
Wrong Image Format for undefined instruction
pc : [<8e1fec44>] lr : [<8ff93518>]
sp : 8f579708 ip : 00000000 fp : 00000000
r10: 8ffb9e18 r9 : 8f57978c r8 : 8f579f38
r7 : 00000003 r6 : 00000000 r5 : 0000070f r4 : 8ffb9e18
r3 : 00000000 r2 : 00000001 r1 : 00000020 r0 : 00000000
Flags: nZCv IRQs off FIQs off Mode SVC_32
Resetting CPU ...
I'll try another SD card, in case this one is defective.
BTW, I made a few edits to:
https://fedoraproject.org/wiki/User:Mrunge/Wandboard_quad
I added a wget of the u-boot package, and how to unpack the
rpm, and I updated the extlinux.conf script for the correct
root UUID for the Alpha-2 build.
One other thing - once I got the system installed and booted, I
could not log in. I tried numerous times, and even edited
/etc/shadow to paste in the crypted PW from my desktop machine.
Finally, I disabled selinux, booted into single-user mode, did
"init 3" and then I could log in. I later tried booting directly
into level 3, and I could log in. Has anyone seen anything similar?
Steve
_______________________________________________
arm mailing list
arm(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm