Re: "busy buffer problem" panics

[Andrew Atrens <atrens@xxxxxxxxxxxxxxxxxx>]

Ouch just got another one. The buildworld was a red herring. The
linux/clearcase command is the real perp. -

Bad timing .. need to get some work done at the moment :( :( 

Andrew.

 Today's panic -
> 
> Debugger("busy buffer problem")
> Stopped at      Debugger+0x3e:  movb    $0,in_Debugger.0
> db> trace
> Debugger(c0417f7f,8,8,8,14) at Debugger+0x3e
> boot(100,c04af2e0,c04379b8,d9c227f4,1010002) at boot+0x265
> poweroff_wait(c04379b8,d73d2b18,d7a02680,d5fa1340,d73d2b18) at
> poweroff_wait lockmgr(d73d2b18,1010002,d9c228ac,d5fa1340,d9c22850) at
> lockmgr+0x339 vop_stdlock(d9c2285c,d9c22890,c0228634,d9c2285c,c0470b60) at
> vop_stdlock+0x2c
>
vop_defaultop(d9c2285c,c0470b60,d2a0bc00,d9dc55a0,d78c09a0,11bb,d9c228a4,d73d2aa0,d9c228ac,1010002,d5fa1340,d9c22b14,2)
> at vop_defau
> ltop+0x18
> vop_lock(d2a0bc00,d73d2aa0,d9c228ac,1010002,d5fa1340) at vop_lock+0x6b
> vn_lock(d73d2aa0,0,2,d5fa1340,c04b0bf8) at vn_lock+0xa3
> vrele(d73d2aa0,d73d2aa0,0,d9c22b14,0) at vrele+0x84
> lookup(d9c22b00,d305f800,6,c2765fa8,0) at lookup+0x58e
> namei(d9c22b00,d2aee80d,3f3,d9c229dc,d5fa1340) at namei+0x232
> linux_copyin_path(bfbfbb78,d9c22b84,2,d9c22bc4,d2aee800) at
> linux_copyin_path+0x171
> linux_readlink(d9c22c24,d9c22d0c,d9c22c1c,d9c22c20,3) at
> linux_readlink+0x38 syscall2(2f,2f,2f,bfbfbb87,bfbfbab7) at syscall2+0x25f
> Xint0x80_syscall() at Xint0x80_syscall+0x2a
> db> c
> Uptime: 6h50m22s
> twe0: failed to delete unit 0