I've got this in my local tree now. I have a note to go dig up which
draft I yanked this from and update it with reference to the draft and
the current spec.
Thanks for pointing this out!
-adrian
___
freebsd-current@freebsd.org mailing list
https://lis
Got it, thank you.
zxystd
> 2021年4月2日 下午12:56，Adrian Chadd 写道：
>
> Hi!
>
> Oh, so from what I recall, implementations got it wrong in the early
> draft days with their interop so the flag values changed.
>
>
> -adrian
>
> On Thu, 1 Apr 2021 at 20:45, qcwap <1051244...@qq.com> wrote:
>>
>>
Hi!
Oh, so from what I recall, implementations got it wrong in the early
draft days with their interop so the flag values changed.
-adrian
On Thu, 1 Apr 2021 at 20:45, qcwap <1051244...@qq.com> wrote:
>
> Well, I see.
>
> I am newly to freebsd, thanks for your answering.
> I had tried using thi
Well, I see.
I am newly to freebsd, thanks for your answering.
I had tried using this section of code and found these flags are not satisfied,
after changing them, I can negotiate VHT80, VHT160 fine with iwm, so I pointed
out this problem. I am also wondering what's the badly wrong of you said
On 05/03/2021 14:01, Antonio Olivares wrote:
… worked well with firefox-esr which I use because the plugins
are deprecated using the newer firefox. Despite that it also used to
work with the regular firefox. …
For reference – I dug up some of what's below in response to a question
in IRC abou
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254698
Andrey Fesenko changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254698
--- Comment #3 from Mark Millard ---
(In reply to Andrey Fesenko from comment #2)
I was only commenting on the reference to
"installer panic", not on other aspects of
the overall behavior. No panic is shown in
the picture, just a debug-ker
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254698
--- Comment #2 from Andrey Fesenko ---
(In reply to Mark Millard from comment #1)
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
127494 root 20 0 2557332 1.0g 18732 S 100.0 53.8 1:25.97 qemu-k
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254698
Mark Millard changed:
What|Removed |Added
CC||marklmi26-f...@yahoo.com
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254698 bug with
screen panic CURRENT snapshot
On Thu, Apr 1, 2021 at 2:03 PM Antonio Olivares wrote:
>
> On Wednesday, March 31, 2021, Glen Barber wrote:
> > On Tue, Mar 30, 2021 at 07:54:45PM -0500, Antonio Olivares wrote:
> >> Dear all,
> >>
>
://lists.freebsd.org/pipermail/freebsd-current/2021-April/079339.html
installer panic after final reboot kvm-efi
FreeBSD-14.0-CURRENT-amd64-20210401-4084b1ab041-245766-disc1.iso
https://64.media.tumblr.com/668d44ed911d93bc33dd300bc8388a13/e90c47870f5a6d6c-cb/s1280x1920
> -Original Message-
> From: owner-freebsd-curr...@freebsd.org curr...@freebsd.org> On Behalf Of Athan Papadimitriou
> Sent: Thursday, 1 April 2021 08:15
> To: freebsd-current@freebsd.org
> Subject: Missing sysctl OID in RC4
>
> Do you know if net.inet.sctp.blackhole has been removed from
> On 1 Apr 2021, at 09:15, Athan Papadimitriou wrote:
>
> Do you know if net.inet.sctp.blackhole has been removed from r13?
> Sysctl says it is unknown though still described in blackhole(4)
>
Did you load the module?
uname -r
13.0-RC4
# kldload sctp
# kldstat
Id Refs Address
Do you know if net.inet.sctp.blackhole has been removed from r13?
Sysctl says it is unknown though still described in blackhole(4)
Thanks
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscri
On Wednesday, March 31, 2021, Glen Barber wrote:
> On Tue, Mar 30, 2021 at 07:54:45PM -0500, Antonio Olivares wrote:
>> Dear all,
>>
>> after updating to RC4 with
>> # freebsd-update -r upgrade 13.0RC4
>> When I shutdown, I get error messages AE_??? PCI
>>
>>
>> Press any key to reboot
>>
>> It sh
15 matches
Mail list logo
