From owner-freebsd-current@FreeBSD.ORG Wed Oct 1 08:43:53 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C114916A4B3 for ; Wed, 1 Oct 2003 08:43:53 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F22443FF5 for ; Wed, 1 Oct 2003 08:43:52 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9p2/8.12.9) with ESMTP id h91Fgc7R015316; Wed, 1 Oct 2003 11:42:38 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h91FgYO0015313; Wed, 1 Oct 2003 11:42:38 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 1 Oct 2003 11:42:34 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Gerhard Schmidt In-Reply-To: <20031001060256.GA84164@augusta.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Harddiskproblems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2003 15:43:53 -0000 On Wed, 1 Oct 2003, Gerhard Schmidt wrote: > since 3 weeks i've problems with my 5.1-CURRENT Box. When i try to > delete very large direktories (for examplte the builddir of a make > release) the box Panics. > > panic: kmem_malloc(4096): kmem_map to small: 275251200 total allocated > cpuid=0: lapic.id = 00000000 > boot() called on cpu#0 > > The Box hangs after that. no automatic reboot. And presumably no backtrace/dump possible? If you're not using a serial console, you might want to try it and see if you get more reliable access to the debugger. The panic message means that the kernel ran out of address space for kernel memory allocation, which is typically a sign of one of two things: (1) a kernel memory leak, or (2) lack of an allocation/resource bound for some type of allocation, or alternatively, a scaling factor for the resource bound that permits too much allocation (perhaps scaled to physical memory). It would be interesting, if this is pretty reproduceable, to see the output of a series of calls to vmstat -m and vmstat -z leading up to the panic, to see if we can track down what is getting allocated "too much". To work around the problem, you can increase the amount of address space allocated to kernel memory, or you might try reducing the amount of memory in the machine and see if that fixes the scaling factor. Getting a dump of the kernel in its toasted state would be highly desirable, as it's possible to run vmstat on the kernel dump to see what state memory allocation is in. Using a serial console might let you get further into the debugger... > > Regards > estartu > > ---- Bootmsg ---- > > Copyright (c) 1992-2003 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 5.1-CURRENT #1: Tue Sep 30 13:23:39 CEST 2003 > root@sol.ze.tu-muenchen.de:/usr/src/sys/i386/compile/SOL > Preloaded elf kernel "/boot/kernel/kernel" at 0xc04f8000. > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04f826c. > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2399.33-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 > Features=0xbfebfbff > Hyperthreading: 2 logical CPUs > real memory = 4160684032 (3967 MB) > avail memory = 4048343040 (3860 MB) > Programming 24 pins in IOAPIC #0 > IOAPIC #0 intpin 2 -> irq 0 > Programming 24 pins in IOAPIC #1 > Programming 24 pins in IOAPIC #2 > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee00000 > cpu1 (AP): apic id: 1, version: 0x00050014, at 0xfee00000 > cpu2 (AP): apic id: 6, version: 0x00050014, at 0xfee00000 > cpu3 (AP): apic id: 7, version: 0x00050014, at 0xfee00000 > io0 (APIC): apic id: 8, version: 0x00178020, at 0xfec00000 > io1 (APIC): apic id: 9, version: 0x00178020, at 0xfec80000 > io2 (APIC): apic id: 10, version: 0x00178020, at 0xfec80400 > Pentium Pro MTRR support enabled > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > pcibios: BIOS version 2.10 > Using $PIR table, 14 entries at 0xc00f2fb0 > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > acpi_cpu0: on acpi0 > acpi_cpu1: on acpi0 > acpi_cpu2: on acpi0 > acpi_cpu3: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > IOAPIC #0 intpin 16 -> irq 2 > IOAPIC #0 intpin 18 -> irq 9 > IOAPIC #0 intpin 17 -> irq 10 > pcib1: at device 2.0 on pci0 > pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P2 - AE_NOT_FOUND > pci2: on pcib1 > pci2: at device 28.0 (no driver attached) > pcib2: at device 29.0 on pci2 > pci4: on pcib2 > IOAPIC #2 intpin 0 -> irq 11 > em0: port 0xd800-0xd83f mem 0xfe9e0000-0xfe9fffff irq 11 at device 1.0 on pci4 > em0: Speed:N/A Duplex:N/A > pci2: at device 30.0 (no driver attached) > pcib3: at device 31.0 on pci2 > pci3: on pcib3 > IOAPIC #1 intpin 4 -> irq 16 > twe0: <3ware Storage Controller> port 0xc800-0xc80f mem 0xfe000000-0xfe7fffff,0xfe8ffc00-0xfe8ffc0f irq 16 at device 6.0 on pci3 > twe0: 8 ports, Firmware FE7S 1.05.00.049, BIOS BE7X 1.08.00.046 > uhci0: port 0xe800-0xe81f irq 2 at device 29.0 on pci0 > usb0: 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 > pcib4: at device 30.0 on pci0 > pci1: on pcib4 > fxp0: port 0xb400-0xb43f mem 0xfd7a0000-0xfd7bffff,0xfd7fe000-0xfd7fefff irq 10 at device 1.0 on pci1 > fxp0: Ethernet address 00:e0:81:26:9e:56 > miibus0: on fxp0 > inphy0: on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > pci1: at device 2.0 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port 0xffa0-0xffaf,0-0x3,0-0x7,0-0x3,0-0x7 irq 9 at device 31.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata0: [MPSAFE] > ata1: at 0x170 irq 15 on atapci0 > ata1: [MPSAFE] > pci0: at device 31.3 (no driver attached) > acpi_button0: on acpi0 > acpi_button1: on acpi0 > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > sio0 port 0x3f8-0x3ff irq 4 on acpi0 > sio0: type 16550A > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > ppc0 port 0x378-0x37f irq 7 on acpi0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > ppbus0: on ppc0 > ppi0: on ppbus0 > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > orm0: