Re: 5.1, Data Corruption, Intel, Oh my! [patch] - Fatal trap 12

From: Mark Johnston <mjohnston_at_skyweb.ca>
Date: Mon, 11 Aug 2003 11:12:36 -0500
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: <APM BIOS> 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
Received on Mon Aug 11 2003 - 07:06:53 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:18 UTC