In message
on Sat, 23 Apr 2022 18:24:00 +0200,
"J. Hannken-Illjes" wrote:
>> In message <029c86d6-e0d2-4c98-8798-4bdc39ba0...@mailbox.org>
>> on Sat, 23 Apr 2022 10:22:13 +0200,
>> "J. Hannken-Illjes" wrote:
On 23. Apr 2022, at 10:15, J. Hannken-Illjes wrote:
>>>
> On 23. Apr 2022, at 14:45, Takahiro Kambe wrote:
>
> Hi,
>
> In message <029c86d6-e0d2-4c98-8798-4bdc39ba0...@mailbox.org>
> on Sat, 23 Apr 2022 10:22:13 +0200,
> "J. Hannken-Illjes" wrote:
>>> On 23. Apr 2022, at 10:15, J. Hannken-Illjes wrote:
>>
>>> Please try the attached
Hi,
In message <029c86d6-e0d2-4c98-8798-4bdc39ba0...@mailbox.org>
on Sat, 23 Apr 2022 10:22:13 +0200,
"J. Hannken-Illjes" wrote:
>> On 23. Apr 2022, at 10:15, J. Hannken-Illjes wrote:
>
>> Please try the attached diff (with mount option "discard").
>
> ... and remove the
> On 23. Apr 2022, at 10:15, J. Hannken-Illjes wrote:
> Please try the attached diff (with mount option "discard").
... and remove the "#define TRIMDEBUG" from the top of ffs_alloc.c first ...
--
J. Hannken-Illjes - hann...@mailbox.org
signature.asc
Description: Message signed with OpenPGP
> On 23. Apr 2022, at 05:17, Takahiro Kambe wrote:
>
> Hi,
>
> In message <15bebcc1-4756-46ad-a424-e5232065b...@mailbox.org>
> on Fri, 22 Apr 2022 19:39:35 +0200,
> "J. Hannken-Illjes" wrote:
>>> #5 0x80e69314 in VOP_FDISCARD (vp=0x879fb253da40,
>>> pos=, len=)
>>>
Hi,
In message <15bebcc1-4756-46ad-a424-e5232065b...@mailbox.org>
on Fri, 22 Apr 2022 19:39:35 +0200,
"J. Hannken-Illjes" wrote:
>> #5 0x80e69314 in VOP_FDISCARD (vp=0x879fb253da40,
>>pos=, len=)
>>at /usr/src/sys/kern/vnode_if.c:845
>> #6 0x80e69314
> On 22. Apr 2022, at 16:25, Takahiro Kambe wrote:
>
> Hi,
>
> In message
> on Fri, 22 Apr 2022 09:44:48 +0200,
> "J. Hannken-Illjes" wrote:
Thanks - I can confirm that a kernel from yesterday doesn't have the
issue any longer.
>>>
>>> I still have panic() on ThinkPad
Hi,
In message
on Fri, 22 Apr 2022 09:44:48 +0200,
"J. Hannken-Illjes" wrote:
>>> Thanks - I can confirm that a kernel from yesterday doesn't have the
>>> issue any longer.
>>
>> I still have panic() on ThinkPad E495.
>>
>> panic: kernel diagnostic assertion "VOP_ISLOCKED(vp)
> On 21. Apr 2022, at 16:57, Takahiro Kambe wrote:
>
> In message
> on Mon, 18 Apr 2022 09:56:55 +0200,
> Thomas Klausner wrote:
>>> Already committed by Taylor R Campbell as sequencer.c Rev. 1.79
>>> on 2022/04/16 11:13:10.
>>
>> Thanks - I can confirm that a kernel from
In message
on Mon, 18 Apr 2022 09:56:55 +0200,
Thomas Klausner wrote:
>> Already committed by Taylor R Campbell as sequencer.c Rev. 1.79
>> on 2022/04/16 11:13:10.
>
> Thanks - I can confirm that a kernel from yesterday doesn't have the
> issue any longer.
I still have panic()
On Sat, Apr 16, 2022 at 05:38:22PM +0200, J. Hannken-Illjes wrote:
> > On 16. Apr 2022, at 17:27, Tobias Nygren wrote:
> >
> > On Sat, 16 Apr 2022 16:51:31 +0200
> > Thomas Klausner wrote:
> >
> >> panic: kernel diagnostic assertion "VOP_ISLOCKED(vp) == LK_EXCLUSIVE"
> >> failed: file
On Sat, Apr 16, 2022 at 03:37:51PM -, Michael van Elst wrote:
> >+ vn_lock(vp, LK_EXCLUSIVE | LK_RETRY);
> >VOP_CLOSE(vp, oflags, kauth_cred_get());
> >- vrele(vp);
> >+ vput(vp);
>
> Sounds like an open-coded version of vn_close().
It's not,
> On 16. Apr 2022, at 17:27, Tobias Nygren wrote:
>
> On Sat, 16 Apr 2022 16:51:31 +0200
> Thomas Klausner wrote:
>
>> panic: kernel diagnostic assertion "VOP_ISLOCKED(vp) == LK_EXCLUSIVE"
>> failed: file "/usr/src/sys/miscfs/specfs/spec_vnops.c", line 1555
>> cpu1: Begin traceback...
>>
t...@netbsd.org (Tobias Nygren) writes:
>+ vn_lock(vp, LK_EXCLUSIVE | LK_RETRY);
> VOP_CLOSE(vp, oflags, kauth_cred_get());
>- vrele(vp);
>+ vput(vp);
Sounds like an open-coded version of vn_close().
On Sat, 16 Apr 2022 16:51:31 +0200
Thomas Klausner wrote:
> panic: kernel diagnostic assertion "VOP_ISLOCKED(vp) == LK_EXCLUSIVE" failed:
> file "/usr/src/sys/miscfs/specfs/spec_vnops.c", line 1555
> cpu1: Begin traceback...
> vpanic()
> kern_assert()
> spec_close() at netbsd:spec_close+0x2fc
>
Hi!
On 9.99.96 from end of March, I wanted to modify the contents of a
tarfile, so I extracted it on a tmpfs, replaced one file and tried
tarring it up again - at which point I got the following panic:
panic: kernel diagnostic assertion "VOP_ISLOCKED(vp) == LK_EXCLUSIVE" failed:
file
16 matches
Mail list logo
