lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Mon, 13 Sep 2010 16:31:04 +0200
From:	Robin Theunis <robint91@...il.com>
To:	linux-kernel@...r.kernel.org, linux-embedded@...r.kernel.org
Subject: Fwd: ARM target not boot after remap memory

hi Johannes

I have compiled  the kernel with early printk on and debug_LL, It
still doesn't nothing after that line.

Robin

2010/9/13 Johannes Stezenbach <js@...21.net>:
> On Mon, Sep 13, 2010 at 01:25:26PM +0200, Robin Theunis wrote:
>>
>> Uncompressing Linux... done, booting the kernel.
>> ---
>>
>> Here is stalls. With my jtag probe I can locate the problem.
>>
>> ---
>> > halt
>> target state: halted
>> target halted in ARM state due to debug-request, current mode: Supervisor
>> cpsr: 0x600000d3 pc: 0xc000af3c
>> MMU: enabled, D-Cache: enabled, I-Cache: enabled
>> >   arm disassemble 0xc000af3c
>> 0xc000af3c    0xeafffffe      B 0xc000af3c
>> ---
>>
>> This just loops at that address. Why does it that?
>
> Maybe it panicked but you can't see the message since
> you have not enabled EARLY_PRINTK.
>
> Since you have JTAG, you could also dump the printk
> buffer __log_buf to see the message.
>
>
> HTH
> Johannes
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ