> --mikej
>>
>>
>>
>>
>>
>> *From:* Rob Wing [mailto:rob.fx...@gmail.com]
>> *Sent:* Monday, February 21, 2022 9:30 PM
>> *To:* Michael Jung
>> *Cc:* Hans Petter Selasky ; freebsd-current <
>> freebsd-current@freebsd.org>
>&
Monday, February 21, 2022 9:30 PM
> *To:* Michael Jung
> *Cc:* Hans Petter Selasky ; freebsd-current <
> freebsd-current@freebsd.org>
> *Subject:* Re: New panic in main-n253273-a52d8d4a6c6:
>
>
>
> The previous attached patch should work for testing purposes, but it&#x
, February 21, 2022 9:30 PM
To: Michael Jung
Cc: Hans Petter Selasky ; freebsd-current
Subject: Re: New panic in main-n253273-a52d8d4a6c6:
The previous attached patch should work for testing purposes, but it's
incorrect if an error occurs.
The fhold() should be below FILEDESC_SUNLOCK(),
ry 21, 2022 9:06 PM
>> *To:* 'Hans Petter Selasky' ; freebsd-current <
>> freebsd-current@freebsd.org>
>> *Subject:* RE: New panic in main-n253273-a52d8d4a6c6:
>>
>>
>>
>> *From:* Hans Petter Selasky [mailto:h...@selasky.org ]
>> *Sent:* Mon
t;
> freebsd-current@freebsd.org>
> *Subject:* RE: New panic in main-n253273-a52d8d4a6c6:
>
>
>
> *From:* Hans Petter Selasky [mailto:h...@selasky.org ]
> *Sent:* Monday, February 21, 2022 8:34 PM
> *To:* Michael Jung ; freebsd-current <
> freebsd-current@freebsd.org&
From: Michael Jung
Sent: Monday, February 21, 2022 9:06 PM
To: 'Hans Petter Selasky' ; freebsd-current
Subject: RE: New panic in main-n253273-a52d8d4a6c6:
From: Hans Petter Selasky [mailto:h...@selasky.org]
Sent: Monday, February 21, 2022 8:34 PM
To: Michael Jung
From: Hans Petter Selasky [mailto:h...@selasky.org]
Sent: Monday, February 21, 2022 8:34 PM
To: Michael Jung ; freebsd-current
Subject: Re: New panic in main-n253273-a52d8d4a6c6:
On 2/22/22 00:42, Michael Jung wrote:
> Hi:
>
> I was trying to remember what I did that was odd when t
kinda thinking this might be related to commit f40dd6c8034b ("tty: switch
ttyhook_register to use fget_cap_locked")
fget_unlocked() must have grabbed an extra reference count on the file
pointer that fget_cap_locked() doesn't get
On Mon, Feb 21, 2022 at 4:35 PM Hans Petter Selasky wrote:
> On 2
On 2/22/22 00:42, Michael Jung wrote:
Hi:
I was trying to remember what I did that was odd when this crash occurred then
it
hit me. You can repeat this panic by doing:
# watch -I -W pts/0
Here is another panic that happened write after issuing "watch" for comparison.
http://mail.mikej.com/c
com/info.1
http://mail.mikej.com/vmcore.1
--mikej
-Original Message-
From: Michael Jung
Sent: Monday, February 21, 2022 6:22 PM
To: 'Hans Petter Selasky' ; freebsd-current
Subject: RE: New panic in main-n253273-a52d8d4a6c6:
-Original Message-
From: Hans Pett
-Original Message-
From: Hans Petter Selasky [mailto:h...@selasky.org]
Sent: Monday, February 21, 2022 8:53 AM
To: Michael Jung ; freebsd-current
Subject: Re: New panic in main-n253273-a52d8d4a6c6:
On 2/21/22 14:07, Michael Jung wrote:
> (kgdb) fram 16
> #16 0x80bad
On 2/21/22 14:07, Michael Jung wrote:
(kgdb) fram 16
#16 0x80bad587 in closefp_impl (fdp=0xfe012b7c0430, fd=4,
fp=0xf801cc119280, td=0xfe00df8d0560, audit=true) at
/usr/src/sys/kern/kern_descrip.c:1300
1300error = closef(fp, td);
(kgdb) print /x *fdp
$1 = {fd_fi
-Original Message-
From: owner-freebsd-curr...@freebsd.org
[mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of Hans Petter Selasky
Sent: Monday, February 21, 2022 2:48 AM
To: Michael Jung ; freebsd-current
Subject: Re: New panic in main-n253273-a52d8d4a6c6:
On 2/20/22 21:53
On 2/20/22 21:53, Michael Jung wrote:
Hi!
The box was quite busy at the time. The only odd thing I am aware of and which
I do
not think is related is I have not been able to expand one of my zpool's. ZFS
sees my
added draid2:2d:10c:0s vdev but I can't seem to force zpool's expansion - my
be
14 matches
Mail list logo
