On 3 Aug 2018, at 20:42, Oliver Pinter wrote:
On 8/3/18, Bjoern A. Zeeb wrote:
On 3 Aug 2018, at 18:48, Oliver Pinter wrote:
Hi all!
One of out users observed an VNET related kernel panic with epairs
in
a jail. Seems like some of the
Well would be great for a start to (a) email
On 8/3/18, Bjoern A. Zeeb wrote:
> On 3 Aug 2018, at 18:48, Oliver Pinter wrote:
>
>> Hi all!
>>
>> One of out users observed an VNET related kernel panic with epairs in
>> a jail. Seems like some of the
>
> Well would be great for a start to (a) email virtualisation@ as well,
> (b) include a
On 3 Aug 2018, at 18:48, Oliver Pinter wrote:
Hi all!
One of out users observed an VNET related kernel panic with epairs in
a jail. Seems like some of the
Well would be great for a start to (a) email virtualisation@ as well,
(b) include a panic message, backtrace or other related
More attempts at tracking this down. The suggested dtrace command does
usually abort with:
Assertion failed: (buf->dtbd_timestamp >= first_timestamp),
file
/usr/src/cddl/contrib/opensolaris/lib/libdtrace/common/dt_consume.c,
line 3330.
but with some luck soon after each machine
Hi all!
One of out users observed an VNET related kernel panic with epairs in
a jail. Seems like some of the
vnet related patches does not gets backported to 11-STABLE (they are
marked as MFC candidate):
SVN r33 and r313168, these are for the panic fix.
