From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Miroslaw Dach" <miroslaw.dach@psi.ch>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux doesn not boot from u-boot on ML403
Date: Mon, 27 Aug 2007 08:53:28 -0600 [thread overview]
Message-ID: <fa686aa40708270753u1411796fv698d3b39ee908599@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0708271634110.30948-100000@slslc02.psi.ch>
On 8/27/07, Miroslaw Dach <miroslaw.dach@psi.ch> wrote:
> Hi Grant,
>
> Thank you for your response.
>
> My u-boot bootargs is set to:
> console=ttyUL0,9600 root=/dev/nfs rw nfsroot=129.117.144.113:/opt/eldk41/ppc_4xx,tcp ip=::::virtex4-mirek:eth0:dhcp panic=1
Drop the ',9600'. It's irrelevant for uartlite.
>
> where I can find __log_buf for kernel messages?
Search for __log_buf in System.map (in the kernel source tree). Use a
debugger to look at the memory.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-08-27 14:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 13:35 Linux doesn not boot from u-boot on ML403 Mirek23
2007-08-27 14:24 ` Grant Likely
2007-08-27 14:36 ` Miroslaw Dach
2007-08-27 14:53 ` Grant Likely [this message]
2007-08-28 11:18 ` Miroslaw Dach
2007-08-28 13:02 ` Grant Likely
2007-08-28 13:37 ` Miroslaw Dach
2007-08-28 13:50 ` Grant Likely
2007-08-28 15:00 ` Miroslaw Dach
2007-08-28 15:10 ` Grant Likely
2007-08-28 15:22 ` Miroslaw Dach
2007-08-28 15:28 ` Grant Likely
2007-08-29 8:41 ` Miroslaw Dach
2007-08-29 15:17 ` Grant Likely
2007-08-29 15:31 ` Miroslaw Dach
2007-08-30 7:50 ` Miroslaw Dach
2007-08-30 13:21 ` Grant Likely
2007-08-29 15:32 ` Miroslaw Dach
-- strict thread matches above, loose matches on Subject: below --
2007-09-23 13:27 Miroslaw Dach
2007-09-23 15:32 ` Grant Likely
2007-09-23 19:44 ` Josh Boyer
2007-09-25 8:25 ` Mirek23
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=fa686aa40708270753u1411796fv698d3b39ee908599@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-embedded@ozlabs.org \
--cc=miroslaw.dach@psi.ch \
/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).