From owner-freebsd-acpi@FreeBSD.ORG Tue Feb 7 18:37:57 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F10616A420 for ; Tue, 7 Feb 2006 18:37:57 +0000 (GMT) (envelope-from duncan.fbsd@gmail.com) Received: from smtp101.sbc.mail.re2.yahoo.com (smtp101.sbc.mail.re2.yahoo.com [68.142.229.104]) by mx1.FreeBSD.org (Postfix) with SMTP id CFA1E43D7E for ; Tue, 7 Feb 2006 18:37:50 +0000 (GMT) (envelope-from duncan.fbsd@gmail.com) Received: (qmail 25136 invoked from network); 7 Feb 2006 18:37:50 -0000 Received: from unknown (HELO ?192.168.1.201?) (donaldj@ameritech.net@69.211.91.186 with plain) by smtp101.sbc.mail.re2.yahoo.com with SMTP; 7 Feb 2006 18:37:50 -0000 From: "Donald J. O'Neill" To: freebsd-acpi@freebsd.org Date: Tue, 7 Feb 2006 12:37:31 -0600 User-Agent: KMail/1.9.1 References: <43E7D1A2.1030008@o2.pl> <43E8B8CB.2060703@o2.pl> <200602071048.56326.jhb@freebsd.org> In-Reply-To: <200602071048.56326.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200602071237.31791.duncan.fbsd@gmail.com> Cc: Subject: Re: Kernel panic with ACPI enabled X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2006 18:37:57 -0000 On Tuesday 07 February 2006 09:48, John Baldwin wrote: > On Tuesday 07 February 2006 10:12, Przemys=B3aw Celej wrote: > > John Baldwin wrote: > > > On Monday 06 February 2006 17:45, Przemys=B3aw Celej wrote: > > >> Hi, > > >> > > >> Since I'm using FreeBSD 5.X and 6.X I've got seriously problem > > >> with ACPI. When I setup ACPI as module, I've got panic soon > > >> after kernel recognize processor: > > >> pmap_mapdev: Couldn't alloc kernel virtual memory > > >> > > >> *but* on GENERIC kernel ACPI works without any problems. I'm > > >> convinced that, this problem is depending on hardware (actually > > >> only on motherboard). > > >> > > >> Please help me, I need ACPI enabled. > > >> > > >> Environment: > > >> System version: FreeBSD-6.0 (but this problem steps out on > > >> FreeBSD 5.X also) Motherboard: Abit NF7-S (on nforce2 chipset) > > >> Memory: 512MB DDR (333Mhz) > > >> Hard drive: Seagate V 60GB/ATA100 > > >> Processor: AMD Athlon2500+/333Mhz > > > > > > What kernel are you using that breaks? Is it a custom kernel > > > config? > > > > Yes, here is the config (currently I'm using FreeBSD 6.0): > > http://80.50.250.246/siano/forum/SYS-acpi-as-module.txt > > > > When I compile acpi directly into the kernel, I've got panic with > > the same message as above (pmap_mapdev...). > > Unfortunately I can't do backtrace, because kernel didn't mount > > disk *before* panic, I will try to move function responsible for > > mounting root device before pmap_mapdev(). > > You can get a backtrace if you include DDB in your kernel and use > 'tr' at the db> prompt after the panic. It might be easier to > capture it if you can setup a serial console. > > Also, you probably don't want the NO_MEMORY_HOLE (only applies to K6 > CPUs, you have an Athlon (K8)), CPU_UPGRADE_HW_CACHE (only applies > to PC-98 machines in Japan), CPU_FASTER_5X86_FPU (only applies to > Cyrix 5x86 CPUs), or CPU_SUSP_HLT (only applies to Cyrix CPUs) > options. You probably don't want the CPU_ATHLON_SSE_HACK unless you > really need it as well, though it won't hurt. Also, try removing the > 'MAXMEM' option and letting the kernel figure out the mappings from > the BIOS. This might actually be the source of the panic since the > kernel might be corrupting the ACPI tables due to the MAXMEM option. > > > Sorry, if my english is terrible, but I come from Poland. > > Regards. > > It's not terrible at all. :) I have a few things. Is there a reason you have 'device apm'? Are you=20 trying to use APM and ACPI at the same time? Why do you have 'device=20 isa' rather than 'device eisa'? Where you, by any chance, just re-using=20 your conf file from 5.x? It kind of looks that way. Have you looked at=20 i386/conf/NOTES? There is some more information in there. Don