I have a box that we recently installed 16GB of RAM on. The box is i386
FreeBSD 6.2. It only recognizes 4gb.
I am currently recompiling the kernel to support options PAE (KERNCONF=PAE)
in order to see this. I understand this is still considered a Beta
implementation ,and this is a production box.
Does anyone have any alternative solutions that would provide a more
reliable environment other than PAE?
Dmesg Output is as follows :
Copyright (c) 1992-2007 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007
root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.13-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0xf64 Stepping = 4
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA
,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=0xe4bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,CNTX-ID,CX16,<b14>,<b15>>
AMD Features=0x20100000<NX,LM>
AMD Features2=0x1<LAHF>
Cores per package: 2
Logical CPUs per core: 2
real memory = 3489005568 (3327 MB)
avail memory = 3414196224 (3256 MB)
ACPI APIC Table: <PTLTD APIC >
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
cpu2 (AP): APIC ID: 2
cpu3 (AP): APIC ID: 3
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 24-47 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0: <PTLTD RSDT> on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
cpu1: <ACPI CPU> on acpi0
acpi_throttle1: <ACPI CPU Throttling> on cpu1
acpi_throttle1: failed to attach P_CNT
device_attach: acpi_throttle1 attach returned 6
cpu2: <ACPI CPU> on acpi0
acpi_throttle2: <ACPI CPU Throttling> on cpu2
acpi_throttle2: failed to attach P_CNT
device_attach: acpi_throttle2 attach returned 6
cpu3: <ACPI CPU> on acpi0
acpi_throttle3: <ACPI CPU Throttling> on cpu3
acpi_throttle3: failed to attach P_CNT
device_attach: acpi_throttle3 attach returned 6
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 2.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> irq 16 at device 0.0 on pci1
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> irq 16 at device 0.0 on pci2
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> irq 18 at device 2.0 on pci2
pci4: <ACPI PCI bus> on pcib4
em0: <Intel(R) PRO/1000 Network Connection Version - 6.2.9> port
0x2000-0x201f mem 0xd8000000-0xd801ffff irq 18 at device 0.0 on pci4
em0: Ethernet address: 00:30:48:8d:e7:8e
em1: <Intel(R) PRO/1000 Network Connection Version - 6.2.9> port
0x2020-0x203f mem 0xd8020000-0xd803ffff irq 19 at device 0.1 on pci4
em1: Ethernet address: 00:30:48:8d:e7:8f
pcib5: <ACPI PCI-PCI bridge> at device 0.3 on pci1
pci5: <ACPI PCI bus> on pcib5
pci0: <base peripheral> at device 8.0 (no driver attached)
pcib6: <ACPI PCI-PCI bridge> irq 17 at device 28.0 on pci0
pci6: <ACPI PCI bus> on pcib6
uhci0: <UHCI (generic) USB controller> port 0x1800-0x181f irq 17 at device
29.0 on pci0
uhci0: [GIANT-LOCKED]
usb0: <UHCI (generic) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <UHCI (generic) USB controller> port 0x1820-0x183f irq 19 at device
29.1 on pci0
uhci1: [GIANT-LOCKED]
usb1: <UHCI (generic) USB controller> on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: <UHCI (generic) USB controller> port 0x1840-0x185f irq 18 at device
29.2 on pci0
uhci2: [GIANT-LOCKED]
usb2: <UHCI (generic) USB controller> on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3: <UHCI (generic) USB controller> port 0x1860-0x187f irq 16 at device
29.3 on pci0
uhci3: [GIANT-LOCKED]
usb3: <UHCI (generic) USB controller> on uhci3
usb3: USB revision 1.0
uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xd8500000-0xd85003ff irq
17
at device 29.7 on pci0
ehci0: [GIANT-LOCKED]
usb4: EHCI version 1.0
usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
usb4: <EHCI (generic) USB 2.0 controller> on ehci0
usb4: USB revision 2.0
uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
pcib7: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci7: <ACPI PCI bus> on pcib7
pci7: <display, VGA> at device 1.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel 63XXESB2 UDMA100 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1880-0x188f at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
atapci1: <Intel 63XXESB2 SATA300 controller> port
0x18c0-0x18c7,0x1894-0x1897,0x1898-0x189f,0x1890-0x1893,0x18a0-0x18bf mem
0xd8500400-0xd85007ff irq 19 at device 31.2 on pci0
atapci1: AHCI Version 01.10 controller with 6 ports detected
ata2: <ATA channel 0> on atapci1
ata3: <ATA channel 1> on atapci1
ata4: <ATA channel 2> on atapci1
ata5: <ATA channel 3> on atapci1
ata6: <ATA channel 4> on atapci1
ata7: <ATA channel 5> on atapci1
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
acpi_button0: <Power Button> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse Explorer, device ID 4
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0
sio0: type 16550A
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on
acpi0
fdc0: [FAST]
ppc0: <ECP parallel printer port> port 0x378-0x37f,0x778-0x77f irq 7 drq 3
on acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
pmtimer0 on isa0
orm0: <ISA Option ROM> at iomem 0xc0000-0xcafff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounters tick every 1.000 msec
acd0: CDRW <Slimtype COMBO SOLC-2481K/1K03> at ata0-slave UDMA33
ad4: 239372MB <WDC WD2500YS-01SHB1 20.06C06> at ata2-master SATA300
ad6: 239372MB <WDC WD2500YS-01SHB1 20.06C06> at ata3-master SATA300
ar0: 239370MB <Intel MatrixRAID RAID1> status: READY
ar0: disk0 READY (master) using ad4 at ata2-master
ar0: disk1 READY (mirror) using ad6 at ata3-master
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
Trying to mount root from ufs:/dev/ar0s1a
ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled,
default to deny, logging disabled
em0: link state changed to UP
Jeremy Chadwick
2008-Feb-19 15:19 UTC
Dual Core Xeon / i386 install w/ more than 4gb of RAM
On Tue, Feb 19, 2008 at 05:10:17PM -0500, Kevin K wrote:> Does anyone have any alternative solutions that would provide a more > reliable environment other than PAE?You have two options, and these are the only two I'm aware of: 1) Run amd64 (64-bit). 2) Run i386 with PAE enabled. I would choose the 64-bit option in your situation. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
On Tue, Feb 19, 2008 at 05:10:17PM -0500, Kevin K wrote:> I have a box that we recently installed 16GB of RAM on. The box is i386 > FreeBSD 6.2. It only recognizes 4gb. > > > > I am currently recompiling the kernel to support options PAE (KERNCONF=PAE) > in order to see this. I understand this is still considered a Beta > implementation ,and this is a production box. > > > > Does anyone have any alternative solutions that would provide a more > reliable environment other than PAE?If you want to use all the 16GB RAM on that machine then your only options is to use the amd64 version of FreeBSD or i386+PAE. amd64 is likely to work better. (Yes, the amd64 version of FreeBSD should work on your hardware according to the quoted dmesg output.)> > > > Dmesg Output is as follows : > > > > Copyright (c) 1992-2007 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > The Regents of the University of California. All rights reserved. > > FreeBSD is a registered trademark of The FreeBSD Foundation. > > FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 > > root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP > > Timecounter "i8254" frequency 1193182 Hz quality 0 > > CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.13-MHz 686-class CPU) > > Origin = "GenuineIntel" Id = 0xf64 Stepping = 4 > > > Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA > ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > Features2=0xe4bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,CNTX-ID,CX16,<b14>,<b15>> > > AMD Features=0x20100000<NX,LM> > > AMD Features2=0x1<LAHF> > > Cores per package: 2 > > Logical CPUs per core: 2 > > real memory = 3489005568 (3327 MB) > > avail memory = 3414196224 (3256 MB) > > ACPI APIC Table: <PTLTD APIC > > > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >[snip] -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
Alfred Perlstein
2008-Feb-20 03:57 UTC
Dual Core Xeon / i386 install w/ more than 4gb of RAM
* Kevin K <kkutzko@teksavvy.com> [080219 14:40] wrote:> I have a box that we recently installed 16GB of RAM on. The box is i386 > FreeBSD 6.2. It only recognizes 4gb. > > > > I am currently recompiling the kernel to support options PAE (KERNCONF=PAE) > in order to see this. I understand this is still considered a Beta > implementation ,and this is a production box. > > > > Does anyone have any alternative solutions that would provide a more > reliable environment other than PAE?Besideds PAE some people have mentioned running an amd64 system. One thing to consider is that PAE in 6-stable (6.3 and beyond) is considered very stable, so if you can't make the jump to amd64 system because you'd have to recompile too much, you might have luck updating sources to 6-stable and trying that kernel, then installing 6.3 userland. good luck, -Alfred
Kevin K <kkutzko@teksavvy.com> wrote:
> I have a box that we recently installed 16GB of RAM on. The box is i386
> FreeBSD 6.2. It only recognizes 4gb.
Several people have already pointed out that you can either
run FreeBSD/i386+PAE or FreeBSD/amd64 (64bit).
However, there's an important piece of information missing:
_Why_ did you install 16 GB of RAM? The answer to that
question might give an indication which of the two ways
would be best for you.
For example, if you need to run a single large application
that needs much RAM, then i386+PAE won't help you at all,
because you still have a 4 GB address space limit and a
4 GB process size limit. Actually much less than 4 GB
because the 32bit address space is shared between kernel
and userland.
To get rid of the 4 GB limit completely, you must install
FreeBSD/amd64. Also, amd64 code is often (but not always)
faster than i386 code.
My recommendation is that you use amd64, unless there is
a specific reason you can't do that, e.g. you depend on
a driver or third-party software that won't run on amd64.
Then i386+PAE is your only choice, unfortunately.
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606, Gesch?ftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M?n-
chen, HRB 125758, Gesch?ftsf?hrer: Maik Bachmann, Olaf Erb, Ralf Gebhart
FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd
"The ITU has offered the IETF formal alignment with its
corresponding technology, Penguins, but that won't fly."
-- RFC 2549