linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "André Schwarz" <Andre.Schwarz@matrix-vision.de>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: MPC8343 - "unable to handle paging request @ 0"
Date: Tue, 08 Apr 2008 21:59:21 +0200	[thread overview]
Message-ID: <47FBCE99.8050108@matrix-vision.de> (raw)
In-Reply-To: <20080408164853.GH2552@loki.buserror.net>

[-- Attachment #1: Type: text/plain, Size: 1858 bytes --]

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_serial_ports() can crash otherwise (we really should fix that).
>
>   
latest u-boot does add the chosen node.
As far as I know it's for initrd setup ... don't know if it's complete.
>> Since we're using a dtb I omit the "console=..." argument for the  
>> kernel. Is this correct ?
>>     
>
> It's OK if you have /chosen/linux,stdout-path.
>
>   
that sounds promising ! Haven't seen this and will have a closer look.
>> If "console=/dev/ttyS0,115200N8" argument is given the serial console  
>> stops working after console_init....
>>
>>
>> On other PowerPC system I could see something like this during boot :
>>
>> -> find_legacy_serial_port()
>> stdout is /soc8568@e0000000/serial@4600
>> legacy_serial_console = 1
>> default console speed = 115340
>> <- find_legacy_serial_port()
>>
>>
>> Should I see this message also ?
>>     
>
> Only if you enable debug messages in legacy_serial.c.
>
>   
ok.
>> Have I misconfigured anything ?
>>     
>
> One thing that sticks out from the above is that you ask for ttyS0, but the
> stdout you list from the other system corresponds to ttyS1.  Is this just a
> difference between the two systems?
>
>   
Yes - the log from the MPC8568 is a copy&paste from another posting. 
It's not my system.
I want ttyS0.
> -Scott
>   
I appreciate your help !

Thanks,
André


MATRIX VISION GmbH, Talstraße 16, DE-71570 Oppenweiler  - Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschäftsführer: Gerhard Thullner, Werner Armingeon, Uwe Furtner

[-- Attachment #2: Type: text/html, Size: 2914 bytes --]

  reply	other threads:[~2008-04-08 19:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-05  8:19 MPC8343 - "unable to handle paging request @ 0" André Schwarz
2008-04-07 16:10 ` Scott Wood
2008-04-08  8:51   ` Andre Schwarz
2008-04-08 16:43     ` Scott Wood
2008-04-08 13:50   ` Andre Schwarz
2008-04-08 16:48     ` Scott Wood
2008-04-08 19:59       ` André Schwarz [this message]
2008-04-09 12:54       ` Andre Schwarz
2008-04-09 18:57         ` Scott Wood
2008-04-09 19:09           ` Andre Schwarz
2008-04-09 19:15             ` Scott Wood
2008-04-10  9:00               ` Andre Schwarz
2009-12-04 22:55 ` MPC8343EA Linux DTS file agnel
2009-12-04 22:56 ` agnel
2009-12-04 23:39   ` Kim Phillips
     [not found]     ` <72d214170912041543g207837a5v67c9bb157e0a2c8b@mail.gmail.com>
2009-12-05  1:47       ` Kim Phillips

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47FBCE99.8050108@matrix-vision.de \
    --to=andre.schwarz@matrix-vision.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).