On Fri, 27 Jan 2017 00:33:10 +0200
Ivan Klymenko wrote:
> On Wed, 28 Dec 2016 09:57:29 -0800
> hiren panchasara wrote:
>
> > On 12/28/16 at 07:53P, Ivan Klymenko wrote:
> > > On Wed, 28 Dec 2016 09:41:42 -0800
> > > hiren panchasara wrote:
> > >
> > > > Can you open a bug report at http
On Fri, 27 Jan 2017 19:16:04 +0300
"Andrey V. Elsukov" wrote:
> On 27.01.2017 17:41, Ivan Klymenko wrote:
> >> I didn't done the merge of the patch into stable/11 and
> >> releng/11.0, because Adrian said it is not good enough and he will
> >> rework it better :)
> >>
> >
> >
> > Jan 27 16:17:0
On 27.01.2017 17:41, Ivan Klymenko wrote:
I didn't done the merge of the patch into stable/11 and releng/11.0,
because Adrian said it is not good enough and he will rework it
better :)
Jan 27 16:17:07 ns kernel: Fatal trap 12: page fault while in kernel mode
Jan 27 16:17:07 ns kernel: cpuid =
On Fri, 27 Jan 2017 15:01:18 +0300
"Andrey V. Elsukov" wrote:
> On 27.01.2017 14:58, Ivan Klymenko wrote:
> > On Fri, 27 Jan 2017 13:46:30 +0300
> > "Andrey V. Elsukov" wrote:
> >
> >> On 27.01.2017 01:33, Ivan Klymenko wrote:
> >>> The reason most panics served as tuning Netisr:
> >>> net.i
On Fri, 27 Jan 2017 15:01:18 +0300
"Andrey V. Elsukov" wrote:
> On 27.01.2017 14:58, Ivan Klymenko wrote:
> > On Fri, 27 Jan 2017 13:46:30 +0300
> > "Andrey V. Elsukov" wrote:
> >
> >> On 27.01.2017 01:33, Ivan Klymenko wrote:
> >>> The reason most panics served as tuning Netisr:
> >>> net.i
On 27.01.2017 14:58, Ivan Klymenko wrote:
On Fri, 27 Jan 2017 13:46:30 +0300
"Andrey V. Elsukov" wrote:
On 27.01.2017 01:33, Ivan Klymenko wrote:
The reason most panics served as tuning Netisr:
net.isr.numthreads=4
net.isr.maxthreads=4
net.isr.bindthreads=1
Apparently, this subsystem at some
On Fri, 27 Jan 2017 13:46:30 +0300
"Andrey V. Elsukov" wrote:
> On 27.01.2017 01:33, Ivan Klymenko wrote:
> > The reason most panics served as tuning Netisr:
> > net.isr.numthreads=4
> > net.isr.maxthreads=4
> > net.isr.bindthreads=1
> >
> > Apparently, this subsystem at some moment had been bro
On 27.01.2017 01:33, Ivan Klymenko wrote:
The reason most panics served as tuning Netisr:
net.isr.numthreads=4
net.isr.maxthreads=4
net.isr.bindthreads=1
Apparently, this subsystem at some moment had been broken.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211836
--
WBR, Andrey V. Elsu
On Wed, 28 Dec 2016 09:57:29 -0800
hiren panchasara wrote:
> On 12/28/16 at 07:53P, Ivan Klymenko wrote:
> > On Wed, 28 Dec 2016 09:41:42 -0800
> > hiren panchasara wrote:
> >
> > > Can you open a bug report at https://bugs.freebsd.org/bugzilla/
> > > with necessary details? Looks like virtua
Next panic
uname -a
FreeBSD ns 11.0-STABLE FreeBSD 11.0-STABLE #1 r310470: Fri Dec 23 12:00:49 EET
2016 root@ns:/usr/obj/usr/src/sys/bzk11 amd64
Dec 28 09:43:21 ns kernel: Fatal trap 12: page fault while in kernel mode
Dec 28 09:43:21 ns kernel: cpuid = 3; apic id = 03
Dec 28 09:43:21 ns ker
On Mon, 21 Nov 2016 18:35:24 +0100
Oliver Pinter wrote:
> On Mon, Nov 21, 2016 at 5:34 PM, Ivan Klymenko wrote:
> > Next
>
> Are you able to reproduce these without loaded VirtualBox kernel
> modules?
>
This is hard to do - server is used on a daily works.
Panic often occur when one of the ow
On Mon, Nov 21, 2016 at 5:34 PM, Ivan Klymenko wrote:
> Next
> uname -a
> FreeBSD nonamehost 11.0-STABLE FreeBSD 11.0-STABLE #10 r308523: Fri Nov 11
> 13:52:01 EET 2016 root@nonamehost:/usr/obj/usr/src/sys/bzk11 amd64
>
> Nov 21 17:33:40 ns kernel: Fatal trap 12: page fault while in kernel
Next
uname -a
FreeBSD nonamehost 11.0-STABLE FreeBSD 11.0-STABLE #10 r308523: Fri Nov 11
13:52:01 EET 2016 root@nonamehost:/usr/obj/usr/src/sys/bzk11 amd64
Nov 21 17:33:40 ns kernel: Fatal trap 12: page fault while in kernel mode
Nov 21 17:33:40 ns kernel: cpuid = 0; apic id = 00
Nov 21 17:
Next panic
Oct 28 09:06:50 ns kernel: panic: sbsndptr: sockbuf 0xf8008f186878 and mbuf
0xf8008f29d200 clashing
Oct 28 09:06:50 ns kernel: cpuid = 7
Oct 28 09:06:50 ns kernel: KDB: stack backtrace:
Oct 28 09:06:50 ns kernel: #0 0x80b5f0e7 at kdb_backtrace+0x67
Oct 28 09:06:50 ns ke
Next
Oct 21 22:06:26 ns syslogd: kernel boot file is /boot/kernel/kernel
Oct 21 22:06:26 ns kernel: panic: sbsndptr: sockbuf 0xf80201038518 and mbuf
0xf802820a1200 clashing
Oct 21 22:06:26 ns kernel: cpuid = 3
Oct 21 22:06:26 ns kernel: KDB: stack backtrace:
Oct 21 22:06:26 ns kernel: #0
Hi, friendly community.
I present to you my collection.
I have :
//===//
System Information
Manufacturer: Supermicro
Product Name: X10SLH-F/X10SLM+-F
//===//
pciconf -lv
hostb0
16 matches
Mail list logo