tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: uvn_fp2 [was: Help with issue with mpt(4) driver]



On Sun, 27 Jan 2013, Patrick Welche wrote:

> 
> More details - so we now know that the page is BUSY. Sadly an
> attempt at a core dump to a separate disk failed and this is
> before I connect the serial port block to the motherboard...
> 
> Cheers,
> 
> Patrick
> 
> 
> PID    LID S CPU FLAGS  STRUCT LWP *         NAME WAIT
> 13322    6 3   3     0  ffff fe82 013f 42c0  vlc  uvn_fp2
> 
> vlc: proc ffff fe81 702c 4cf8  vmspace/map ffff fe81 c79f e5c8   flags 4000
> lwp 6  ffff fe82 013f 42c0  pcb ffff fe81 21ff 5d80
>   stat 3 flags 0 cpu 3 pri 43
>   wmesg uvn_fp2  wchan ffff 8000 0827 2390
> 
> PAGE 0xffff 8000 0827 2390:
>   flags=0x4f<BUSY,WANTED,TABLED,CLEAN,FAKE>, pqflags=0x0, wire_count=0,
>   pa=0x4468 8000
>   uobject=0xffff fe81 8ef3 9270, uanon=0x0, offset=0x8ee 0000 loan_count=0
>   [page ownership tracking disabled]
>   checking object list
>   page found on object list

Hm.  BUSY usually means I/O in progress, and FAKE indicates the page is 
still being initialized, probably reading data from disk.  

WANTED was probably set by the thread in uvn_fp2 state so it'll get woken up.  

TABLED means it's on an object's list.


> 
> OBJECT 0xffff fe81 8ef3 9270:
>   locked=0, pgops=0xffff ffff 808f d9e0, npages=38064, refs=1
> 
> VNODE flags 0x30<MPSAFE,LOCKSWORK>
> mp 0xffff fe81 0e37 a008  numoutput 0  size 0x1fe3d08f  writesize 0x1fe3d08f
> data 0xffff fe81 5ea4 4900  writecount 0  holdcnt 6
> tag VT_UFS(1) type VREG(1)
> mount    0xffff fe81 0e37 a008
> typedata 0xffff fe81 8a0f 74c8
> v_lock   0xffff fe81 8ef3 9380

Let's see.  

VREG and VT_UFS indicate it's a normal file on a UFS filesystem.

numoutput of 0 means there are no pending writes on this vnode.

Isn't there a /f flag to dump more vnode information?

If we had the inode number, we could hunt it down from the mountpoint to 
figure out which file this is.


> 
> v_uobj.vmobjlock lock details:
> lock address : 0xffff fe80 5d68 6640    type: sleep/adaptive
> initialized  : 0xffff ffff 8046 52a5
> shared holds = shared wanted = current cpu = 0
> current lwp  : 0xffff fe82 1f55 3840  last held : 0   <--- LWP different...
> last locked  : 0xffff ffff 8074 a6d2  unlocked*: 0xffff ffff 8074 a708
> owner field  : 0 wait/spin : 0/0

Looks like the lock is free at the moment.  


> 
> Turnstile chain at 0xffff ffff 80c4 7e40
> => No active turnstile for this lock.
> 
> 
> lwp_t ffff fe82 1f55 3840
> system: pid 0  proc ffff ffff 80c3 1000 vmspace/map ffff ffff 80c6 a980 flags 
> 20002
>   lwp 2 [idle/0]  ffff fe82 1f55 3840  pcb ffff fe81 0e07 8d80
>     stat 7 flags 201 cpu 0 pri 0
> 
> mount:
>   flag=MNT_LOG,MNT_LOCAL
>   iflag=IMNT_MPSAFE,IMNT_HAS_TRANS,IMNT_DTYPE
>   locked vnodes = 0xffff fe81 8ef3 9270
> 
> db{0}> show ncache fffffe818ef39270
> name not found
> 
> lock address : 0xffff fe81 8ef3 9380  type: sleep/adaptive
> initialized  : 0xffff ffff 8077 c329
> shared holds : 1                      exclusive : 0
> shared wanted: 0                      exclusive : 0
> current cpu  : 0                      last held : 3
> current lwp  : 0xffff fe82 1f55 3840  last held : 0xffff fe82 013f 42c0
> last locked  : 0xffff ffff 802a b74c  unlocked* : 0xffff ffff 802a b7bd
> owner/count  : 0x10  flags: 0
> 
> Turnstile chain at 0xffff ffff 80c4 80c0
> => No active turnstile for this lock.
> 
> 
> db{0}> reboot 0x104
> usbd_do_request: not in process context
> usbd_do_request: not in process context
> usbd_do_request: not in process context
> 


Home | Main Index | Thread Index | Old Index