Re: LOR in yesterday CURRENT: system map vs Giant

On Sunday 07 March 2004 10:44 am, Paolo Pisati wrote:
> Just after starting X, i got this on the console:
>
> drm0: <ATI Radeon LY Mobility M6> port 0xd800-0xd8ff mem
> 0xef000000-0xef00ffff,0 xf0000000-0xf7ffffff irq 11 at device 0.0 on
> pci1
> info: [drm] AGP at 0xf8000000 64MB
> info: [drm] Initialized radeon 1.10.0 20020828 on minor 0
> drm0: [MPSAFE]
> lock order reversal
>  1st 0xc0c3b060 system map (system map) _at_
> /usr/src/sys/vm/vm_map.c:2210 2nd 0xc066db40 Giant (Giant) _at_
> /usr/src/sys/vm/vm_fault.c:1084 Stack backtrace:
> backtrace(c0621dad,c066db40,c061dc30,c061dc30,c062cd15) at
> backtrace+0x17 witness_checkorder(c066db40,9,c062cd15,43c,c062eb5e)
> at witness_checkorder+0x6f8
>
> _mtx_lock_flags(c066db40,0,c062cd15,43c,c0c39780) at
> _mtx_lock_flags+0x9d
> vm_fault_unwire(c0c3b000,d3143000,d3144000,c0c39690,d244cc24) at
> vm_fault_unwire +0x36
> vm_map_entry_unwire(c0c3b000,c0c39780,d3144000,d244cc24,c059cfe6) at
> vm_map_entr y_unwire+0x25
> vm_map_delete(c0c3b000,d3143000,d3144000,c2805580,c2ccc85c) at
> vm_map_delete+0x1 65
> vm_map_remove(c0c3b000,d3143000,d3144000,d244cc80,c05e20b0) at
> vm_map_remove+0x5 5
> kmem_free(c0c3b000,d3143000,1000,16a,1) at kmem_free+0x32
> user_ldt_free(c287d7e0,c2ccc74c,d244ccd4,c04b5ece,c287d7e0) at
> user_ldt_free+0xf 0
> cpu_exit(c287d7e0,0,c061be87,1f8,1) at cpu_exit+0x36
> exit1(c287d7e0,0,d244cd40,c05e3660,c287d7e0) at exit1+0x116e
> sys_exit(c287d7e0,d244cd14,4,7,1) at sys_exit+0x1d
> syscall(2f,2f,2f,bfbfed1c,bfbfed24) at syscall+0x2a0
> Xint0x80_syscall() at Xint0x80_syscall+0x1d
> --- syscall (1), eip = 0x287ca89b, esp = 0xbfbfec8c, ebp = 0xbfbfecf4
> ---
>
> I wish it helps...

This particular one was my fault, I believe it's been fixed.  However, I 
also believe this particular LOR happens via other code paths that were 
not my fault.

-- 
Peter Wemm - peter_at_wemm.org; peter_at_FreeBSD.org; peter_at_yahoo-inc.com
"All of this is for nothing if we don't go to the stars" - JMS/B5