From owner-freebsd-i386@FreeBSD.ORG Thu May 22 14:30:11 2003 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C4B237B401 for ; Thu, 22 May 2003 14:30:11 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2225643FA3 for ; Thu, 22 May 2003 14:30:10 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h4MLU9Up010139 for ; Thu, 22 May 2003 14:30:09 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h4MLU9fh010138; Thu, 22 May 2003 14:30:09 -0700 (PDT) Resent-Date: Thu, 22 May 2003 14:30:09 -0700 (PDT) Resent-Message-Id: <200305222130.h4MLU9fh010138@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-i386@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Kevin Oberman Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F1B937B401 for ; Thu, 22 May 2003 14:26:28 -0700 (PDT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADCF943F3F for ; Thu, 22 May 2003 14:26:27 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP id MUA74016 for ; Thu, 22 May 2003 14:26:26 -0700 Received: by ptavv.es.net (Tachyon Server, from userid 9381) id 3DC9D5D04; Thu, 22 May 2003 14:26:26 -0700 (PDT) Message-Id: <20030522212626.3DC9D5D04@ptavv.es.net> Date: Thu, 22 May 2003 14:26:26 -0700 (PDT) From: Kevin Oberman To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: i386/52593: Kernel panic when starting apm X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Kevin Oberman List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2003 21:30:11 -0000 >Number: 52593 >Category: i386 >Synopsis: Kernel panic when starting apm >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu May 22 14:30:09 PDT 2003 >Closed-Date: >Last-Modified: >Originator: Kevin Oberman >Release: FreeBSD 5.1-BETA i386 >Organization: ESnet >Environment: System: FreeBSD puppeteer.es.net 5.1-BETA FreeBSD 5.1-BETA #0: Thu May 22 10:07:13 PDT 2003 oberman@puppeteer.es.net:/usr/obj/usr/src/sys/IBM-T30-D i386 >Description: System panics during boot when apm is loaded. May be compiled into the kernel or loaded at boot time. The system is an IBM ThinkPad T30 with 1.8 GHz P4 with current (as of Tuesday) BIOS. System runs fine with no issues if APM is not loaded (other than lack of apm(4) capability). The system works fine with a kernel built on May 8. I first noticed the problem in a system built on May 16 (cvsup about 18:00 UTC). apm0: on motherboard Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1c fault code = supervisor write, page not present instruction pointer = 0x8:0xc0327e18 stack pointer = 0x10:0xc050d976 frame pointer = 0x10:0xc050dad2 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) kernel: type 12 trap, code=0 Stopped at vm_fault+0x268: cmpxchgl %edx,0x1c(%ecx) db> tr vm_fault(c0541000,c0000000,2,0,c0422d60) at vm_fault+0x268 trap_pfault(c050db6a,0,c00004d8,dbfc0000,c00004d8) at trap_pfault+0x1c8 trap(db8c0018,59880010,dbac0060,1c,0) at trap+0x3bd calltrap() at calltrap+0x5 --- trap 0xc, eip = 0x5812, esp = 0xc050dbaa, ebp = 0xc050ddb0 --- (null)(dbc40058,0,530e0102,80202,50592a) at 0x5812 db> This was transcribed by hand, although I have checked for typos several times, I may have missed one. Since I have not heard any similar reports (except one from a T40 owner on mobile), I suspect it is platform dependent. I am not familiar with the debugger, so I may need to add information. Finally, I don't get a dump. The system simply reboots! :-( >How-To-Repeat: Boot with apm driver >Fix: No idea at this time >Release-Note: >Audit-Trail: >Unformatted: