Scott Wood schrieb:
Andre Schwarz wrote:
Scott Wood schrieb:
Andre Schwarz wrote:
-> find_legacy_serial_port()
stdout is /[EMAIL PROTECTED]/[EMAIL PROTECTED]
It looks like you have some memory corruption between here...
clocksource: timebase mult[3c1] shift[22] registered
!!!
Andre Schwarz wrote:
Scott Wood schrieb:
Andre Schwarz wrote:
-> find_legacy_serial_port()
stdout is /[EMAIL PROTECTED]/[EMAIL PROTECTED]
It looks like you have some memory corruption between here...
clocksource: timebase mult[3c1] shift[22] registered
Scott Wood schrieb:
Andre Schwarz wrote:
-> find_legacy_serial_port()
stdout is /[EMAIL PROTECTED]/[EMAIL PROTECTED]
It looks like you have some memory corruption between here...
clocksource: timebase mult[3c1] shift[22] registered
!!
Andre Schwarz wrote:
-> find_legacy_serial_port()
stdout is /[EMAIL PROTECTED]/[EMAIL PROTECTED]
It looks like you have some memory corruption between here...
clocksource: timebase mult[3c1] shift[22] registered
!!
-> check_legacy_ser
Scott Wood schrieb:
On Tue, Apr 08, 2008 at 03:50:26PM +0200, Andre Schwarz wrote:
after building a debug kernel and attaching the bdi2000 it looks like
the crash occurs during "console_init()" ...
Does your device tree have a /chosen node after u-boot is done with it?
find_legacy_se
Scott Wood wrote:
On Tue, Apr 08, 2008 at 03:50:26PM +0200, Andre Schwarz wrote:
after building a debug kernel and attaching the bdi2000 it looks like
the crash occurs during "console_init()" ...
Does your device tree have a /chosen node after u-boot is done with it?
find_legacy_seri
On Tue, Apr 08, 2008 at 03:50:26PM +0200, Andre Schwarz wrote:
> after building a debug kernel and attaching the bdi2000 it looks like
> the crash occurs during "console_init()" ...
Does your device tree have a /chosen node after u-boot is done with it?
find_legacy_serial_ports() can crash othe
On Tue, Apr 08, 2008 at 10:51:18AM +0200, Andre Schwarz wrote:
> Call Trace:
> [c01f9ef0] [c001c190] (unreliable)
> [c01f9f10] [c0140c84]
> [c01f9f20] [c0140ccc]
> [c01f9f40] [c014145c]
> [c01f9f60] [c0014014]
> [c01f9fa0] [c01d1a40]
> [c01f9fb0] [c01ce64c]
> [c01f9fc0] [c01c55ac]
> [c01f9ff0] [00
Scott Wood schrieb:
On Sat, Apr 05, 2008 at 10:19:49AM +0200, André Schwarz wrote:
Kernel starts and crashes with "unable to handle kernel paging request @
".
After turning debug on in some files I can see that the initrd memory
gets reserved and the dtb is parsed correctly.
PCI
sorry - forgot Kim + List
Original-Nachricht
Betreff:Re: MPC8343 - "unable to handle paging request @ 0"
Datum: Tue, 08 Apr 2008 13:29:20 +0200
Von:Andre Schwarz <[EMAIL PROTECTED]>
An: Scott Wood <[EMAIL PROTECTED]>
Referenzen: <[E
Scott Wood schrieb:
On Sat, Apr 05, 2008 at 10:19:49AM +0200, André Schwarz wrote:
Kernel starts and crashes with "unable to handle kernel paging request @
".
After turning debug on in some files I can see that the initrd memory
gets reserved and the dtb is parsed correctly.
PCI
On Sat, Apr 05, 2008 at 10:19:49AM +0200, André Schwarz wrote:
> Kernel starts and crashes with "unable to handle kernel paging request @
> ".
>
> After turning debug on in some files I can see that the initrd memory
> gets reserved and the dtb is parsed correctly.
> PCI memory/io space
Kim,
sorry for the general questions - but I'm running out of ideas.
We never ever had that many problems getting a PowerPC running during
the past 10 years.
I've cross-checked the hardware and design with Freescale FAE.
Everything looks fine and is approved.
We're running latest u-boot v1.
13 matches
Mail list logo