FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 01-21-2010, 03:19 AM
Stan Hoeppner
 
Default Problem with Lenny

Roman Gelfand put forth on 1/20/2010 9:26 PM:
> Jan 20 21:59:37 mail kernel: [ 0.000000] Linux version 2.6.26-2-686
> (Debian 2.6.26-19lenny2) (dannf@debian.org) (gcc version 4.1.3
> 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Nov 4 20:45:37 UTC
> 2009
> My machine freezes every so often. I was wodering if there is any
> clues in kernel.log exerpts below. Thanks in advance

Define "freezes". Post the machine brand/model/specs.

> Jan 20 21:59:37 mail kernel: [ 0.000000] SMP: Allowing 0 CPUs, 0 hotplug CPUs
> Jan 20 21:59:37 mail kernel: [ 0.000000] PERCPU: Allocating 37992
> bytes of per cpu data
> Jan 20 21:59:37 mail kernel: [ 0.000000] NR_CPUS: 8, nr_cpu_ids: 1

This ^^ is very odd. "Allowing 0 CPUs" is very strange. Given that, this
"NR_CPUS: 8" is even more strange.

> Jan 20 21:59:37 mail kernel: [ 0.004000] Memory: 598724k/614336k
> available (1770k kernel code, 14940k reserved, 750k data, 244k init,
> 0k highmem)

Also very strange ^^

According to that above, your system has 0 smp cpus, but it has 8 cpus, and only
one of those 8 has an ID. This also says you have ~600MB of system memory.
There is no physical combo of DIMMs that yields 600MB so we can assume you have
motherboard video chip and the BIOS is assigning system RAM for the frame
buffer. But on a modern system, why do you have so little RAM installed?

Unfortunately the system information provided by kern.log is incomplete. Please
post output from dmesg so we can get a more complete picture of your system.
Your kern.log info alone is not enough to diagnose what is causing your system
to "freeze". Something to consider is that kernel issues usually cause panics,
not freezes. If your system is freezing, or "hard locking", this is usually a
sign of:

1. A thermal issue
2. Defective hardware
3. Hardware compatibility mismatch

For comparison to your kern.log, I have a two CPU system, each a single core CPU:

Jan 20 01:59:42 greer kernel: found SMP MP-table at [c00f5b90] f5b90
Jan 20 01:59:42 greer kernel: SMP: Allowing 2 CPUs, 0 hotplug CPUs
Jan 20 01:59:42 greer kernel: NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1

--
Stan


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-21-2010, 01:14 PM
Roman Gelfand
 
Default Problem with Lenny

I didn't mention before that this is guest os running on virtualbox.
Below, is dmesg.log

[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.26-2-686 (Debian 2.6.26-19lenny2)
(dannf@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian
4.1.2-25)) #1 SMP Wed Nov 4 20:45:37 UTC 2009
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 00000000257f0000 (usable)
[ 0.000000] BIOS-e820: 00000000257f0000 - 0000000025800000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved)
[ 0.000000] WARNING: strange, CPU MTRRs all blank?
[ 0.000000] ------------[ cut here ]------------
[ 0.000000] WARNING: at arch/x86/kernel/cpu/mtrr/main.c:696
mtrr_trim_uncached_memory+0x178/0x183()
[ 0.000000] Modules linked in:
[ 0.000000] Pid: 0, comm: swapper Not tainted 2.6.26-2-686 #1
[ 0.000000] [<c01225f3>] warn_on_slowpath+0x40/0x66
[ 0.000000] [<c02b9b2b>] _spin_lock_irqsave+0x16/0x2f
[ 0.000000] [<c02b9bb9>] _spin_unlock_irqrestore+0xd/0x10
[ 0.000000] [<c0122a94>] release_console_sem+0x173/0x18c
[ 0.000000] [<c0122f0b>] vprintk+0x2d2/0x2de
[ 0.000000] [<c010cd84>] mtrr_wrmsr+0xf/0x2e
[ 0.000000] [<c0122f2b>] printk+0x14/0x18
[ 0.000000] [<c03873cb>] mtrr_trim_uncached_memory+0x178/0x183
[ 0.000000] [<c0385060>] setup_arch+0x254/0x6bb
[ 0.000000] [<c0122f2b>] printk+0x14/0x18
[ 0.000000] [<c037f5e4>] start_kernel+0x62/0x2d7
[ 0.000000] =======================
[ 0.000000] ---[ end trace 4eaa2a86a8e2da22 ]---
[ 0.000000] 0MB HIGHMEM available.
[ 0.000000] 599MB LOWMEM available.
[ 0.000000] Entering add_active_range(0, 0, 153584) 0 entries of 256 used
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0 -> 4096
[ 0.000000] Normal 4096 -> 153584
[ 0.000000] HighMem 153584 -> 153584
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0 -> 153584
[ 0.000000] On node 0 totalpages: 153584
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 4064 pages, LIFO batch:0
[ 0.000000] Normal zone: 1168 pages used for memmap
[ 0.000000] Normal zone: 148320 pages, LIFO batch:31
[ 0.000000] HighMem zone: 0 pages used for memmap
[ 0.000000] Movable zone: 0 pages used for memmap
[ 0.000000] DMI 2.5 present.
[ 0.000000] ACPI: RSDP 000E0000, 0024 (r2 VBOX )
[ 0.000000] ACPI: XSDT 257F0030, 002C (r1 VBOX VBOXXSDT 1
ASL 61)
[ 0.000000] ACPI: FACP 257F00E0, 00F4 (r4 VBOX VBOXFACP 1
ASL 61)
[ 0.000000] ACPI: DSDT 257F0220, 1A0C (r1 VBOX VBOXBIOS 2
INTL 20061109)
[ 0.000000] ACPI: FACS 257F01E0, 0040
[ 0.000000] ACPI: PM-Timer IO Port: 0x4008
[ 0.000000] Allocating PCI resources starting at 30000000 (gap:
25800000:da7c0000)
[ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
[ 0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
[ 0.000000] SMP: Allowing 0 CPUs, 0 hotplug CPUs
[ 0.000000] PERCPU: Allocating 37992 bytes of per cpu data
[ 0.000000] NR_CPUS: 8, nr_cpu_ids: 1
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 152384
[ 0.000000] Kernel command line: root=/dev/hda1 ro quiet
[ 0.000000] Found and enabled local APIC!
[ 0.000000] mapped APIC to ffffb000 (fee00000)
[ 0.000000] Enabling fast FPU save and restore... done.
[ 0.000000] Enabling unmasked SIMD FPU exception support... done.
[ 0.000000] Initializing CPU#0
[ 0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
[ 0.000000] Detected 2389.864 MHz processor.
[ 0.004000] Console: colour VGA+ 80x25
[ 0.004000] console [tty0] enabled
[ 0.004000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.004000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.004000] Memory: 598724k/614336k available (1770k kernel code,
14940k reserved, 750k data, 244k init, 0k highmem)
[ 0.004000] virtual kernel memory layout:
[ 0.004000] fixmap : 0xfff4c000 - 0xfffff000 ( 716 kB)
[ 0.004000] pkmap : 0xff800000 - 0xffc00000 (4096 kB)
[ 0.004000] vmalloc : 0xe6000000 - 0xff7fe000 ( 407 MB)
[ 0.004000] lowmem : 0xc0000000 - 0xe57f0000 ( 599 MB)
[ 0.004000] .init : 0xc037f000 - 0xc03bc000 ( 244 kB)
[ 0.004000] .data : 0xc02baaa1 - 0xc0376620 ( 750 kB)
[ 0.004000] .text : 0xc0100000 - 0xc02baaa1 (1770 kB)
[ 0.004000] Checking if this processor honours the WP bit even in
supervisor mode...Ok.
[ 0.004000] CPA: page pool initialized 1 of 1 pages preallocated
[ 0.096210] Calibrating delay using timer specific routine..
5090.78 BogoMIPS (lpj=10181576)
[ 0.098717] Security Framework initialized
[ 0.098816] SELinux: Disabled at boot.
[ 0.098887] Capability LSM initialized
[ 0.101906] Mount-cache hash table entries: 512
[ 0.141608] Initializing cgroup subsys ns
[ 0.141896] Initializing cgroup subsys cpuacct
[ 0.142113] Initializing cgroup subsys devices
[ 0.143338] CPU: Trace cache: 12K uops, L1 D cache: 8K
[ 0.143624] CPU: L2 cache: 512K
[ 0.143855] Intel machine check architecture supported.
[ 0.144528] Intel machine check reporting enabled on CPU#0.
[ 0.145453] Checking 'hlt' instruction... OK.
[ 0.199434] SMP alternatives: switching to UP code
[ 1.424031] Freeing SMP alternatives: 16k freed
[ 1.425883] ACPI: Core revision 20080321
[ 1.453007] ACPI: setting ELCR to 0200 (from 0e00)
[ 1.521880] weird, boot CPU (#0) not listedby the BIOS.
[ 1.522270] SMP motherboard not detected.
[ 1.532031] SMP disabled
[ 1.568720] Brought up 1 CPUs
[ 1.568783] Total of 1 processors activated (5090.78 BogoMIPS).
[ 1.568858] CPU0 attaching sched-domain:
[ 1.568907] domain 0: span 0
[ 1.568966] groups: 0
[ 1.632024] net_namespace: 660 bytes
[ 1.633726] Booting paravirtualized kernel on bare hardware
[ 1.643479] NET: Registered protocol family 16
[ 1.654238] ACPI: bus type pci registered
[ 1.670883] PCI: PCI BIOS revision 2.10 entry at 0xfc080, last bus=0
[ 1.671148] PCI: Using configuration type 1 for base access
[ 1.671423] Setting up standard PCI resources
[ 1.716768] ACPI: EC: Look up EC in DSDT
[ 1.762069] ACPI: Interpreter enabled
[ 1.762139] ACPI: (supports S0 S5)
[ 1.762375] ACPI: Using PIC for interrupt routing
[ 1.807540] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 1.838948] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 1.865318] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 9 10 11) *0, disabled.
[ 1.866938] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 9 10 *11)
[ 1.867213] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 9 *10 11)
[ 1.868851] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 *9 10 11)
[ 1.871511] Linux Plug and Play Support v0.97 (c) Adam Belay
[ 1.873158] pnp: PnP ACPI init
[ 1.873267] ACPI: bus type pnp registered
[ 1.885384] pnp: PnP ACPI: found 6 devices
[ 1.885427] ACPI: ACPI bus type pnp unregistered
[ 1.885460] PnPBIOS: Disabled by ACPI PNP
[ 1.901465] PCI: Using ACPI for IRQ routing
[ 1.959186] NET: Registered protocol family 2
[ 1.970097] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 1.971283] TCP established hash table entries: 131072 (order: 8,
1048576 bytes)
[ 1.983993] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[ 1.984084] TCP: Hash tables configured (established 131072 bind 65536)
[ 1.984084] TCP reno registered
[ 1.984084] NET: Registered protocol family 1
[ 1.987569] checking if image is initramfs... it is
[ 2.468117] Switched to high resolution mode on CPU 0
[ 2.952228] Freeing initrd memory: 6037k freed
[ 2.958039] platform rtc_cmos: registered platform RTC device (no
PNP device found)
[ 2.990770] audit: initializing netlink socket (disabled)
[ 2.998123] type=2000 audit(1264024612.993:1): initialized
[ 3.008155] Total HugeTLB memory allocated, 0
[ 3.008155] VFS: Disk quotas dquot_6.5.1
[ 3.008155] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 3.008155] msgmni has been set to 1181
[ 3.011812] Block layer SCSI generic (bsg) driver version 0.4
loaded (major 253)
[ 3.011883] io scheduler noop registered
[ 3.011927] io scheduler anticipatory registered
[ 3.011963] io scheduler deadline registered
[ 3.012027] io scheduler cfq registered (default)
[ 3.012109] pci 0000:00:00.0: Limiting direct PCI/PCI transfers
[ 3.013194] pci 0000:00:01.0: Activating ISA DMA hang workarounds
[ 3.013299] pci 0000:00:02.0: Boot video device
[ 3.038646] isapnp: Scanning for PnP cards...
[ 3.484147] isapnp: No Plug & Play device found
[ 3.580259] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports,
IRQ sharing enabled
[ 3.646022] brd: module loaded
[ 3.648109] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at
0x60,0x64 irq 1,12
[ 3.668214] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 3.670618] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 3.677432] mice: PS/2 mouse device common for all mice
[ 3.704173] input: AT Translated Set 2 keyboard as /class/input/input0
[ 3.704173] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
[ 3.710502] rtc0: alarms up to one day
[ 3.721128] cpuidle: using governor ladder
[ 3.721188] cpuidle: using governor menu
[ 3.721271] No iBFT detected.
[ 3.722403] TCP cubic registered
[ 3.722468] NET: Registered protocol family 17
[ 3.722597] Using IPI No-Shortcut mode
[ 3.726773] registered taskstats version 1
[ 3.728099] rtc_cmos rtc_cmos: setting system clock to 2010-01-20
21:56:55 UTC (1264024615)
[ 3.739479] Freeing unused kernel memory: 244k freed
[ 7.803716] Uniform Multi-Platform E-IDE driver
[ 7.803819] ide: Assuming 33MHz system bus speed for PIO modes;
override with idebus=xx
[ 8.014649] PIIX4: IDE controller (0x8086:0x7111 rev 0x01) at PCI
slot 0000:00:01.1
[ 8.015078] PIIX4: not 100% native mode: will probe irqs later
[ 8.015302] ide0: BM-DMA at 0xd000-0xd007
[ 8.015431] ide1: BM-DMA at 0xd008-0xd00f
[ 8.015764] Probing IDE interface ide0...
[ 8.178635] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
[ 8.178703] Copyright (c) 1999-2006 Intel Corporation.
[ 8.422597] hda: VBOX HARDDISK, ATA DISK drive
[ 8.752388] Floppy drive(s): fd0 is 1.44M
[ 8.786938] FDC 0 is a S82078B
[ 9.099340] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
[ 9.103485] hda: UDMA/33 mode selected
[ 9.104123] Probing IDE interface ide1...
[ 9.847328] hdc: VBOX CD-ROM, ATAPI CD/DVD-ROM drive
[ 10.522781] hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4
[ 10.523076] hdc: UDMA/33 mode selected
[ 10.523695] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[ 10.532219] ide1 at 0x170-0x177,0x376 on irq 15
[ 10.571264] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
[ 10.571264] PCI: setting IRQ 10 as level-triggered
[ 10.571264] ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKC] ->
GSI 10 (level, low) -> IRQ 10
[ 10.571264] PCI: Setting latency timer of device 0000:00:03.0 to 64
[ 10.591005] No dock devices found.
[ 11.149852] e1000: 0000:00:03.0: e1000_probe: (PCI:33MHz:32-bit)
08:00:27:74:27:cc
[ 11.162148] SCSI subsystem initialized
[ 11.210906] libata version 3.00 loaded.
[ 11.278916] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
[ 11.477994] hda: max request size: 128KiB
[ 11.478083] hda: 16777216 sectors (8589 MB) w/256KiB Cache, CHS=16644/16/63
[ 11.537609] hda: cache flushes supported
[ 11.537832] hda: hda1 hda2 < hda5 >
[ 11.644436] hdc: ATAPI 32X DVD-ROM drive, 128kB Cache
[ 11.644717] Uniform CD-ROM driver Revision: 3.20
[ 12.598276] PM: Starting manual resume from disk
[ 12.803507] EXT3-fs: INFO: recovery required on readonly filesystem.
[ 12.803581] EXT3-fs: write access will be enabled during recovery.
[ 15.699406] kjournald starting. Commit interval 5 seconds
[ 15.699768] EXT3-fs: hda1: orphan cleanup on readonly fs
[ 15.701524] ext3_orphan_cleanup: deleting unreferenced inode 188057
[ 15.701849] ext3_orphan_cleanup: deleting unreferenced inode 188056
[ 15.702096] ext3_orphan_cleanup: deleting unreferenced inode 188055
[ 15.702172] ext3_orphan_cleanup: deleting unreferenced inode 188054
[ 15.702248] ext3_orphan_cleanup: deleting unreferenced inode 188053
[ 15.702311] EXT3-fs: hda1: 5 orphan inodes deleted
[ 15.702376] EXT3-fs: recovery complete.
[ 15.715935] EXT3-fs: mounted filesystem with ordered data mode.
[ 17.725260] udevd version 125 started
[ 23.422723] piix4_smbus 0000:00:07.0: Found 0000:00:07.0 device
[ 23.422952] piix4_smbus 0000:00:07.0: SMB base address
uninitialized - upgrade BIOS or use force_addr=0xaddr
[ 23.518214] input: PC Speaker as /class/input/input1
[ 24.144343] input: Power Button (FF) as /class/input/input2
[ 24.177667] ACPI: Power Button (FF) [PWRF]
[ 24.178019] input: Sleep Button (FF) as /class/input/input3
[ 24.209570] input: ImExPS/2 Generic Explorer Mouse as /class/input/input4
[ 24.297553] ACPI: Sleep Button (FF) [SLPF]
[ 25.101514] ACPI: AC Adapter [AC] (on-line)
[ 25.674248] parport_pc 00:05: reported by Plug and Play ACPI
[ 25.689941] Error: Driver 'pcspkr' is already registered, aborting...
[ 28.668281] Adding 409616k swap on /dev/hda5. Priority:-1
extents:1 across:409616k
[ 29.080334] EXT3 FS on hda1, internal journal
[ 30.581608] loop: module loaded
[ 31.456264] fuse init (API version 7.9)
[ 33.728775] e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps
Full Duplex, Flow Control: RX
[ 35.786317] NET: Registered protocol family 10
[ 35.801116] lo: Disabled Privacy Extensions


On Wed, Jan 20, 2010 at 11:19 PM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
> Roman Gelfand put forth on 1/20/2010 9:26 PM:
>> Jan 20 21:59:37 mail kernel: [ * *0.000000] Linux version 2.6.26-2-686
>> (Debian 2.6.26-19lenny2) (dannf@debian.org) (gcc version 4.1.3
>> 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Nov 4 20:45:37 UTC
>> 2009
>> My machine freezes every so often. *I was wodering if there is any
>> clues in kernel.log exerpts below. *Thanks in advance
>
> Define "freezes". *Post the machine brand/model/specs.
>
>> Jan 20 21:59:37 mail kernel: [ * *0.000000] SMP: Allowing 0 CPUs, 0 hotplug CPUs
>> Jan 20 21:59:37 mail kernel: [ * *0.000000] PERCPU: Allocating 37992
>> bytes of per cpu data
>> Jan 20 21:59:37 mail kernel: [ * *0.000000] NR_CPUS: 8, nr_cpu_ids: 1
>
> This ^^ is very odd. *"Allowing 0 CPUs" is very strange. *Given that, this
> "NR_CPUS: 8" is even more strange.
>
>> Jan 20 21:59:37 mail kernel: [ * *0.004000] Memory: 598724k/614336k
>> available (1770k kernel code, 14940k reserved, 750k data, 244k init,
>> 0k highmem)
>
> Also very strange ^^
>
> According to that above, your system has 0 smp cpus, but it has 8 cpus, and only
> one of those 8 has an ID. *This also says you have ~600MB of system memory.
> There is no physical combo of DIMMs that yields 600MB so we can assume you have
> motherboard video chip and the BIOS is assigning system RAM for the frame
> buffer. *But on a modern system, why do you have so little RAM installed?
>
> Unfortunately the system information provided by kern.log is incomplete. *Please
> post output from dmesg so we can get a more complete picture of your system.
> Your kern.log info alone is not enough to diagnose what is causing your system
> to "freeze". *Something to consider is that kernel issues usually cause panics,
> not freezes. *If your system is freezing, or "hard locking", this is usually a
> sign of:
>
> 1. *A thermal issue
> 2. *Defective hardware
> 3. *Hardware compatibility mismatch
>
> For comparison to your kern.log, I have a two CPU system, each a single core CPU:
>
> Jan 20 01:59:42 greer kernel: found SMP MP-table at [c00f5b90] f5b90
> Jan 20 01:59:42 greer kernel: SMP: Allowing 2 CPUs, 0 hotplug CPUs
> Jan 20 01:59:42 greer kernel: NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1
>
> --
> Stan
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-22-2010, 01:40 AM
Jeffrey Cao
 
Default Problem with Lenny

On 2010-01-21, Stan Hoeppner <stan@hardwarefreak.com> wrote:
> Roman Gelfand put forth on 1/20/2010 9:26 PM:
>> Jan 20 21:59:37 mail kernel: [ 0.000000] Linux version 2.6.26-2-686
>> (Debian 2.6.26-19lenny2) (dannf@debian.org) (gcc version 4.1.3
>> 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Nov 4 20:45:37 UTC
>> 2009
>> My machine freezes every so often. I was wodering if there is any
>> clues in kernel.log exerpts below. Thanks in advance
>
> Define "freezes". Post the machine brand/model/specs.
>
>> Jan 20 21:59:37 mail kernel: [ 0.000000] SMP: Allowing 0 CPUs, 0 hotplug CPUs
>> Jan 20 21:59:37 mail kernel: [ 0.000000] PERCPU: Allocating 37992
>> bytes of per cpu data
>> Jan 20 21:59:37 mail kernel: [ 0.000000] NR_CPUS: 8, nr_cpu_ids: 1
>
> This ^^ is very odd. "Allowing 0 CPUs" is very strange. Given that, this
> "NR_CPUS: 8" is even more strange.
"NR_CPUS: 8" is not a strange thing. It's the number of CPUs that the kernel
supports, not the CPUs existed in the machine.

config NR_CPUS
int "Maximum number of CPUs" if SMP && !MAXSMP
range 2 8 if SMP && X86_32 && !X86_BIGSMP
range 2 512 if SMP && !MAXSMP
default "1" if !SMP
default "4096" if MAXSMP
default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
default "8" if SMP
---help---
This allows you to specify the maximum number of CPUs which this
kernel will support. The maximum supported value is 512 and the
minimum value which makes sense is 2.

This is purely to save memory - each supported CPU adds
approximately eight kilobytes to the kernel image.

>
>> Jan 20 21:59:37 mail kernel: [ 0.004000] Memory: 598724k/614336k
>> available (1770k kernel code, 14940k reserved, 750k data, 244k init,
>> 0k highmem)
>
> Also very strange ^^
>
> According to that above, your system has 0 smp cpus, but it has 8 cpus, and only
> one of those 8 has an ID. This also says you have ~600MB of system memory.
> There is no physical combo of DIMMs that yields 600MB so we can assume you have
> motherboard video chip and the BIOS is assigning system RAM for the frame
> buffer. But on a modern system, why do you have so little RAM installed?
>
> Unfortunately the system information provided by kern.log is incomplete. Please
> post output from dmesg so we can get a more complete picture of your system.
> Your kern.log info alone is not enough to diagnose what is causing your system
> to "freeze". Something to consider is that kernel issues usually cause panics,
> not freezes. If your system is freezing, or "hard locking", this is usually a
> sign of:
>
> 1. A thermal issue
> 2. Defective hardware
> 3. Hardware compatibility mismatch
>
> For comparison to your kern.log, I have a two CPU system, each a single core CPU:
>
> Jan 20 01:59:42 greer kernel: found SMP MP-table at [c00f5b90] f5b90
> Jan 20 01:59:42 greer kernel: SMP: Allowing 2 CPUs, 0 hotplug CPUs
> Jan 20 01:59:42 greer kernel: NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-01-2010, 04:16 PM
Roman Gelfand
 
Default Problem with Lenny

Ran out memory. This is my conclusion. Originally, I had given
500mb ram. Though top was showing 300mb utilization, memstat showed
1.1gig. It seems the later is the one I was supposed to pay attention
to. I am currently looking into the difference between the top's
memory utilization display and that of memstat.

On Thu, Jan 21, 2010 at 9:40 PM, Jeffrey Cao <jcao.linux@gmail.com> wrote:
> On 2010-01-21, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>> Roman Gelfand put forth on 1/20/2010 9:26 PM:
>>> Jan 20 21:59:37 mail kernel: [ * *0.000000] Linux version 2.6.26-2-686
>>> (Debian 2.6.26-19lenny2) (dannf@debian.org) (gcc version 4.1.3
>>> 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Nov 4 20:45:37 UTC
>>> 2009
>>> My machine freezes every so often. *I was wodering if there is any
>>> clues in kernel.log exerpts below. *Thanks in advance
>>
>> Define "freezes". *Post the machine brand/model/specs.
>>
>>> Jan 20 21:59:37 mail kernel: [ * *0.000000] SMP: Allowing 0 CPUs, 0 hotplug CPUs
>>> Jan 20 21:59:37 mail kernel: [ * *0.000000] PERCPU: Allocating 37992
>>> bytes of per cpu data
>>> Jan 20 21:59:37 mail kernel: [ * *0.000000] NR_CPUS: 8, nr_cpu_ids: 1
>>
>> This ^^ is very odd. *"Allowing 0 CPUs" is very strange. *Given that, this
>> "NR_CPUS: 8" is even more strange.
> "NR_CPUS: 8" is not a strange thing. It's the number of CPUs that the kernel
> supports, not the CPUs existed in the machine.
>
> config NR_CPUS
> * *int "Maximum number of CPUs" if SMP && !MAXSMP
> * *range 2 8 if SMP && X86_32 && !X86_BIGSMP
> * *range 2 512 if SMP && !MAXSMP
> * *default "1" if !SMP
> * *default "4096" if MAXSMP
> * *default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
> * *default "8" if SMP
> * *---help---
> * * *This allows you to specify the maximum number of CPUs which this
> * * * kernel will support. *The maximum supported value is 512 and the
> * * *minimum value which makes sense is 2.
>
> * * * This is purely to save memory - each supported CPU adds
> * * *approximately eight kilobytes to the kernel image.
>
>>
>>> Jan 20 21:59:37 mail kernel: [ * *0.004000] Memory: 598724k/614336k
>>> available (1770k kernel code, 14940k reserved, 750k data, 244k init,
>>> 0k highmem)
>>
>> Also very strange ^^
>>
>> According to that above, your system has 0 smp cpus, but it has 8 cpus, and only
>> one of those 8 has an ID. *This also says you have ~600MB of system memory.
>> There is no physical combo of DIMMs that yields 600MB so we can assume you have
>> motherboard video chip and the BIOS is assigning system RAM for the frame
>> buffer. *But on a modern system, why do you have so little RAM installed?
>>
>> Unfortunately the system information provided by kern.log is incomplete. *Please
>> post output from dmesg so we can get a more complete picture of your system.
>> Your kern.log info alone is not enough to diagnose what is causing your system
>> to "freeze". *Something to consider is that kernel issues usually cause panics,
>> not freezes. *If your system is freezing, or "hard locking", this is usually a
>> sign of:
>>
>> 1. *A thermal issue
>> 2. *Defective hardware
>> 3. *Hardware compatibility mismatch
>>
>> For comparison to your kern.log, I have a two CPU system, each a single core CPU:
>>
>> Jan 20 01:59:42 greer kernel: found SMP MP-table at [c00f5b90] f5b90
>> Jan 20 01:59:42 greer kernel: SMP: Allowing 2 CPUs, 0 hotplug CPUs
>> Jan 20 01:59:42 greer kernel: NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1
>>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-02-2010, 01:36 AM
Stan Hoeppner
 
Default Problem with Lenny

Operating systems don't run themselves out of memory. Applications, processes,
do that. You need to identify why your application mix is consuming more memory
than is available on the system.

A couple of tips regarding virtual machines and guest operating systems:

1. If you're constantly running out of memory, use a dedicated box
2. If you're constantly running out of CPU, use a dedicated box

The entire concept behind virtualization is consolidating light-medium workloads
from many physical hosts to a single (more powerful) host, and enabling system
fault isolation--one consolidated server crashes and the rest keep running.

Roman, give this VM guest Lenny the maximum amount of memory you are allowed to
assign to a single VM, after kicking all other VMs off the hypervisor, and see
if you run out of memory. You likely will.

And it wouldn't hurt to tell us what applications/daemons/etc you're running on
this VM, since *THEY* are what's eating all the damn memory. If you want help,
we need the details.

--
Stan



Roman Gelfand put forth on 2/1/2010 11:16 AM:
> Ran out memory. This is my conclusion. Originally, I had given
> 500mb ram. Though top was showing 300mb utilization, memstat showed
> 1.1gig. It seems the later is the one I was supposed to pay attention
> to. I am currently looking into the difference between the top's
> memory utilization display and that of memstat.
>
> On Thu, Jan 21, 2010 at 9:40 PM, Jeffrey Cao <jcao.linux@gmail.com> wrote:
>> On 2010-01-21, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>>> Roman Gelfand put forth on 1/20/2010 9:26 PM:
>>>> Jan 20 21:59:37 mail kernel: [ 0.000000] Linux version 2.6.26-2-686
>>>> (Debian 2.6.26-19lenny2) (dannf@debian.org) (gcc version 4.1.3
>>>> 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Nov 4 20:45:37 UTC
>>>> 2009
>>>> My machine freezes every so often. I was wodering if there is any
>>>> clues in kernel.log exerpts below. Thanks in advance
>>>
>>> Define "freezes". Post the machine brand/model/specs.
>>>
>>>> Jan 20 21:59:37 mail kernel: [ 0.000000] SMP: Allowing 0 CPUs, 0 hotplug CPUs
>>>> Jan 20 21:59:37 mail kernel: [ 0.000000] PERCPU: Allocating 37992
>>>> bytes of per cpu data
>>>> Jan 20 21:59:37 mail kernel: [ 0.000000] NR_CPUS: 8, nr_cpu_ids: 1
>>>
>>> This ^^ is very odd. "Allowing 0 CPUs" is very strange. Given that, this
>>> "NR_CPUS: 8" is even more strange.
>> "NR_CPUS: 8" is not a strange thing. It's the number of CPUs that the kernel
>> supports, not the CPUs existed in the machine.
>>
>> config NR_CPUS
>> int "Maximum number of CPUs" if SMP && !MAXSMP
>> range 2 8 if SMP && X86_32 && !X86_BIGSMP
>> range 2 512 if SMP && !MAXSMP
>> default "1" if !SMP
>> default "4096" if MAXSMP
>> default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
>> default "8" if SMP
>> ---help---
>> This allows you to specify the maximum number of CPUs which this
>> kernel will support. The maximum supported value is 512 and the
>> minimum value which makes sense is 2.
>>
>> This is purely to save memory - each supported CPU adds
>> approximately eight kilobytes to the kernel image.
>>
>>>
>>>> Jan 20 21:59:37 mail kernel: [ 0.004000] Memory: 598724k/614336k
>>>> available (1770k kernel code, 14940k reserved, 750k data, 244k init,
>>>> 0k highmem)
>>>
>>> Also very strange ^^
>>>
>>> According to that above, your system has 0 smp cpus, but it has 8 cpus, and only
>>> one of those 8 has an ID. This also says you have ~600MB of system memory.
>>> There is no physical combo of DIMMs that yields 600MB so we can assume you have
>>> motherboard video chip and the BIOS is assigning system RAM for the frame
>>> buffer. But on a modern system, why do you have so little RAM installed?
>>>
>>> Unfortunately the system information provided by kern.log is incomplete. Please
>>> post output from dmesg so we can get a more complete picture of your system.
>>> Your kern.log info alone is not enough to diagnose what is causing your system
>>> to "freeze". Something to consider is that kernel issues usually cause panics,
>>> not freezes. If your system is freezing, or "hard locking", this is usually a
>>> sign of:
>>>
>>> 1. A thermal issue
>>> 2. Defective hardware
>>> 3. Hardware compatibility mismatch
>>>
>>> For comparison to your kern.log, I have a two CPU system, each a single core CPU:
>>>
>>> Jan 20 01:59:42 greer kernel: found SMP MP-table at [c00f5b90] f5b90
>>> Jan 20 01:59:42 greer kernel: SMP: Allowing 2 CPUs, 0 hotplug CPUs
>>> Jan 20 01:59:42 greer kernel: NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1
>>>
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>>
>>
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-02-2010, 04:48 AM
Roman Gelfand
 
Default Problem with Lenny

I use this the virtual machine as mail gateway. I run postfix,
sqlgrey, opendkim, senderid milter, dspam, grossd, policyd-weight.

I gave this machine 2gig of memory. So far, so good. I have already
used it for couple of weeks and no issues.

On Mon, Feb 1, 2010 at 9:36 PM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
> Operating systems don't run themselves out of memory. *Applications, processes,
> do that. *You need to identify why your application mix is consuming more memory
> than is available on the system.
>
> A couple of tips regarding virtual machines and guest operating systems:
>
> 1. *If you're constantly running out of memory, use a dedicated box
> 2. *If you're constantly running out of CPU, use a dedicated box
>
> The entire concept behind virtualization is consolidating light-medium workloads
> from many physical hosts to a single (more powerful) host, and enabling system
> fault isolation--one consolidated server crashes and the rest keep running.
>
> Roman, give this VM guest Lenny the maximum amount of memory you are allowed to
> assign to a single VM, after kicking all other VMs off the hypervisor, and see
> if you run out of memory. *You likely will.
>
> And it wouldn't hurt to tell us what applications/daemons/etc you're running on
> this VM, since *THEY* are what's eating all the damn memory. *If you want help,
> we need the details.
>
> --
> Stan
>
>
>
> Roman Gelfand put forth on 2/1/2010 11:16 AM:
>> Ran out memory. *This is my conclusion. *Originally, I had given
>> 500mb ram. * Though top was showing 300mb utilization, memstat showed
>> 1.1gig. *It seems the later is the one I was supposed to pay attention
>> to. * I am currently looking into the difference between the top's
>> memory utilization display and that of memstat.
>>
>> On Thu, Jan 21, 2010 at 9:40 PM, Jeffrey Cao <jcao.linux@gmail.com> wrote:
>>> On 2010-01-21, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>>>> Roman Gelfand put forth on 1/20/2010 9:26 PM:
>>>>> Jan 20 21:59:37 mail kernel: [ * *0.000000] Linux version 2.6.26-2-686
>>>>> (Debian 2.6.26-19lenny2) (dannf@debian.org) (gcc version 4.1.3
>>>>> 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Nov 4 20:45:37 UTC
>>>>> 2009
>>>>> My machine freezes every so often. *I was wodering if there is any
>>>>> clues in kernel.log exerpts below. *Thanks in advance
>>>>
>>>> Define "freezes". *Post the machine brand/model/specs.
>>>>
>>>>> Jan 20 21:59:37 mail kernel: [ * *0.000000] SMP: Allowing 0 CPUs, 0 hotplug CPUs
>>>>> Jan 20 21:59:37 mail kernel: [ * *0.000000] PERCPU: Allocating 37992
>>>>> bytes of per cpu data
>>>>> Jan 20 21:59:37 mail kernel: [ * *0.000000] NR_CPUS: 8, nr_cpu_ids: 1
>>>>
>>>> This ^^ is very odd. *"Allowing 0 CPUs" is very strange. *Given that, this
>>>> "NR_CPUS: 8" is even more strange.
>>> "NR_CPUS: 8" is not a strange thing. It's the number of CPUs that the kernel
>>> supports, not the CPUs existed in the machine.
>>>
>>> config NR_CPUS
>>> * *int "Maximum number of CPUs" if SMP && !MAXSMP
>>> * *range 2 8 if SMP && X86_32 && !X86_BIGSMP
>>> * *range 2 512 if SMP && !MAXSMP
>>> * *default "1" if !SMP
>>> * *default "4096" if MAXSMP
>>> * *default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
>>> * *default "8" if SMP
>>> * *---help---
>>> * * *This allows you to specify the maximum number of CPUs which this
>>> * * * kernel will support. *The maximum supported value is 512 and the
>>> * * *minimum value which makes sense is 2.
>>>
>>> * * * This is purely to save memory - each supported CPU adds
>>> * * *approximately eight kilobytes to the kernel image.
>>>
>>>>
>>>>> Jan 20 21:59:37 mail kernel: [ * *0.004000] Memory: 598724k/614336k
>>>>> available (1770k kernel code, 14940k reserved, 750k data, 244k init,
>>>>> 0k highmem)
>>>>
>>>> Also very strange ^^
>>>>
>>>> According to that above, your system has 0 smp cpus, but it has 8 cpus, and only
>>>> one of those 8 has an ID. *This also says you have ~600MB of system memory.
>>>> There is no physical combo of DIMMs that yields 600MB so we can assume you have
>>>> motherboard video chip and the BIOS is assigning system RAM for the frame
>>>> buffer. *But on a modern system, why do you have so little RAM installed?
>>>>
>>>> Unfortunately the system information provided by kern.log is incomplete. *Please
>>>> post output from dmesg so we can get a more complete picture of your system.
>>>> Your kern.log info alone is not enough to diagnose what is causing your system
>>>> to "freeze". *Something to consider is that kernel issues usually cause panics,
>>>> not freezes. *If your system is freezing, or "hard locking", this is usually a
>>>> sign of:
>>>>
>>>> 1. *A thermal issue
>>>> 2. *Defective hardware
>>>> 3. *Hardware compatibility mismatch
>>>>
>>>> For comparison to your kern.log, I have a two CPU system, each a single core CPU:
>>>>
>>>> Jan 20 01:59:42 greer kernel: found SMP MP-table at [c00f5b90] f5b90
>>>> Jan 20 01:59:42 greer kernel: SMP: Allowing 2 CPUs, 0 hotplug CPUs
>>>> Jan 20 01:59:42 greer kernel: NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1
>>>>
>>>
>>>
>>> --
>>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>>>
>>>
>>
>>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-02-2010, 09:13 AM
Stan Hoeppner
 
Default Problem with Lenny

Roman Gelfand put forth on 2/1/2010 11:48 PM:
> I use this the virtual machine as mail gateway. I run postfix,
> sqlgrey, opendkim, senderid milter, dspam, grossd, policyd-weight.
>
> I gave this machine 2gig of memory. So far, so good. I have already
> used it for couple of weeks and no issues.

Is this the same VM you mentioned below that ran out of memory when you gave it
500MB?

On my Lenny MX (which used to be only a postfix firewall/gateway but now stores
mail locally) I run postfix+postgrey with some pretty large regexp and cidr
tables (12,000+ cidr entries), dovecot, lighttpd, roundcube, samba, and
pdns_recursor. This is a bare metal Debian system with only 384MB of RAM, of
which over 200MB is normally system cache. It currently has over 100MB free
memory. Granted, this is a very low volume box. That said...

You must have one helluva mail stream going through that system to exceed 500MB
of memory and have to kick it up to 2GB.

--
Stan


> On Mon, Feb 1, 2010 at 9:36 PM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>> Operating systems don't run themselves out of memory. Applications, processes,
>> do that. You need to identify why your application mix is consuming more memory
>> than is available on the system.
>>
>> A couple of tips regarding virtual machines and guest operating systems:
>>
>> 1. If you're constantly running out of memory, use a dedicated box
>> 2. If you're constantly running out of CPU, use a dedicated box
>>
>> The entire concept behind virtualization is consolidating light-medium workloads
>> from many physical hosts to a single (more powerful) host, and enabling system
>> fault isolation--one consolidated server crashes and the rest keep running.
>>
>> Roman, give this VM guest Lenny the maximum amount of memory you are allowed to
>> assign to a single VM, after kicking all other VMs off the hypervisor, and see
>> if you run out of memory. You likely will.
>>
>> And it wouldn't hurt to tell us what applications/daemons/etc you're running on
>> this VM, since *THEY* are what's eating all the damn memory. If you want help,
>> we need the details.
>>
>> --
>> Stan
>>
>>
>>
>> Roman Gelfand put forth on 2/1/2010 11:16 AM:
>>> Ran out memory. This is my conclusion. Originally, I had given
>>> 500mb ram. Though top was showing 300mb utilization, memstat showed
>>> 1.1gig. It seems the later is the one I was supposed to pay attention
>>> to. I am currently looking into the difference between the top's
>>> memory utilization display and that of memstat.
>>>
>>> On Thu, Jan 21, 2010 at 9:40 PM, Jeffrey Cao <jcao.linux@gmail.com> wrote:
>>>> On 2010-01-21, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>>>>> Roman Gelfand put forth on 1/20/2010 9:26 PM:
>>>>>> Jan 20 21:59:37 mail kernel: [ 0.000000] Linux version 2.6.26-2-686
>>>>>> (Debian 2.6.26-19lenny2) (dannf@debian.org) (gcc version 4.1.3
>>>>>> 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Nov 4 20:45:37 UTC
>>>>>> 2009
>>>>>> My machine freezes every so often. I was wodering if there is any
>>>>>> clues in kernel.log exerpts below. Thanks in advance
>>>>>
>>>>> Define "freezes". Post the machine brand/model/specs.
>>>>>
>>>>>> Jan 20 21:59:37 mail kernel: [ 0.000000] SMP: Allowing 0 CPUs, 0 hotplug CPUs
>>>>>> Jan 20 21:59:37 mail kernel: [ 0.000000] PERCPU: Allocating 37992
>>>>>> bytes of per cpu data
>>>>>> Jan 20 21:59:37 mail kernel: [ 0.000000] NR_CPUS: 8, nr_cpu_ids: 1
>>>>>
>>>>> This ^^ is very odd. "Allowing 0 CPUs" is very strange. Given that, this
>>>>> "NR_CPUS: 8" is even more strange.
>>>> "NR_CPUS: 8" is not a strange thing. It's the number of CPUs that the kernel
>>>> supports, not the CPUs existed in the machine.
>>>>
>>>> config NR_CPUS
>>>> int "Maximum number of CPUs" if SMP && !MAXSMP
>>>> range 2 8 if SMP && X86_32 && !X86_BIGSMP
>>>> range 2 512 if SMP && !MAXSMP
>>>> default "1" if !SMP
>>>> default "4096" if MAXSMP
>>>> default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
>>>> default "8" if SMP
>>>> ---help---
>>>> This allows you to specify the maximum number of CPUs which this
>>>> kernel will support. The maximum supported value is 512 and the
>>>> minimum value which makes sense is 2.
>>>>
>>>> This is purely to save memory - each supported CPU adds
>>>> approximately eight kilobytes to the kernel image.
>>>>
>>>>>
>>>>>> Jan 20 21:59:37 mail kernel: [ 0.004000] Memory: 598724k/614336k
>>>>>> available (1770k kernel code, 14940k reserved, 750k data, 244k init,
>>>>>> 0k highmem)
>>>>>
>>>>> Also very strange ^^
>>>>>
>>>>> According to that above, your system has 0 smp cpus, but it has 8 cpus, and only
>>>>> one of those 8 has an ID. This also says you have ~600MB of system memory.
>>>>> There is no physical combo of DIMMs that yields 600MB so we can assume you have
>>>>> motherboard video chip and the BIOS is assigning system RAM for the frame
>>>>> buffer. But on a modern system, why do you have so little RAM installed?
>>>>>
>>>>> Unfortunately the system information provided by kern.log is incomplete. Please
>>>>> post output from dmesg so we can get a more complete picture of your system.
>>>>> Your kern.log info alone is not enough to diagnose what is causing your system
>>>>> to "freeze". Something to consider is that kernel issues usually cause panics,
>>>>> not freezes. If your system is freezing, or "hard locking", this is usually a
>>>>> sign of:
>>>>>
>>>>> 1. A thermal issue
>>>>> 2. Defective hardware
>>>>> 3. Hardware compatibility mismatch
>>>>>
>>>>> For comparison to your kern.log, I have a two CPU system, each a single core CPU:
>>>>>
>>>>> Jan 20 01:59:42 greer kernel: found SMP MP-table at [c00f5b90] f5b90
>>>>> Jan 20 01:59:42 greer kernel: SMP: Allowing 2 CPUs, 0 hotplug CPUs
>>>>> Jan 20 01:59:42 greer kernel: NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1
>>>>>
>>>>
>>>>
>>>> --
>>>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>>>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>>>>
>>>>
>>>
>>>
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>>
>>
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-02-2010, 02:48 PM
Roman Gelfand
 
Default Problem with Lenny

A lot of spam attempts.

On Tue, Feb 2, 2010 at 5:13 AM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
> Roman Gelfand put forth on 2/1/2010 11:48 PM:
>> I use this the virtual machine as mail gateway. *I run postfix,
>> sqlgrey, opendkim, senderid milter, dspam, grossd, policyd-weight.
>>
>> I gave this machine 2gig of memory. *So far, so good. *I have already
>> used it for couple of weeks and no issues.
>
> Is this the same VM you mentioned below that ran out of memory when you gave it
> 500MB?
>
> On my Lenny MX (which used to be only a postfix firewall/gateway but now stores
> mail locally) I run postfix+postgrey with some pretty large regexp and cidr
> tables (12,000+ cidr entries), dovecot, lighttpd, roundcube, samba, and
> pdns_recursor. *This is a bare metal Debian system with only 384MB of RAM, of
> which over 200MB is normally system cache. *It currently has over 100MB free
> memory. *Granted, this is a very low volume box. *That said...
>
> You must have one helluva mail stream going through that system to exceed 500MB
> of memory and have to kick it up to 2GB.
>
> --
> Stan
>
>
>> On Mon, Feb 1, 2010 at 9:36 PM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>>> Operating systems don't run themselves out of memory. *Applications, processes,
>>> do that. *You need to identify why your application mix is consuming more memory
>>> than is available on the system.
>>>
>>> A couple of tips regarding virtual machines and guest operating systems:
>>>
>>> 1. *If you're constantly running out of memory, use a dedicated box
>>> 2. *If you're constantly running out of CPU, use a dedicated box
>>>
>>> The entire concept behind virtualization is consolidating light-medium workloads
>>> from many physical hosts to a single (more powerful) host, and enabling system
>>> fault isolation--one consolidated server crashes and the rest keep running.
>>>
>>> Roman, give this VM guest Lenny the maximum amount of memory you are allowed to
>>> assign to a single VM, after kicking all other VMs off the hypervisor, and see
>>> if you run out of memory. *You likely will.
>>>
>>> And it wouldn't hurt to tell us what applications/daemons/etc you're running on
>>> this VM, since *THEY* are what's eating all the damn memory. *If you want help,
>>> we need the details.
>>>
>>> --
>>> Stan
>>>
>>>
>>>
>>> Roman Gelfand put forth on 2/1/2010 11:16 AM:
>>>> Ran out memory. *This is my conclusion. *Originally, I had given
>>>> 500mb ram. * Though top was showing 300mb utilization, memstat showed
>>>> 1.1gig. *It seems the later is the one I was supposed to pay attention
>>>> to. * I am currently looking into the difference between the top's
>>>> memory utilization display and that of memstat.
>>>>
>>>> On Thu, Jan 21, 2010 at 9:40 PM, Jeffrey Cao <jcao.linux@gmail.com> wrote:
>>>>> On 2010-01-21, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>>>>>> Roman Gelfand put forth on 1/20/2010 9:26 PM:
>>>>>>> Jan 20 21:59:37 mail kernel: [ * *0.000000] Linux version 2.6.26-2-686
>>>>>>> (Debian 2.6.26-19lenny2) (dannf@debian.org) (gcc version 4.1.3
>>>>>>> 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Nov 4 20:45:37 UTC
>>>>>>> 2009
>>>>>>> My machine freezes every so often. *I was wodering if there is any
>>>>>>> clues in kernel.log exerpts below. *Thanks in advance
>>>>>>
>>>>>> Define "freezes". *Post the machine brand/model/specs.
>>>>>>
>>>>>>> Jan 20 21:59:37 mail kernel: [ * *0.000000] SMP: Allowing 0 CPUs, 0 hotplug CPUs
>>>>>>> Jan 20 21:59:37 mail kernel: [ * *0.000000] PERCPU: Allocating 37992
>>>>>>> bytes of per cpu data
>>>>>>> Jan 20 21:59:37 mail kernel: [ * *0.000000] NR_CPUS: 8, nr_cpu_ids: 1
>>>>>>
>>>>>> This ^^ is very odd. *"Allowing 0 CPUs" is very strange. *Given that, this
>>>>>> "NR_CPUS: 8" is even more strange.
>>>>> "NR_CPUS: 8" is not a strange thing. It's the number of CPUs that the kernel
>>>>> supports, not the CPUs existed in the machine.
>>>>>
>>>>> config NR_CPUS
>>>>> * *int "Maximum number of CPUs" if SMP && !MAXSMP
>>>>> * *range 2 8 if SMP && X86_32 && !X86_BIGSMP
>>>>> * *range 2 512 if SMP && !MAXSMP
>>>>> * *default "1" if !SMP
>>>>> * *default "4096" if MAXSMP
>>>>> * *default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
>>>>> * *default "8" if SMP
>>>>> * *---help---
>>>>> * * *This allows you to specify the maximum number of CPUs which this
>>>>> * * * kernel will support. *The maximum supported value is 512 and the
>>>>> * * *minimum value which makes sense is 2.
>>>>>
>>>>> * * * This is purely to save memory - each supported CPU adds
>>>>> * * *approximately eight kilobytes to the kernel image.
>>>>>
>>>>>>
>>>>>>> Jan 20 21:59:37 mail kernel: [ * *0.004000] Memory: 598724k/614336k
>>>>>>> available (1770k kernel code, 14940k reserved, 750k data, 244k init,
>>>>>>> 0k highmem)
>>>>>>
>>>>>> Also very strange ^^
>>>>>>
>>>>>> According to that above, your system has 0 smp cpus, but it has 8 cpus, and only
>>>>>> one of those 8 has an ID. *This also says you have ~600MB of system memory.
>>>>>> There is no physical combo of DIMMs that yields 600MB so we can assume you have
>>>>>> motherboard video chip and the BIOS is assigning system RAM for the frame
>>>>>> buffer. *But on a modern system, why do you have so little RAM installed?
>>>>>>
>>>>>> Unfortunately the system information provided by kern.log is incomplete. *Please
>>>>>> post output from dmesg so we can get a more complete picture of your system.
>>>>>> Your kern.log info alone is not enough to diagnose what is causing your system
>>>>>> to "freeze". *Something to consider is that kernel issues usually cause panics,
>>>>>> not freezes. *If your system is freezing, or "hard locking", this is usually a
>>>>>> sign of:
>>>>>>
>>>>>> 1. *A thermal issue
>>>>>> 2. *Defective hardware
>>>>>> 3. *Hardware compatibility mismatch
>>>>>>
>>>>>> For comparison to your kern.log, I have a two CPU system, each a single core CPU:
>>>>>>
>>>>>> Jan 20 01:59:42 greer kernel: found SMP MP-table at [c00f5b90] f5b90
>>>>>> Jan 20 01:59:42 greer kernel: SMP: Allowing 2 CPUs, 0 hotplug CPUs
>>>>>> Jan 20 01:59:42 greer kernel: NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>>>>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>>>
>>>
>>
>>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-02-2010, 11:21 PM
Stan Hoeppner
 
Default Problem with Lenny

Roman Gelfand put forth on 2/2/2010 9:48 AM:
> A lot of spam attempts.

Post your process list. You're probably (unnecessarily) running out of memory
due to too many processes. Try setting "default_process_limit = 30" in
/etc/postfix/main.cf, reload postfix, and see if this helps the memory use
problem. It should have an impact.

You may also want to look into optimizing your policy daemons' memory footprint.

--
Stan


> On Tue, Feb 2, 2010 at 5:13 AM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>> Roman Gelfand put forth on 2/1/2010 11:48 PM:
>>> I use this the virtual machine as mail gateway. I run postfix,
>>> sqlgrey, opendkim, senderid milter, dspam, grossd, policyd-weight.
>>>
>>> I gave this machine 2gig of memory. So far, so good. I have already
>>> used it for couple of weeks and no issues.
>>
>> Is this the same VM you mentioned below that ran out of memory when you gave it
>> 500MB?
>>
>> On my Lenny MX (which used to be only a postfix firewall/gateway but now stores
>> mail locally) I run postfix+postgrey with some pretty large regexp and cidr
>> tables (12,000+ cidr entries), dovecot, lighttpd, roundcube, samba, and
>> pdns_recursor. This is a bare metal Debian system with only 384MB of RAM, of
>> which over 200MB is normally system cache. It currently has over 100MB free
>> memory. Granted, this is a very low volume box. That said...
>>
>> You must have one helluva mail stream going through that system to exceed 500MB
>> of memory and have to kick it up to 2GB.
>>
>> --
>> Stan
>>
>>
>>> On Mon, Feb 1, 2010 at 9:36 PM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>>>> Operating systems don't run themselves out of memory. Applications, processes,
>>>> do that. You need to identify why your application mix is consuming more memory
>>>> than is available on the system.
>>>>
>>>> A couple of tips regarding virtual machines and guest operating systems:
>>>>
>>>> 1. If you're constantly running out of memory, use a dedicated box
>>>> 2. If you're constantly running out of CPU, use a dedicated box
>>>>
>>>> The entire concept behind virtualization is consolidating light-medium workloads
>>>> from many physical hosts to a single (more powerful) host, and enabling system
>>>> fault isolation--one consolidated server crashes and the rest keep running.
>>>>
>>>> Roman, give this VM guest Lenny the maximum amount of memory you are allowed to
>>>> assign to a single VM, after kicking all other VMs off the hypervisor, and see
>>>> if you run out of memory. You likely will.
>>>>
>>>> And it wouldn't hurt to tell us what applications/daemons/etc you're running on
>>>> this VM, since *THEY* are what's eating all the damn memory. If you want help,
>>>> we need the details.
>>>>
>>>> --
>>>> Stan
>>>>
>>>>
>>>>
>>>> Roman Gelfand put forth on 2/1/2010 11:16 AM:
>>>>> Ran out memory. This is my conclusion. Originally, I had given
>>>>> 500mb ram. Though top was showing 300mb utilization, memstat showed
>>>>> 1.1gig. It seems the later is the one I was supposed to pay attention
>>>>> to. I am currently looking into the difference between the top's
>>>>> memory utilization display and that of memstat.
>>>>>
>>>>> On Thu, Jan 21, 2010 at 9:40 PM, Jeffrey Cao <jcao.linux@gmail.com> wrote:
>>>>>> On 2010-01-21, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>>>>>>> Roman Gelfand put forth on 1/20/2010 9:26 PM:
>>>>>>>> Jan 20 21:59:37 mail kernel: [ 0.000000] Linux version 2.6.26-2-686
>>>>>>>> (Debian 2.6.26-19lenny2) (dannf@debian.org) (gcc version 4.1.3
>>>>>>>> 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Nov 4 20:45:37 UTC
>>>>>>>> 2009
>>>>>>>> My machine freezes every so often. I was wodering if there is any
>>>>>>>> clues in kernel.log exerpts below. Thanks in advance
>>>>>>>
>>>>>>> Define "freezes". Post the machine brand/model/specs.
>>>>>>>
>>>>>>>> Jan 20 21:59:37 mail kernel: [ 0.000000] SMP: Allowing 0 CPUs, 0 hotplug CPUs
>>>>>>>> Jan 20 21:59:37 mail kernel: [ 0.000000] PERCPU: Allocating 37992
>>>>>>>> bytes of per cpu data
>>>>>>>> Jan 20 21:59:37 mail kernel: [ 0.000000] NR_CPUS: 8, nr_cpu_ids: 1
>>>>>>>
>>>>>>> This ^^ is very odd. "Allowing 0 CPUs" is very strange. Given that, this
>>>>>>> "NR_CPUS: 8" is even more strange.
>>>>>> "NR_CPUS: 8" is not a strange thing. It's the number of CPUs that the kernel
>>>>>> supports, not the CPUs existed in the machine.
>>>>>>
>>>>>> config NR_CPUS
>>>>>> int "Maximum number of CPUs" if SMP && !MAXSMP
>>>>>> range 2 8 if SMP && X86_32 && !X86_BIGSMP
>>>>>> range 2 512 if SMP && !MAXSMP
>>>>>> default "1" if !SMP
>>>>>> default "4096" if MAXSMP
>>>>>> default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
>>>>>> default "8" if SMP
>>>>>> ---help---
>>>>>> This allows you to specify the maximum number of CPUs which this
>>>>>> kernel will support. The maximum supported value is 512 and the
>>>>>> minimum value which makes sense is 2.
>>>>>>
>>>>>> This is purely to save memory - each supported CPU adds
>>>>>> approximately eight kilobytes to the kernel image.
>>>>>>
>>>>>>>
>>>>>>>> Jan 20 21:59:37 mail kernel: [ 0.004000] Memory: 598724k/614336k
>>>>>>>> available (1770k kernel code, 14940k reserved, 750k data, 244k init,
>>>>>>>> 0k highmem)
>>>>>>>
>>>>>>> Also very strange ^^
>>>>>>>
>>>>>>> According to that above, your system has 0 smp cpus, but it has 8 cpus, and only
>>>>>>> one of those 8 has an ID. This also says you have ~600MB of system memory.
>>>>>>> There is no physical combo of DIMMs that yields 600MB so we can assume you have
>>>>>>> motherboard video chip and the BIOS is assigning system RAM for the frame
>>>>>>> buffer. But on a modern system, why do you have so little RAM installed?
>>>>>>>
>>>>>>> Unfortunately the system information provided by kern.log is incomplete. Please
>>>>>>> post output from dmesg so we can get a more complete picture of your system.
>>>>>>> Your kern.log info alone is not enough to diagnose what is causing your system
>>>>>>> to "freeze". Something to consider is that kernel issues usually cause panics,
>>>>>>> not freezes. If your system is freezing, or "hard locking", this is usually a
>>>>>>> sign of:
>>>>>>>
>>>>>>> 1. A thermal issue
>>>>>>> 2. Defective hardware
>>>>>>> 3. Hardware compatibility mismatch
>>>>>>>
>>>>>>> For comparison to your kern.log, I have a two CPU system, each a single core CPU:
>>>>>>>
>>>>>>> Jan 20 01:59:42 greer kernel: found SMP MP-table at [c00f5b90] f5b90
>>>>>>> Jan 20 01:59:42 greer kernel: SMP: Allowing 2 CPUs, 0 hotplug CPUs
>>>>>>> Jan 20 01:59:42 greer kernel: NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>>>>>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>>>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>>>>
>>>>
>>>
>>>
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>>
>>
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-02-2010, 11:54 PM
Celejar
 
Default Problem with Lenny

On Tue, 2 Feb 2010 10:48:47 -0500
Roman Gelfand <rgelfand2@gmail.com> wrote:

> A lot of spam attempts.

1) Do not top post
2) Trim your replies

Celejar
--
foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 06:50 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org