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]
Message-ID: <569685F045B85741820D0265E0D2999D019CFE84@tddhh01.hh.thales-naval.de>
Date:	Mon, 3 May 2010 16:51:46 +0200 
From:	"Dunda, Matthias" <Matthias.Dunda@...thalesgroup.com>
To:	"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>
Subject: PPC: Problems at early stage after starting from U-Boot

Hi everybody,

I am trying to get the 2.6.29.6-rt23 kernel running on our self-designed
board based on a Freescale MPC8568 CPU. I launch the kernel out of U-Boot.

I have serial console output from U-Boot until I reach the point where the
kernel is called.

As I don't see output, I was reading out the memory at the log_buf location
with our Abatron BDI3000 debugger (dump 0x003e1c9c 0x2000)

As I am new to kernel debugging at that early stage, I would really
appreciate if someone could help explaining the log - so far for me it just
says that the device tree is faulty. ;-)

I've attached the log and DTS.

I have no idea where to look next... :-(

Cheers
Matthias


Download attachment "kernel-log.001" of type "application/octet-stream" (3377 bytes)

Download attachment "thales_dge.dts" of type "application/octet-stream" (12736 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ