on doesn't verify it works for NFS
>>> traffic.
>>>
>>> Also, the large RPC messages are a chain of about 33 mbufs of
>>> various lengths, including a mix of partial clusters and regular
>>> data mbufs, whereas a bulk send on a socket will typically
ufs, whereas a bulk send on a socket will typically
>> result in an mbuf chain of a lot of full 2K clusters.
>> --> As such, NFS can be good at tickling subtle bugs it the
>> net driver related to mbuf handling.
>>
>> rick
>>
>>>>
ous lengths, including a mix of partial clusters and regular
> data mbufs, whereas a bulk send on a socket will typically
> result in an mbuf chain of a lot of full 2K clusters.
> --> As such, NFS can be good at tickling subtle bugs it the
> net driver related to mbuf handling.
verted.
>>>It is currently in all of releng13, stable13 and main, although
>>>the patch to fix this is was just reviewed and may hit main soon.
>>
>> Do you want a debug kernel to be used? Do you have a preference
>> for main vs. stable/13 vs. release/1
Hi List,
I’m observing some odd behaviour after I decided to put the 2 interfaces in my
system into a lagg failover bond
- Can’t add the lagg to a bridge, it will say:
$ sudo ifconfig vm-public addm lagg0
ifconfig: BRDGADD lagg0: Device busy
I also witnessed that starting a vm after having it
ferring to a release/13.0.0 context.)
>
>> ps: I do not think that r367492 could cause this, but it would be
>>nice if you try a kernel with the r367492 patch reverted.
>>It is currently in all of releng13, stable13 and main, although
>>the patch to fix this i
could cause this, but it would be
> nice if you try a kernel with the r367492 patch reverted.
> It is currently in all of releng13, stable13 and main, although
> the patch to fix this is was just reviewed and may hit main soon.
Do you want a debug kernel to be used? Do you ha
[Direct drive connection to machine: no problem.]
On 2021-May-20, at 21:40, Mark Millard wrote:
> [main test example and main/releng/13 mixed example]
>
> On 2021-May-20, at 20:36, Mark Millard wrote:
>
>> [stable/13 test: example ends up being odder. That might
>>
[main test example and main/releng/13 mixed example]
On 2021-May-20, at 20:36, Mark Millard wrote:
> [stable/13 test: example ends up being odder. That might
> allow eliminating some potential alternatives.]
>
> On 2021-May-20, at 19:38, Mark Millard wrote:
>>
>>
[stable/13 test: example ends up being odder. That might
allow eliminating some potential alternatives.]
On 2021-May-20, at 19:38, Mark Millard wrote:
>
> On 2021-May-20, at 18:09, Rick Macklem wrote:
>>
>> Oh, one additional thing that I'll dare to top post...
&
ebsd.org on
> behalf of Rick Macklem
> Sent: Thursday, May 20, 2021 8:55 PM
> To: FreeBSD-STABLE Mailing List; Mark Millard
> Subject: Re: releng/13 release/13.0.0 : odd/incorrect diff result over nfs
> (in a zfs file systems context)
>
> Mark Millard wrote:
>> [I wa
m
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On 2021-May-16 11:48:24 +1000, Peter Jeremy via freebsd-stable
wrote:
>I am running 13-stable from a couple of weeks ago, without Capsicum
>(neither CAPABILITY_MODE nor CAPABILITIES are specified in my kernel).
>Despite this, I am getting Capsicum-related errors. As an example:
&g
I am running 13-stable from a couple of weeks ago, without Capsicum
(neither CAPABILITY_MODE nor CAPABILITIES are specified in my kernel).
Despite this, I am getting Capsicum-related errors. As an example:
openat(AT_FDCWD, "/")
will return ENOTCAPABLE.
Rummaging around the sources
On 2021-May-06 19:07:23 -0400, monochrome wrote:
...
>On 5/6/21 7:49 AM, Peter Jeremy via freebsd-stable wrote:
...
>> server% tail /COPYRIGHT <&-
>> Assertion failed: (procfd > STDERR_FILENO), function service_clean, file
>> /usr/src/lib/libcasper/libcasper/servi
ewsyslog.conf.d/[!.]*.conf
/usr/local/etc/newsyslog.conf.d/[!.]*.conf
Specifically, the 7 lines with "@" involved under "when" get the
complaints.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
______
On 2021-May-06 12:59:54 +0200, Mariusz Zaborski wrote:
>Could you provide details how to reproduce this?
>
>On Thu, 6 May 2021 at 12:13, Peter Jeremy via freebsd-stable
> wrote:
>>
>> Since updating from 12-stable to 13-stable, I've found that tail(1)
>> cras
Since updating from 12-stable to 13-stable, I've found that tail(1)
crashes, reporting:
Assertion failed: (procfd > STDERR_FILENO), function service_clean, file
/usr/src/lib/libcasper/libcasper/service.c, line 394.
tail: unable to init casper: Socket is not connected
unless all three
case time to allocate space. If we
have less than this amount of free space, most ZPL
operations (e.g. write, create) will return ENOSPC.
Default value: 5.
END QUOTE
So in my simple context, apparently not much else
contributes and the
arly 2018-Mar)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD CA72_4c8G_ZFS 13.0-RELEASE FreeBSD 13.0-RELEASE #0
>>> releng/13.0-n244733-ea31abc261ff-dirty: Thu Apr 29 21:53:20 PDT 2021
>>> root@CA72_4c8G_ZFS:/usr/obj/BUILDs/13_0R-CA72-nodbg-clang/usr/13_0R-src/arm64.aarch64/sys/GENERIC-NODBG-CA72
>>> arm64 aarch64
y run a 'target cortex-a7 (so: armv7) from aarch64' test
> next. That was the context for the original discovery and
> report.
>
>
The armv7 builds and installs get the same sort of diff
results as the aarch64 ones.
So it does not look like I can readily reproduce the
problem files that had differences.
Given the time it takes to run the experiments, I would
not expect to reproduce the problem on any given
timescale. I'll stop the reporting as I go along in
my activities --unless I end up with a repetition
of the problem.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
as apparently no longer
>> available under that naming.
>> For reference:
>> # uname -apKU
>> FreeBSD CA72_4c8G_ZFS 13.0-RELEASE FreeBSD 13.0-RELEASE #0
>> releng/13.0-n244733-ea31abc261ff-dirty: Thu Apr 29 21:53:20 PDT 2021
>> root@CA72_4c8G_ZFS:/usr/obj/BUIL
n a 'target cortex-a7 (so: armv7) from aarch64' test
next. That was the context for the original discovery and
report.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
139
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
_______
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
accidentally
discovered the presence of the few files with
differences. My new experiments were different
and I'd not though of needing to vary the
procedure to get you the right evidence.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
_
line 293, in load
return loads(fp.read(),
File "/usr/local/lib/python3.7/codecs.py", line 504, in read
newchars, decodedbytes = self.decode(data, self.errors)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb7 in position 18:
invalid start byte
Not exactly an obvious error me
.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-uns
00018 29 100 8
[29] .strtab STRTAB 51c8
0363 0 0 1
> 50c4-000050b8 == 0xC
Note: 0xC+0x4 == 0x10 (the size), so the last 4 bytes
of .gnu_debuglink
> For all I know, some
the 4 might accidentally
match sometimes. The addition offset after .gnu_debuglink's file
offset does vary (0xC and 0x10 above).
The content of those differences do not look like
file path components, for example the 0x08 byte.
I do build with:
# Avoid stripping but do not control host -g sta
ars, decodedbytes = self.decode(data, self.errors)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb7 in position 18:
invalid start byte
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
instwrld-norm/usr/tests/local: No such file
or directory
diff:
/usr/obj/DESTDIRs/13_0R-CA72-instwrld-norm/usr/tests/sys/pjdfstest/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/tests/t
ec can't decode byte 0xb7 in position 18:
invalid start byte
The two older snapshots of a Boot Environment have
bin/sh files that compare equal. But every program I
tried the above sort of thing against on got the same
UnicodeDecodeError result from diffoscope, byte value
and position matching.
T
, you might need to send
notes about how you want me to use the tool to get the
output that you would want. (And, so, I get to learn . . .)
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
e "enough is enough" and let you know.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On 2021-04-30 11:12, Arrigo Marchiori via freebsd-stable wrote:
> On Fri, Apr 30, 2021 at 10:29:33AM +0200, Andrea Brancatelli via
> freebsd-stable wrote:
>
>> Hello,
>>
>> I'm having an annoying problem with FreeBSD 12.2-RELEASE-p6, iscsid,
>> geo
Hello,
On Fri, Apr 30, 2021 at 10:29:33AM +0200, Andrea Brancatelli via freebsd-stable
wrote:
> Hello,
>
> I'm having an annoying problem with FreeBSD 12.2-RELEASE-p6, iscsid,
> geom multiparty, a Dell MD3200i and fstab.
>
> Long story short, iSCSI login/connection/
On 2021-04-30 10:29, Andrea Brancatelli via freebsd-stable wrote:
> Hello,
>
> I'm having an annoying problem with FreeBSD 12.2-RELEASE-p6, iscsid,
> geom multiparty, a Dell MD3200i and fstab.
Geom multiparty is probably the best typo/autocorrect ever.
---
A
bus0 target 6 lun 0 (pass1,da1)
at scbus3 target 0 lun 0 (cd0,pass2)
at scbus5 target 0 lun 0 (da2,pass3)
at scbus5 target 0 lun 1f (da3,pass4)
Any interesting suggestions?
Thanks a lot.
--
Andrea Brancatelli
_______
freebsd-stable@freebsd.org mailing
ht notice and care about such differences.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
_______
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send an
On 28/04/21 00:12, parv wrote:
Hi there,
I had updated FreeBSD, in VirtualBox 5.22 on Windows with EFI, from
12-STABLE
to 13-STABLE; upgraded the ZFS pools & the EFI boot loader. Currently
testing with 13 GENERIC kernel.
You mean you enabled EFI inside virtualbox? Why do you need that?
> 在 2021年4月25日，23:04，Li-Wen Hsu 写道：
>
> On Sun, Apr 25, 2021 at 9:55 PM 宋立杰 wrote:
>>
>> Yes, there is no ue0. And I made a mistake, it is 12.2-RELEASE other than
>> STABLE. Sorry for that. Do I need to install STABLE to keep up with the
>> newest deve
?
Is mergemaster going to stay as the recommented
command to use? If so, with which command line
options?
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
_______
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
‐‐‐
On Saturday, April 24, 2021 3:03 PM, Jeff Love j...@burgh.net wrote:
> I'm running 12.2 and 13.0 on KVM using virtio and zfs. I am not having
> disk I/O issues.
> Jeff Love
> On 4/24/21 5:25 AM, dashdruid via freebsd-stable wrote:
>
>> Hello List,
>> I ho
I tried to connect my iPhone SE2 (iOS 13.7) to FreeBSD 12.2-stable. After
loaded the kernel module if_ipheth, I connected my phone.
> ugen0.2: at usbus0
Then I typed usbconfig -u 0 -a 2 set_config 3
> ipeth0 on uhub6
> Ipeth0: on usbus0
Then I chose to trust the computer, bu
j/DESTDIRs/13_0R-CA7-for-chroot/var/db/etcupdate/
I have not checked on if "etcupdate build" has a similar issue
vs. not.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
_______
freebsd-stable@freebsd.org mailing
guests only if we have to.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
variants.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
d URL conventions
chosen were put in place. The below illustrates an example
of the mess for how things are currently presented.
https://artifact.ci.freebsd.org/snapshot/stable-13/?C=M&O=D
lists ac845558f7b626d9a31b8f6dab686c45d39dc5a0/ as having
date/time 2021-Apr-10 18:43 .
Bu
On 4/23/21 13:53, mike tancsa wrote:
> Starting to play around with RELENG_13 and wanted explore ZFS' built in
> encryption. Is there a best practices doc on how to do full disk
> encryption anywhere thats not GELI based ? There are lots for
> GELI,
> but nothing I could find for native OpenZFS
Is stable/13 going to start getting snapshot builds?
(As stands, main , stable/12 , and stable/11 are getting them.)
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-stable@freebsd.org mailing list
https
ng / writable at this
stage either.)
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
_______
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send an
I newly installed FreeBSD 12.2-release, but I found my wireless card Dell
1901(AR9462) work only at 11g and not steadily . "Failed to add supported
operating classes IE" occurs occasionally, why?
___
freebsd-stable@freebsd.org mailing
llard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
t was fast.
---
Andrea Brancatelli
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
aving to a) download the
entire source tree, b) make buildworld, and c) make buildkernel.
The kernel developers in their wisdom--ahem--have burdened all new
installations with the abysmal performance of the ULE scheduler.
The installation images for -STABLE versions are much the same.
The 4BSD sch
Eugene Grosbein wrote:
> 07.04.2021 12:49, Scott Bennett via freebsd-stable wrote:
>
> > At least w.r.t. gvinum's raid5, I can attest that the kernel panics
> > are real. Before settling on ZFS raidz2 for my largest storage pool, I
> > experimented with gst
disciplined militia, is at all times a good *
* objection to the introduction of that bane of all free governments *
* -- a standing army." *
*-- Gov. John Hancock, New York Journal, 28 January 1790 *
*
> On Apr 6, 2021, at 7:10 AM, Gary Palmer wrote:
>
> On Tue, Apr 06, 2021 at 06:49:17AM -0400, Robert Blayzor via freebsd-stable
> wrote:
>> I have several servers running 11.4 and 12.2 that do nightly portsnap
>> updates and the last time they've seen anything ne
XMPP: rblayzor.AT.inoc.net
PGP: https://pgp.inoc.net/rblayzor/
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On 2021-04-05 02:05, Daniel Morante via freebsd-stable wrote:
> My vote is for no.
>
> Reasoning is simple... at what point does it stop? By continuously moving
> stuff from base to ports, FreeBSD slowly becomes just a Kernel. 😉
I strongly agree with this consideration.
> On Apr 5, 2021, at 3:01 PM, Patrick M. Hausen wrote:
>
> Hi all,
>
> I absolutely freaked out when Apple removed the telnet and ftp clients
> from Mac OS and I needed to reinstall them via MacPorts.
Yep, and what I think many miss IRT to the stock ftpd is that it’s dumb simple
and “just wo
eebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> On 3 Apr 2021, at 22:39, Ed Maste wrote:
>
> I propose deprecating the ftpd currently included in the base system
> before FreeBSD 14, and opened review D26447
> (https://reviews.freebsd.org/D26447) to add a notice to the man page.
> I had originally planned to try to do this before 13.0, but
> On Apr 4, 2021, at 8:05 PM, Daniel Morante via freebsd-stable
> wrote:
>
> My vote is for no.
>
> Reasoning is simple... at what point does it stop? By continuously moving
> stuff from base to ports, FreeBSD slowly becomes just a Kernel. 😉
That’s a +1 here, both
happy to make a port for it if anyone needs it. Comments?
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
smime.p7s
nt Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b
We cannot change human failings by ridding ourselves of machines. -unknown
___
freebsd-stable@freebsd.org mailing list
https://
/unibia/freebsd/misc/arm64/qlnxe_13.0-RC4-arm64.log
On 3/30/21 2:31 PM, John-Mark Gurney wrote:
Daniel Morante via freebsd-stable wrote this message on Sun, Mar 28, 2021 at
03:23 -0400:
I installed 13.0-RC3 ARM64 from the DVD ISO image
(FreeBSD-13.0-BETA4-arm64-aarch64-dvd1.iso
<h
When I looked at https://www.freebsd.org/platforms/ I noticed
that "64-bit little-endian PowerPC" powerpc64le is not listed.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-stable@freebsd.org ma
e-with "${LINUXKPI_C}" dev/qlnx/qlnxe/qlnx_ioctl.c optional qlnxe
pci \ compile-with "${LINUXKPI_C}" dev/qlnx/qlnxe/qlnx_os.c optional
qlnxe pci \ compile-with "${LINUXKPI_C}"|
On 3/30/21 3:00 PM, Hans Petter Selasky wrote:
On 3/30/21 8:31 PM, John-Mark Gurney wr
On 30/03/21 17:38, tech-lists wrote:
On Tue, Mar 30, 2021 at 05:22:30PM +0200, Guido Falsi via freebsd-stable
wrote:
No, as you can see in the commit in the official git [1] while for
current and stable the new upstream version of openssl was imported for
the release the fix was applied
enSSL 1.1.1h-freebsd 22 Sep 2020
Up-to-date stable/13-n245043-7590d7800c4 reports OpenSSL 1.1.1k-freebsd
25 Mar 2021
shouldn't the 12.2-p5 be reporting openssl 1.1.1k-freebsd as well?
No, as you can see in the commit in the official git [1] while for
current and stable the new upstream
bsd 22 Sep 2020
Up-to-date stable/13-n245043-7590d7800c4 reports OpenSSL 1.1.1k-freebsd
25 Mar 2021
shouldn't the 12.2-p5 be reporting openssl 1.1.1k-freebsd as well?
thanks,
_______
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org
ig: Error: device "qlnxe" is unknown
Is this module not available for ARM64 architecture?
_______
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
r in a context that is not otherwise
paging (nor swapping)? If yes, is the behavior different
in any readily noticeable way?
> This system is CometLake and graphics are not supported on 12. I am not
> absolutely sure that there is not a hardware issue even though the main
> board, the disk, and the keyboard/mouse pad have all been replace since I
> received the system back last June. I now wonder what else could go wrong.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Hello,
I see the RC3 in the "Latest News" but not here:
https://www.freebsd.org/releases/13.0R/schedule/
I hope I'm writing to the proper channels/list about this.
Regards,
meka
signature.asc
Description: PGP signature
On 3/20/21 10:26 AM, Kevin Oberman wrote:
On Sat, Mar 20, 2021 at 8:35 AM Fred via freebsd-stable <
freebsd-stable@freebsd.org> wrote:
On 3/19/21 7:59 PM, Mathias Picker wrote:
Fred Hall via freebsd-stable writes:
I have a ThinkPad X1 Carbon Gen 4 (20FCS0NB00) which has happi
On 3/19/21 7:59 PM, Mathias Picker wrote:
Fred Hall via freebsd-stable writes:
I have a ThinkPad X1 Carbon Gen 4 (20FCS0NB00) which has happily run
FreeBSD 11 and 12, but which can't boot 13.0-RC1 from memstick or via
freebsd-update. In both cases the boot process locks up on the
Hi,
> On 13 Mar 2021, at 1:11, Glen Barber wrote:
>
> The second RC build of the 13.0-RELEASE release cycle is now available.
Might it be interesting to change the
zfs mount -a / zfs unmount -a
in /etc/rc.d/zfs to
zfs mount -al / zfs unmount -au
so that filesystems using the openzfs encryp
anyone know the status of
hwpstate_intel on ThinkPads?
Cheers,
Fred
_______
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
nsole"
comconsole_speed="115200"
boot_serial="YES"
Am I missing something else that has changed requiring a new option to
be set for serial consoles?
--
Thanks,
Dean E. Weimer
http://www.dweimer.net/
_______
freebsd-stable@
On 2021-03-17 9:59 am, tech-lists wrote:
On Sun, Mar 14, 2021 at 09:59:21AM +0100, Stefan Bethke wrote:
I'm planning to upgrade three production machines with existing ZFS
pools to 13-stable. Is there anything I need to pay attention to wrt
OpenZFS? Or should it be fully transparent,
I got the idea for the question: some
similarity to operational problems that I've seen
when not using my patches that provide a work around
matching the times better in my contexts.
(I'm told the type of issue is not limited to PowerMacs,
but PowerMacs are the only PowerPCish machines I've
had access to. Doing the most accurate time matching
gets into platform specific operations, no general
solution for such accuracy. Similarly, only platform
specifics might scale to lots of sockets/cores well,
even without trying to be as well matched. My workaround
is generic to the range of PowerMacs that I've had
access to but is not as accurate about matching the
times.)
For your context: how many sockets? Cores per socket?
Any other information that might be relevant to
matching times across sockets/cores? I suppose that
the board matters, not just the processor(s) in the
sockets. But what all would be appropriate information?
I do not know.
I'm not sure if the kern.hz=100 results fit with this
idea or not. (Such was never involved in my PowerMac
experiments.)
It is only somewhat suggestive evidence as stands. But
time mismatches across socket/cores might be a
direction for investigation? (Not that I've a great
idea for how to investigate such.)
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
e system performs well unless I
> do something that tries a bulk disk data move. Building world takes about 75
> minutes. I just have a very hard time building big ports.
Almost like things were stuck-sleeping and then the
sleep(s) finished?
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
I’ve updated the installation to RC2, the behaviour has changed in vmware
fusion to when I installed one of the BETA releases.
The initial boot fails, the system will reboot again and then it succeeds,
though more predictable than with the BETAs
I’m trying to see the differences in screen reco
nteraction is a bug in VMware or an edge case that needs to be supported too.
Btw, bhyve is looking nice these days!
Cheers,
Ruben
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe
> Also, I’m missing /boot/*efifat* in FreeBSD13. What is the procedure for
> updating EFI loaders?
>
> They have been removed because they are no longer needed (filesystem images
> for boot blocks trouble me too).
Agree, but I’ve felt I’ve missed the memo
>
> mount -t msdos /dev/da0pX /mnt
>
Hi List,
With FreeBSD 13 getting near release I was trying out a new hardware setup for
a future upgrade, in where a zfs SATA RAID-10 array would be accelated by some
NVME devices for cache, log, and special meta data.
However, booting the setup under VMWare fusion gives me a lot of zio_read
e
On 2021-Mar-06 19:18:37 +1100, Peter Jeremy via freebsd-stable
>> > wrote:
>> >>Somewhere between 13.0-ALPHA2 (c256201-g02611ef8ee9) and 13.0-BETA4
>> >>(releng/13.0-n244592-e32bc253629), geli (at least on my RockPro64 -
>> >>RK3399, arm64) has changed
[Adding arm@ and making it clearer that this is armv8-only]
On 2021-Mar-06 20:26:19 +1100, Peter Jeremy wrote:
>On 2021-Mar-06 19:18:37 +1100, Peter Jeremy via freebsd-stable
> wrote:
>>Somewhere between 13.0-ALPHA2 (c256201-g02611ef8ee9) and 13.0-BETA4
>>(releng/13.0-n244592-
On 2021-Mar-06 19:18:37 +1100, Peter Jeremy via freebsd-stable
wrote:
>Somewhere between 13.0-ALPHA2 (c256201-g02611ef8ee9) and 13.0-BETA4
>(releng/13.0-n244592-e32bc253629), geli (at least on my RockPro64 -
>RK3399, arm64) has changed so that a geli-encrypted partition (using
>AES-X
Somewhere between 13.0-ALPHA2 (c256201-g02611ef8ee9) and 13.0-BETA4
(releng/13.0-n244592-e32bc253629), geli (at least on my RockPro64 -
RK3399, arm64) has changed so that a geli-encrypted partition (using
AES-XTS 128) that was readable on 13.0-ALPHA2 becomes garbage on
13.0-BETA4.
I've verified th
27;ll note that there are other reports of wide variance
in transfer rates observed during an overall operation
such as "make extract". The one I'm thinking of is:
https://lists.freebsd.org/pipermail/freebsd-stable/2021-March/093251.html
which is an update to earlier reports, but ba
gt;96 average unshared stack size
>> 12288156 page reclaims
>>23 page faults
>> 0 swaps
>> 31207 block input operations
>> 175 block output operations
>> 4412 messages sent
>> 2536379 messages receive
ages received
> 0 signals received
> 385527 voluntary context switches
>369 involuntary context switches
>
> --
>
> Differences between 13.0 and 14-CURRENT maybe related to debugging features.
>
> But 13.0-BETA4 is slower than 12.2. Does someon
Dear All,
On Tue, Mar 02, 2021 at 10:55:15AM +0200, Andriy Gapon wrote:
> On 02/03/2021 09:50, Arrigo Marchiori via freebsd-stable wrote:
> > Dear All,
> >
> > On Sat, Feb 27, 2021 at 04:34:52PM +0100, Arrigo Marchiori via
> > freebsd-stable wrote:
> >
&g
klmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Dear All,
On Sat, Feb 27, 2021 at 04:34:52PM +0100, Arrigo Marchiori via freebsd-stable
wrote:
> Hello Helge, and thank you for replying again.
>
> On Sat, Feb 27, 2021 at 03:43:52PM +0100, Helge Oldach wrote:
>
> > Arrigo Marchiori via freebsd-stable wrote on Sat, 27
Hello Helge, and thank you for replying again.
On Sat, Feb 27, 2021 at 03:43:52PM +0100, Helge Oldach wrote:
> Arrigo Marchiori via freebsd-stable wrote on Sat, 27 Feb 2021 14:00:24 +0100
> (CET):
> > On the memstick, the root filesystem is mounted read-only. I
> > apolog
Hello Helge, Kevin, and thank you for replying.
On Sat, Feb 27, 2021 at 09:21:39AM +0100, Helge Oldach wrote:
> Kevin P. Neal wrote on Sat, 27 Feb 2021 03:04:35 +0100 (CET):
> > On Fri, Feb 26, 2021 at 06:25:05PM +0100, Helge Oldach wrote:
> > > Arrigo Marchiori via freebsd-s
1 - 100 of 425 matches
Mail list logo
