panic after starting X with r238120

Steve Wills swills at FreeBSD.org
Wed Jul 4 21:57:47 UTC 2012


Setting kern.ipc.shm_use_phys back to 0 (the default) fixed it. I had set it to 1 for some reason that I can't recall.

Steve

On Jul 4, 2012, at 5:41 PM, Steve Wills wrote:

> Hi,
> 
> After updating to r238120, I get a panic whenever X starts up. It works for a few seconds, then panics. The messages don't look too useful to me, but here they are:
> 
> Unread portion of the kernel message buffer:
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 3610 (kdm_greet)
> trap number             = 12
> panic: page fault
> cpuid = 0
> 
> (kgdb) bt
> #0  doadump (textdump=dwarf2_read_address: Corrupted DWARF expression.
> ) at pcpu.h:224
> #1  0xffffffff8087ef79 in kern_reboot (howto=dwarf2_read_address: Corrupted DWARF expression.
> ) at kern_shutdown.c:449
> #2  0xffffffff8087f413 in panic (fmt=dwarf2_read_address: Corrupted DWARF expression.
> ) at kern_shutdown.c:637
> #3  0xffffffff80b77d08 in trap_fatal (frame=dwarf2_read_address: Corrupted DWARF expression.
> ) at trap.c:852
> #4  0xffffffff80b78012 in trap_pfault (frame=dwarf2_read_address: Corrupted DWARF expression.
> ) at trap.c:678
> #5  0xffffffff80b777aa in trap (frame=Variable "frame" is not available.
> ) at trap.c:456
> #6  0xffffffff80b62142 in calltrap () at /tmp/exception-vH8hmc.s:179
> #7  0xffffffff80b6f6b0 in pmap_enter (pmap=dwarf2_read_address: Corrupted DWARF expression.
> ) at pmap.c:3587
> #8  0xffffffff80adafa0 in vm_fault_hold (map=dwarf2_read_address: Corrupted DWARF expression.
> ) at vm_fault.c:935
> #9  0xffffffff80ad9787 in vm_fault (map=Variable "map" is not available.
> ) at vm_fault.c:229
> #10 0xffffffff80b77f26 in trap_pfault (frame=dwarf2_read_address: Corrupted DWARF expression.
> ) at trap.c:736
> #11 0xffffffff80b77670 in trap (frame=Variable "frame" is not available.
> ) at trap.c:358
> #12 0xffffffff80b62142 in calltrap () at /tmp/exception-vH8hmc.s:179
> #13 0x00000008040d7796 in ?? ()
> Previous frame inner to this frame (corrupt stack?)
> Current language:  auto; currently minimal
> (kgdb) 
> 
> Something I saw in a previous panic made me think this was drm related, but I don't see it in this particular one.
> 
> Steve
> 
> _______________________________________________
> 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"



More information about the freebsd-current mailing list