On 3/13/16 1:44 PM, Bryan Drewery wrote:
> On 2/22/2016 2:01 PM, Bryan Drewery wrote:
>> Running CURRENT r295632.
>>
>> # vmstat -m|grep routetbl
>> routetbl 103952 51995K - 155861 512,1024
>>
>> This seems quite large for my dev build system.
>>
>
> Now on r296480:
>
> # vmstat -m|
Vitalij,
although the first patch should fixup the panic, can you please
instead run this one. And if it is possible, can you please
monitor this sysctl:
sysctl kern.ipc.sf_long_headers
--
Totus tuus, Glebius.
Index: sys/kern/kern_descrip.c
=
Hi,
On 19.03.16 21:58, Florian Limberger wrote:
I omitted the later frame adresses, I typed this off a photo, I missed
to create a crash dump, but I can provide one if it is needed:
> panic: ufs_dirbad: /usr/home: bad dir ino 6742590 at offset 512:
I resolved my issue, the fs was in an incons
On 03/23/16 11:55, Eir Nym wrote:
Hi,
Is there method to check this with compiled binaries?
Hi,
You might try:
strings /boot/modules/*.ko | grep me
But you need to analyze the output. Possibly you could add a
kdb_backtrace() call around the printf in question in the kernel. That
would gi
Vitalij,
can you please try with this patch?
On Fri, Mar 04, 2016 at 02:40:54PM +0200, Vitalij Satanivskij wrote:
V> Hello.
V>
V> I get kernel panic on high loaded server with messages
V>
V> savecore: reboot after panic:
V>vn_sendfile: mlen 326 space -20 hdrlen 326
V>
V>
V> # kgdb ke
Hi,
Is there method to check this with compiled binaries?
I never update world on live system since it is -CURRENT branch and I keep
possible incompatibility in mind.
You can also look into my build script I’ve published in same repository.
—
Arseny Nasokin
✪
> On 22 Mar 2016, at 19:29, Hans
