Possible hammer problem

Gergo Szakal bastyaelvtars at gmail.com
Sun Nov 16 08:16:23 PST 2008

Oops, I misconfigured my mail client, this was actually me.
@Matt: thanks for looking into it and do not hurry since I couldn't 
reproduce it since then. :-)

"DFBSD" <bastyaelvtars at gmail.com> wrote in message 
4919d02a$0$882$415eb37d at crater_reader.dragonflybsd.org">news:4919d02a$0$882$415eb37d at crater_reader.dragonflybsd.org...
The lighttpd process got stuck in the select state unkillably. I decided 
to reboot and got a panic.

syncing disks... 87 87 87 87 87 87 87 87 87 87 87 87 87 87 87 87 87 87 87 
giving up on 1 buffers
Debugger("busy buffer problem")
Stopped at      Debugger+0x34:  movb    $0,in_Debugger.3949
db> trace
Debugger(c05382b5,c053829c,1,0,0) at Debugger+0x34
boot(0,caf18d34,c04d2fdd,caf18cf0,6) at boot+0x1e2
sys_reboot(caf18cf0,6,55d93,0,c9708c58) at sys_reboot+0x23
syscall2(caf18d40) at syscall2+0x1e9
Xint0x80_syscall() at Xint0x80_syscall+0x36

Needless to say, lighttpd serves from a hammer partition and also runs 
from another. Kernel and vmcore are also available: 

More information about the Bugs mailing list