Hello! mpd (fresh) on FreeBSD 6.1p12 sometimes hangs system, totally, to reset. Tried two completely different boxes, so it cannot be a hardware problem. I'm updating to 6.2 now, but have little hope. What can I turn on in kernel to fix it or at least to make computer reboot? Alex.
Alex Povolotsky wrote:> Hello! > > mpd (fresh) on FreeBSD 6.1p12 sometimes hangs system, totally, to reset. > Tried two completely different boxes, so it cannot be a hardware problem. > > I'm updating to 6.2 now, but have little hope. What can I turn on in > kernel to fix it or at least to make computer reboot? >Which version of mpd are you using? Have you tried the latest version from ports, 4.1? I've read it fixes a *lot* of problems found with the older versions. Richard -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2709 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20070219/635065bf/smime.bin
Hi. Alex Povolotsky wrote:> mpd (fresh) on FreeBSD 6.1p12 sometimes hangs system, totally, to reset. > Tried two completely different boxes, so it cannot be a hardware problem. > > I'm updating to 6.2 now, but have little hope. What can I turn on in > kernel to fix it or at least to make computer reboot?I didn't check this, but have heard that this can hapend if you are trying to send tunnel (pptp/l2tp/...) traffic inside this tunnel. It can make infinite loop and consume all possible resources. Check your routing table for possible traffic loop. -- Alexander Motin mav@alkar.net Optima Telecom
Richard Tector wrote:> Or perhaps it doesn't. All I can remember is it requires the bpf > netgraph module.ng_bpf is not from this opera. It does just packets filtering by bpf-like filter program and it is not related to interfaces and traffic capturing. -- Alexander Motin mav@alkar.net Optima Telecom
Alex Povolotsky ?????:> mpd (fresh) on FreeBSD 6.1p12 sometimes hangs system, totally, to reset. > Tried two completely different boxes, so it cannot be a hardware problem.It's easy to reproduce? Can you try make debug-friendly kernel? http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-deadlocks.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online-ddb.html> I'm updating to 6.2 now, but have little hope. What can I turn on in > kernel to fix it or at least to make computer reboot?See the above links. -- WBR, Andrey V. Elsukov