On 01/09/19 20:41, Evilham wrote:
> On dg., set. 01 2019, Evilham wrote:
>
>> On dg., set. 01 2019, Guido Falsi wrote:
>>
>>> Hi,
>>>
>>> I'm experiencing a recurring panic I can trigger repeatably.
>>>
>>
>> I was going to send a similar email a few hours ago to the current
>> ML but decided to
On dg., set. 01 2019, Evilham wrote:
On dg., set. 01 2019, Guido Falsi wrote:
Hi,
I'm experiencing a recurring panic I can trigger repeatably.
I was going to send a similar email a few hours ago to the
current
ML but decided to debug some more before that.
FWIW: I am not 100% sure I
On 01/09/19 15:19, Mateusz Guzik wrote:
> This is fixed in https://svnweb.freebsd.org/base?view=revision=351642
Thanks! I missed that one!
--
Guido Falsi
___
freebsd-current@freebsd.org mailing list
On 01/09/19 15:25, Evilham wrote:
>
> FWIW: I am not 100% sure I it's the same panic, I am missing a cable ATM
> to get a full dump, but I do think they sound very similar.
I'm not using serial communications to get dumps, not necessary anymore.
You can have the kernel debugger output this
(VI_ACTIVE)
VI_LOCKedlock type zfs: UNLOCKED
name = portshaker-2019-09-01:11:04:20
parent_id = 2
id = 269
panic: No vop_need_inactive(0xf800abfcbd20,
0xfe00ba39b3f0)
cpuid = 2
time = 1567342436
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper
ntedhere 0
> flags (VI_ACTIVE)
> VI_LOCKedlock type zfs: UNLOCKED
> name = portshaker-2019-09-01:11:04:20
> parent_id = 2
> id = 269
> panic: No vop_need_inactive(0xf800abfcbd20, 0xfe00ba39b3f0)
> cpuid = 2
> time = 1567342436
> KDB: stack
zfs, type VDIR
usecount 0, writecount 0, refcount 1 mountedhere 0
flags (VI_ACTIVE)
VI_LOCKedlock type zfs: UNLOCKED
name = portshaker-2019-09-01:11:04:20
parent_id = 2
id = 269
panic: No vop_need_inactive(0xf800abfcbd20, 0xfe00ba39b3f0)
cpuid = 2
time
