Date: Tue, 10 Jul 2012 08:30:50 -0700 From: Garrett Cooper <yanegomi@gmail.com> To: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: kernel: abra-kadabra Message-ID: <CAGH67wSa87=vycE4r_=ikKtsvP1n9qoT=ydM1MsMYE5J65Fbfg@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.1207101634050.1437@wojtek.tensor.gdynia.pl> References: <alpine.BSF.2.00.1207101208040.46945@wojtek.tensor.gdynia.pl> <2E148ED4-F2E6-4B3D-99D8-C84E4E11F0F4@my.gd> <alpine.BSF.2.00.1207101634050.1437@wojtek.tensor.gdynia.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 10, 2012 at 7:36 AM, Wojciech Puchar
<wojtek@wojtek.tensor.gdynia.pl> wrote:
>
>
> On Tue, 10 Jul 2012, Damien Fleuriot wrote:
>
>>
>> On 10 Jul 2012, at 12:10, Wojciech Puchar <wojtek@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
Increasing that value [to 1k, 2k, etc] will help at the cost of
some more memory usage, but it won't fix the problem. The issue should
be less prominent in 9.x+.
HTH,
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGH67wSa87=vycE4r_=ikKtsvP1n9qoT=ydM1MsMYE5J65Fbfg>