On 7/10/12 4:36 PM, Wojciech Puchar wrote: > > > On Tue, 10 Jul 2012, Damien Fleuriot wrote: > >> >> On 10 Jul 2012, at 12:10, Wojciech Puchar >> <woj...@wojtek.tensor.gdynia.pl> wrote: >> >>> this is what i've got from kernel (same visible after dmesg of course) >>> >>> >>> Jul 9 08:56:53 ... kernel: <<66<>p>ipd6id >p336i65d0 43432 >>> ((hh6ttt6p2d4 )(t,p dht)t,pu di)du,i ud1i 0d14 80:10 e44x88i::t eex >>> die txoiedtn eo dn sosini ggnsnaalilg n1a1l >>> Jul 9 08:56:53 .. kernel: 1 >>> Jul 9 08:56:53 ... kernel: >>> Jul 9 08:56:53 ... kernel: <<66>>11 >>> Jul 9 08:56:53 ... kernel: 1 >>> Jul 9 08:56:53 ... kernel: >>> >>> everything before and after seems usual. >>> >>> when reading every second letter it SEEMS to make more sense but >>> still not much. >>> >>> What it is? >>> >> >> You're seeing several messages at jumbled together, or your message >> and other parts of the buffer. >> >> Either way, you can see the word "signal" there ;) >> > i think it was httpd (probably PHP trash) crashed with sig11 but want to > be sure. > > httpd rarely do crash... Strange i have ports rather up to date and no > KNOWN vulnerabilities are according to portaudit output. > > how can i prevent mixing kernel messages? > > i have > > options PRINTF_BUFR_SIZE=256 # Prevent printf output being > interspersed. > > in kernel config
Regarding the mixing of kernel messages I'm afraid I won't be able to help with that. Regarding your HTTPd dying, I've also experienced signal 11 quits when I was using apache and PHP as a module. _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
