From owner-freebsd-stable@FreeBSD.ORG Tue Jun 27 13:11:56 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2889316A528 for ; Tue, 27 Jun 2006 13:11:56 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp106.rog.mail.re2.yahoo.com (smtp106.rog.mail.re2.yahoo.com [68.142.225.204]) by mx1.FreeBSD.org (Postfix) with SMTP id 5580C43DA3 for ; Tue, 27 Jun 2006 13:11:39 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 691 invoked from network); 27 Jun 2006 13:11:39 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=mgTaxi6R2q14t16hMI8e9Sby1LOQgUlBJPh8Pk/oQ3vDiXYk7rgoWYUh5WviagfSdPoKnafMsXM83deDofi9GRi6PpCYECJ6O5j3lK8RYlSaNkZsdr65w4ye6WerLQP8mWWkwJdINcOug20dPVX+H9bU66JVSPI71vBlYml8ZyM= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp106.rog.mail.re2.yahoo.com with SMTP; 27 Jun 2006 13:11:39 -0000 Message-ID: <44A12E8D.3040002@rogers.com> Date: Tue, 27 Jun 2006 09:11:41 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: stable@freebsd.org References: <4486F6D8.7050002@rogers.com> In-Reply-To: <4486F6D8.7050002@rogers.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: ad4: FAILURE - out of memory in start X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jun 2006 13:11:56 -0000 Mike Jakubik wrote: > Today i noticed this in the log of one of my systems. Does any one > know what this means? The system has been up for over a month with no > problems. > > --- > Copyright (c) 1992-2006 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 6.1-RELEASE #0: Tue May 9 12:48:42 EDT 2006 > root@mail.xxx.com:/usr/obj/usr/src/sys/SPAMTOASTER > ACPI APIC Table: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Pentium(R) D CPU 2.80GHz (2793.02-MHz K8-class CPU) > Origin = "GenuineIntel" Id = 0xf62 Stepping = 2 > > Features=0xbfebfbff > > Features2=0xe43d,> > AMD Features=0x20100800 > AMD Features2=0x1 > Cores per package: 2 > real memory = 535691264 (510 MB) > avail memory = 510005248 (486 MB) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > cpu0: on acpi0 > acpi_throttle0: on cpu0 > cpu1: on acpi0 > acpi_throttle1: on cpu1 > acpi_throttle1: failed to attach P_CNT > device_attach: acpi_throttle1 attach returned 6 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: irq 16 at device 1.0 on pci0 > pci1: on pcib1 > pcib2: irq 17 at device 28.0 on pci0 > pci2: on pcib2 > pcib3: at device 0.0 on pci2 > pci3: on pcib3 > pci2: at device 0.1 (no driver > attached) > pcib4: irq 17 at device 28.4 on pci0 > pci4: on pcib4 > em0: port > 0x4000-0x401f mem 0xed200000-0xed21ffff irq 16 at device 0.0 on pci4 > em0: Ethernet address: 00:30:48:55:c0:da > pcib5: irq 16 at device 28.5 on pci0 > pci5: on pcib5 > em1: port > 0x5000-0x501f mem 0xed300000-0xed31ffff irq 17 at device 0.0 on pci5 > em1: Ethernet address: 00:30:48:55:c0:db > pcib6: at device 30.0 on pci0 > pci10: on pcib6 > pci10: at device 0.0 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port > 0x3040-0x3047,0x3034-0x3037,0x3038-0x303f,0x3030-0x3033,0x3020-0x302f > mem 0xed000000-0xed0003ff irq 19 at device 31.2 on pci0 > ata2: on atapci0 > ata3: on atapci0 > ata4: on atapci0 > ata5: on atapci0 > pci0: at device 31.3 (no driver attached) > acpi_button0: on acpi0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > orm0: at iomem 0xc0000-0xc7fff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounters tick every 1.000 msec > ad4: 76319MB at ata2-master SATA300 > ad6: 76319MB at ata3-master SATA300 > SMP: AP CPU #1 Launched! > GEOM_MIRROR: Device gm created (id=464137677). > GEOM_MIRROR: Device gm: provider ad4 detected. > GEOM_MIRROR: Device gm: provider ad6 detected. > GEOM_MIRROR: Device gm: provider ad6 activated. > GEOM_MIRROR: Device gm: provider ad4 activated. > GEOM_MIRROR: Device gm: provider mirror/gm launched. > Trying to mount root from ufs:/dev/mirror/gms1a > em0: link state changed to UP > ad4: FAILURE - out of memory in start After another ~month of uptime i am now receiving the same message on ad6. Does anyone have an idea what this means? Perhaps is should file a PR... Jun 26 21:58:49 mail kernel: ad6: FAILURE - out of memory in start