From owner-freebsd-current@FreeBSD.ORG Mon Aug 11 09:06:53 2003 Return-Path: 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 73B4E37B40B for ; Mon, 11 Aug 2003 09:06:53 -0700 (PDT) Received: from skyweb.ca (smtp-1.vancouver.ipapp.com [216.152.192.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42C9343F3F for ; Mon, 11 Aug 2003 09:06:52 -0700 (PDT) (envelope-from mjohnston@skyweb.ca) Received: from mjohnston ([209.5.243.50]) by smtp-1.vancouver.ipapp.com ; Mon, 11 Aug 2003 09:06:48 -0700 From: "Mark Johnston" To: "'Bosko Milekic'" Date: Mon, 11 Aug 2003 11:12:36 -0500 Message-ID: <010801c36023$6198c6b0$be0fa8c0@MJOHNSTON> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 In-Reply-To: <20030811100549.GA33392@technokratis.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Country: CA cc: current@freebsd.org Subject: Re: 5.1, Data Corruption, Intel, Oh my! [patch] - Fatal trap 12 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2003 16:06:53 -0000 Bosko Milekic wrote: > The information I'd like to see, if possible (private mail is OK): > > 1) Your hardware, UP or SMP. UP - the hardware is an IBM Thinkpad A31 with a Pentium 4 "M" chip. ACPI is disabled. > 2) Whether you have PAE turned on. PAE is not enabled. > 3) If you had the data corruption problem, does the patch solve it? > Please make sure you do NOT include the DISABLE_PSE and > DISABLE_PG_G options when you test for this, as they should no > longer be needed. I didn't notice data corruption, but I haven't heavily stressed this laptop at all. I applied this patch to Friday's CURRENT, stock except for Soeren's ATAng patch. The result is a crash very early in the boot. I've transcribed the message below as accurately as possible, but there may be typos. Good dmesg/kernel config files can be had at http://www.skyweb.ca/~mark/. Using $PIR table, 14 entries at 0xc00fdeb0 apm0: on motherboard kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc059a773 stack pointer = 0x10:0xc0c219e2 frame pointer = 0x10:0xc0c21a02 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 _mtx_lock_flags+0x43: cmpl $0xc07edf8c,0(%ebx) db> trace _mtx_lock_flags(0,0,c07aa287,11e,c0c21aaa) at _mtx_lock_flags+0x43 vm_fault(c102f000,c0000000,2,0,c08205c0) at vm_fault+0x2b4 trap_pfault(c0c21b9e,0,c00004d8,100000,c00004d8) at trap_pfault+0x152 trap(6c200018,10,1bc40060,1c,0) at trap+0x30d calltrap() at calltrap+0x5 --- trap 0xc, eip = 0x5949, esp = 0xc0c21bde, dbp = 0xc0c21be4 --- (null)(1bf80058,0,530e0102,80202,505a61) at 0x5949 db> The old kernel (Friday's CURRENT plus ATAng) still boots and works fine. Please ask for any more information you need or any other steps I can take. Mark