ow it can work because I had a smaller font before I re-installed over
the previous installation (which originally came from ghostbsd in Aug
2020), so - I assume - it can't be rocket science :-)
I'd appreciate further hints/pointers/RTFMs (though I've tried quite a few
of those).
TIA
Michael
--
Micha
On 2/27/22 16:09, Larry Rosenman wrote:
On 02/27/2022 3:03 pm, Michael Butler wrote:
[ cc list trimmed ]
On 2/27/22 14:16, Larry Rosenman wrote:
I was able to export the rest of the datasets, and re-install
14-CURRENT from a recent snapshot, and restore the datasets I care
about.
I'm now
On boot. Ideas?
These messages may or may not be related. I found both the mfi and mrsas
drivers to be 'chatty' in this way - IOCTL complaints. I ended up
setting the debug flag for mrsas in /etc/sysctl.conf ..
dev.mrsas.0.mrsas_debug=0
There's an equivalent for mfi
Michael
get any
feedback.
Thx
Michael
On Sun, Feb 20, 2022 at 3:12 PM Michael Schuster
wrote:
> Hi,
>
> I'm currently running on -CURRENT from November, though I think the
> message for amdgpu.ko ("kernel: linker_load_file: /boot/modules/amdgpu.ko -
> unsupported file type") s
, 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
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
mailto:mi
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
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 Petter Selasky
-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 0x80
-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
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
bet this
is somehow related to the
t no, I didn't go
through all the output that generated).
Does anyone have an idea what I can do to get past this obstacle? I could
of course always re-install, but that feels like giving in :-)
TIA
Michael
--
Michael Schuster
http://recursiveramblings.wordpress.com/
recursion, n: see 'recursion'
at least AFAIK.
Unless ecosystems provide impls for sendmail(8) I see it very hard to
live without localhost:25 for many cases.
Michael
Hi:
Here are the kernel.full files some of you asked for. Let me know what else
may be helpful to test.
Thanks!
Michael Jung
Notes below * (UPDATED)
* Started fresh
Installed FreeBSD-14.0-CURRENT-amd64-20220113-0910a41ef3b-252413-disc1.iso
with its accompany source tree. Built
Dump header from device: /dev/ada0p2
Architecture: amd64
Architecture Version: 2
Dump Length: 900231168
Blocksize: 512
Compression: none
Dumptime: 2022-02-04 15:48:08 -0500
Hostname: draid.mikej.com
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 14.0-CURRENT #1
P (e.g., Java Mail or other
programming libraries)
Another feature I have forgot:
* .forward support. All mails received on a Unix account shall be
redirected to the user's email address.
Michael
raries)
The issues with certificates and OpenSSL in the base system I have
already extensively dicussed with kevans@ [2].
I hope this can be put into consideration.
Regards,
Michael
[1]
https://www.openssl.org/docs/man1.1.1/man3/SSL_CTX_set_default_verify_paths.html
[2] https://reviews.freebsd.org/
-src
> tuexen@head:~/freebsd-src %
>
> any idea what I did wrong and how to fix it?
>
> Thanks for any hints.
>
> Best regards
> Michael
Timecounter "TSC" frequency 701570048 Hz quality 800
.. but before initializing ipfw as it used to,
Michael
On 12/21/21 12:01, Michael Butler via freebsd-current wrote:
I have an old pentium-3 that also won't boot kernels built after Dec 6th.
I suspect the commits li
currently running git rev e43d081f352 and I have a kernel at git
rev f06f1d1fdb969fa7a0a6eefa030d8536f365eb6e to test later this evening,
Michael
On 12/17/21 15:07, Larry Rosenman wrote:
On 12/17/2021 1:36 pm, Mark Johnston wrote:
On Fri, Dec 10, 2021 at 10:43:19AM -0600, Larry
> On 10. Dec 2021, at 16:57, Chris wrote:
>
> On 2021-12-09 05:36, Sergey V. Dyatko wrote:
>> Hi,
>> Yesterday I tried to upgrade old 13-current (svn rev r368473) to fresh
>> 14-current from git,it looked like this:
>> 1) git pull https://git.freebsd.org/src.git /usr/src
>> 2) cd /usr/src ;
I should have been more specific ..
I'm observing that "/usr/src/release/release.sh -c release-i386.conf"
fails when targeting a i386 build on an amd64 host :-(
On 11/16/21 02:33, Warner Losh wrote:
A meta-build worked for me just now...
Warner
On Mon, Nov 15, 2021 at 9:35
Haven't had time to identify which change caused this yet but I now get ..
===> lib/libsbuf (obj,all,install)
===> cddl/lib/libumem (obj,all,install)
===> cddl/lib/libnvpair (obj,all,install)
===> cddl/lib/libavl (obj,all,install)
ld: error:
On 11/3/21 11:13, Konstantin Belousov wrote:
On Wed, Nov 03, 2021 at 11:05:11AM -0400, Michael Butler via freebsd-emulation
wrote:
On 11/3/21 10:36, Ed Maste wrote:
The kgdb back-trace isn't any more enlightening to me :-(
__curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
55
On 11/3/21 10:36, Ed Maste wrote:
On Tue, 2 Nov 2021 at 18:32, Michael Butler via freebsd-emulation
wrote:
Before reporting this, I rebuilt world including kernel, all kmods and
virtualbox itself to no avail :-(
Thanks for confirming.
Now that the WARN_ON noise is disabled by default would
On 11/2/21 17:48, Cy Schubert wrote:
In message <36923A7F-23DE-490D-B1FA-A8B064740BD6@unrelenting.technology>,
Greg
V via freebsd-current writes:
On November 2, 2021 5:16:35 PM GMT+03:00, Michael Butler via freebsd-current
wrote:
On current as of this morning (I haven't tried to bise
On current as of this morning (I haven't tried to bisect yet) ..
FreeBSD toshi.auburn.protected-networks.net 14.0-CURRENT FreeBSD
14.0-CURRENT #42 main-a670e1c13a: Tue Nov 2 09:29:28 EDT 2021
r...@toshi.auburn.protected-networks.net:/usr/obj/usr/src/amd64.amd64/sys/TOSHI
amd64
.. with
This seems to have gone away after
https://freshbsd.org/freebsd/src/commit/70f51f0e474ffe1fb74cb427423a2fba3637544d
Not sure if the bug that commit fixes was the underlying cause,
Michael
On 10/25/21 11:40, Nuno Teixeira wrote:
Same here:
kldxref /boot/kernel
failed to read progbits
Well this is different .. I did a full rebuild (after "rm -rf
/usr/obj/*") this morning and now see ..
===> linux_common (install)
install -T release -o root -g wheel -m 555 linux_common.ko /boot/kernel/
install -T dbg -o root -g wheel -m 555 linux_common.ko.debug
red *active_cred __unused, struct thread *td __unused)
+#endif
{
/* XXX need to define flags for st_mode */
On 10/11/21, Michael Butler via freebsd-current
wrote:
After the latest freebsd version bump in param.h, I tried to rebuild the
DRM modules. It failed with ..
--- dma-bu
After the latest freebsd version bump in param.h, I tried to rebuild the
DRM modules. It failed with ..
--- dma-buf.o ---
/usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.5.19_4/drivers/dma-buf//dma-buf.c:121:1:
error: conflicting types for 'dma_buf_stat'
dma_buf_stat(struct file *fp,
On 10/7/21 20:19, Konstantin Belousov wrote:
On Thu, Oct 07, 2021 at 05:43:14PM -0400, Michael Butler wrote:
On 10/7/21 16:52, Mark Johnston wrote:
On Thu, Oct 07, 2021 at 04:18:28PM -0400, Michael Butler via freebsd-current
wrote:
On 10/7/21 15:39, Konstantin Belousov wrote:
On Thu, Oct 07
On 10/7/21 16:52, Mark Johnston wrote:
On Thu, Oct 07, 2021 at 04:18:28PM -0400, Michael Butler via freebsd-current
wrote:
On 10/7/21 15:39, Konstantin Belousov wrote:
On Thu, Oct 07, 2021 at 03:28:44PM -0400, Michael Butler via freebsd-current
wrote:
While building a local release bundle
On 10/7/21 15:39, Konstantin Belousov wrote:
On Thu, Oct 07, 2021 at 03:28:44PM -0400, Michael Butler via freebsd-current
wrote:
While building a local release bundle, I sometimes get bsdtar failing (and
dumping core) as follows below. Worse, as can be seen below, it doesn't stop
the build
While building a local release bundle, I sometimes get bsdtar failing
(and dumping core) as follows below. Worse, as can be seen below, it
doesn't stop the build unless I happen to notice and it yields an
incomplete package.
a usr/src/sys/netgraph/ng_checksum.h
a
On Tue, 14 Sep 2021 09:02:46 +
Gary Jennejohn wrote:
> On Mon, 13 Sep 2021 21:30:02 -0400
> Michael Butler via freebsd-current
> wrote:
>
> > After commit ddedf2a11eb20af1ee52cb3da70a57c21904af8f date fails to
> > recognize any configured timezone whe
After commit ddedf2a11eb20af1ee52cb3da70a57c21904af8f date fails to
recognize any configured timezone when WITH_DETECT_TZ_CHANGES is not set.
For example ..
imb@vm01:/home/imb> date
Tue Sep 14 01:25:57 2021
Every other daemon also thinks it's running in UTC+0 :-(
When libc is recompiled
6260U+%40+1.80GHz=2671
>
> Cheers,
> --
> Jeremie Le Hen
> j...@freebsd.org
>
>
regards
Michael
--
Michael Schuster
http://recursiveramblings.wordpress.com/
recursion, n: see 'recursion'
ding (see
https://www.freebsd.org/cgi/man.cgi?build(7)) is set.
HTH
Michael
--
Michael Schuster
http://recursiveramblings.wordpress.com/
recursion, n: see 'recursion'
GZ._TMP due to previous error (AE_AML_PACKAGE_LIMIT)
(20210604/psparse-689)
... roughly every ten seconds.
I'd be grateful for any pointers or advice to get my power management fixed.
I have yet to test w/o graphics driver (as someone suggested I do).
regards & TIA
Michae
there any (security) reasons why this might be a bad idea?
Best,
Michael
--
Michael Gmelin
On 7/29/21 6:09 AM, Michael Gmelin wrote:
On Wed, 28 Jul 2021 16:02:30 -0400
Ed Maste wrote:
On Wed, 28 Jul 2021 at 15:15, Michael Butler via freebsd-current
wrote:
What prompted the question was my (obviously poor) attempt to debug
and resolve this failure when attempting to build
On Wed, 28 Jul 2021 16:02:30 -0400
Ed Maste wrote:
> On Wed, 28 Jul 2021 at 15:15, Michael Butler via freebsd-current
> wrote:
> >
> > What prompted the question was my (obviously poor) attempt to debug
> > and resolve this failure when attempting to build a release
On 7/28/21 1:36 PM, Warner Losh wrote:
On Wed, Jul 28, 2021 at 11:31 AM Michael Butler via freebsd-current <
freebsd-current@freebsd.org> wrote:
I tripped over this while trying to build a local release ..
imb@toshi:/home/imb> pkg --version | awk -F. '{print $$1 * 1 + $$2 *
On Wed, 28 Jul 2021 13:29:20 -0400
Michael Butler via freebsd-current wrote:
> I tripped over this while trying to build a local release ..
>
> imb@toshi:/home/imb> pkg --version | awk -F. '{print $$1 * 1 +
> $$2 * 100 + $$3}'
> 10001
>
> imb@toshi:/home/imb&g
NVM .. it's the escaping of '$' ..
On 7/28/21 1:29 PM, Michael Butler via freebsd-current wrote:
I tripped over this while trying to build a local release ..
imb@toshi:/home/imb> pkg --version | awk -F. '{print $$1 * 1 + $$2 *
100 + $$3}'
10001
imb@toshi:/home/imb> pkg --version
I tripped over this while trying to build a local release ..
imb@toshi:/home/imb> pkg --version | awk -F. '{print $$1 * 1 + $$2 *
100 + $$3}'
10001
imb@toshi:/home/imb> pkg --version
1.17.1
Is this expected?
imb
> On 16. Jul 2021, at 19:38, Warner Losh wrote:
>
> On Fri, Jul 16, 2021 at 6:14 AM Thomas Laus wrote:
>
>> Group:
>>
>> This is an issue for more than just CURRENT. The 'usr/src/UPDATING'
>> file has the instructions for updating the ZFS bootblocks but not the
>> EFI partition. I
a lot
of sense to me.
-m
> Is there a
> good reason for this convention, or is it just inertia?
> -Alan
--
Michael Gmelin
On Wed, 30 Jun 2021 20:05:43 +0200
"O. Hartmann" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Am Mon, 28 Jun 2021 23:34:44 +0200
> Michael Gmelin schrieb:
>
> > > On 28. Jun 2021, at 22:41, O. Hartmann
> > > wrot
> On 28. Jun 2021, at 22:41, O. Hartmann wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
>
> Hello,
>
> we ran into serious trouble here with an www/nextcloud installation on a
> recent 14-CURRENT
> (FreeBSD 14.0-CURRENT #23 main-n247612-e6dd0e2e8d4: Mon Jun 28 18:08:20
> On 13. Jun 2021, at 20:50, Ronald Klop wrote:
>
> What do you have configured as prompt? Or shell startup script?
> Does it contain a call to git?
>
I agree that this smells like a prompt that calls "git status" or something
similar (when on the FreeBSD source tree on an rpi, 15
> On 11. Jun 2021, at 00:42, Cameron Katri via freebsd-current
> wrote:
>
> On 6/10/21 6:26 PM, Kevin Oberman wrote:
>> I have never seen it return anything from /usr/src.
>
> It seems to return stuff from /usr/src for me
> > whereis cc
> cc: /usr/bin/cc /usr/share/man/man1/cc.1.gz
>
> On 11. Jun 2021, at 00:28, Kevin Oberman wrote:
>
> On Wed, Jun 9, 2021 at 2:02 AM Michael Gmelin wrote:
>
>>
>>
>>>> On 9. Jun 2021, at 01:15, Ian Lepore wrote:
>>>
>>> On Tue, 2021-06-08 at 15:11 -0700, Rodney W. Grimes wro
; if it can't find the sources
directly, so e.g., in case of `whereis -s ls', it will get through the
results of `locate '*'/ls` and see if they match "^/usr/src" (or
whatever you gave as source dir using -S).
Therefore if
locate '*'/ntp.conf | grep "^/usr/src"
gives you a result, then `whereis -s ntp.conf' will too.
See also
https://cgit.freebsd.org/src/tree/usr.bin/whereis/whereis.c#n607
Michael
(re-sent, as the previous mail bounced from the list)
--
Michael Gmelin
> On 9. Jun 2021, at 04:17, grarpamp wrote:
>
> On 4/17/20, Ryan Moeller wrote:
>>
On Apr 17, 2020, at 4:56 PM, Pete Wright wrote:
>>>
>>> On 4/17/20 11:35 AM, Ryan Moeller wrote:
OpenZFS brings many exciting features to FreeBSD, including:
* native encryption
>>> Is there
f it called whereis(1).
>>
>
> revolution > whereis ntp.conf
> ntp.conf:
> revolution > whereis netif
> netif:
That line might make it to a shirt one day:
> revolution > whereis services
;)
Michael
On Thu, 3 Jun 2021 15:09:06 +0200
Michael Gmelin wrote:
> On Tue, 1 Jun 2021 13:47:47 +0200
> Michael Gmelin wrote:
>
> > Hi,
> >
> > Since upgrading servers from 12.2 to 13.0, I get
> >
> > Fssh_packet_write_wait: Connection to 1.2.3.4 por
On 6/8/21 3:42 PM, Juraj Lutter wrote:
On 8 Jun 2021, at 21:38, bob prohaska wrote:
FWIW, same problem seen here. In an added twist, git pull (hoping for
a fix) fails also:
root@www:/usr/src # git pull
error: cannot lock ref 'refs/remotes/freebsd/vendor/openzfs/legacy':
being "September 2020".
> >
> > So: 2020-Oct through 2021-Apr are completely missing.
> >
> > Then, going for more detail for 2020-Sep and 2021-May . . .
> >
> > https://lists.freebsd.org/archives/freebsd-hackers/2021-May/date.html
> > shows "Starting Tue May 18 2021 - 21:07:44 UTC".
> >
> > https://lists.freebsd.org/pipermail/freebsd-hackers/2020-September/date.html
> > shows "Ending: Tue Sep 15 14:12:20 UTC 2020".
> >
> > So there are about 2 more half-months missing.
> >
> > Some other lists have other date ranges, some similar,
> > some not.
>
> This missing month are being populated right now
Will historic links still work though (so that old references work and
current google results are ok)?
Just stumbled over this one:
https://lists.freebsd.org/archives/freebsd-jail/2017-March/003360.html
Cheers
Michael
>
> Best regards,
> Bapt
--
Michael Gmelin
> On 6. Jun 2021, at 01:44, Warner Losh wrote:
>
>
>
>
>> On Sat, Jun 5, 2021, 5:29 PM Steve Kargl
>> wrote:
>> On Sun, Jun 06, 2021 at 01:04:46AM +0200, Michael Gmelin wrote:
>> >
>> > p.s. If you go to https://lists.fr
> On 6. Jun 2021, at 01:00, Michael Gmelin wrote:
>
>
>
>
>>> On 6. Jun 2021, at 00:53, Steve Kargl
>>> wrote:
>>>
>> It seems someone has tried to migrate the mailing list archives
>> from mailman to some new fangle code. This ha
021-June/index.html
As we still have mailman archives and https://docs.freebsd.org/mail/, merging
or cross linking would certainly be useful.
Michael
> --
> Steve
On Fri, 28 May 2021 20:50:52 +0200
Michael Gmelin wrote:
> On Fri, 28 May 2021 20:37:14 +0200
> Mathieu Arnold wrote:
>
> > On Wed, May 19, 2021 at 07:32:43PM +0200, Michael Gmelin wrote:
> > >
> > >
> > > On Wed, 19 May 20
On Tue, 1 Jun 2021 13:47:47 +0200
Michael Gmelin wrote:
> Hi,
>
> Since upgrading servers from 12.2 to 13.0, I get
>
> Fssh_packet_write_wait: Connection to 1.2.3.4 port 22: Broken pipe
>
> consistently, usually after about 11 idle minutes, that's with and
> wi
, same everything). On 12.2
before the update: Connection stays open for hours. After the update
(same server): connections breaks consistently after < 15 minutes (this
is with unaltered configurations, no *AliveInterval configured on
either side of the connection).
Thanks
Michael
--
Michael Gmelin
On Fri, 28 May 2021 20:37:14 +0200
Mathieu Arnold wrote:
> On Wed, May 19, 2021 at 07:32:43PM +0200, Michael Gmelin wrote:
> >
> >
> > On Wed, 19 May 2021 19:09:06 +0200
> > Kurt Jaeger wrote:
> >
> > > Hi!
> > >
> > >
What about using "."? Or "/" (which would match the muscle memory of "search"
in less/more/vi/some browsers)?
-m
> On 7. May 2021, at 23:05, Maxim Sobolev wrote:
>
> Replace '*' with ^T perhaps and catch SIGINFO? 樂
>
> -Max
>
>> On Fri., May 7, 2021, 10:11 a.m. Shawn Webb,
>> wrote:
>>
On Wed, 28 Apr 2021 21:45:03 +0200
Michael Gmelin wrote:
> > On 28. Apr 2021, at 21:37, Stefan Esser wrote:
> >
> > Am 28.04.21 um 20:44 schrieb Michael Gmelin:
> >>
> >>
> >>> On Wed, 28 Apr 2021 20:00:38 +0300
> >>> Yuri P
> On 28. Apr 2021, at 21:37, Stefan Esser wrote:
>
> Am 28.04.21 um 20:44 schrieb Michael Gmelin:
>>
>>
>>> On Wed, 28 Apr 2021 20:00:38 +0300
>>> Yuri Pankov wrote:
>>>
>>> Not sure if it's just me, but I'm seeing a bit of git wei
files (basically
every line). It's all whitespace characters, as `git diff -w' is empty.
Turns out EOLs changed, I suspect this is due to the eol overrides in
contrib/bc/.gitattributes. If I comment those out, "git diff" is silent
again.
Cheers,
Michael
>
> $ cd freebsd-src
> $ gi
t carefully
> chosen, but haven't found any sound/audio specific mailing lists.
>
Just out of curiosity: Going to chrome://settings/content/microphone
won't allow you to select the input device to use? (it seems like having
the select box in there is platform specif
> On 16. Apr 2021, at 19:29, Rodney W. Grimes
> wrote:
>
>
>>
>> n Fri, Apr 16, 2021 at 11:36 AM Rainer Hurling wrote:
>>>
>>> While viewing sys/sys/param.h I noticed that the comment of the
>>> definition of __FreeBSD_version is probably out of date.
>>>
>>> Since the switch to Git,
ent_preview(1)".'.
I don't know who has the access permissions and time to fix the problem
or at least implement a temporary workaround.
Best,
Michael
> when I tried
> > putting "base ", so I'm wondering how do you link
> > to git revisions?
>
> We'll (bugmeist
This is likely fixed as of ~30 mins ago on commit
e8b9c508b7ae5be618ada089103468c400e465cd
The cause appears to have been commit d36d6816151705907393889
imb
On 4/9/21 4:55 PM, Yasuhiro Kimura wrote:
yasu@rolling-vm-freebsd1[1044]% uname -a
FreeBSD rolling-vm-freebsd1.home.utahime.org
router is going to return an
> icmp message, and if configured to do so frag the packets and
> forward them on, no retransmission would occur as the DF flag
> is not normally set unless explicitly requested.
1. Isn't a router either fragmenting a packet and forwarding the
fragments or sending
cally "whatever Mozilla did", as the certificates are
> imported from NSS.
>
> Regards,
> Christoph
>
--
Michael Gmelin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
he one busy.
> dtrace -x stackframes=100 -n 'profile-99 /arg0 && pid == 31/ {
> @[stack()] = count(); } tick-60s { exit(0); }'
>
> One striking thing is how many times hpet_get_timecount is present...
Does tuning of
- vfs.zfs.scrub_delay
- vfs.zfs.resilver_min_time_ms
-
ers crossed, whatever it may be.
Best,
Michael
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
lowest
- different kern.eventtimer.timer
Try running with powerd disabled.
Try disabling acpi_thermal (debug.acpi.disabled="thermal") as stated in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234455#c9
Certainly someone else has better ideas though.
Best,
Michael
--
Michael G
On 3/13/21 3:00 PM, Hartmann, O. wrote:
On Sat, 13 Mar 2021 19:52:47 + (UTC)
Filippo Moretti via freebsd-current wrote:
I had the same problem in console modeFiippo
On Saturday, March 13, 2021, 8:33:57 PM GMT+1, Stefan Esser
wrote:
Am 13.03.21 um 20:17 schrieb Hartmann, O.:
o the first difficulty is to find
> man page in which possible tunable may be explained. If the problem is
> releted to some device, it is most hopeful to check its man page. But
> in this case, even after reading the commit message, I had no idea
> which man page to check.
>
see
Hi:
So I've had a crash - below is the relevant information.
FreeBSD firewall.mikej.com 13.0-CURRENT FreeBSD 13.0-CURRENT #22 r369328: Sun
Feb 21 09:26:46 EST 2021
Seems there's a typo in this when INVARIANTS is not turned on ..
diff --git a/sys/kern/kern_jail.c b/sys/kern/kern_jail.c
index 48c91a95bf..342af50462 100644
--- a/sys/kern/kern_jail.c
+++ b/sys/kern/kern_jail.c
@@ -2671,7 +2671,7 @@ prison_free_not_last(struct prison *pr)
Any ideas what broke this?
--
>>> Kernel build for GENERIC completed on Tue Feb 9 20:48:05 UTC 2021
--
>>> Kernel(s) GENERIC built in 465 seconds, ncpu: 8, make -j8
it in sshd_config,
therefore it is not necessary to add libfido2 as a dependency to base.
Michael
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-uns
he project (we won’t change
it as part of developing FreeBSD)
Cheers,
Michael
>
> ---
> Yasuhiro Kimura
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscrib
the ABI change. It downloaded a new pkg
> program and then upgraded all of my packages because of the change in ABI.
>
There was a problem with xorg-server which made it build without udev on 14.
Try reinstalling xorg-server from ports (something like: portsnap fetch
extr
gt; ---
> Kazuhiko Kiriyama
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to
> "freebsd-current-unsubscr...@freebsd.org"
--
Michael Gmelin
___
I have a few machines on which I've been hesitant to run 'zpool upgrade'
as I'm not sure of the (boot?) implications. They report like this ..
imb@toshi:/home/imb> uname -a
FreeBSD toshi.auburn.protected-networks.net 14.0-CURRENT FreeBSD
14.0-CURRENT #25 main-eb61de5b78: Fri Jan 22 10:03:02
:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252757
WITHOUT_TESTS_SUPPORT PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252843
I am happy to test patches!
All the best,
Michael
___
freebsd-current@freebsd.org mailing list
https
On 1/20/21 5:47 PM, Michael Dexter wrote:
Two have been fixed and PRs exist for the majority of them with some
possible fixes for those who know the code best to consider. One broken
option is a recent regression while one pair,
WITHOUT_LIBTHR/WITHOUT_LIBPTHREAD is quite stale
ppy to send individuals my minimum VM script and fortunately,
it is out-of-date with every build option fix.
All the best,
Michael
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, se
l to (re)start daemons (plus, as a safety measure, configure
"_fib=2" within the jail's /etc/rc.conf).
Cheers,
Michael
--
Michael Gmelin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
> On 2. Jan 2021, at 19:44, Graham Perrin wrote:
>
> FreeBSD mowa219-gjp4-8570p 13.0-CURRENT FreeBSD 13.0-CURRENT #0
> main-c530-g8b4c3a03f: Fri Jan 1 15:27:15 GMT 2021
> root@mowa219-gjp4-8570p:/usr/obj/usr/src/freebsd-current/amd64.amd64/sys/GENERIC-NODEBUG
> amd64
>
>
Christian Weisgerber wrote:
>
> Michael Grimm:
>> Correct? If so I wonder how future security advisories and errata notices
>> will be composed. Will there be a date of the commit besides its hash being
>> reported?
>
> For over TWENTY YEARS, FreeBSD adv
> On 25. Dec 2020, at 01:43, KIRIYAMA Kazuhiko wrote:
>
> Hi, all
>
> I've found RISC-V images in snapshots/ISO-IMAGES. Is there
> any machine RISC-V implemented so far ?
You mind find some information you need at:
https://wiki.freebsd.org/riscv
Be
Correction:
> On 24. Dec 2020, at 15:11, Michael Grimm wrote:
>
> In the past I could easily judge if there was a need to buildworld or
> buildkernel: If uname shows a larger revision number than those in advisories
> or notices.
In the past I could easily judge if t
?
Thanks and regards,
Michael
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ng git-worktree.
If I understand git-worktree(1) correctly I will most probably not need it,
because I will only follow one single branch stable/12, and soon stable/13. Or
do I miss something important?
Thanks and regards,
Michael
___
freebsd-curr
101 - 200 of 1691 matches
Mail list logo
