lowing:
VM:
CPU: x4
Memory: 8GB
Disk: 100GB SATA
Host:
CPU: Intel Core i7 4770S
Memory: 16GB
Disk: 2TB SATA
OS: 64bit Windows 10 Enterprise 1803
Best Regards.
---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
https://lists.f
From: Yasuhiro KIMURA
Subject: Fatal trap 9 when rebooting after installkernel on VirtualBox VM
Date: Sun, 02 Sep 2018 23:51:45 +0900 (JST)
> I'm tracking head with VirtualBox VM. Everytime new snapshot is
> released I update to same revision. So buildworld, buildkernel and
>
Hello.
On 13-CURRENT r339548 build of lang/perl5.26 fails with configure error.
--
yasu@rolling-vm-freebsd1[2100]% uname -a
FreeBSD rolling-vm-freebsd1.home.utahime.org 13.0-CURRENT FreeBSD 13.0-CURRENT
r339548 GENERIC_UTAHIME
From: Yasuhiro KIMURA
Subject: Regression of dtrace on 13-CURRENT
Date: Thu, 25 Oct 2018 14:46:00 +0900 (JST)
> So there is regression about dtrace between r339436 and r339548.
I submitted this problem to Bugzilla.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675
---
Yasuhiro KIM
JDIRPREFIX -C /usr0/freebsd/base/stable/12
yasu@eastasia[2404]%
I used env(1) to customize but I got same results when I use
src-env.conf.
Then is this just bug? Or are there any reason that behavior is
changed from 11.x to 12.x and later?
Best Regards.
---
Yasuh
From: Yasuhiro KIMURA
Subject: Getting value of MAKEOBJDIRPREFIX with 'make -V MAKEOBJDIRPREFIX'
Date: Sat, 17 Nov 2018 01:57:58 +0900 (JST)
> Then is this just bug? Or are there any reason that behavior is
> changed from 11.x to 12.x and later?
To find when behavior changed
From: Yasuhiro KIMURA
Subject: Re: Getting value of MAKEOBJDIRPREFIX with 'make -V MAKEOBJDIRPREFIX'
Date: Sat, 17 Nov 2018 09:18:53 +0900 (JST)
> As far as I read this, behavior change of 'make -V MAKEOBJDIRPREFIX`
> doesn't seem intentional. So I'll submit
?
Best Regards.
---
Yasuhiro KIMURA
___
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"
it's 100% reproducible on my P5020 machine.
Thank you for reply. I updated my system to r342006 and now the
problem disappeared.
Just FYI.
---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/free
It is fixed with poudriere 3.3.1.
---
Yasuhiro KIMURA
___
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"
Dear Committers,
Would someone please commit following bug report?
Bug 236564 - periodic.sh: Anticongestion function does not work as is expected.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236564
Best Regards.
---
Yasuhiro KIMURA
___
freebsd
://www.utahime.org/FreeBSD/FreeBSD.13-CURRENT.amd64.r352669.screenshot.1.png
https://www.utahime.org/FreeBSD/FreeBSD.13-CURRENT.amd64.r352669.screenshot.2.png
Any idea?
Regards.
---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
https
From: David Wolfskill
Subject: Re: panic: sched_pickcpu: Failed to find a cpu.
Date: Wed, 25 Sep 2019 08:08:15 -0700
> Yes; mav@ fixed it with r352677.
Thanks. I'll update source tree and rebuild kernel.
Regards.
---
Yasuhiro KIMURA
___
From: Yasuhiro KIMURA
Subject: Re: panic: sched_pickcpu: Failed to find a cpu.
Date: Thu, 26 Sep 2019 00:12:48 +0900 (JST)
>> Yes; mav@ fixed it with r352677.
>
> Thanks. I'll update source tree and rebuild kernel.
I updated kernel to r352685 and now system boots successful
sd1[2064]%
Why such difference happens?
---
Yasuhiro KIMURA
___
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"
ion' isn't executed by normal upgrade steps. So
it's a bug and should be fixed.
---
Yasuhiro KIMURA
___
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"
From: Yasuhiro KIMURA
Subject: Re: /etc/os-release isn't created
Date: Mon, 25 Nov 2019 08:13:19 +0900 (JST)
> I recieved report by private mail that /etc/os-release is created only
> when 'make distribution' is executed. And I found that's exactly what
> is wri
ted in /var/tmp/temproot when running
> mergemaster but not moved to /
Thank you for investigation. Then is is bug of mergemaster?
---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
T
0 because remnants of BIND are still left.
Best Regards.
---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
y only if either tinderbox or
poudriere are used, or all packages have to be rebuilt anyway if pkgng
is used?
Best Regards.
---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To un
know current status about it.
Best Regards.
---
Yasuhiro Kimura
From: Yasuhiro Kimura
Subject: Re: Boot hangs up with Alderlake's intel GbE NIC
Date: Tue, 24 May 2022 02:02:20 +0900 (JST)
>> 2 months ago I updated my home server to Intel Alderlake Core i3 12100
>> and GIGABYTE H610I DDR4 (rev. 1.0) motherboard.
>>
>> The lat
n should do
`make delete-old-libs`.
If you use official binary packages, then you should wait until all
packages are built with OpenSSL 3.0.
HTH.
---
Yasuhiro Kimura
After updating my 14.0-CURRENT amd64 system from
main-n264162-f58378393fb to main-n264268-ff4633d9f89, kernel crashes
with panic as following.
https://people.freebsd.org/~yasu/FreeBSD-14-CURRENT-amd64-main-n264268-ff4633d9f89.20230721.panic.png
---
Yasuhiro Kimura
From: Yasuhiro Kimura
Subject: Kernel panic after updating 14-CURRENT amd64 to
main-n264268-ff4633d9f89
Date: Sat, 22 Jul 2023 02:50:23 +0900 (JST)
> After updating my 14.0-CURRENT amd64 system from
> main-n264162-f58378393fb to main-n264268-ff4633d9f89, kernel crashes
> with panic as
:0:3:0: class=0x02 rev=0x02 hdr=0x00 vendor=0x8086 device=0x100e
subvendor=0x8086 subdevice=0x001e
vendor = 'Intel Corporation'
device = '82540EM Gigabit Ethernet Controller'
class = network
subclass = ethernet
Regards.
---
Yasuhiro Kimura
And it finished successfully.
Full build log:
https://people.freebsd.org/~yasu/poudriere/data/logs/bulk/curamd64-default/2023-08-15_15h42m59s/logs/openvpn-2.6.5.log
HTH.
---
Yasuhiro Kimura
.panic.png
---
Yasuhiro Kimura
ing-vm-freebsd4[182]#
What is wrong?
---
Yasuhiro Kimura
From: Glen Barber
Subject: Re: FreeBSD 14.0-BETA3 Now Available
Date: Fri, 22 Sep 2023 23:32:53 +
> On Sat, Sep 23, 2023 at 08:16:47AM +0900, Yasuhiro Kimura wrote:
>> I tried to update from 14.0-BETA2 to 14.0-BETA3 with freebsd-update(8)
>> but it fai
iffcult there is good chance you can select
and buy the PC that can update BIOS with similar way as above.
HTH.
---
Yasuhiro Kimura
From: Yasuhiro KIMURA
Subject: Re: /etc/os-release isn't created
Date: Mon, 25 Nov 2019 10:27:36 +0900 (JST)
> From: "Herbert J. Skuhra"
> Subject: Re: /etc/os-release isn't created
> Date: Mon, 25 Nov 2019 02:11:35 +0100
>
>> - mergemaster runs '
again. Then the problem was reproduced.
Does anybody else experience it?
---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-uns
From: Yasuhiro KIMURA
Subject: After update to r357104 build of poudriere jail fails with 'out of
swap space'
Date: Sat, 25 Jan 2020 23:43:28 +0900 (JST)
> I use VirtualBox to run 13-CURRENT. Host is 64bit Windows 10 1909 and
> spec of VM is as following.
>
> * 4 CPU
&g
ct, I
> can't find amd
> on this system. Has amd been removed and all we have for automatically
> mounting
> filesystems autofs?
Amd is not build by default now and will be removed from base. But you
can continue using it by installing sysutils/am-utils
e from r357653 to r357969 and boot completes
successfully. My environment is guest of VirtualBox on Windows, 4 CPUs
and 8GB of memory. And root is ZFS.
---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/li
is too much
> for bi-sect :-(
Then why don't you try FreeBSD snapshot?
https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/13.0/
Currently there are r357276, r357606 and r357847 of boot images. If
your H/W boots successfully with r357276 you can narrow ran
ail/freebsd-ports/2020-February/117710.html
---
Yasuhiro KIMURA
___
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"
ith either 11.4-RELEASE and
12.1-RELEASE.
---
Yasuhiro KIMURA
___
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"
From: Yasuhiro KIMURA
Subject: `shutdown -p now` fails to power off with VirtualBox UEFI boot
Date: Fri, 19 Jun 2020 05:23:48 +0900 (JST)
> I have VirtualBox VM running 13-CURRENT. In order to switch from
> legacy BIOS to UEFI I reinstalled OS by using
> FreeBSD-13.0-CURRENT-amd64
From: Yasuhiro KIMURA
Subject: Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot
Date: Mon, 22 Jun 2020 16:45:23 +0900 (JST)
> I tried bisect and found this problem happens with r342108 and
> after. Commit message of r342108 says as following.
>
> yasu@rolling-vm-f
of this tunable mean that there are some UEFI
implementations that have problem with power off functionality?
(And VirtualBox is unfortunately one of such implementations?)
---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
ht
u for reply.
---
Yasuhiro KIMURA
___
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"
is necessary when
installing OS even if 32bit libraries aren't instlled?
Best Regards.
---
Yasuhiro KIMURA
___
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"
#x27;make buildworld'
yasu@rolling-vm-freebsd1[1004]%
------
What is wrong?
---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To
/src/Makefile. But update of poudriere jail is failed with
>> error.
>
> Please see: https://reviews.freebsd.org/D26395
Thank you for quick reply. Then I'll wait until this review is
committed.
---
Yasuhiro KIMURA
___
freebsd-cur
rce tree is updated to r365643 or later, take following steps
at first.
# cd /usr/src/bin/cp
# make
# make install
Otherwise `make buildworld` fails with same error as that of update of
poudriere jail.
---
Yasuhiro KIMURA
___
freebsd-current@freebsd.
-- all_subdir_share ---
> --- all_subdir_lib ---
>
> The error is recurringFilippo
1. Update source tree to r365643 or later.
2. cd /usr/src/bin/cp
3. make
4. make install
5. cd /usr/src
6. make buildworld
---
Yasuhiro KIMURA
___
freebsd-
o rollback zroot/poudriere/jails/curamd64-original-ref/02 to
prepkg
How should I fix it?
Best Regards.
---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
hanks for suggestion. But I already fixed the problem by making clean
install of base system with latest snapshot.
---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send an
_common.ko - unsupported file type
KLD linprocfs.ko: depends on linux_common - not available or version mismatch
linker_load_file: /boot/kernel/linprocfs.ko - unsupported file type
--
What's wrong?
Best Regards.
---
From: Yasuhiro KIMURA
Subject: Fails to load linprocfs
Date: Sat, 07 Nov 2020 05:11:20 +0900 (JST)
> I updated both host and poudriere jail from r367172 to r367418. But
> after that `poudriere bulk` fails as following.
>
(snip)
>
> What's wrong?
Two people told me fol
can't remember exactly when,
similar situation happened within a week.
---
Yasuhiro KIMURA
___
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"
s down if it is not all mirrors.
I use 192.50.199.249. But svnweb.freebsd.org had also been lagging. So
It doesn't seem the problem was specific to one mirror.
---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/
{
zfs unshare -a
zfs unmount -a
}
--
At this point syslog process still running and it opens some files
under /var/log. So it make sence that `zfs unmount -a` results in th
Dear Committers,
From: Yasuhiro KIMURA
Subject: Re: /etc/os-release isn't created
Date: Wed, 22 Jan 2020 15:56:54 +0900 (JST)
> I created patch adding logic that handles symbolik link to mergemaster
> and submitted it to following bug report.
>
> Bug 242212 usr.sbin/mergemast
src.git /somewhere/you/want/to/chechout
2. Build poudriere jail with source tree checked out at step 1
poudriere jail -c jailname -m src=/somewhere/you/want/to/chechout -b
Then you can update jail to any commit hash with following command.
git -C /somewhere/you/want/to/chechout checkout (h
can say is
* It happens only after I login in the VM and do something for a
while. If I boot the VM and shut it down immediately, it never
happens.
* When the problem happens, one or more unkillable processes seem to
be left.
---
Yasuhiro Kimura
__
From: Yasuhiro Kimura
Subject: Re: Waiting for bufdaemon
Date: Fri, 15 Jan 2021 20:10:30 +0900 (JST)
> I have been experiencing same problem with my 13-CURRENT amd64
> VirtualBox VM for about a month. The conditions that the problem
> happens are unclear and all what I can say is
a/vga_isa.c: .d_flags = D_NEEDGIANT,
sys/kern/kern_conf.c: if (devsw->d_flags & D_NEEDGIANT) {
sys/kern/kern_conf.c: if (devsw->d_flags & D_NEEDGIANT) {
sys/kern/kern_conf.c: } else if (devsw->d_flags & D
roblem still happens with my
environment.
---
Yasuhiro Kimura
___
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"
I must have missed the
> announcement.
https://lists.freebsd.org/pipermail/dev-commits-src-all/2021-January/001588.html
---
Yasuhiro Kimura
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To
e git to pull the exact sources that match
> this specifc kernel?
cd /usr
git clone https://git.freebsd.org/src.git
cd src
git checkout 3cc0c0d66a0
---
Yasuhiro Kimura
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/list
est/packagesite.txz:
>> Not Found
>> Unable to update repository FreeBSD
>> Error updating repositories!
All what you can do is to wait until build of offical packages for
14-CURRENT has completed unless you build them by yourself.
---
Yasuhiro Kimura
__
From: Yasuhiro Kimura
Subject: Re: pkg for 14-current
Date: Sun, 24 Jan 2021 19:18:29 +0900 (JST)
>> I updated to 14-current from 13-current and reinstalled ports-mgmt/pkg.
>> I cannot get meta files for 14-current.
>> How can I use pkg on 14-current ?
>>
>
ase
"3cc0c0d66a0-c255241(main)-dirty" means there isn't any change in src
tree.
Just FYI.
---
Yasuhiro Kimura
___
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"
From: Mark Linimon
Subject: Re: pkg for 14-current
Date: Mon, 25 Jan 2021 03:41:26 +
> On Sun, Jan 24, 2021 at 07:45:08PM +0900, Yasuhiro Kimura wrote:
>> By the way, when -CURRENT was bumped from 12 to 13, there were some
>> ports that failed to be built on 13-CURRENT simp
nces, checkout f9fe7b28bc2 that is just
previous commit of 65c207758a9
9. Repeat step 7 and 8 until there is no difference between
/tmp/usr/src and /usr/src.
---
Yasuhiro Kimura
___
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"
From: Yasuhiro Kimura
Subject: Re: Waiting for bufdaemon
Date: Sat, 16 Jan 2021 04:03:23 +0900 (JST)
> From: Yasuhiro Kimura
> Subject: Re: Waiting for bufdaemon
> Date: Fri, 15 Jan 2021 20:10:30 +0900 (JST)
>
>> I have been experiencing same problem with my 13-CURRENT amd6
From: Yasuhiro Kimura
Subject: Re: Waiting for bufdaemon
Date: Thu, 28 Jan 2021 05:02:42 +0900 (JST)
> It took for a while to investigate, but according to the result of
> bisect following commit is the source of problem in m
make: stopped in /usr/src/release
--
Full buld log is
https://www.utahime.org/FreeBSD/release.sh.2021-01-31-09-10-35.log
(Caution: Size of the file is about 75MB)
Does this mean that release.sh is simply broken right now or I did
something wrong?
B
44eb2: Mon Feb 1 11:30:28 JST 2021
ro...@rolling-vm-freebsd5.home.utahime.org:/usr0/freebsd/src/obj/usr0/freebsd/src/git/amd64.amd64/sys/GENERIC
amd64
---
Yasuhiro Kimura
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailm
From: Yasuhiro Kimura
Subject: Setting for displaying utf8 characters on all vt consoles results in
panic on 14-CURRENT and 13.0-ALPHA3
Date: Mon, 01 Feb 2021 11:41:35 +0900 (JST)
> To display utf8 characters on all vt console I did following settings.
>
> 1. Download GNU Unifont
rds.
---
Yasuhiro Kimura
___
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"
c/Hugo is 100% complete. (It is
> effectively complete, but there are a few nits here and there that need
> to be resolved.)
I got it. Since textproj/docproj is meta port, it also need to be
updated to depend on new required tools.
---
Yasuhiro Kimura
icial package, the latter is installed by using ports tree checked
out in chroot.
Then is there any reason doing so? Why aren't both of them installed
by using offical package nor by using ports tree?
---
Yasuhiro Kimura
___
freebsd-current@freebsd.org ma
-020210225.01.png
https://www.utahime.org/FreeBSD/install-snapshot-020210225.02.png
https://www.utahime.org/FreeBSD/install-snapshot-020210225.03.png
If I start `bsdinstall` after installation is completed, then it works
normal color mode. So it seems bug of install image.
---
Yasuhiro Kimura
From: Yasuhiro Kimura
Subject: Installer of 20210225 snapshot works with monochrome mode
Date: Tue, 02 Mar 2021 16:02:37 +0900 (JST)
> I created VirtualBox VM on Windows host and tried to make clean
> install of 14-CURRENT with iso image of 20210225 snapshot
> (FreeBSD-14.0-CURR
From: Yasuhiro Kimura
Subject: Re: Installer of 20210225 snapshot works with monochrome mode
Date: Wed, 03 Mar 2021 00:43:24 +0900 (JST)
>> I created VirtualBox VM on Windows host and tried to make clean
>> install of 14-CURRENT with iso image of 20210225 snapshot
>> (FreeBSD-
From: Yasuhiro Kimura
Subject: Re: Installer of 20210225 snapshot works with monochrome mode
Date: Thu, 04 Mar 2021 06:15:34 +0900 (JST)
> From: Yasuhiro Kimura
> Subject: Re: Installer of 20210225 snapshot works with monochrome mode
> Date: Wed, 03 Mar 2021 00:43:24 +0900 (JST)
Dear src committers,
From: Yasuhiro Kimura
Subject: Re: Waiting for bufdaemon
Date: Thu, 28 Jan 2021 05:02:42 +0900 (JST)
>>> I have been experiencing same problem with my 13-CURRENT amd64
>>> VirtualBox VM for about a month. The conditions that the problem
>>> happe
n this case, even after reading the commit message, I had no idea
which man page to check.
---
Yasuhiro Kimura
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to &q
From: Yasuhiro Kimura
Subject: Re: Waiting for bufdaemon
Date: Sat, 06 Mar 2021 08:33:23 +0900 (JST)
>> My belief is that this commit helps more users than it hurts. Namely,
>> the VMWare and KVM users, which are majority, use fast timecounter,
>> comparing to the more nich
still one question remains. Why have the value of
kern.timecounter.hardware and kern.timecounter.tc.ACPI-fast.counter
changed by applying the patch? My understanding is that it only makes
'kern.timecounter.hardware' loader tunable that can be configured with
loader.conf. Is it unexpecte
From: Yasuhiro Kimura
Subject: Re: Waiting for bufdaemon
Date: Tue, 09 Mar 2021 00:57:32 +0900 (JST)
> But still one question remains. Why have the value of
> kern.timecounter.hardware and kern.timecounter.tc.ACPI-fast.counter
> changed by applying the patch? My understanding is tha
> size = (mp_maxid + 1) * 3;
> data = malloc(sizeof(*data) * size * N, M_TEMP, M_WAITOK);
After updating to 6ffdaa5f2d4, I confirmed timeout of bufdaemon
dosen't happen even if I don't set kern.timecounter.hardware at all in
loader.conf.
Thank you for fixing
case files under /usr/obj are used to create jail. So you need
not do 'make buildworld' again for jail.
---
Yasuhiro Kimura
___
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"
ail -u -j jailname
---
Yasuhiro Kimura
___
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"
take effect.
--
The problem also happens with poudriere.
I tried boot with old 36d6e65722e kernel but the problem still
happens. So the cause may be older than it.
Does anyone else have the same problem?
Best Regards.
---
Yasuhir
been commit d36d6816151705907393889
>
> imb
Thanks for information. I'll try another update.
---
Yasuhiro Kimura
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any m
From: Yasuhiro Kimura
Subject: Re: Build of some ports hang up on recent 14-CURRENT amd64
Date: Sat, 10 Apr 2021 06:30:22 +0900 (JST)
> From: Michael Butler via freebsd-current
> Subject: Re: Build of some ports hang up on recent 14-CURRENT amd64
> Date: Fri, 9 Apr 2021 17:20
ail to
bugmeis...@freebsd.org.
---
Yasuhiro Kimura
___
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"
From: Yasuhiro Kimura
Subject: Install of 13.0-RELEASE i386 with ZFS root hangs up
Date: Fri, 07 May 2021 21:47:59 +0900 (JST)
> Hello,
>
> Does anyone succeed to install 13.0-RELEASE i386 with ZFS root?
>
> I tried this with VirtualBox and VMware Player on Windows with
From: Yasuhiro Kimura
Subject: Loading zfs module results in hangup on i386 (Re: Install of
13.0-RELEASE i386 with ZFS root hangs up)
Date: Sat, 08 May 2021 07:31:47 +0900 (JST)
> Now I think I know what is the source of problem. After all, on
> 13.0-RELEASE i386 system simply loadi
From: Yasuhiro Kimura
Subject: Re: Loading zfs module results in hangup on i386
Date: Sat, 08 May 2021 07:44:15 +0900 (JST)
>> Now I think I know what is the source of problem. After all, on
>> 13.0-RELEASE i386 system simply loading zfs module results in system
>> hang up.
&
Hello,
Recently `make delete-old` ask if it removes
/usr/share/man/man7/zpool-features.7.gz when I take regular update
step. But even if I answer 'y' and the file is removed, it happens
again when I do next update.
Should the file be removed or not?
Best Regards.
---
Yasuhiro Kimura
From: Yasuhiro Kimura
Subject: Should /usr/share/man/man7/zpool-features.7.gz be removed or not?
Date: Sat, 26 Jun 2021 10:20:09 +0900 (JST)
> Recently `make delete-old` ask if it removes
> /usr/share/man/man7/zpool-features.7.gz when I take regular update
> step. But even if I answe
MFC after: 1 week
Differential revision: https://reviews.freebsd.org/D32901
--
It seems likely this is the cause of build error.
---
Yasuhiro Kimura
d. But build of
lang/gcc11 still failed with same error.
---
Yasuhiro Kimura
From: Yasuhiro Kimura
Subject: Re: Build of devel/ninja and lang/gcc11 fails with latest 14-CURRENT
amd64
Date: Sat, 13 Nov 2021 12:21:40 +0900 (JST)
> I tried it and build of devel/ninja is surely fixed. But build of
> lang/gcc11 still failed with same error.
With the commit of 90fa9
1 - 100 of 128 matches
Mail list logo
