Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 11
We've got a 3Ghz dual core Xeon which we've just stuck 8GB of RAM into. It shows it all during boot up but when I run more /proc/meminfo I get ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Oct 2008
    Posts
    5

    New RAM not showing up


    We've got a 3Ghz dual core Xeon which we've just stuck 8GB of RAM into. It shows it all during boot up but when I run more /proc/meminfo I get this:
    Code:
    MemTotal:       904340 kB
    MemFree:        504420 kB
    Buffers:         44928 kB
    Cached:         207964 kB
    SwapCached:          0 kB
    Active:         263836 kB
    Inactive:       114116 kB
    HighTotal:           0 kB
    HighFree:            0 kB
    LowTotal:       904340 kB
    LowFree:        504420 kB
    SwapTotal:     1975864 kB
    SwapFree:      1975864 kB
    Dirty:               8 kB
    Writeback:           0 kB
    Mapped:         151448 kB
    Slab:            15376 kB
    CommitLimit:   2428032 kB
    Committed_AS:   352608 kB
    PageTables:       1432 kB
    VmallocTotal:   122580 kB
    VmallocUsed:      2796 kB
    VmallocChunk:   119780 kB
    Which seems to tell me that only 900MB is on the system.

    Can anyone help me figure out what's going wrong here?

    (I have some Linux experience but I'm not an expert by any means so please make advice nice and verbose! )

  2. #2
    Linux Guru smolloy's Avatar
    Join Date
    Apr 2005
    Location
    CA, but from N.Ireland
    Posts
    2,414
    What's the output of this command?
    Code:
    free -m
    (By the way, welcome to the forums )
    Registered Linux user #388328 || Registered LFS user #15880
    AMD 64 X2 4600+ :: 2X1GB DDR2 800 :: GeForce 9400 GT 512MB :: ASUS M2N32 Deluxe :: 4X250GB SATAII
    Need instant help? Try us on IRC -- #linuxforums on freenode

  3. #3
    Just Joined!
    Join Date
    Oct 2008
    Posts
    5
    Thanks for the welcome! and for the blistering speed of the reply!

    This is the output:


    Code:
                 total       used       free     shared    buffers     cached
    Mem:           883        467        415          0         47        261
    -/+ buffers/cache:        158        724
    Swap:         1929          0       1929
    Strangely, the web box does appear to be responding much more quickly than before we chucked more RAM at it but that's only an end-user observation on a decidedly unstable internet connection. I'll have to wait till I get home to test it on a solid 8Mbit line.

    One guy in the office "theorised" (i.e. picked the idea out the ether!) that we might have to rebuild the kernel but I've no idea if this would be necessary or not.

  4. #4
    Linux Guru smolloy's Avatar
    Join Date
    Apr 2005
    Location
    CA, but from N.Ireland
    Posts
    2,414
    That's weird. The total memory reported by free is 883 MB (i.e. the same as you saw).

    Hmmmm.....

    Can you post the output of "dmesg" (it will be long, but stick it in code tags, and it won't look too ugly!).

    Also, are you running a 32 or 64 bit kernel?
    Registered Linux user #388328 || Registered LFS user #15880
    AMD 64 X2 4600+ :: 2X1GB DDR2 800 :: GeForce 9400 GT 512MB :: ASUS M2N32 Deluxe :: 4X250GB SATAII
    Need instant help? Try us on IRC -- #linuxforums on freenode

  5. #5
    Just Joined!
    Join Date
    Oct 2008
    Posts
    5
    Here's the output:
    Code:
    Linux version 2.6.15-gentoo-r1 (root@livecd) (gcc version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)) #1 SMP Fri Mar 17 16:57:28 GMT 2006
    BIOS-provided physical RAM map:
     BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
     BIOS-e820: 0000000000100000 - 00000000dffc0000 (usable)
     BIOS-e820: 00000000dffc0000 - 00000000dffcfc00 (ACPI data)
     BIOS-e820: 00000000dffcfc00 - 00000000dffff000 (reserved)
     BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
     BIOS-e820: 00000000fec00000 - 00000000fec90000 (reserved)
     BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved)
     BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
     BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
     BIOS-e820: 0000000100000000 - 00000001ffffe000 (usable)
     BIOS-e820: 00000001ffffe000 - 0000000200000000 (reserved)
     BIOS-e820: 0000000200000000 - 0000000220000000 (usable)
    Warning only 896MB will be used.
    Use a PAE enabled kernel.
    896MB LOWMEM available.
    found SMP MP-table at 000fe710
    On node 0 totalpages: 229376
      DMA zone: 4096 pages, LIFO batch:0
      DMA32 zone: 0 pages, LIFO batch:0
      Normal zone: 225280 pages, LIFO batch:31
      HighMem zone: 0 pages, LIFO batch:0
    DMI 2.3 present.
    ACPI: RSDP (v000 DELL                                  ) @ 0x000fd5b0
    ACPI: RSDT (v001 DELL   PE BKC   0x00000001 MSFT 0x0100000a) @ 0x000fd5c4
    ACPI: FADT (v001 DELL   PE BKC   0x00000001 MSFT 0x0100000a) @ 0x000fd620
    ACPI: MADT (v001 DELL   PE BKC   0x00000001 MSFT 0x0100000a) @ 0x000fd694
    ACPI: SPCR (v001 DELL   PE BKC   0x00000001 MSFT 0x0100000a) @ 0x000fd774
    ACPI: HPET (v001 DELL   PE BKC   0x00000001 MSFT 0x0100000a) @ 0x000fd7c4
    ACPI: MCFG (v001 DELL   PE BKC   0x00000001 MSFT 0x0100000a) @ 0x000fd7fc
    ACPI: DSDT (v001 DELL   PE BKC   0x00000001 MSFT 0x0100000e) @ 0x00000000
    ACPI: Local APIC address 0xfee00000
    ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    Processor #0 15:4 APIC version 20
    ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    Processor #1 15:4 APIC version 20
    ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] disabled)
    ACPI: LAPIC (acpi_id[0x04] lapic_id[0x02] disabled)
    ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] disabled)
    ACPI: LAPIC (acpi_id[0x06] lapic_id[0x07] disabled)
    ACPI: LAPIC (acpi_id[0x07] lapic_id[0x03] disabled)
    ACPI: LAPIC (acpi_id[0x08] lapic_id[0x05] disabled)
    ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
    ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
    ACPI: IOAPIC (id[0x03] address[0xfec80000] gsi_base[32])
    IOAPIC[1]: apic_id 3, version 32, address 0xfec80000, GSI 32-55
    ACPI: IOAPIC (id[0x04] address[0xfec83000] gsi_base[64])
    IOAPIC[2]: apic_id 4, version 32, address 0xfec83000, GSI 64-87
    ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    ACPI: IRQ0 used by override.
    ACPI: IRQ2 used by override.
    ACPI: IRQ9 used by override.
    Enabling APIC mode:  Flat.  Using 3 I/O APICs
    Using ACPI (MADT) for SMP configuration information
    Allocating PCI resources starting at f1000000 (gap: f0000000:0ec00000)
    Built 1 zonelists
    Kernel command line: root=/dev/md4
    mapped APIC to ffffd000 (fee00000)
    mapped IOAPIC to ffffc000 (fec00000)
    mapped IOAPIC to ffffb000 (fec80000)
    mapped IOAPIC to ffffa000 (fec83000)
    Initializing CPU#0
    PID hash table entries: 4096 (order: 12, 65536 bytes)
    Detected 2993.210 MHz processor.
    Using tsc for high-res timesource
    Console: colour VGA+ 80x25
    Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    Memory: 904080k/917504k available (3294k kernel code, 13000k reserved, 952k data, 220k init, 0k highmem)
    Checking if this processor honours the WP bit even in supervisor mode... Ok.
    Calibrating delay using timer specific routine.. 5993.98 BogoMIPS (lpj=11987961)
    Mount-cache hash table entries: 512
    CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000641d 00000000 00000000
    CPU: After vendor identify, caps: bfebfbff 20100000 00000000 00000000 0000641d 00000000 00000000
    monitor/mwait feature present.
    using mwait in idle threads.
    CPU: Trace cache: 12K uops, L1 D cache: 16K
    CPU: L2 cache: 2048K
    CPU: Physical Processor ID: 0
    CPU: After all inits, caps: bfebfbff 20100000 00000000 00000080 0000641d 00000000 00000000
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#0.
    CPU0: Intel P4/Xeon Extended MCE MSRs (24) available
    CPU0: Thermal monitoring enabled
    mtrr: v2.0 (20020519)
    Enabling fast FPU save and restore... done.
    Enabling unmasked SIMD FPU exception support... done.
    Checking 'hlt' instruction... OK.
    CPU0: Intel(R) Xeon(TM) CPU 3.00GHz stepping 03
    Booting processor 1/1 eip 2000
    Initializing CPU#1
    Calibrating delay using timer specific routine.. 5985.87 BogoMIPS (lpj=11971744)
    CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000641d 00000000 00000000
    CPU: After vendor identify, caps: bfebfbff 20100000 00000000 00000000 0000641d 00000000 00000000
    monitor/mwait feature present.
    CPU: Trace cache: 12K uops, L1 D cache: 16K
    CPU: L2 cache: 2048K
    CPU: Physical Processor ID: 0
    CPU: After all inits, caps: bfebfbff 20100000 00000000 00000080 0000641d 00000000 00000000
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#1.
    CPU1: Intel P4/Xeon Extended MCE MSRs (24) available
    CPU1: Thermal monitoring enabled
    CPU1: Intel(R) Xeon(TM) CPU 3.00GHz stepping 03
    Total of 2 processors activated (11979.85 BogoMIPS).
    ENABLING IO-APIC IRQs
    ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
    checking TSC synchronization across 2 CPUs: passed.
    Brought up 2 CPUs
    NET: Registered protocol family 16
    ACPI: bus type pci registered
    PCI: PCI BIOS revision 2.10 entry at 0xfbe4e, last bus=9
    PCI: Using MMCONFIG
    ACPI: Subsystem revision 20050902
    ACPI: Interpreter enabled
    ACPI: Using IOAPIC for interrupt routing
    ACPI: PCI Root Bridge [PCI0] (0000:00)
    PCI: Probing PCI hardware (bus 00)
    PCI quirk: region 0800-087f claimed by ICH4 ACPI/GPIO/TCO
    PCI quirk: region 0880-08bf claimed by ICH4 GPIO
    PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
    PCI: PXH quirk detected, disabling MSI for SHPC device
    PCI: PXH quirk detected, disabling MSI for SHPC device
    Boot video device is 0000:09:0d.0
    PCI: Transparent bridge - 0000:00:1e.0
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PALO._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PALO.DOBA._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PALO.DOBB._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PBLO._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.VPR0._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PBHI._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PBHI.PXB1._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PBHI.PXB2._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PICH._PRT]
    ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12)
    ACPI: PCI Interrupt Link [LNKB] (IRQs *3 4 5 6 7 10 11 12)
    ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 *7 10 11 12)
    ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 11 12)
    ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12) *0, disabled.
    ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12) *0, disabled.
    ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12) *0, disabled.
    ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 10 11 12)
    Linux Plug and Play Support v0.97 (c) Adam Belay
    pnp: PnP ACPI init
    pnp: PnP ACPI: found 9 devices
    SCSI subsystem initialized
    usbcore: registered new driver usbfs
    usbcore: registered new driver hub
    PCI: Using ACPI for IRQ routing
    PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
    pnp: 00:06: ioport range 0x800-0x87f could not be reserved
    pnp: 00:06: ioport range 0x880-0x8bf has been reserved
    pnp: 00:06: ioport range 0x8c0-0x8df has been reserved
    pnp: 00:06: ioport range 0x8e0-0x8e3 has been reserved
    pnp: 00:06: ioport range 0xc00-0xc0f has been reserved
    pnp: 00:06: ioport range 0xc10-0xc1f has been reserved
    pnp: 00:06: ioport range 0xca0-0xcaf has been reserved
    pnp: 00:06: ioport range 0xc20-0xc3f has been reserved
    PCI: Bridge: 0000:01:00.0
      IO window: e000-efff
      MEM window: fe900000-feafffff
      PREFETCH window: f8000000-f8ffffff
    PCI: Bridge: 0000:01:00.2
      IO window: disabled.
      MEM window: disabled.
      PREFETCH window: disabled.
    PCI: Bridge: 0000:00:02.0
      IO window: e000-efff
      MEM window: fe800000-feafffff
      PREFETCH window: f8000000-f8ffffff
    PCI: Bridge: 0000:00:04.0
      IO window: disabled.
      MEM window: disabled.
      PREFETCH window: disabled.
    PCI: Bridge: 0000:05:00.0
      IO window: d000-dfff
      MEM window: fe600000-fe7fffff
      PREFETCH window: disabled.
    PCI: Bridge: 0000:05:00.2
      IO window: c000-cfff
      MEM window: fe400000-fe5fffff
      PREFETCH window: disabled.
    PCI: Bridge: 0000:00:05.0
      IO window: c000-dfff
      MEM window: fe300000-fe7fffff
      PREFETCH window: disabled.
    PCI: Bridge: 0000:00:06.0
      IO window: disabled.
      MEM window: disabled.
      PREFETCH window: disabled.
    PCI: Bridge: 0000:00:1e.0
      IO window: b000-bfff
      MEM window: fe100000-fe2fffff
      PREFETCH window: f0000000-f7ffffff
    ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16
    PCI: Setting latency timer of device 0000:00:02.0 to 64
    PCI: Setting latency timer of device 0000:01:00.0 to 64
    PCI: Setting latency timer of device 0000:01:00.2 to 64
    ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 16 (level, low) -> IRQ 16
    PCI: Setting latency timer of device 0000:00:06.0 to 64
    PCI: Setting latency timer of device 0000:00:1e.0 to 64
    Machine check exception polling timer started.
    audit: initializing netlink socket (disabled)
    audit(1223652563.688:1): initialized
    Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
    Initializing Cryptographic API
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered
    Intel E7520/7320/7525 detected.<6>ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16
    PCI: Setting latency timer of device 0000:00:02.0 to 64
    Allocate Port Service[pcie00]
    Allocate Port Service[pcie01]
    ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 16 (level, low) -> IRQ 16
    PCI: Setting latency timer of device 0000:00:04.0 to 64
    Allocate Port Service[pcie00]
    Allocate Port Service[pcie01]
    ACPI: PCI Interrupt 0000:00:05.0[A] -> GSI 16 (level, low) -> IRQ 16
    PCI: Setting latency timer of device 0000:00:05.0 to 64
    Allocate Port Service[pcie00]
    Allocate Port Service[pcie01]
    ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 16 (level, low) -> IRQ 16
    PCI: Setting latency timer of device 0000:00:06.0 to 64
    Allocate Port Service[pcie00]
    Allocate Port Service[pcie01]
    ACPI: Power Button (FF) [PWRF]
    ACPI: Video Device [EVGA] (multi-head: no  rom: yes  post: no)
    Linux agpgart interface v0.101 (c) Dave Jones
    PNP: No PS/2 controller found. Probing ports directly.
    serio: i8042 AUX port at 0x60,0x64 irq 12
    serio: i8042 KBD port at 0x60,0x64 irq 1
    Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
    serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    mice: PS/2 mouse device common for all mice
    FDC 0 is a National Semiconductor PC87306
    Intel(R) PRO/1000 Network Driver - version 6.1.16-k2
    Copyright (c) 1999-2005 Intel Corporation.
    ACPI: PCI Interrupt 0000:06:07.0[A] -> GSI 64 (level, low) -> IRQ 17
    e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
    ACPI: PCI Interrupt 0000:07:08.0[A] -> GSI 65 (level, low) -> IRQ 18
    e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
    Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
    ICH5: IDE controller at PCI slot 0000:00:1f.1
    PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
    ACPI: PCI Interrupt 0000:00:1f.1[A]: no GSI
    ICH5: chipset revision 2
    ICH5: not 100% native mode: will probe irqs later
        ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio
        ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:pio
    Probing IDE interface ide0...
    hda: HL-DT-ST GCR-8240N, ATAPI CD/DVD-ROM drive
    ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
    Probing IDE interface ide1...
    Probing IDE interface ide1...
    hda: ATAPI 24X CD-ROM drive, 128kB Cache
    Uniform CD-ROM driver Revision: 3.20
    libata version 1.20 loaded.
    Fusion MPT base driver 3.03.04
    Copyright (c) 1999-2005 LSI Logic Corporation
    Fusion MPT SPI Host driver 3.03.04
    ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 34 (level, low) -> IRQ 19
    mptbase: Initiating ioc0 bringup
    ioc0: 53C1030: Capabilities={Initiator,Target}
    scsi0 : ioc0: LSI53C1030, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=19
      Vendor: FUJITSU   Model: MAW3073NC         Rev: 5803
      Type:   Direct-Access                      ANSI SCSI revision: 03
    SCSI device sda: 143374650 512-byte hdwr sectors (73408 MB)
    SCSI device sda: drive cache: write through
    SCSI device sda: 143374650 512-byte hdwr sectors (73408 MB)
    SCSI device sda: drive cache: write through
     sda: sda1 sda2 sda3 sda4
    sd 0:0:0:0: Attached scsi disk sda
    sd 0:0:0:0: Attached scsi generic sg0 type 0
      Vendor: FUJITSU   Model: MAW3073NC         Rev: 5803
      Type:   Direct-Access                      ANSI SCSI revision: 03
    SCSI device sdb: 143374650 512-byte hdwr sectors (73408 MB)
    SCSI device sdb: drive cache: write through
    SCSI device sdb: 143374650 512-byte hdwr sectors (73408 MB)
    SCSI device sdb: drive cache: write through
     sdb: sdb1 sdb2 sdb3 sdb4
    sd 0:0:1:0: Attached scsi disk sdb
    sd 0:0:1:0: Attached scsi generic sg1 type 0
      Vendor: PE/PV     Model: 1x2 SCSI BP       Rev: 1.0
      Type:   Processor                          ANSI SCSI revision: 02
     0:0:6:0: Attached scsi generic sg2 type 3
    Fusion MPT FC Host driver 3.03.04
    Fusion MPT SAS Host driver 3.03.04
    ieee1394: raw1394: /dev/raw1394 device initialized
    usbmon: debugfs is not available
    ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 20
    PCI: Setting latency timer of device 0000:00:1d.7 to 64
    ehci_hcd 0000:00:1d.7: EHCI Host Controller
    ehci_hcd 0000:00:1d.7: debug port 1
    PCI: cache line size of 128 is not supported by device 0000:00:1d.7
    ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:1d.7: irq 20, io mem 0xfeb00000
    ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 6 ports detected
    USB Universal Host Controller Interface driver v2.3
    ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
    PCI: Setting latency timer of device 0000:00:1d.0 to 64
    uhci_hcd 0000:00:1d.0: UHCI Host Controller
    uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
    uhci_hcd 0000:00:1d.0: irq 16, io base 0x0000ace0
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 2 ports detected
    ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 21
    PCI: Setting latency timer of device 0000:00:1d.1 to 64
    uhci_hcd 0000:00:1d.1: UHCI Host Controller
    uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
    uhci_hcd 0000:00:1d.1: irq 21, io base 0x0000acc0
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 2 ports detected
    ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 22
    PCI: Setting latency timer of device 0000:00:1d.2 to 64
    uhci_hcd 0000:00:1d.2: UHCI Host Controller
    uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
    uhci_hcd 0000:00:1d.2: irq 22, io base 0x0000aca0
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 2 ports detected
    usb 1-3: new high speed USB device using ehci_hcd and address 2
    Initializing USB Mass Storage driver...
    hub 1-3:1.0: USB hub found
    hub 1-3:1.0: 2 ports detected
    usbcore: registered new driver usb-storage
    USB Mass Storage support registered.
    usbcore: registered new driver usbhid
    drivers/usb/input/hid-core.c: v2.6:USB HID core driver
    md: raid1 personality registered as nr 3
    md: raid5 personality registered as nr 4
    raid5: automatically using best checksumming function: pIII_sse
       pIII_sse  :  4630.000 MB/sec
    raid5: using function: pIII_sse (4630.000 MB/sec)
    md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
    md: bitmap version 4.39
    oprofile: using NMI interrupt.
    NET: Registered protocol family 2
    IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
    TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
    TCP: Hash tables configured (established 131072 bind 65536)
    TCP reno registered
    ip_conntrack version 2.4 (7168 buckets, 57344 max) - 212 bytes per conntrack
    ip_tables: (C) 2000-2002 Netfilter core team
    ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>.  http://snowman.net/projects/ipt_recent/
    arp_tables: (C) 2002 David S. Miller
    TCP bic registered
    NET: Registered protocol family 1
    NET: Registered protocol family 10
    lo: Disabled Privacy Extensions
    IPv6 over IPv4 tunneling driver
    NET: Registered protocol family 17
    Starting balanced_irq
    Using IPI Shortcut mode
    md: Autodetecting RAID arrays.
    md: autorun ...
    md: considering sdb4 ...
    md:  adding sdb4 ...
    md: sdb3 has different UUID to sdb4
    md: sdb2 has different UUID to sdb4
    md: sdb1 has different UUID to sdb4
    md:  adding sda4 ...
    md: sda3 has different UUID to sdb4
    md: sda2 has different UUID to sdb4
    md: sda1 has different UUID to sdb4
    md: created md4
    md: bind<sda4>
    md: bind<sdb4>
    md: running: <sdb4><sda4>
    raid1: raid set md4 active with 2 out of 2 mirrors
    md: considering sdb3 ...
    md:  adding sdb3 ...
    md: sdb2 has different UUID to sdb3
    md: sdb1 has different UUID to sdb3
    md:  adding sda3 ...
    md: sda2 has different UUID to sdb3
    md: sda1 has different UUID to sdb3
    md: created md3
    md: bind<sda3>
    md: bind<sdb3>
    md: running: <sdb3><sda3>
    raid1: raid set md3 active with 2 out of 2 mirrors
    md: considering sdb2 ...
    md:  adding sdb2 ...
    md: sdb1 has different UUID to sdb2
    md:  adding sda2 ...
    md: sda1 has different UUID to sdb2
    md: created md2
    md: bind<sda2>
    md: bind<sdb2>
    md: running: <sdb2><sda2>
    raid1: raid set md2 active with 2 out of 2 mirrors
    md: considering sdb1 ...
    md:  adding sdb1 ...
    md:  adding sda1 ...
    md: created md1
    md: bind<sda1>
    md: bind<sdb1>
    md: running: <sdb1><sda1>
    raid1: raid set md1 active with 2 out of 2 mirrors
    md: ... autorun DONE.
    ReiserFS: md4: found reiserfs format "3.6" with standard journal
    ReiserFS: md4: using ordered data mode
    ReiserFS: md4: journal params: device md4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
    ReiserFS: md4: checking transaction log (md4)
    ReiserFS: md4: Using r5 hash to sort names
    VFS: Mounted root (reiserfs filesystem) readonly.
    Freeing unused kernel memory: 220k freed
    Adding 1975864k swap on /dev/md3.  Priority:-1 extents:1 across:1975864k
    kjournald starting.  Commit interval 5 seconds
    EXT3 FS on md1, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    ReiserFS: md2: found reiserfs format "3.6" with standard journal
    ReiserFS: md2: using ordered data mode
    ReiserFS: md2: journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
    ReiserFS: md2: checking transaction log (md2)
    ReiserFS: md2: Using r5 hash to sort names
    Thing is, I think I may have spotted something in the .config file:

    Code:
    CONFIG_NOHIGHMEM=y
    # CONFIG_HIGHMEM4G is not set
    # CONFIG_HIGHMEM64G is not set
    CONFIG_SELECT_MEMORY_MODEL=y
    Correct me if I'm wrong, but isn't this the culprit?

  6. #6
    Linux Guru smolloy's Avatar
    Join Date
    Apr 2005
    Location
    CA, but from N.Ireland
    Posts
    2,414
    Right at the top of the dmesg output
    Code:
    Warning only 896MB will be used.
    Use a PAE enabled kernel.
    896MB LOWMEM available.
    Which agrees with your CONFIG_NOHIGHMEM theory.

    Sorry to be the bearer of bad news, but I think a kernel recompile is in your future :S
    Registered Linux user #388328 || Registered LFS user #15880
    AMD 64 X2 4600+ :: 2X1GB DDR2 800 :: GeForce 9400 GT 512MB :: ASUS M2N32 Deluxe :: 4X250GB SATAII
    Need instant help? Try us on IRC -- #linuxforums on freenode

  7. #7
    Just Joined!
    Join Date
    Oct 2008
    Posts
    5
    To be honest, that's probably a good thing - may give me the motivation to upgrade it to the latest 64bit kernel.

    Thanks for the help - no doubt I'll be visiting here more and more in the coming weeks

  8. #8
    Just Joined!
    Join Date
    Oct 2008
    Posts
    5
    OK, so I'm back after a refreshing weekend (not!) and I need to work out how to do this recompile safely bearing in mind the server is at a remote site a long way way and there's no way I can be in front of the machine in case something goes wrong.

    I seem to remember that when we had an issue with a linux box in the office, we added the mem command to the config file and ran update-grub. I take it that's not an option here?

    A little advice on a recompile would be greatly appreciated. I've googled a lot and found plenty on completely new compiles but I think to be safe, we'll want to stick with the current version and just do as simple a recompile as possible to minimise the possibility of having problems.

  9. #9
    Linux Guru smolloy's Avatar
    Join Date
    Apr 2005
    Location
    CA, but from N.Ireland
    Posts
    2,414
    I can't give you the exact details (since it's been a long time since I rolled my own kernel), but you only want to make a small change -- that of the low memory limit -- since there's less chance of something going wrong if you only make small changes.

    You should call "make-menuconfig" from the folder where you have your kernel source, load your current kernel config, make the one change you need, save as a different config (don't wipe out the old version!), and compile. Then edit Grub to include an additional option to boot into the new kernel, and, hey presto, you're done!

    Please note that that was only only a rough outline. Since I'm recommending basing the new kernel on your old one, you have to be really careful not to overwrite your old kernel and config files. In case the new kernel doesn't work, you will want to be able to boot back into the old one.

    Try to read up on all this, and make sure it makes sense. It's very likely that I've missed some important detail, and I take no responsibility if something goes wrong! Be sure you understand each and every step before you do it.

    Man, the idea of compiling and booting a new kernel remotely gives me the shivers.....
    Registered Linux user #388328 || Registered LFS user #15880
    AMD 64 X2 4600+ :: 2X1GB DDR2 800 :: GeForce 9400 GT 512MB :: ASUS M2N32 Deluxe :: 4X250GB SATAII
    Need instant help? Try us on IRC -- #linuxforums on freenode

  10. #10
    Just Joined! sathiya's Avatar
    Join Date
    Feb 2008
    Location
    Bangalore, India
    Posts
    97
    if you are going for recompile of the kernel, better test it on a testing machine, and then go for the real one.

    and also, instead of doing this recompile, you can go for the kernel which has the _bigmem as suffix, where it will support big sized memories....

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •