From owner-freebsd-current Thu Jan 23 20:56:28 2003 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 3FC2537B401 for ; Thu, 23 Jan 2003 20:56:27 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id C19D743F5F for ; Thu, 23 Jan 2003 20:56:26 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.6/8.12.6) with ESMTP id h0O4uQXv008705; Thu, 23 Jan 2003 20:56:26 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.6/8.12.6/Submit) id h0O4uQKh008704; Thu, 23 Jan 2003 20:56:26 -0800 (PST) Date: Thu, 23 Jan 2003 20:56:26 -0800 From: Steve Kargl To: Vincent Poy Cc: current@FreeBSD.ORG Subject: Re: Options MAXMEM added to GENERIC kernel config causes kernel panic in -current Message-ID: <20030124045626.GA8647@troutmask.apl.washington.edu> References: <20030123173821.F3206-100000@oahu.WURLDLINK.NET> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030123173821.F3206-100000@oahu.WURLDLINK.NET> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jan 23, 2003 at 05:40:16PM -1000, Vincent Poy wrote: > > /boot/kernel/acpi.ko text=0x2fab4 data=-0x1a84+0x6e0 > syms=[0x4+0x5540+0x702d|] snip > embedded 0 6 A 0x60 3 4 5 6 7 9 10 11 12 14 15 > panic: pmap_mapdev: Couldn't alloc kernel virtual memory > Debugger("panic") > Stopped at Debugger+0x45: xchgl %ebx,in_Debugger.0 > db> trace > Debugger(c0435e9c) at Debugger+0x45 > panic(c0460ba0,0,0,c064cbc4,0) at panic+0x7c > pmap_mapdev(1ffd0000,0,c064cc54,c064cbd4,c060547a) at pmap_mapdev+0x5d > AcpiOsMapMemory(1ffd0000,0,0,c064cbc4,0) at AcpiOsMapMemory+0x12 > AcpiTbGetThisTable(c064cc54,c064cc08,c064cc64,c064cc54,c064cc54) at > AcpiTbGetThisTable+0xa6 > AcpiTbGetTableBody(c064cc54,c064cc08,c064cc64,0,0) at AcpiTbTableBody+0x3b > AcpiTbGetTable(c064cc54,c064cc64,c064cc54,9,1ffd0000) at AcpiTbGetTable+0x29 > AcpiTbGetTableRsdt(1,fd6e0,0,c061a520,c159ec80) at AcpiTbGetTableRsdt+0x1a > AcpiLoadTables(0,c66d8118,c061a3c8,c1586aa0,c064ccfc) at AcpiLoadTables+0x85 > acpi_identify(c061a3c8,c159ec80) at acpi_identify+0x99 > bus_generic_probe(c159ec80,c66b1090,c064cd34,c028e724,c159ec80) at > bus_generic_probe+0x54 > nexus_probe(c159ec80) at nexus_probe+0x186 > device_probe_child(c159ef00,c159ec80,c028e4e5,c15917c8,1) at > device_probe_child+0xcc > device_probe_and_attach(c159ec80) at device_probe_and_attach+0x4b > root_bus_configure(c159ef00,c045b660,0,4) at root_bus_configure+0x16 > configure(0,649c00,649000,0,c01378b5) at configure+0x22 > mi_startup() at mi_startup+0x9a > begin() at begin+0x2c > db> > Disable acpi. acpi is broken. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message