[FUG-BR] Mensagem estranha no dmesg

[Diogo Dalfovo]

Bom dia pessoal...

Estava verificando o dmesg de um FreeBSD 8.2 Stable e olha a mensagem que
apareceu:
[root em cerberus ~]# dmesg
arp: 192.168.1.14 moved from d8:9e:3f:31:d0:c4 to 0c:60:76:35:5a:eb on re0
arp: 192.168.1.10 moved from a8:6a:6f:15:e6:b3 to d8:9e:3f:31:d0:c4 on re0
em0: promiscuous mode enabled
pflog0: promiscuous mode enabled
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
pflog0: promiscuous mode disabled
arp: 192.168.1.11 moved from d0:df:9a:1d:49:d9 to 14:da:e9:3e:6d:a8 on re0
arp: 192.168.1.15 moved from a8:6a:6f:15:e6:b3 to 30:38:55:23:ec:81 on re0
arp: 192.168.1.10 moved from 14:da:e9:25:18:b2 to e8:3e:b6:47:19:c9 on re0
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.
Ap
p<roachi1n18g> Ftehbe  2l0i m0i8t: 1o3n: 0P4V  ecnterribeeruss ,i
mcsopenctsori:d eErr rionrc:r eDaosni'ntg  keniotwh ehro wt hteo
vhma.npdmlaep .csohnpngepcetriporno ct oo r
 the vm.pmap.pv_entry_max tunable.
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.

A mensagem que me chamou atenção é esta:
p<roachi1n18g> Ftehbe  2l0i m0i8t: 1o3n: 0P4V  ecnterribeeruss ,i
mcsopenctsori:d eErr rionrc:r eDaosni'ntg  keniotwh ehro wt hteo
vhma.npdmlaep .csohnpngepcetriporno ct oo r
 the vm.pmap.pv_entry_max tunable.

Alguem ja viu isso, sera que o servidor teve alguma avaria maior? Passei o
rkhunter e não foi detectado nada, last tb nao teve nada todas as
atualizaçoes foram instaladas alguem tem ideia?

Diogo Dalfovo