From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: PB1176 broken in -rc1
Date: Wed, 10 Aug 2011 16:24:00 +0100 [thread overview]
Message-ID: <20110810152400.GO10121@e102144-lin.cambridge.arm.com> (raw)
Hi Linus,
My PB1176 platform appears to lock up as soon as it hits userspace when
running a 3.1-rc1 kernel. If I revert the commit:
f022e4e4 ("ARM: 6986/1: mach-realview: add TCM support for PB1176")
Then things start working again.
My dmesg contains:
[ 0.000000] CPU: found DTCM0 4k @ 00000000, not enabled
[ 0.000000] CPU: moved DTCM0 4k to fffe8000, enabled
[ 0.000000] CPU: found DTCM1 4k @ 00000000, not enabled
[ 0.000000] CPU: moved DTCM1 4k to fffe9000, enabled
[ 0.000000] CPU: found ITCM0 4k @ 00000000, not enabled
[ 0.000000] CPU: moved ITCM0 4k to fffe0000, enabled
[ 0.000000] CPU: found ITCM1 4k @ 00000000, not enabled
[ 0.000000] CPU: moved ITCM1 4k to fffe1000, enabled
[ 0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
[ 0.000000] Kernel command line: root=/dev/nfs ip=dhcp console=ttyAMA0 nfsroot=10.1.69.60:/export/debian,tcp rw
[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Memory: 128MB = 128MB total
[ 0.000000] Memory: 123692k/123692k available, 7380k reserved, 0K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] DTCM : 0xfffe8000 - 0xfffea000 ( 8 kB)
[ 0.000000] ITCM : 0xfffe0000 - 0xfffe2000 ( 8 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
[ 0.000000] vmalloc : 0xc8800000 - 0xf8000000 ( 760 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc05670d4 (5501 kB)
[ 0.000000] .init : 0xc0568000 - 0xc059e000 ( 216 kB)
[ 0.000000] .data : 0xc059e000 - 0xc05c8ac8 ( 171 kB)
[ 0.000000] .bss : 0xc05c9024 - 0xc0610578 ( 286 kB)
But then later hangs at:
[ 6.581778] VFS: Mounted root (nfs filesystem) on device 0:12.
Any thoughts on how to debug this? The NULL addresses in the dmesg look
strange to me, but I'm not familiar with the TCMs.
Cheers,
Will
next reply other threads:[~2011-08-10 15:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 15:24 Will Deacon [this message]
2011-08-10 15:39 ` PB1176 broken in -rc1 Jamie Iles
2011-08-10 15:53 ` Will Deacon
2011-08-11 13:02 ` Linus Walleij
2011-08-11 14:05 ` Linus Walleij
2011-08-11 14:24 ` Will Deacon
2011-08-16 9:21 ` Linus Walleij
2011-08-16 9:26 ` Will Deacon
2011-08-16 9:35 ` Linus Walleij
2011-08-16 9:59 ` Will Deacon
2011-08-16 10:09 ` Russell King - ARM Linux
2011-08-16 10:17 ` Will Deacon
2011-08-16 11:34 ` Russell King - ARM Linux
2011-08-16 21:38 ` Will Deacon
2011-08-16 12:44 ` Linus Walleij
2011-08-16 12:52 ` Russell King - ARM Linux
2011-08-16 9:28 ` Jamie Iles
2011-08-16 9:50 ` Jamie Iles
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=20110810152400.GO10121@e102144-lin.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.