7492 was just
>>>>> committed to "main" by rscheff@ with a two week MFC, so it
>>>>> should be in stable/13 soon. Not sure if an errata can be done
>>>>> for it for releng13.0?
>>>>
>>>> That update is reported to be
ted to be causing "rack" related panics:
>>>
>>> https://lists.freebsd.org/pipermail/dev-commits-src-main/2021-May/004440.html
>>>
>>> reports (via links):
>>>
>>> panic: _mtx_lock_sleep: recursed on non-recursive mutex so_snd @
>>&
aller/managers/i386/kernel/sys/modules/tcp/rack/../../../netinet/tcp_stacks/rack.c:10632
>>
>> Still, I have a non-debug update to main building and will
>> likely do a debug build as well. llvm is rebuilding, so
>> the builds will take a notable time.
I got the following built
so
the builds will take a notable time.
> Thanks for isolating this, rick
> ps: Co-incidentally, I've been thinking of buying an RBPi4 as a toy.
I'll warn that the primary "small arm" development/support
folk(s) do not work on the RPi*'s these days, beyond
committing what others provide and
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
et0 or its supporting software
is contributing to the problems that I had reported.
It is interesting that there were no examples of the
content of files reporting a mismatch, just some file
names/paths not finding matches, some with truncated
names or obvious-garbage bytes in names.
Note: T
ain vs. stable/13 vs. release/13.0.0 based? Is it okay to
stick to the base version things are now based on --or do you
want me to update to more recent? (That last only applies if
main or stable/13 is to be put to use.)
> . . . old history deleted . . .
===
Mark Millard
marklmi at yahoo.com
( dsl-o
t; I'll have to figure out how to experiment with such. Things
>>> are at defaults rather generally on the systems. I'm not
>>> literate in the subject areas.
>>>
>>> I'm the only user of the machines and network. It is not
>>> outward facing. It is
they are often broken
>>> in various network device drivers.
>>
>> I'll have to figure out how to experiment with such. Things
>> are at defaults rather generally on the systems. I'm not
>> literate in the subject areas.
>>
>> I'm the only user of the machines an
t; literate in the subject areas.
>
> I'm the only user of the machines and network. It is not
> outward facing. It is a rather small EtherNet network.
>
>> rick
>>
>> ____
>> From: owner-freebsd-sta...@freebsd.org on
>> behal
faults rather generally on the systems. I'm not
literate in the subject areas.
I'm the only user of the machines and network. It is not
outward facing. It is a rather small EtherNet network.
> rick
>
> ________
> From: owner-freebsd-sta...@freebsd.org on
> b
odd result of the diff -r no longer happened: no
differences reported.
For reference (both machines reported):
# uname -apKU
FreeBSD CA72_16Gp_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-n
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
, it seems that there's a non-trivial
amount of code in kern/vfs_lookup.c that's capable of returning
capability-related errors but isn't protected by CAPABILITY_MODE.
This seems undesirable since it means that FreeBSD is defaulting to
being locked down but unless I build it with Capsicum, ther
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
of the
content in:
# more /etc/newsyslog.conf
# configuration file for newsyslog
# $FreeBSD$
#
# Entries which do not specify the '/pid_file' field will cause the
# syslogd process to be signalled when that log file is rotated. This
# action is only appropriate for log files which are written
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)
>> crashes,
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 of stdin,
On 2021-May-5, at 17:01, Yuri Pankov wrote:
> Mark Millard via freebsd-current wrote:
>> Context:
>>
>> # gpart show -pl da0
>> => 40 468862048da0 GPT (224G)
>> 40 532480 da0p1 efiboot0 (260M)
>> 532520 2
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"
On 2021-May-5, at 05:28, Mark Millard wrote:
> On 2021-May-5, at 02:47, Andriy Gapon wrote:
>
>> On 05/05/2021 01:59, Mark Millard via freebsd-current wrote:
>>> I had a:
>>> # zfs list -tall
>>> NAME USED AVAIL
(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"
On 2021-May-5, at 02:47, Andriy Gapon wrote:
> On 05/05/2021 01:59, Mark Millard via freebsd-current wrote:
>> I had a:
>> # zfs list -tall
>> NAME USED AVAIL REFER MOUNTPOINT
>> . . .
>> zroot/DESTDIRs/13_0R-CA72
toolchain metadata from build at CA72_4c8G_ZFS on Tue May
4 10:55:26 PDT 2021
+.info Using cached toolchain metadata from build at CA72_4c8G_ZFS on Tue May
4 16:14:24 PDT 2021
_LOADED_TOOLCHAIN_METADATA=t
COMPILER_VERSION=110001
X_COMPILER_VERSION=110001
I may run a 'target cortex-a7 (so
name -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/BUILDs/13_0R-CA72-nodbg-clang/usr/13_0R-src/arm64.aarch64/sys/GENERIC-NODBG-CA72
arm64 aarch64 1300139 1300139
===
Mark Milla
lly
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)
ad
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 message for the issue.
===
Mark
.
===
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
.strtab STRTAB 51c8
0363 0 0 1
> 50c4-50b8 == 0xC
Note: 0xC+0x4 == 0x10 (the size), so the last 4 bytes
of .gnu_debuglink
> For all I know, some individual byte(s) in the 4 might accid
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 status as well:
DEBUG_FLAGS+=
#
WITH_REPRODUCIBL
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"
On 2021-May-3, at 21:27, Mark Millard wrote:
> On 2021-May-3, at 19:26, Mark Millard wrote:
>
>> On 2021-May-3, at 10:51, Mark Millard wrote:
>>
>>> On 2021-May-3, at 07:47, Ed Maste wrote:
>>>
>>>> On Thu, 29 Apr 2021 at 02:
On 2021-May-3, at 19:26, Mark Millard wrote:
> On 2021-May-3, at 10:51, Mark Millard wrote:
>
>> On 2021-May-3, at 07:47, Ed Maste wrote:
>>
>>> On Thu, 29 Apr 2021 at 02:50, Mark Millard via freebsd-current
>>> wrote:
>>>>
>>
On 2021-May-3, at 10:51, Mark Millard wrote:
> On 2021-May-3, at 07:47, Ed Maste wrote:
>
>> On Thu, 29 Apr 2021 at 02:50, Mark Millard via freebsd-current
>> wrote:
>>>
>>> Files /usr/obj/DESTDIRs/13_0R-CA7-chroot/sbin/ping and
>>> /usr
On 2021-May-3, at 07:47, Ed Maste wrote:
> On Thu, 29 Apr 2021 at 02:50, Mark Millard via freebsd-current
> wrote:
>>
>> Files /usr/obj/DESTDIRs/13_0R-CA7-chroot/sbin/ping and
>> /usr/obj/DESTDIRs/13_0R-CA7-poud/sbin/ping differ
>> Files /usr/obj/DESTDI
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,
>> geom mul
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/whate
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.
---
Andrea
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/whatever is slower than the
boot process and the machine always get stuck with "cannot find
/san_storage (/dev/multipath/...) p
I did 2 test buildworld's based on:
# ~/fbsd-based-on-what-freebsd.sh
branch: releng/13.0
merge-base: ea31abc261ffc01b6ff5671bffb15cf910a07f4b
merge-base: CommitDate: 2021-04-09 00:14:30 +
ea31abc261ff (HEAD -> releng/13.0, tag: release/13.0.0, freebsd/releng/13.0)
13.0: update to RELE
(Changed my email address to the one I used to subscribe to the mailing
list.)
On Wed, Apr 28, 2021 at 10:05 AM Guido Falsi wrote:
Hi,
On 28/04/21 00:12, parv wrote:
> > I had updated FreeBSD, in VirtualBox 5.22 on Windows with EFI, from
> > 12-STABLE
> > to 13-STABLE; upgr
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?
tly the same behavior on iOS 14 without that patch so upgrading to
> a newer version might help.
>
> Best,
> Li-Wen
Sorry, I made another mistake , this is my first time to use a mailing list.
Applying the 12.2-RELEASE-p6 patch doesn’t seem to work, how can I transfer to
On 2021-Apr-25, at 08:14, Graham Perrin wrote:
> On 23/04/2021 08:39, Mark Millard via freebsd-current wrote:
>
>> [3]
>
>
> With regard to mounting ZFS file systems in single user mode
>
> What's currently footnote 3 will probabl
Hello,
I have reinstalled it with GPT/ZFS and your right it's much better. Same search
taking 3-6 seconds so I have deleted now all my old UFS based FreeBSD images.
I wonder how I didn't notice this earlier because I had 12.0, 12.2 base images
and now that I retested them they had the exact
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
We have over 50 FreeBSD VM on KVM for years, several Proxmox (5x,6x) and
Centos (6.x,7.x) servers, and never experienced performance problem like
this.
Your example on fresh new 13 VM:
# time -p find / -name cacert.pem
real 0.28
user 0.00
sys 0.13
12.2 our syslog server:
# time -p find
Hello List,
I hope some other folks out there running FreeBSD on KVM as well. I set up a
base VM while doing so I noticed that the disk operations are very slow. Many
times I edit a file in vim or try to run a command there is a huge lag.
I use UFS as the root filesystem. To have something
://artifact.ci.freebsd.org/snapshot/stable-13/n??-HASHID/
where the ?? is from:
git rev-list --first-parent --count
(as used elsewhere by FreeBSD).
(The HASHID might be just the 12 character prefix instead of the
whole hash-id as well.)
Such a convention would be more independent of dates possibly
being
find for native OpenZFS encryption on FreeBSD
>
> i.e box gets rebooted, enter in passphrase to allow it to boot kind of
> thing from the boot loader prompt ?
I think loader do not support the native OpenZFS encryption yet.
However, you can encrypt non-essential datasets on a boot pool (that is,
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
Booted RPi4 via micrsd card dd'd from:
FreeBSD-13.0-RELEASE-arm64-aarch64-RPI.img
I attempted a bsdinstall onto a USB3 SSD. The following
reports what happened.
# bsdinstall
default keymap Select
Hostname OK
ftp mirror OK
Auto (ZFS) OK
Install Select
stripe OK
[*] da0 OK
Last Chance! da0 YES
On 2021-04-15 14:20, Ferdinand Goldmann wrote:
> I've noticed that ever since update3.freebsd.org is gone (which was in Czech
> republic I think), FreeBSD updates are often quite slow for me (=
> Austria/Europe)
> Especially so for major release upgrades. In fact so slow that
On Fri, 09 Apr 2021 07:32:12 +0900 aventa...@fastmail.fm wrote:
>It makes me think that there should be an offering for two completely
>different audiences:
>(1) FreeBSD core (a very minimal offering for folks that want to build things,
>like a Desktop, etc.)
>(2)
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 gstripe(
Ed,
On Thu, 25 Mar 2021 13:25:44 -0400 Ed Maste wrote:
>Vinum is a Logical Volume Manager that was introduced in FreeBSD 3.0,
>and for FreeBSD 5 was ported to geom(4) as gvinum. gvinum has had no
>specific development at least as far back as 2010 and it is not clear
>how well it
> 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
: 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.
spares on-site for less than what a year of SmartNet coverage would cost.
My server platform of choice when I want a “support server” for this old stuff
has always been FreeBSD. Stock tftpd and ftpd are wonderful, and anyone
professing that those two tiny daemons are “bloat” just hasn’t used Lin
I don't know, ask yourself that, you did the same thing
On 4/4/21 6:21 PM, Glen Barber wrote:
Is it necessary to quote the*entire* email (including checksums)?
Glen
Sent from my phone.
Please excuse my brevity and/or typos.
___
freebsd
> 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 d
> 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 her
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.
On 4/3/2021 4:39 PM, Ed Maste wrote:
I propose deprecating the ftpd currently included in the base system
before FreeBSD 14
On Thu, Apr 1, 2021 at 3:38 PM parv/freebsd wrote:
I am wondering if $SRC_BASE, $MAKEOBJDIRPREFIX, & $WRKDIRPREFIX being
ZFS datasets now would increase compile time. I will found that out in
few weeks (in case of buildworld & kernel) as earlier I had both $SRC_BASE &
$MAKEOBJDIRPRE
Hi there,
I have FreeBSD 12-STABLE in VirtualBox 5.2.44 on Windows 10. All the "disks"
are file-backed virtual disks.
I noticed that after making $HOME a ZFS dataset, there were delays ...
- generally in start of Xorg;
- exhibited by xauth (after using "startx") error me
pdated schedule is available on the FreeBSD Project website:
>
> https://www.freebsd.org/releases/13.0R/schedule/
>
> As usual, we will continue to consider critical bug fixes only for the
> duration of this release cycle.
>
> Thank you for your cooperation, and for your patience.
/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
On 30/03/21 15:35, tech-lists wrote:
Hi,
Recently there was
https://lists.freebsd.org/pipermail/freebsd-security/2021-March/010380.html
about openssl. Upgraded to 12.2-p5 with freebsd-update and rebooted.
What I'm unsure about is the openssl version.
Up-to-date 12.1-p5 instances report OpenSSL
Hi,
Did you mean 12.1-p5 or 12.2-p5 ? I'm asking because you refer to both
12.1-p5 and 12.2-p5 (typo?).
If you meant 12.2-p5: Perhaps the FreeBSD security team did not bump the
version, but "only" backported the patches to version 1.1.1h ?
Regards,
Ruben
On 3/30/21 3:35 PM,
I installed 13.0-RC3 ARM64 from the DVD ISO image
(FreeBSD-13.0-BETA4-arm64-aarch64-dvd1.iso
<http://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/13.0/FreeBSD-13.0-BETA4-arm64-aarch64-dvd1.iso>).
There is no "if_qlnxe" kernel model present on the install media, or on
in under a minute and performance seldom dropped below 1.4 MB/s.
>>
>> Did you find a resolution? I wonder if setting kern.hz is kicking
>> some process(es) to get some time more frequently due to bugs
>> elsewhere in the system (interrupts, IPI handling, wake-ups, etc)
>
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 line
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
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 line "hwpstate_intel0: on cpu0"
If running freebsd-update, a work around
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@
Everything worked as expected.
--
Thanks,
Dean E. Weimer
http://www.dweimer.net/
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-uns
13G throughout hte
> operatioin.
>
>>> > then things got really bad and behaved in a manner that was baffling to
>>> > me. The screen froze again, but stayed frozen after half a minute. I
>>> > clicked on a couple of buttons in Firefox to no effect and t
ss 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
?)
interaction 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
On 2021-Mar-06 10:39:02 -0800, Oleksandr Tymoshenko wrote:
>Peter Jeremy via freebsd-current (freebsd-curr...@freebsd.org) wrote:
>> [Adding arm@ and making it clearer that this is armv8-only]
>>
>> On 2021-Mar-06 20:26:19 +1100, Peter Jeremy
>> wrote:
>> >
[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
>
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
4TB HDDs models)
> >
> > FreeBSD 12.2p4
> >
> >99.45 real34.90 user59.63 sys
> > 100.00 real34.91 user59.97 sys
> >82.95 real 35.98 user60.68 sys
> >
> > FreeBSD 13.0-RC1
> >
>
/output operation count
issues.)
> (13.0-BETA2 showed a large "voluntary context switches"
> difference as well, but I ignore that middle step in
> the version sequence here.)
>
> So I expect publishing the "rm -fr /usr/ports" figures
> from "time -l" would
. I do not know if
the reports should be via separate topic or not but I
doubt the figures with large differences will be the
same for most-modern vs. older: I do not expect notable
IPC from "rm -fr".
> --
>
> FreeBSD 12.2p4
>
>98.18 real35.31 use
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:
> >
s are seeing?
I'll note that someone submitted:
https://lists.freebsd.org/pipermail/freebsd-bugs/2021-March/100124.html
against 13.0-BETA4 for the UFS journaled soft-updates
related performance issue(s). They compared something
to 12.1-RELEASE for illustration.
===
Mark Millard
marklmi
1 - 100 of 2332 matches
Mail list logo
