From: Octavian Purdila <tavi@cs.pub.ro>
To: "linuxppc-embedded" <linuxppc-embedded@ozlabs.org>
Subject: linux kernel PPC 405GP stucked after running init
Date: Tue, 8 Feb 2005 16:56:24 +0200 [thread overview]
Message-ID: <200502081656.25023.tavi@cs.pub.ro> (raw)
Hi list,
I am playing with an embedded system based on an IBM PPC 405GP. So far I made
the kernel boot, but it gets stuck after running the the init process
(busybox). Any hints?
I notice that ShowRegs does not output anything, and I traced this behavior to
pt_regs passed as NULL in the serial irq routine. Is this normal?
Thank you,
tavi
SysRq : Show Regs
SysRq : Show State
sibling
task PC pid father child younger older
busybox R running 0 1 0 2 (NOTLB)
ksoftirqd/0 S 00000000 0 2 1 3 (L-TLB)
Call trace:
[c0005a70] __switch_to+0x48/0x70
[c00a4928] schedule+0x2e8/0x684
[c001a228] ksoftirqd+0xa4/0xc8
[c00281e8] kthread+0xb8/0xc0
[c000594c] kernel_thread+0x44/0x60
events/0 S 00000000 0 3 1 4 8 2 (L-TLB)
Call trace:
[c0005a70] __switch_to+0x48/0x70
[c00a4928] schedule+0x2e8/0x684
[c0023a40] worker_thread+0x1fc/0x220
[c00281e8] kthread+0xb8/0xc0
[c000594c] kernel_thread+0x44/0x60
khelper S 00000000 0 4 3 5 (L-TLB)
Call trace:
[c0005a70] __switch_to+0x48/0x70
[c00a4928] schedule+0x2e8/0x684
[c0023a40] worker_thread+0x1fc/0x220
[c00281e8] kthread+0xb8/0xc0
[c000594c] kernel_thread+0x44/0x60
kblockd/0 S 00000000 0 5 3 6 4 (L-TLB)
Call trace:
[c0005a70] __switch_to+0x48/0x70
[c00a4928] schedule+0x2e8/0x684
[c0023a40] worker_thread+0x1fc/0x220
[c00281e8] kthread+0xb8/0xc0
[c000594c] kernel_thread+0x44/0x60
pdflush S 00000000 0 6 3 7 5 (L-TLB)
Call trace:
[c0005a70] __switch_to+0x48/0x70
[c00a4928] schedule+0x2e8/0x684
[c0030f44] __pdflush+0xb0/0x1e4
[c0031098] pdflush+0x20/0x30
[c00281e8] kthread+0xb8/0xc0
[c000594c] kernel_thread+0x44/0x60
pdflush S 00000000 0 7 3 9 6 (L-TLB)
Call trace:
[c0005a70] __switch_to+0x48/0x70
[c00a4928] schedule+0x2e8/0x684
[c0030f44] __pdflush+0xb0/0x1e4
[c0031098] pdflush+0x20/0x30
[c00281e8] kthread+0xb8/0xc0
[c000594c] kernel_thread+0x44/0x60
aio/0 S 00000000 0 9 3 7 (L-TLB)
Call trace:
[c0005a70] __switch_to+0x48/0x70
[c00a4928] schedule+0x2e8/0x684
[c0023a40] worker_thread+0x1fc/0x220
[c00281e8] kthread+0xb8/0xc0
[c000594c] kernel_thread+0x44/0x60
kswapd0 S 00000000 0 8 1 10 3 (L-TLB)
Call trace:
[c0005a70] __switch_to+0x48/0x70
[c00a4928] schedule+0x2e8/0x684
[c00375cc] kswapd+0x84/0xa0
[c000594c] kernel_thread+0x44/0x60
mtdblockd S 00000000 0 10 1 8 (L-TLB)
Call trace:
[c0005a70] __switch_to+0x48/0x70
[c00a4928] schedule+0x2e8/0x684
[c009885c] mtd_blktrans_thread+0x18c/0x1c4
[c000594c] kernel_thread+0x44/0x60
SysRq : Show Memory
Mem-info:
DMA per-cpu:
cpu 0 hot: low 2, high 6, batch 1
cpu 0 cold: low 0, high 2, batch 1
Normal per-cpu: empty
HighMem per-cpu: empty
Free pages: 14240kB (0kB HighMem)
Active:1 inactive:173 dirty:0 writeback:0 unstable:0 free:3560 slab:57
mapped:14 pagetables:2
DMA free:14240kB min:512kB low:640kB high:768kB active:4kB inactive:692kB
present:16384kB pages_scanned:0 all_unreclaimable? no
protections[]: 0 0 0
Normal free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB
pages_scanned:0 all_unreclaimable? no
protections[]: 0 0 0
HighMem free:0kB min:128kB low:160kB high:192kB active:0kB inactive:0kB
present:0kB pages_scanned:0 all_unreclaimable? no
protections[]: 0 0 0
DMA: 6*4kB 3*8kB 1*16kB 1*32kB 1*64kB 0*128kB 1*256kB 1*512kB 1*1024kB
0*2048kB 3*4096kB = 14240kB
Normal: empty
HighMem: empty
Free swap: 0kB
4096 pages of RAM
0 pages of HIGHMEM
3576 free pages
265 reserved pages
14 pages shared
0 pages swap cached
reply other threads:[~2005-02-08 15:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200502081656.25023.tavi@cs.pub.ro \
--to=tavi@cs.pub.ro \
--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 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).