-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, Micha
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
On 21 Feb 2022, at 7:43, Hans Petter Selasky wrote:
FYI:
After a lot of digging trying everything, I found that the pxeboot and
loader.efi was too big simply due to ZFS support.
So I did this after buildworld:
cd /usr/src/stand
make WITHOUT_LOADER_ZFS=YES clean
make WITHOUT_LOADER_ZFS=YES a
> On 21. Feb 2022, at 09:43, Hans Petter Selasky wrote:
>
> FYI:
>
> After a lot of digging trying everything, I found that the pxeboot and
> loader.efi was too big simply due to ZFS support.
>
> So I did this after buildworld:
>
> cd /usr/src/stand
> make WITHOUT_LOADER_ZFS=YES clean
> ma
Toomas Soome wrote:
> > Why should pxeboot have ZFS support?
>
> Well, the feature X can be helpful for recovery purposes. The root
> cause is not the feature X itself, but the size limit. And the
> unfortunate fact, the size limit is not fixed, but depends on the
> system. Therefore there are tw
> On 21. Feb 2022, at 19:18, Simon J. Gerraty wrote:
>
> Toomas Soome wrote:
>>> Why should pxeboot have ZFS support?
>>
>> Well, the feature X can be helpful for recovery purposes. The root
>> cause is not the feature X itself, but the size limit. And the
>> unfortunate fact, the size limit
On 2/21/22 18:18, Simon J. Gerraty wrote:
Toomas Soome wrote:
Why should pxeboot have ZFS support?
Well, the feature X can be helpful for recovery purposes. The root
cause is not the feature X itself, but the size limit. And the
unfortunate fact, the size limit is not fixed, but depends on th
On 21.02.2022 12:43, Toomas Soome wrote:
On 21. Feb 2022, at 19:18, Simon J. Gerraty wrote:
Toomas Soome wrote:
Why should pxeboot have ZFS support?
Well, the feature X can be helpful for recovery purposes. The root
cause is not the feature X itself, but the size limit. And the
unfortunate f
-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 0x80bad587 in close
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/core.txt.1
http://mail.mikej.com/info.1
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
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
CONFIDENTIALITY NOTE: This message is intended only for the use
of the individual or entity to whom it is addressed and may
contain information that is privileged, confidential, and
exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are h
CONFIDENTIALITY NOTE: This message is intended only for the use
of the individual or entity to whom it is addressed and may
contain information that is privileged, confidential, and
exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you ar
try the attached patch
On Mon, Feb 21, 2022 at 5:14 PM Michael Jung
wrote:
>
>
>
>
>
> CONFIDENTIALITY NOTE: This message is intended only for the use
> of the individual or entity to whom it is addressed and may
> contain information that is privileged, confidential, and
> exempt from disclosur
The previous attached patch should work for testing purposes, but it's
incorrect if an error occurs.
The fhold() should be below FILEDESC_SUNLOCK(), this patch addresses that.
On Mon, Feb 21, 2022 at 5:18 PM Rob Wing wrote:
> try the attached patch
>
> On Mon, Feb 21, 2022 at 5:14 PM Michael Ju
Rob:
I did not remove Hans earlier patch, but your “latest” patch applied and
compiled with no errors.
I can now watch and control a TTY (v0) or a SSH session (pts/1) without
crashing.
Anything else you would like me to try?
--mikej
From: Rob Wing [mailto:rob.fx...@gmail.com]
Sent: Monday,
Think that's it...thanks for testing for the patch.
I opened up https://reviews.freebsd.org/D34335 for review.
-Rob
On Mon, Feb 21, 2022 at 6:05 PM Michael Jung
wrote:
> Rob:
>
>
>
> I did not remove Hans earlier patch, but your “latest” patch applied and
> compiled with no errors.
>
>
>
> I c
18 matches
Mail list logo
