From: Wolfgang Denk <wd@denx.de>
To: "Srivatsan" <srivatsan@deccanetworld.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux Kernel boot problem
Date: Tue, 28 Dec 2004 18:42:17 +0100 [thread overview]
Message-ID: <20041228174222.79FC7C14EC@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 28 Dec 2004 22:12:28 +0530." <000001c4ecfc$38442400$1269cb0a@bgcw301>
In message <000001c4ecfc$38442400$1269cb0a@bgcw301> you wrote:
>
> We were able to see the log buffer. It gave the following data:
Good.
> It is having the data what should be dumped out of Serial port. Any
> pointers which can lead us to the problem?
Well, what are the last readable messages you can find in the buffer?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
If I had to live my life again, I'd make the same mistakes, only
sooner. -- Tallulah Bankhead
next prev parent reply other threads:[~2004-12-28 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 5:52 Linux Kernel boot problem Srivatsan
2004-12-28 15:33 ` Wolfgang Denk
2004-12-28 16:42 ` Srivatsan
2004-12-28 17:42 ` Wolfgang Denk [this message]
2004-12-29 4:56 ` Srivatsan
2005-01-04 13:32 ` Srivatsan
2005-01-04 14:06 ` Jerry Van Baren
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=20041228174222.79FC7C14EC@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=srivatsan@deccanetworld.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