From owner-freebsd-acpi@FreeBSD.ORG Tue Feb 7 19:05:25 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 41C2F16A420 for ; Tue, 7 Feb 2006 19:05:25 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id A421B43D46 for ; Tue, 7 Feb 2006 19:05:24 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 7950969 for multiple; Tue, 07 Feb 2006 14:06:09 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k17J5AOU050024; Tue, 7 Feb 2006 14:05:10 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Donald J. O'Neill" Date: Tue, 7 Feb 2006 14:04:42 -0500 User-Agent: KMail/1.9.1 References: <43E7D1A2.1030008@o2.pl> <200602071048.56326.jhb@freebsd.org> <200602071237.31791.duncan.fbsd@gmail.com> In-Reply-To: <200602071237.31791.duncan.fbsd@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200602071404.44314.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1280/Tue Feb 7 05:11:53 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-acpi@freebsd.org 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 19:05:25 -0000 On Tuesday 07 February 2006 13:37, Donald J. O'Neill wrote: > 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 > trying to use APM and ACPI at the same time? Why do you have 'device > isa' rather than 'device eisa'? Where you, by any chance, just re-using > your conf file from 5.x? It kind of looks that way. Have you looked at > i386/conf/NOTES? There is some more information in there. device isa is normal, and he probably just commented out eisa since modern= =20 systems don't have EISA slots. The apm thing won't hurt, though it probabl= y=20 adds a small bit of bloat to the kernel. If you have both apm and acpi the= n=20 acpi will be used if it is present, otherwise if acpi is not present (or is= =20 disabled) then apm will be used. =2D-=20 John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org