From: Sylvain Munaut <tnt@246tNt.com>
To: John F Davis <johndavi@us.ibm.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: linux hangs after uncompress kernel image
Date: Thu, 01 Sep 2005 16:30:09 +0200 [thread overview]
Message-ID: <43171071.40400@246tNt.com> (raw)
In-Reply-To: <OF4A6E57B7.047A8CB6-ON8725706F.00264CE2-C125706F.00264A01@us.ibm.com>
Or take the address of the __log_buf symbol then after the crash,
reboot and dump the buffer there, so you can see erly printk (before
console is up).
Sylvain
John F Davis wrote:
>
> Hello Lily,
>
> Maybe you could try to put in some printk's and see which line of code
> generates an exception.
>
> JD
>
>
> *"lily" <lichanjuan04@st.lzu.edu.cn>*
> Sent by: linuxppc-embedded-bounces@ozlabs.org
>
> 09/01/2005 05:55 AM
>
>
> To
> <linuxppc-embedded@ozlabs.org>
> cc
>
> Subject
> linux hangs after uncompress kernel image
>
>
>
>
>
>
>
>
> i work on octobusHPPC405EP board . when I try to bring up the kernel i
> meet the problem that linux hangs after uncompressing image:
>
> U-Boot 1.1.2 (Jun 3 2005 - 12:05:48)
>
> CPU: IBM PowerPC 405EP Rev. B at 133.333 MHz (PLB=133, OPB=66, EBC=33 MHz)
> IIC Boot EEPROM disabled
> PCI async ext clock used, internal PCI arbiter enabled
> 16 kB I-Cache 16 kB D-Cache
> OCTOBUS Board: ### No HW ID - assuming OCTOBUS HPPC405
> I2C: ready
> DRAM: 32 MB
> FLASH: 4 MB
> =>iminfo 1000000
> ## Checking Image at 01000000 ...
> Image Name: Linux-2.4.21-pre5
> Created: 2005-08-03 17:45:20 UTC
> Image Type: PowerPC Linux Kernel Image (gzip compressed)
> Data Size: 548345 Bytes = 535.5 kB
> Load Address: 00000000
> Entry Point: 00000000
> Verifying Checksum ... OK
> => bootm 1000000
> ## Booting image at 01000000 ...
> Image Name: Linux-2.4.21-pre5
> Created: 2005-08-03 17:45:20 UTC
> Image Type: PowerPC Linux Kernel Image (gzip compressed)
> Data Size: 548345 Bytes = 535.5 kB
> Load Address: 00000000
> Entry Point: 00000000
> Verifying Checksum ... OK
> Uncompressing Kernel Image ... OK
>
> <hang>
> what's the problem?? _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
prev parent reply other threads:[~2005-09-01 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 3:55 linux hangs after uncompress kernel image lily
2005-09-01 3:55 ` lily
2005-09-01 6:58 ` John F Davis
2005-09-01 14:30 ` Sylvain Munaut [this message]
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=43171071.40400@246tNt.com \
--to=tnt@246tnt.com \
--cc=johndavi@us.ibm.com \
--cc=linuxppc-embedded@ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.