From: "Gary Smith" <gary.smith@3phoenix.com>
To: <linux-mips@linux-mips.org>
Subject: 'mem= ' Kernel Boot Parameter on BCM1250/1480 Platform
Date: Thu, 29 Mar 2007 14:56:49 -0400 [thread overview]
Message-ID: <001301c77234$04d014c0$8eacaac0@3PiGAS> (raw)
[-- Attachment #1: Type: text/plain, Size: 4457 bytes --]
Dear Linux-Mips Developers:
I'd like to ask a question about use of the 'mem=' kernel parameter. When
booting without this parameter, the kernel automatically detects the amount
of memory as 989020 kB. If a kernel parameter is added to specify
'mem=989020k' a TLB Miss error is encountered. Do you all have guidance
about how the memory parameter can be specified without causing the error?
Since the mem= parameter was set to an identical value as the memory
reported by meminfo in the /proc filesystem, use of this kernel parameter
should be OK. This behavior has been observed on both the BCM1250/1480
platforms when running Debian linux. The 2.6.17-2 kernel is used with the
system.
Thanks,
Gary
--
Gary A. Smith, ABD PhD
Engineer, 3Phoenix, Inc.
3331 Heritage Trade Drive
Suite 101
Wake Forest, NC 27587
919.562.5333 x107
<http://www.3Phoenix.com> http://www.3Phoenix.com
Gary.Smith@3Phoenix.com
debian:/proc# more meminfo
MemTotal: 989020 kB
MemFree: 957876 kB
Buffers: 1660 kB
Cached: 12076 kB
SwapCached: 0 kB
Active: 10308 kB
Inactive: 5224 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 989020 kB
LowFree: 957876 kB
SwapTotal: 72252 kB
SwapFree: 72252 kB
Dirty: 524 kB
Writeback: 0 kB
Mapped: 4496 kB
Slab: 7236 kB
CommitLimit: 566760 kB
Committed_AS: 4360 kB
PageTables: 188 kB
VmallocTotal: 1073741824 kB
VmallocUsed: 916 kB
VmallocChunk: 1073739640 kB
CFE version 1.3.3 for SWARM (64bit,MP,BE,MIPS) Build Date: Tue Dec 19
06:41:38 EST 2006 (root@static-host) Copyright (C)
2000,2001,2002,2003,2004,2005 Broadcom Corporation.
Initializing Arena.
Initializing Devices.
SWARM board revision 3
sbeth: found phy 1, vendor 000818 part 0C
sbeth: found phy 1, vendor 000818 part 0C Config switch: 0
CPU: BCM1250 B2
L2 Cache Status: OK
Wafer ID: 0x7F21A009 [Lot 8136, Wafer 13]
Manuf Test: Bin A [2CPU_FI_FD_F2 (OK)]
SysCfg: 0000000008C20800 [PLL_DIV: 16, IOB0_DIV: CPUCLK/4, IOB1_DIV:
CPUCLK/3]
CPU type 0x1040102: 800MHz
Total memory: 0x40000000 bytes (1024MB)
Total memory used by CFE: 0x8FEB3000 - 0x8FFFF520 (1361184)
Initialized Data: 0x8FEF5408 - 0x8FEFD100 (31992)
BSS Area: 0x8FEFD100 - 0x8FEFD520 (1056)
Local Heap: 0x8FEFD520 - 0x8FFFD520 (1048576)
Stack Area: 0x8FFFD520 - 0x8FFFF520 (8192)
Text (code) segment: 0x8FEB3000 - 0x8FEF4C75 (269429)
Boot area (physical): 0x0FE72000 - 0x0FEB2000
Relocation Factor: I:F02B3000 - D:F02B3000
*** Autoboot: Trying device 'ide0.0' file (ide0.0,raw)
Loader:raw Filesys:raw Dev:ide0.0 File: Options:(null)
Loading: ........... 130560 bytes read
Entry at 0x20000000
Starting program at 0x20000000
SiByte Loader, version 2.4.2
Built on Oct 4 2005
Getting configuration file ext2:ide0.0:*:sibyl.conf...
Config file retrieved.
Loading kernel (ELF64):
4256456@0x80100000
done
Set up command line arguments to: root=/dev/hda3 console=duart0 mem=989020k
Setting up initial prom_init arguments **Exception 32: EPC=0000000020000BC8,
Cause=00009008 (TLBMissRd) (CPU0)
RA=0000000020000BB4, VAddr=0000000000000000, SR=00000082
0 ($00) = 0000000000000000 AT ($01) = 0000000000000001
v0 ($02) = FFFFFFFF8FEFCC70 v1 ($03) = 0000000000000000
a0 ($04) = 0000000000000010 a1 ($05) = 0000000000000000
a2 ($06) = 000000008FEB3CDC a3 ($07) = 0000000000000000
t0 ($08) = 0000000000000080 t1 ($09) = 0000000000000001
t2 ($10) = 0000000000000001 t3 ($11) = 0000000000000000
t4 ($12) = 0000000000000000 t5 ($13) = 0000000000000000
t6 ($14) = 0000000000000015 t7 ($15) = 0000000045000000
s0 ($16) = FFFFFFFF8FEB3AF4 s1 ($17) = FFFFFFFF8FEFD4E0
s2 ($18) = FFFFFFFF8FFFF250 s3 ($19) = FFFFFFFF8FEFD0B8
s4 ($20) = 0000000000000000 s5 ($21) = 0000000000000000
s6 ($22) = 0000000000000000 s7 ($23) = FFFFFFFF8FEB3000
t8 ($24) = 0000000000000000 t9 ($25) = 0000000000000000
k0 ($26) = 0000000000000001 k1 ($27) = 000000008FEB3CDC
gp ($28) = 00000000200278F0 sp ($29) = FFFFFFFF8FFFECE0
fp ($30) = FFFFFFFF8FFFECE0 ra ($31) = 0000000020000BB4
[-- Attachment #2: Type: text/html, Size: 23160 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Gary Smith" <gary.smith@3phoenix.com>
To: linux-mips@linux-mips.org
Subject: 'mem= ' Kernel Boot Parameter on BCM1250/1480 Platform
Date: Thu, 29 Mar 2007 14:56:49 -0400 [thread overview]
Message-ID: <001301c77234$04d014c0$8eacaac0@3PiGAS> (raw)
Message-ID: <20070329185649.Ut7lF1jV9fStmeLlV4Bi8-uiveKsMmz70FCMwVxaH8Q@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 4457 bytes --]
Dear Linux-Mips Developers:
I'd like to ask a question about use of the 'mem=' kernel parameter. When
booting without this parameter, the kernel automatically detects the amount
of memory as 989020 kB. If a kernel parameter is added to specify
'mem=989020k' a TLB Miss error is encountered. Do you all have guidance
about how the memory parameter can be specified without causing the error?
Since the mem= parameter was set to an identical value as the memory
reported by meminfo in the /proc filesystem, use of this kernel parameter
should be OK. This behavior has been observed on both the BCM1250/1480
platforms when running Debian linux. The 2.6.17-2 kernel is used with the
system.
Thanks,
Gary
--
Gary A. Smith, ABD PhD
Engineer, 3Phoenix, Inc.
3331 Heritage Trade Drive
Suite 101
Wake Forest, NC 27587
919.562.5333 x107
<http://www.3Phoenix.com> http://www.3Phoenix.com
Gary.Smith@3Phoenix.com
debian:/proc# more meminfo
MemTotal: 989020 kB
MemFree: 957876 kB
Buffers: 1660 kB
Cached: 12076 kB
SwapCached: 0 kB
Active: 10308 kB
Inactive: 5224 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 989020 kB
LowFree: 957876 kB
SwapTotal: 72252 kB
SwapFree: 72252 kB
Dirty: 524 kB
Writeback: 0 kB
Mapped: 4496 kB
Slab: 7236 kB
CommitLimit: 566760 kB
Committed_AS: 4360 kB
PageTables: 188 kB
VmallocTotal: 1073741824 kB
VmallocUsed: 916 kB
VmallocChunk: 1073739640 kB
CFE version 1.3.3 for SWARM (64bit,MP,BE,MIPS) Build Date: Tue Dec 19
06:41:38 EST 2006 (root@static-host) Copyright (C)
2000,2001,2002,2003,2004,2005 Broadcom Corporation.
Initializing Arena.
Initializing Devices.
SWARM board revision 3
sbeth: found phy 1, vendor 000818 part 0C
sbeth: found phy 1, vendor 000818 part 0C Config switch: 0
CPU: BCM1250 B2
L2 Cache Status: OK
Wafer ID: 0x7F21A009 [Lot 8136, Wafer 13]
Manuf Test: Bin A [2CPU_FI_FD_F2 (OK)]
SysCfg: 0000000008C20800 [PLL_DIV: 16, IOB0_DIV: CPUCLK/4, IOB1_DIV:
CPUCLK/3]
CPU type 0x1040102: 800MHz
Total memory: 0x40000000 bytes (1024MB)
Total memory used by CFE: 0x8FEB3000 - 0x8FFFF520 (1361184)
Initialized Data: 0x8FEF5408 - 0x8FEFD100 (31992)
BSS Area: 0x8FEFD100 - 0x8FEFD520 (1056)
Local Heap: 0x8FEFD520 - 0x8FFFD520 (1048576)
Stack Area: 0x8FFFD520 - 0x8FFFF520 (8192)
Text (code) segment: 0x8FEB3000 - 0x8FEF4C75 (269429)
Boot area (physical): 0x0FE72000 - 0x0FEB2000
Relocation Factor: I:F02B3000 - D:F02B3000
*** Autoboot: Trying device 'ide0.0' file (ide0.0,raw)
Loader:raw Filesys:raw Dev:ide0.0 File: Options:(null)
Loading: ........... 130560 bytes read
Entry at 0x20000000
Starting program at 0x20000000
SiByte Loader, version 2.4.2
Built on Oct 4 2005
Getting configuration file ext2:ide0.0:*:sibyl.conf...
Config file retrieved.
Loading kernel (ELF64):
4256456@0x80100000
done
Set up command line arguments to: root=/dev/hda3 console=duart0 mem=989020k
Setting up initial prom_init arguments **Exception 32: EPC=0000000020000BC8,
Cause=00009008 (TLBMissRd) (CPU0)
RA=0000000020000BB4, VAddr=0000000000000000, SR=00000082
0 ($00) = 0000000000000000 AT ($01) = 0000000000000001
v0 ($02) = FFFFFFFF8FEFCC70 v1 ($03) = 0000000000000000
a0 ($04) = 0000000000000010 a1 ($05) = 0000000000000000
a2 ($06) = 000000008FEB3CDC a3 ($07) = 0000000000000000
t0 ($08) = 0000000000000080 t1 ($09) = 0000000000000001
t2 ($10) = 0000000000000001 t3 ($11) = 0000000000000000
t4 ($12) = 0000000000000000 t5 ($13) = 0000000000000000
t6 ($14) = 0000000000000015 t7 ($15) = 0000000045000000
s0 ($16) = FFFFFFFF8FEB3AF4 s1 ($17) = FFFFFFFF8FEFD4E0
s2 ($18) = FFFFFFFF8FFFF250 s3 ($19) = FFFFFFFF8FEFD0B8
s4 ($20) = 0000000000000000 s5 ($21) = 0000000000000000
s6 ($22) = 0000000000000000 s7 ($23) = FFFFFFFF8FEB3000
t8 ($24) = 0000000000000000 t9 ($25) = 0000000000000000
k0 ($26) = 0000000000000001 k1 ($27) = 000000008FEB3CDC
gp ($28) = 00000000200278F0 sp ($29) = FFFFFFFF8FFFECE0
fp ($30) = FFFFFFFF8FFFECE0 ra ($31) = 0000000020000BB4
[-- Attachment #2: Type: text/html, Size: 23160 bytes --]
next reply other threads:[~2007-03-29 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 18:56 Gary Smith [this message]
2007-03-29 18:56 ` 'mem= ' Kernel Boot Parameter on BCM1250/1480 Platform Gary Smith
2007-03-29 19:53 ` Maciej W. Rozycki
2007-03-29 21:10 ` Ralf Baechle
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='001301c77234$04d014c0$8eacaac0@3PiGAS' \
--to=gary.smith@3phoenix.com \
--cc=linux-mips@linux-mips.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