Re: New Kernel panic

From: Roman Kurakin <rik_at_cronyx.ru>
Date: Sun, 22 Aug 2004 15:03:56 +0400
I've just seen changes in current that may solve your problem.
Please try update your sources.

rik

Roman Kurakin:

> Manfred Antar:
>
>> A current from today give this panic:
>> /boot/kernel/acpi.ko text=0x3f9c0 data=0x1bc4+0x110c 
>> syms=[0x4+0x7290+0x4+0x972f]
>> GDB: no debug ports present
>> KDB: debugger backends: ddb
>> KDB: current backend: ddb
>> Copyright (c) 1992-2004 The FreeBSD Project.
>> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>>        The Regents of the University of California. All rights reserved.
>> FreeBSD 6.0-CURRENT #0: Sat Aug 21 16:03:04 PDT 2004
>>    root_at_pozo.com:/usr/src/sys/i386/compile/DELL
>> Timecounter "i8254" frequency 1193182 Hz quality 0
>> CPU: Intel Pentium III (996.68-MHz 686-class CPU)
>>  Origin = "GenuineIntel"  Id = 0x68a  Stepping = 10
>>  Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
>> real memory  = 534736896 (509 MB)
>> 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:0xc0550b0a
>> stack pointer           = 0x10:0xc0c21b90
>> frame pointer           = 0x10:0xc0c21b90
>> code segment            = base 0x0, limit 0xfffff, type 0x1b
>>                        = DPL 0, pres 1, def32 1, gran 1
>> processor eflags        = resume, IOPL = 0
>> current process         = 0 ()
>> [thread 0]
>> Stopped at      turnstile_head+0x6:     movl    0(%eax),%eax
>> db> trace
>> turnstile_head(0,c0c21c2c,1,c0773ec0,c0c21bcc) at turnstile_head+0x6
>> _mtx_unlock_sleep(c0757f80,0,0,0) at _mtx_unlock_sleep+0x40
>> _unlock_things(c0c21c2c,1) at _unlock_things+0x218
>> vm_fault(c103a000,cbd57000,3,1,c1037e14) at vm_fault+0x1339
>> vm_fault_wire(c103a000,cbd57000,cbf1f000,0,0) at vm_fault_wire+0x30
>> vm_map_wire(c103a000,cbd57000,cbf1f000,0,be58000) at vm_map_wire+0x1d6
>> kmem_alloc(c103a000,1c8000,0,c0c21d84,0) at kmem_alloc+0x1d4
>> vm_ksubmap_init(c07882f8,c194c45c,c073e7f0,c0c21d98,c05091ea) at 
>> vm_ksubmap_init+0x66
>> cpu_startup(0,c1ec00,c1e000,0,c0437965) at cpu_startup+0xc2
>> mi_startup() at mi_startup+0x96
>> begin() at begin+0x2c
>> db>
>
> Is it persistent? I have a bit different trace, but there is big 
> probability that
> this is the same problem I have.
>
> See: "Boot code broken in some way in recent current (Was: Panic at 
> boot)"
> thread for details.
>
> rik
>
>>
>>
>>
>>
>> ==================================
>> ||      null_at_pozo.com           ||
>> ||      Ph. (415) 681-6235      ||
>> ==================================
>> _______________________________________________
>> freebsd-current_at_freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to 
>> "freebsd-current-unsubscribe_at_freebsd.org"
>>
>>
>>  
>>
>
>
>
>
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to 
> "freebsd-current-unsubscribe_at_freebsd.org"
>
>
Received on Sun Aug 22 2004 - 09:17:12 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:07 UTC