Re: panic: getnewbuf: locked buf on heavy load 5.4-STABLE

2005-09-19 Thread AK
On Friday 16 September 2005 19:25, Chuck Swiger wrote: To get a crashdump I should have swapspace = total ram. Currently it is only 2G, I'm trying to think of smth. to get more swapspace. dmesg is available @ http://getfile.biz/dmesg.txt Take a look at /boot/loader.conf, you can limit

panic: getnewbuf: locked buf on heavy load 5.4-STABLE

2005-09-16 Thread Alex
Hello! For some reason my 5.4 STABLE is dying each 4-5 hours with panic above. This is big Web server with Apache configured to 1500 MaxClients. All kernel tunings suggested for high load servers by freebsd handbook are in place. Hardware is Intel server board, P4-3.0 cpu with HT off, 3Gb ram,

Re: panic: getnewbuf: locked buf on heavy load 5.4-STABLE

2005-09-16 Thread Chuck Swiger
Please read man crash and the part of the handbook which talks about how to obtain a crashdump or backtrace with more information about the panic you see. You might consider putting both a backtrace and a dmesg from the system on the web somewhere, and post links to that. Alex wrote: For

Re: panic: getnewbuf: locked buf on heavy load 5.4-STABLE

2005-09-16 Thread AK
Hello! On Friday 16 September 2005 18:40, Chuck Swiger wrote: Please read man crash and the part of the handbook which talks about how to obtain a crashdump or backtrace with more information about the panic you see. You might consider putting both a backtrace and a dmesg from the system on

Re: panic: getnewbuf: locked buf on heavy load 5.4-STABLE

2005-09-16 Thread Chuck Swiger
AK wrote: Hello! Hello. On Friday 16 September 2005 18:40, Chuck Swiger wrote: Please read man crash and the part of the handbook which talks about how to obtain a crashdump or backtrace with more information about the panic you see. You might consider putting both a backtrace and a dmesg

Re: panic: getnewbuf: locked buf on heavy load 5.4-STABLE

2005-09-16 Thread AK
Greetings! On Friday 16 September 2005 19:25, Chuck Swiger wrote: Take a look at /boot/loader.conf, you can limit the amount of physical RAM FreeBSD uses to less than 2GB for long enough to get a valid dump, assuming the crash is easily reproducable. Will look into it... Currently it is up