From: Andrew Liu <andrew.liu200917@gmail.com>
To: Anton Blanchard <anton@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: PowerPC 85xx board are caused die by Commit: 864b9e6fd76489aab422bac62162f57c52e06ed8(powerpc: Use lwarx/ldarx hint in bit locks)
Date: Thu, 11 Mar 2010 11:20:52 +0800 [thread overview]
Message-ID: <54d399751003101920j598de9fdkd7c8617c8e4fa191@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
Hi Guys:
I have done several experiments on fsl_8548cds and fsl_p2020rdb, pinpointed
the commit: 864b9e6fd76489aab422bac62162f57c52e06ed8(powerpc: Use
lwarx/ldarx hint in bit locks) cause the bootup stalledd.
"
Filename 'fsl_8548cds/uImage'.
Load address: 0x1000000
Loading: #################################################################
#######################################
done
Bytes transferred = 1526546 (174b12 hex)
Speed: 100, full duplex
Using eTSEC0 device
Filename 'sliu/fsl_8548cds/mpc8548cds.dtb'.
Load address: 0xc00000
Loading: #
done
Bytes transferred = 9993 (2709 hex)
## Booting image at 01000000 ...
Image Name: Linux-2.6.34-rc1-00005-g522dba7
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1526482 Bytes = 1.5 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Booting using the fdt at 0xc00000
Loading Device Tree to 007fb000, end 007fd708 ... OK
"
I guess all 85xx or booke board has this issue.
Thanks
Andrew
[-- Attachment #2: Type: text/html, Size: 1196 bytes --]
next reply other threads:[~2010-03-11 3:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 3:20 Andrew Liu [this message]
2010-03-11 5:20 ` PowerPC 85xx board are caused die by Commit: 864b9e6fd76489aab422bac62162f57c52e06ed8(powerpc: Use lwarx/ldarx hint in bit locks) Kumar Gala
2010-03-11 5:39 ` Kumar Gala
2010-03-11 8:57 ` Andrew Liu
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=54d399751003101920j598de9fdkd7c8617c8e4fa191@mail.gmail.com \
--to=andrew.liu200917@gmail.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@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 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).