Re: Loading zfs module results in hangup on i386
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.
>>
>> The steps to reproduce it are,
>>
>> 1. Boot with install media of 13.0-RELEASE i386
>> 2. At the first menu of FreeBSD installer, select 'Shell'.
>> 3. At the shell prompt, type `kldload zfs` and return key.
>>
>> I confirmed hangup happens with VirtualBox, VMware Player and my bare
>> metal PC environement. So the problem doesn't depend on hardware.
>>
>> And hangup also happens with 13-STABLE and 14-CURRENT.
>
> This problem is already reported to Bugzilla.
>
> Bug 254177 When ZFS is recognized, An i386 machine with a lot of memory hangs.
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254177
Referencing the bug report, I applied attached patch to d474440ab33 of
main (14-CURRENT). built install image and tried install of ZFS root
i386 system with it. Then it completed successfully with 8GB memory.
Additionally GENERIC kernel recognizes 8GB of memory. And ZFS root
system works fine without any tuning.
--
diff --git a/sys/contrib/openzfs/module/zfs/dbuf.c
b/sys/contrib/openzfs/module/zfs/dbuf.c
index d48dc7943a2..c85500453fb 100644
--- a/sys/contrib/openzfs/module/zfs/dbuf.c
+++ b/sys/contrib/openzfs/module/zfs/dbuf.c
@@ -796,7 +796,7 @@ dbuf_init(void)
* By default, the table will take up
* totalmem * sizeof(void*) / 8K (1MB per GB with 8-byte pointers).
*/
- while (hsize * zfs_arc_average_blocksize < physmem * PAGESIZE)
+ while (hsize * zfs_arc_average_blocksize < (uint64_t)physmem * PAGESIZE)
hsize <<= 1;
retry:
--
---
Yasuhiro Kimura
___
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"
Re: Loading zfs module results in hangup on i386
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 loading zfs module results in system > hang up. > > The steps to reproduce it are, > > 1. Boot with install media of 13.0-RELEASE i386 > 2. At the first menu of FreeBSD installer, select 'Shell'. > 3. At the shell prompt, type `kldload zfs` and return key. > > I confirmed hangup happens with VirtualBox, VMware Player and my bare > metal PC environement. So the problem doesn't depend on hardware. > > And hangup also happens with 13-STABLE and 14-CURRENT. This problem is already reported to Bugzilla. Bug 254177 When ZFS is recognized, An i386 machine with a lot of memory hangs. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254177 --- Yasuhiro Kimura ___ 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"
Loading zfs module results in hangup on i386 (Re: Install of 13.0-RELEASE i386 with ZFS root hangs up)
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 > following VM condition. > > * 4 CPUs > * 8GB memory > * 100GB disk > * Bridge mode NIC > > But in both cases, VM gets high CPU load and hangs up after I moved > to 'YES' at 'ZFS Configuration' menu and type return key. > > If I select UFS root installation completes successfully. So the > problem is specific to ZFS root. 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. The steps to reproduce it are, 1. Boot with install media of 13.0-RELEASE i386 2. At the first menu of FreeBSD installer, select 'Shell'. 3. At the shell prompt, type `kldload zfs` and return key. I confirmed hangup happens with VirtualBox, VMware Player and my bare metal PC environement. So the problem doesn't depend on hardware. And hangup also happens with 13-STABLE and 14-CURRENT. --- Yasuhiro Kimura ___ 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"
Re: Install of 13.0-RELEASE i386 with ZFS root hangs up
From: 8zwk...@oldach.net (Helge Oldach) Subject: Re: Install of 13.0-RELEASE i386 with ZFS root hangs up Date: Fri, 7 May 2021 15:41:45 +0200 (CEST) > Yasuhiro Kimura wrote on Fri, 07 May 2021 14:47:59 +0200 (CEST): >> Does anyone succeed to install 13.0-RELEASE i386 with ZFS root? > > >> * 8GB memory > > Try with 4GB perhaps? > > Kind regards > Helge Thank you for suggestion. But unfortunately hangup still happens with 4GB memory. --- Yasuhiro Kimura ___ 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"
Install of 13.0-RELEASE i386 with ZFS root hangs up
Hello, Does anyone succeed to install 13.0-RELEASE i386 with ZFS root? I tried this with VirtualBox and VMware Player on Windows with following VM condition. * 4 CPUs * 8GB memory * 100GB disk * Bridge mode NIC But in both cases, VM gets high CPU load and hangs up after I moved to 'YES' at 'ZFS Configuration' menu and type return key. If I select UFS root installation completes successfully. So the problem is specific to ZFS root. --- Yasuhiro Kimura ___ 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"
Re: How to make 'named' rc script invokded earlier at boot time
From: b56...@oldach.net (Helge Oldach) Subject: Re: How to make 'named' rc script invokded earlier at boot time Date: Fri, 30 Apr 2021 11:25:03 +0200 (CEST) > Looks like this is caused by security/trousers which has "BEFORE: named > hastd". This port had been touched 3 weeks ago. You provide me very good hint! On my home server security/trousers and emulators/tpm-emulator are installed as dependencies of security/gnutls. They install /usr/local/etc/rc.d/tcsd and /usr/local/etc/rc.d/tpmd respectivley. And there is circular dependency between these 2 rc srcipts and /usr/local/etc/rc.d/named. -- root@eastasia[1067]# rcorder /etc/rc.d/* /usr/local/etc/rc.d/* > /dev/null rcorder: file `/usr/local/etc/rc.d/tcsd' is before unknown provision `kerberos' rcorder: Circular dependency on file `/usr/local/etc/rc.d/named'. rcorder: Circular dependency on provision `fake_prov_0004': /usr/local/etc/rc.d/tcsd -> /usr/local/etc/rc.d/tpmd -> /etc/rc.d/SERVERS -> /usr/local/etc/rc.d/named -> /usr/local/etc/rc.d/tcsd. rcorder: `/usr/local/etc/rc.d/named' was seen in circular dependencies for 1 times. rcorder: `/etc/rc.d/SERVERS' was seen in circular dependencies for 1 times. rcorder: `/usr/local/etc/rc.d/tpmd' was seen in circular dependencies for 1 times. rcorder: `/usr/local/etc/rc.d/tcsd' was seen in circular dependencies for 1 times. rcorder: `/usr/local/etc/rc.d/named' was seen in circular dependencies for 1 times. root@eastasia[1068]# -- If I temporally move /usr/local/etc/rc.d/tcsd to somewhere else and add 'ntpdate' to 'BEFORE' line of /usr/local/etc/rc.d/named, then 'named' comes before 'ntpupdate' in the result of rcorder. --- Yasuhiro Kimura ___ 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"
Re: How to make 'named' rc script invokded earlier at boot time
From: Yasuhiro Kimura Subject: Re: How to make 'named' rc script invokded earlier at boot time Date: Fri, 30 Apr 2021 17:18:26 +0900 (JST) >> The only way I can see is modify the named rc script and add the >> services that needs named to be started on the BEFORE line at the >> beginning of the script. Mind you, it really needs to start after >> syslog (unless you log directly to files and do not use syslog.) > > Thanks for advice. I'll try it. I tried it but am confused by the result. I modified /usr/local/etc/rc.d/named on my home server as following. -- root@eastasia[1051]# head /usr/local/etc/rc.d/named #!/bin/sh # PROVIDE: named # REQUIRE: NETWORKING ldconfig syslogd # BEFORE: SERVERS ntpdate # KEYWORD: shutdown # # Add the following lines to /etc/rc.conf to enable BIND: # named_enable (bool): Run named, the DNS server (or NO). root@eastasia[1052]# -- And I executed `rcorder /etc/rc.d/* /usr/local/etc/rc.d/*`. Then I got just same result as before the modification. So I modifed /etc/rc.d/ntpdate as following. -- root@eastasia[1053]# head /etc/rc.d/ntpdate ~ #!/bin/sh # # $FreeBSD$ # # PROVIDE: ntpdate # REQUIRE: NETWORKING syslogd named # KEYWORD: nojail . /etc/rc.subr root@eastasia[1054]# -- But the result still didn't changed. As I wrote another mail my result of `rcorder -p` is different from that of Helge Oldach. These oddities may be related. I'll investigate further but it may take for a while. --- Yasuhiro Kimura ___ 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"
Re: How to make 'named' rc script invokded earlier at boot time
From: Mathieu Arnold Subject: Re: How to make 'named' rc script invokded earlier at boot time Date: Fri, 30 Apr 2021 10:02:31 +0200 > There is an option in the port to have named start later, but up to now, > it was starting early enough. > > The only way I can see is modify the named rc script and add the > services that needs named to be started on the BEFORE line at the > beginning of the script. Mind you, it really needs to start after > syslog (unless you log directly to files and do not use syslog.) Thanks for advice. I'll try it. --- Yasuhiro Kimura ___ 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"
Re: How to make 'named' rc script invokded earlier at boot time
From: b56...@oldach.net (Helge Oldach) Subject: Re: How to make 'named' rc script invokded earlier at boot time Date: Fri, 30 Apr 2021 10:01:47 +0200 (CEST) > Can you try rcorder -p? That will group equally ranked scripts on the same > line. > > On 13, I'm seeing: > > (snip) > /etc/rc.d/pwcheck /etc/rc.d/watchdogd /usr/local/etc/rc.d/named > /etc/rc.d/auditd /etc/rc.d/ntpdate /etc/rc.d/bsnmpd /etc/rc.d/savecore > /etc/rc.d/power_profile /etc/rc.d/localpkg /etc/rc.d/hastd > /etc/rc.d/rpcbind /etc/rc.d/SERVERS /etc/rc.d/auditdistd > (snip) > > which implies that the ordering of named and ntpdate is random however both > are before SERVERS. > > Kind regards > Helge I get following result. (snip) /etc/rc.d/NETWORKING /etc/rc.d/kdc /etc/rc.d/kfd /etc/rc.d/pppoed /etc/rc.d/nfsuserd /etc/rc.d/iscsid /etc/rc.d/iscsictl /etc/rc.d/nfscbd /etc/rc.d/kpasswdd /etc/rc.d/kadmind /etc/rc.d/ipropd_slave /etc/rc.d/ipropd_master/etc/rc.d/mountcritremote /etc/rc.d/devfs /etc/rc.d/virecover /etc/rc.d/os-release /etc/rc.d/motd /etc/rc.d/archdep /etc/rc.d/mdconfig2 /etc/rc.d/gptboot /etc/rc.d/wpa_supplicant /etc/rc.d/accounting /etc/rc.d/dmesg /etc/rc.d/cleartmp /etc/rc.d/hostapd /etc/rc.d/newsyslog /etc/rc.d/syslogd /etc/rc.d/sysvipc /etc/rc.d/linux /etc/rc.d/pwcheck /etc/rc.d/localpkg /etc/rc.d/power_profile /etc/rc.d/auditd /etc/rc.d/bsnmpd /etc/rc.d/ntpdate /etc/rc.d/savecore /etc/rc.d/watchdogd /etc/rc.d/rpcbind /etc/rc.d/auditdistd /etc/rc.d/nfsclient /usr/local/etc/rc.d/tpmd /usr/local/etc/rc.d/tcsd /etc/rc.d/hastd /usr/local/etc/rc.d/named /etc/rc.d/SERVERS (snip) 'named' is still later than 'ntpdate' on my home server. --- Yasuhiro Kimura ___ 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"
How to make 'named' rc script invokded earlier at boot time
I installed dns/bind916 on my home server and configured it so it worked as both authoritative and recursor. Then I added 'nameserver 127.0.0.1' to /etc/resolv.conf and everything worked fine. But after updating OS from 12.2-RELEASE to 13.0-RELEASE I noticed execution of some rc scripts fails at boot time because of DNS lookup error. And I also found these scripts are executed earlier than 'named'. Now let me use 'ntpdate' as an example. If I run `rcorder /etc/rc.d/* /usr/local/etc/rc.d/*` on 12.2-RELEASE, then I get following result. -- root@rolling-vm-freebsd3[474]# uname -a FreeBSD rolling-vm-freebsd3.home.utahime.org 12.2-RELEASE-p6 FreeBSD 12.2-RELEASE-p6 GENERIC amd64 root@rolling-vm-freebsd3[475]# rcorder /etc/rc.d/* /usr/local/etc/rc.d/* /etc/rc.d/growfs /etc/rc.d/sysctl /etc/rc.d/hostid /etc/rc.d/zvol /etc/rc.d/dumpon (snip) /etc/rc.d/static_arp /etc/rc.d/bridge /etc/rc.d/route6d /etc/rc.d/NETWORKING /etc/rc.d/mountcritremote /etc/rc.d/devfs /etc/rc.d/ipmon /etc/rc.d/kdc /etc/rc.d/mdconfig2 /etc/rc.d/newsyslog /etc/rc.d/syslogd /usr/local/etc/rc.d/tcsd /usr/local/etc/rc.d/named /etc/rc.d/watchdogd /etc/rc.d/savecore /etc/rc.d/archdep /etc/rc.d/linux /etc/rc.d/sysvipc /etc/rc.d/SERVERS /usr/local/etc/rc.d/tpmd /usr/local/etc/rc.d/stunnel /etc/rc.d/accounting /etc/rc.d/ntpdate /etc/rc.d/rpcbind /etc/rc.d/nfsclient /etc/rc.d/nisdomain (snip) -- As you can see, while 'named' is executed before SERVERS, 'ntpdate' is done after it. On the other hand I get following result on 13.0-RELEASE. -- root@rolling-vm-freebsd2[332]# uname -a FreeBSD rolling-vm-freebsd2.home.utahime.org 13.0-RELEASE FreeBSD 13.0-RELEASE #0 releng/13.0-n244733-ea31abc261f: Fri Apr 9 04:24:09 UTC 2021 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 root@rolling-vm-freebsd2[333]# rcorder /etc/rc.d/* /usr/local/etc/rc.d/* /etc/rc.d/dhclient /etc/rc.d/dumpon /etc/rc.d/growfs /etc/rc.d/natd (snip) /etc/rc.d/netwait /etc/rc.d/blacklistd /etc/rc.d/local_unbound /etc/rc.d/NETWORKING /etc/rc.d/pppoed /etc/rc.d/kdc /etc/rc.d/kfd /etc/rc.d/nfsuserd /etc/rc.d/iscsid /etc/rc.d/ipropd_slave /etc/rc.d/nfscbd /etc/rc.d/iscsictl /etc/rc.d/ipropd_master /etc/rc.d/kadmind /etc/rc.d/kpasswdd /etc/rc.d/mountcritremote /etc/rc.d/wpa_supplicant /etc/rc.d/motd /etc/rc.d/accounting /etc/rc.d/cleartmp /etc/rc.d/dmesg /etc/rc.d/archdep /etc/rc.d/gptboot /etc/rc.d/hostapd /etc/rc.d/virecover /etc/rc.d/mdconfig2 /etc/rc.d/devfs /etc/rc.d/os-release /etc/rc.d/newsyslog /etc/rc.d/linux /etc/rc.d/syslogd /etc/rc.d/sysvipc /etc/rc.d/watchdogd /etc/rc.d/savecore /etc/rc.d/ntpdate /etc/rc.d/localpkg /etc/rc.d/auditd /etc/rc.d/bsnmpd /etc/rc.d/pwcheck /etc/rc.d/power_profile /etc/rc.d/rpcbind /etc/rc.d/auditdistd /usr/local/etc/rc.d/named /etc/rc.d/nfsclient /etc/rc.d/hastd /etc/rc.d/SERVERS /etc/rc.d/nisdomain /usr/local/etc/rc.d/stunnel /usr/local/etc/rc.d/tpmd /usr/local/etc/rc.d/tcsd (snip) -- Now both 'named' and 'ntpdate' are executed before SERVERS. And unfortunately the latter is earlier than the former. So it is natural that execution of 'ntpdate' fails with DNS lookup failure. I compared ntpdate rc script between releng/12.2 and releng/13.0 but there is no difference. -- yasu@rolling-vm-freebsd2[1035]% pwd /usr/src yasu@rolling-vm-freebsd2[1036]% git diff origin/releng/12.2 origin/releng/13.0 -- libexec/rc/rc.d/ntpdate yasu@rolling-vm-freebsd2[1037]% -- And of cource there is no difference with /usr/local/etc/rc.d/named either. So it seems evaluation of rcorder(8) is changed between 12.2-RELASE and 13.0-RELEASE. Then is there any way to make 'named' rc script invoked earlier at boot time on 13.0-RELEASE? Best Regards. --- Yasuhiro Kimura ___ 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"
Re: Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3
From: Toomas Soome via freebsd-current Subject: Re: Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3 Date: Tue, 2 Feb 2021 00:35:49 +0200 > Should be fixed on current now. Confirmed. Would you please MFC to stable/13? Best Regards. --- Yasuhiro Kimura ___ 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"
Re: Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3
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 BDF file > > (http://unifoundry.com/pub/unifont/unifont-13.0.05/font-builds/unifont-13.0.05.bdf.gz) > 2. gunzip unifont-13.0.05.bdf.gz > 3. vtfontcvt unifont-13.0.05.bdf unifont.fnt > 4. cp unifont.fnt /usr/share/vt/fonts > 5. Add 'allscreens_flags="-f 8x16 unifont.fnt"' to /etc/rc.conf > 6. Add 'hw.vga.textmode=0' to /boot/loader.conf.local > 7. shutdown -r now > > On 12.2-RELEASE and 11.4-RELEASE it works as is expected. But on > 14-CURRENT(man) and 13.0-ALPHA3(stable/13) it result in kernel panic. > > Screen shot of 14-CURRENT. > https://www.utahime.org/FreeBSD/panic.20210201.14-CURRENT.png > > 14-CURRENT(main): > yasu@rolling-vm-freebsd1[1006]% uname -a > FreeBSD rolling-vm-freebsd1.home.utahime.org 14.0-CURRENT FreeBSD > 14.0-CURRENT #0 main-n244517-f17fc5439f5: Mon Feb 1 10:55:51 JST 2021 > ro...@rolling-vm-freebsd1.home.utahime.org:/usr0/freebsd/src/obj/usr0/freebsd/src/git/amd64.amd64/sys/GENERIC > amd64 > > 13.0-ALPHA3(stable/13): > yasu@rolling-vm-freebsd5[1005]% uname -a > FreeBSD rolling-vm-freebsd5.home.utahime.org 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 > #0 stable/13-c256214-g40cb0344eb2: 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 I submitted this problem to Bugzilla. Bug 253147 - Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253147 --- Yasuhiro Kimura ___ 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"
Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3
To display utf8 characters on all vt console I did following settings. 1. Download GNU Unifont BDF file (http://unifoundry.com/pub/unifont/unifont-13.0.05/font-builds/unifont-13.0.05.bdf.gz) 2. gunzip unifont-13.0.05.bdf.gz 3. vtfontcvt unifont-13.0.05.bdf unifont.fnt 4. cp unifont.fnt /usr/share/vt/fonts 5. Add 'allscreens_flags="-f 8x16 unifont.fnt"' to /etc/rc.conf 6. Add 'hw.vga.textmode=0' to /boot/loader.conf.local 7. shutdown -r now On 12.2-RELEASE and 11.4-RELEASE it works as is expected. But on 14-CURRENT(man) and 13.0-ALPHA3(stable/13) it result in kernel panic. Screen shot of 14-CURRENT. https://www.utahime.org/FreeBSD/panic.20210201.14-CURRENT.png 14-CURRENT(main): yasu@rolling-vm-freebsd1[1006]% uname -a FreeBSD rolling-vm-freebsd1.home.utahime.org 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-n244517-f17fc5439f5: Mon Feb 1 10:55:51 JST 2021 ro...@rolling-vm-freebsd1.home.utahime.org:/usr0/freebsd/src/obj/usr0/freebsd/src/git/amd64.amd64/sys/GENERIC amd64 13.0-ALPHA3(stable/13): yasu@rolling-vm-freebsd5[1005]% uname -a FreeBSD rolling-vm-freebsd5.home.utahime.org 13.0-ALPHA3 FreeBSD 13.0-ALPHA3 #0 stable/13-c256214-g40cb0344eb2: 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-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: No more update on stable/12
From: Peter Blok Subject: No more update on stable/12 Date: Wed, 30 Dec 2020 10:24:27 +0100 > I switched to git, but I noticed there were no MFC or any other updates over > the last couple of days after the migration. git fetch doesn’t show any > change. > > Is this correct and just the learning process of git or is something wrong > with my git clone? Which repository do you use?. Currently new canonical src repository (https://git.freebsd.org/src.git) is updated but not mirrored to GitHub yet. --- Yasuhiro Kimura ___ 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"
Re: Size of EFI system partition is much smaller when it is mounted
From: Warner Losh Subject: Re: Size of EFI system partition is much smaller when it is mounted Date: Mon, 30 Nov 2020 21:44:58 -0700 > 11.x puts a pre-canned image into the ESP that's tiny, regardless of the > size, while 12.x does a newfs_msdos and sizes it properly. It's kinda hard > to fix in 11.x since there's a number of changes in a number of places. > > You can, though, on 11.x, newfs_msdos the filesystem and copy boot1.efi > from FreeBSD's /boot to the ESP's \efi\boot\bootx64.efi if you need more > space on the ESP for some reason. Thank you for explanation. What I would like do is to update loader file keeping old one as backup after freebsd-update, something like # mount -t msdosfs /dev/ada0p1 /mnt # cd /mnt/efi/boot # mv bootx64.efi bootx64.efi.old # install -m 755 -p /boot/loader.efi bootx64.efi And 779KB is too small to put 2 loader files. So I'll try reformatting EFI system partition. --- Yasuhiro KIMURA ___ 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"
Size of EFI system partition is much smaller when it is mounted
I made clean install of 11.4-RELEASE amd64 with ZFS root and UEFI boot mode. 'Auto (ZFS)' was used at disk setup phase and disk was partitioned as following. -- root@rolling-vm-freebsd3[80]# uname -a FreeBSD rolling-vm-freebsd3.home.utahime.org 11.4-RELEASE-p3 FreeBSD 11.4-RELEASE-p3 #0: Tue Sep 1 08:22:33 UTC 2020 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 root@rolling-vm-freebsd3[81]# gpart show ada0 => 40 209715120 ada0 GPT (100G) 40 409600 1 efi (200M) 409640 2008- free - (1.0M) 411648 16777216 2 freebsd-swap (8.0G) 17188864 192524288 3 freebsd-zfs (92G) 209713152 2008- free - (1.0M) -- According to it the size of EFI system partition is 200MB. But if I mount it to filesystem and check its size with df(1), then it is much smaller than 200MB. -- root@rolling-vm-freebsd3[82]# mount -t msdosfs /dev/ada0p1 /mnt root@rolling-vm-freebsd3[83]# df -k /mnt Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/ada0p1 779 384 39549%/mnt -- And if I try to copy large file to /mnt then it fails. -- root@rolling-vm-freebsd3[94]# ls -l dummy.1MB.date -rw-r--r-- 1 root wheel 1048576 Nov 29 10:39 dummy.1MB.date root@rolling-vm-freebsd3[95]# cp dummy.1MB.date /mnt cp: /mnt/dummy.1MB.date: No space left on device -- So it seems kernel(?) really regards the size of mounted EFI system part as only 779KB. I also tried it with 12.2-RELEASE and df(1) reported correctly. -- root@eastasia[1002]# uname -a FreeBSD eastasia.home.utahime.org 12.2-RELEASE FreeBSD 12.2-RELEASE r366954 GENERIC amd64 root@eastasia[1003]# gpart show ada0 =>40 1953525088 ada0 GPT (932G) 40 409600 1 efi (200M) 4096402008- free - (1.0M) 41164816777216 2 freebsd-swap (8.0G) 17188864 1936334848 3 freebsd-zfs (923G) 19535237121416- free - (708K) root@eastasia[1004]# mount -t msdosfs /dev/ada0p1 /mnt root@eastasia[1005]# df -k /mnt Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/ada0p1 204696 976 203720 0%/mnt -- Is there any bug fix about it that is merged to 12.x but not 11.x? Best Regards. --- Yasuhiro KIMURA ___ 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"
Re: `efivar -l` fails on UEFI booted 11.4-RELEASE
From: Kyle Evans
Subject: Re: `efivar -l` fails on UEFI booted 11.4-RELEASE
Date: Sat, 27 Jun 2020 21:21:10 -0500
> This should be an easy fix. :-) EFI Runtime Services on FreeBSD
> ("EFIRT") wasn't necessarily globally stable until right around 12.0.
> For 11.x, you'll need to `kldload efirt` or add `options EFIRT` to
> your kernel config before efivar/efibootmgr become usable.
Thank you for reply. After loading efirt.ko `efivar -l` succesfully
lists UEFI environment variables.
---
Yasuhiro KIMURA
___
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"
`efivar -l` fails on UEFI booted 11.4-RELEASE
On UEFI booted 11.4-RELEASE system `efivar -l` fails as following. root@rolling-vm-freebsd3[160]# uname -a FreeBSD rolling-vm-freebsd3.home.utahime.org 11.4-RELEASE FreeBSD 11.4-RELEASE #0 r362094: Fri Jun 12 18:27:15 UTC 2020 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 root@rolling-vm-freebsd3[161]# efivar -l efivar: Error listing names: No such file or directory root@rolling-vm-freebsd3[162]# It also happens with latest (20200625) 11-STABLE snapshot, but not with either 12.1-RELEASE or 13-CURRENT. --- Yasuhiro KIMURA ___ 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"
Re: Buildworld and buildkernel with very slow compilation, recently
From: Ronald Klop Subject: Re: Buildworld and buildkernel with very slow compilation, recently Date: Sun, 21 Jun 2020 14:48:51 +0200 (CEST) > Building ports/pkgs is also significantly slower on 13 (new clang) > than on 12.1. > http://thunderx1.nyi.freebsd.org/ > 13 = 140 hours12.1 = 103 hoursFor roughly the same amount of ports. >From /usr/src/UPDATING of head: NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW: FreeBSD 13.x has many debugging features turned on, in both the kernel and userland. These features attempt to detect incorrect use of system primitives, and encourage loud failure through extra sanity checking and fail stop semantics. They also substantially impact system performance. If you want to do performance measurement, benchmarking, and optimization, you'll want to turn them off. This includes various WITNESS- related kernel options, INVARIANTS, malloc debugging flags in userland, and various verbose features in the kernel. Many developers choose to disable these features on build machines to maximize performance. (To completely disable malloc debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely disable the most expensive debugging functionality run "ln -s 'abort:false,junk:false' /etc/malloc.conf".) --- Yasuhiro KIMURA ___ 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"
Re: php56
From: tech-lists Subject: php56 Date: Sun, 13 Jan 2019 12:29:36 + > Is there a way of installing php56 and php56-extensions from ports or > packages now? > > I know it's EoL, but need it because I need to support a (non-ports) > program for the time being and said program will not work under php7* > > context is 11-stable/amd64 > > thanks, svn checkout -r 488893 /usr/ports --- Yasuhiro KIMURA ___ 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"
Re: Getting value of MAKEOBJDIRPREFIX with 'make -V MAKEOBJDIRPREFIX'
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 bug report. Submitted. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233265 --- Yasuhiro KIMURA ___ 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"
Re: Getting value of MAKEOBJDIRPREFIX with 'make -V MAKEOBJDIRPREFIX'
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 I bisected head from r302408 (revision that stable/11 is cleated) to r340439 and got following result. Order RevisionDoes 'make -V MAKEOBJDIRPREFIX` work? -- 1 302408 Yes 2 340439 No 3 323176 Yes 4 332305 No 5 327441 No 6 325415 No 7 324362 Yes 8 324940 Yes 9 325181 Yes 10 325295 No 11 325248 Yes 12 325271 Yes 13 325285 Yes 14 325290 No 15 325288 No 16 325287 Yes That is, behavior changed at r325288. And commit message says as following. -- Add option UNIFIED_OBJDIR, on by default, which moves the default build OBJDIR. This changes the build OBJDIR from the older style of /usr/obj/ for native builds, and /usr/obj/./ for cross builds to a new simpler format of /usr/obj//.. This new format is used regardless of cross or native build. It allows easier management of multiple source tree object directories. The UNIFIED_OBJDIR option will be removed and its feature made permanent for the 12.0 release. -- As far as I read this, behavior change of 'make -V MAKEOBJDIRPREFIX` doesn't seem intentional. So I'll submit bug report. --- Yasuhiro KIMURA ___ 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"
Getting value of MAKEOBJDIRPREFIX with 'make -V MAKEOBJDIRPREFIX'
Hello, I'm writing shell script to build and install base system from source and -V option of make(1) is used in it to get value of MAKEOBJDIRPREFIX. By default it works fine with all of head, releng/11.2, releng/12.0, stable/11 and stable/12. yasu@eastasia[2389]% svn info /usr0/freebsd/base/head Path: /usr0/freebsd/base/head Working Copy Root Path: /usr0/freebsd/base/head URL: https://svn.freebsd.org/base/head Relative URL: ^/head Repository Root: https://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 340474 Node Kind: directory Schedule: normal Last Changed Author: karels Last Changed Rev: 340474 Last Changed Date: 2018-11-16 12:42:29 +0900 (Fri, 16 Nov 2018) yasu@eastasia[2390]% make -V MAKEOBJDIRPREFIX -C /usr0/freebsd/base/head /usr/obj yasu@eastasia[2391]% svn info /usr0/freebsd/base/releng/11.2 Path: /usr0/freebsd/base/releng/11.2 Working Copy Root Path: /usr0/freebsd/base/releng/11.2 URL: https://svn.freebsd.org/base/releng/11.2 Relative URL: ^/releng/11.2 Repository Root: https://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 338990 Node Kind: directory Schedule: normal Last Changed Author: gordon Last Changed Rev: 338981 Last Changed Date: 2018-09-28 03:36:30 +0900 (Fri, 28 Sep 2018) yasu@eastasia[2392]% make -V MAKEOBJDIRPREFIX -C /usr0/freebsd/base/releng/11.2 /usr/obj yasu@eastasia[2393]% svn info /usr0/freebsd/base/releng/12.0 Path: /usr0/freebsd/base/releng/12.0 Working Copy Root Path: /usr0/freebsd/base/releng/12.0 URL: https://svn.freebsd.org/base/releng/12.0 Relative URL: ^/releng/12.0 Repository Root: https://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 340471 Node Kind: directory Schedule: normal Last Changed Author: gjb Last Changed Rev: 340470 Last Changed Date: 2018-11-16 09:00:59 +0900 (Fri, 16 Nov 2018) yasu@eastasia[2394]% make -C /usr0/freebsd/base/releng/12.0 -V MAKEOBJDIRPREFIX /usr/obj yasu@eastasia[2395]% svn info /usr0/freebsd/base/stable/11 Path: /usr0/freebsd/base/stable/11 Working Copy Root Path: /usr0/freebsd/base/stable/11 URL: https://svn.freebsd.org/base/stable/11 Relative URL: ^/stable/11 Repository Root: https://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 340473 Node Kind: directory Schedule: normal Last Changed Author: ygy Last Changed Rev: 340449 Last Changed Date: 2018-11-15 17:43:17 +0900 (Thu, 15 Nov 2018) yasu@eastasia[2396]% make -V MAKEOBJDIRPREFIX -C /usr0/freebsd/base/stable/11 /usr/obj yasu@eastasia[2397]% svn info /usr0/freebsd/base/stable/12 Path: /usr0/freebsd/base/stable/12 Working Copy Root Path: /usr0/freebsd/base/stable/12 URL: https://svn.freebsd.org/base/stable/12 Relative URL: ^/stable/12 Repository Root: https://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 340474 Node Kind: directory Schedule: normal Last Changed Author: gjb Last Changed Rev: 340471 Last Changed Date: 2018-11-16 09:03:31 +0900 (Fri, 16 Nov 2018) yasu@eastasia[2398]% make -V MAKEOBJDIRPREFIX -C /usr0/freebsd/base/stable/12 /usr/obj But if I customize value of MAKEOBJDIRPREFIX then it still works with releng/11.2 and stable/11 but doesn't with head, releng/12.0 and stable/12. yasu@eastasia[2399]% env MAKEOBJDIRPREFIX=/usr0/freebsd/base/ogj make -V MAKEOBJDIRPREFIX -C /usr0/freebsd/base/head yasu@eastasia[2400]% env MAKEOBJDIRPREFIX=/usr0/freebsd/base/ogj make -V MAKEOBJDIRPREFIX -C /usr0/freebsd/base/releng/11.2 /usr0/freebsd/base/ogj yasu@eastasia[2401]% env MAKEOBJDIRPREFIX=/usr0/freebsd/base/ogj make -V MAKEOBJDIRPREFIX -C /usr0/freebsd/base/releng/12.0 yasu@eastasia[2402]% env MAKEOBJDIRPREFIX=/usr0/freebsd/base/ogj make -V MAKEOBJDIRPREFIX -C /usr0/freebsd/base/stable/11 /usr0/freebsd/base/ogj yasu@eastasia[2403]% env MAKEOBJDIRPREFIX=/usr0/freebsd/base/ogj make -V MAKEOBJDIRPREFIX -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. --- Yasuhiro KIMURA ___ 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"
Re: Console is broken after updating to 11.2-RELEASE
I submitted this problem as following bug report. Bug 229235 - vt(4) of 11.2-RELEASE is broken with hardware dependent problem. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229235 Just FYI. --- Yasuhiro KIMURA ___ 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"
Re: Console is broken after updating to 11.2-RELEASE
From: "Chris H" Subject: Re: Console is broken after updating to 11.2-RELEASE Date: Fri, 22 Jun 2018 06:13:39 -0700 > Try adding the following to your loader.conf(5) file > (/boot/loader.conf): > > # Load SysCons driver > kern.vty=sc > # noisy boot > boot_verbose="YES" > > Hope this helps! Thank you for information. I added above lines to /boot/loader.conf and rebooted system. Then all boot messages are displayed and console works fine! --- Yasuhiro KIMURA ___ 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"
Re: Console is broken after updating to 11.2-RELEASE
From: Warner Losh Subject: Re: Console is broken after updating to 11.2-RELEASE Date: Fri, 22 Jun 2018 05:03:43 -0600 > UEFI or legacy boot? Is a BMC involved? Legacy boot. And BMC is not involved. --- Yasuhiro KIMURA ___ 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"
Re: Console is broken after updating to 11.2-RELEASE
From: tech-lists Subject: Re: Console is broken after updating to 11.2-RELEASE Date: Fri, 22 Jun 2018 11:44:29 +0100 > I've seen this effect elsewhere. Not exactly the same, but it's been > happening with me on some systems since 11.1. The context I see it is > when spinning up a bhyve instance in screen. I see a bit more than > just booting, something like "unreferenced ps/2 interrupt" after > "Booting...". > > The bhyve instance itself is fully functional. Logging into the bhyve > instance through ssh I can see its dmesg and it all looks OK. However, > if in syslogd.conf I enable console logging via console.log and > reboot, *nothing gets written to it*. Thank you for information. I created /etc/syslog.d/console.log.conf as below and rebooted system. yasu@maybe[2012]% cat /etc/syslog.d/console.log.conf ~ # Log all writes to /dev/console to a separate file. !* console.* /var/log/console.log !* yasu@maybe[2013]% Then boot messages are written in /var/log/console.log yasu@maybe[2016]% LANG=C ls -l /var/log/console.log ~ -rw-r--r-- 1 root wheel 9568 Jun 22 20:29 /var/log/console.log yasu@maybe[2016]% So my case seems to be different from yours. --- Yasuhiro KIMURA ___ 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"
Re: Console is broken after updating to 11.2-RELEASE
From: Yasuhiro KIMURA Subject: Console is broken after updating to 11.2-RELEASE Date: Fri, 22 Jun 2018 17:07:20 +0900 (JST) > With the commit of r335510 releng/11.2 switched to -RELEASE. So I > updated one of my home server from 11.1-RELEASE-p11 to 11.2-RELEASE. > > But when I rebooted I found OS boot messages are not displayed on > console while OS itself has booted successfully. To be exact, > > 1. BIOS message are displayed. > 2. Boot menu of FreeBSD is displayed. > 3. Kernel boot starts but after 'Booting...' no following messages >are displayed. > 4. After OS has booted console stays unusable. I have another 11.1-RELEASE-p11 amd64 environment working as guest of VirtualBox whose host is 64bit Windows 10. So I updated it to 11.2-RELEASE like my home server in question. But in this case console worked fine just as it was 11.1-RELEASE-p11. So the problem seems to be hardwear dependent. --- Yasuhiro KIMURA ___ 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"
Re: Console is broken after updating to 11.2-RELEASE,Re: Console is broken after updating to 11.2-RELEASE
From: "Andrey V. Elsukov" Subject: Re: Console is broken after updating to 11.2-RELEASE,Re: Console is broken after updating to 11.2-RELEASE Date: Fri, 22 Jun 2018 11:47:24 +0300 > Do you have some tweaks for serial console in your loader.conf? No. I don't use serial console at all. Folloging is loader.conf of my home server in question. yasu@maybe[2019]% cat /boot/loader.conf kern.geom.label.disk_ident.enable="0" kern.geom.label.gptid.enable="0" #zfs_load="YES" yasu@maybe[2020]% --- Yasuhiro KIMURA ___ 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"
Console is broken after updating to 11.2-RELEASE
Hello. With the commit of r335510 releng/11.2 switched to -RELEASE. So I updated one of my home server from 11.1-RELEASE-p11 to 11.2-RELEASE. But when I rebooted I found OS boot messages are not displayed on console while OS itself has booted successfully. To be exact, 1. BIOS message are displayed. 2. Boot menu of FreeBSD is displayed. 3. Kernel boot starts but after 'Booting...' no following messages are displayed. 4. After OS has booted console stays unusable. Kernel configuration is as follwing. -- yasu@maybe[2006]% uname -a ~ FreeBSD maybe.home.utahime.org 11.2-RELEASE FreeBSD 11.2-RELEASE #0 r335513: Fri Jun 22 16:12:12 JST 2018 ro...@maybe.home.utahime.org:/usr0/freebsd/base/obj/usr0/freebsd/base/releng/11.2/sys/MAYBE amd64 yasu@maybe[2007]% cat /usr/src/sys/amd64/conf/MAYBE ~ # # MAYBE -- Local kernel configuration file of maybe for FreeBSD/amd64 # # For more information on this file, please read the config(5) manual page, # and/or the handbook section on Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD$ include GENERIC ident MAYBE # ZFS support options ZFS # PF support device pf #PF OpenBSD packet-filter firewall device pflog #logging support interface for PF # # Temperature sensors: # # coretemp: on-die sensor on Intel Core and newer CPUs # device coretemp yasu@maybe[2008]% -- I tried GENERIC kernel but the problem still happened. HWs are, M/B: ASUS N3150I-C (https://www.asus.com/us/Motherboards/N3150IC/) Display: EIZO FlexScan L565 (http://www.eizoglobal.com/support/db/products/model/L565) M/B and display are connected with analog VGA. Does anyone experiences same problem? Are there any solution or workaound? Best Regards. --- Yasuhiro KIMURA ___ 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"
Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282
From: Michael Grimm Subject: syslogd became silent between 11.2-PRERELEASE r334874 and r335282 Date: Sun, 17 Jun 2018 16:27:33 +0200 > I am running service jails (VNET/bridge/epair) and a host at 11.2-PRERELEASE > r335282, upgraded from r334874 today. There was a large MFC about syslogd at r335059: https://svnweb.freebsd.org/base?view=revision=335059 -- MFC r309925, r309931, r309933, r310035, r310278, r310310, r310311, r310323, r310349, r310350, r310351, r310352, r310383, r310384, r310385, r310386, r310393, r310453, r310456, r310494, r310504, r310528, r310890, r310893, r310974, r311918, r312921, r313357, r314563, r314585, r314642, r315322, r315618, r315620, r315622, r315643, r316951, r316973, r326338, r326339, r326573, r331270, r332099, r332110, r332111, r332118, r332165, r332510 and r332511. This commit brings syslogd(8) in sync with the copy in HEAD. The key improvement of this change is that it adds support for RFC 5424 log ingestion and exposition (enabled by passing in -O rfc5424). This allows for saner logging in environments with multiple time zones. The list of changes to merge back were obtained by running: svn mergeinfo --show-revs eligible \ ^/head/usr.sbin/syslogd ^/stable/11/usr.sbin/syslogd Of the commits listed, r314436, r325188 and r326025 were excluded, as they affect a significant number of unrelated files (SPDX and 4-clause license renumbering). Due to the large number of directly committed changes on this branch, I had no choice but to perform the merge as follows: svn merge --accept=theirs-full -c ^/head . This would, however, cause some unrelated changes, such as undoing the r56 (MFC of r332877) and still adding the SPDX tag to syslogd.c. These have been reverted manually. Requested by: Dave Cottlehuber Thanks to: dim@ for sharing his insight on hackers@ -- So how about take following steps? 1. svn update -r 335058 /usr/src 2. Rebuild and reinstall /usr/sbin/syslogd and /usr/bin/wall on both host and jail. 3. Restart syslogd on both host and jail. And if the problem is dissapeared, then you should open bug report. Best, --- Yasuhiro KIMURA ___ 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"
Two problems about ASUS N3150I-C
Hello. I have two 11.1-RELEASE amd64 boxes working as my home servers. Their hardware spec are same and ASUS N3150I-C is used as motherboad. And there are two problems about it. 1. 'shutdown -r now' doesn't work after system has been up for a while If I try 'shutdown -r now' just after system is up or after few hours, it works as is expected. But, for example, if I try it after one week of uptime, then it doesn't work anymore. OS is shutdown successfully but reset never happens. I updated BIOS of motherboard to latest one but it didn't fix the problem. And this problem happens on both boxes. 2. NIC gets no response with 're0: watchdog timeout' kernel message Realtek RTL8111H is used as NIC of this motherboad. Sometime it gets no response after following kernel messages are displayed some times. Dec 10 01:11:37 maybe kernel: re0: watchdog timeout Dec 10 01:11:37 maybe kernel: re0: link state changed to DOWN Dec 10 01:11:41 maybe kernel: re0: link state changed to UP If this happens system need to be rebooted. It is very variable when NIC get this status. Sometime it happens after few hours system is up, but sometimes it doesn't happen after a month of uptime. And this problem happens only one of two boxes. One box is used for internal services and the other is used for external ones. The problem only happens on the latter. As is explaind above they have same hardware spec, but OS settings and/or installed applications are differnt. So it seems some of them specific to the latter are cause of NIC hangup. Then, are there any way to fix these problems or investigate why they happens? Any suggestions or comments are welcome. --- Yasuhiro KIMURA ___ 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"
Re: Freebsd 10 to 11 sendmail compile issues..
From: Howard Leadmon <how...@leadmon.net> Subject: Freebsd 10 to 11 sendmail compile issues.. Date: Sat, 21 Oct 2017 19:22:40 -0400 > I have the following flags in /etc/make.conf: > > SENDMAIL_CFLAGS= -I/usr/local/include -DSASL=2 -DDNSMAP -DSTARTTLS > SENDMAIL_LDFLAGS= -L/usr/local/lib > SENDMAIL_LDADD= -lsasl2 -lssl -lcrypto > > > So I trhought OK, simple enough looking at the error and changed this > over to the following: > > SENDMAIL_CFLAGS= -I/usr/local/include -DSASL=2 -DDNSMAP -DSTARTTLS > SENDMAIL_LDFLAGS= -L/usr/local/lib > SENDMAIL_LIBADD+= sasl2 ssl crypto It seems you intend to link base sendmail binary with library that is installed by security/cyrus-sasl2 port. If so I think following steps are required. 1. Temporarily comment out all sendmail related settings in /etc/make.conf 2. Rebuild operating system and upgrade from 10.3 to 11.1. 3. Rebuild all installed ports on 11.1. 4. Enable settings again that is disabled at step 1 and rebuild base sendmail. To be honest I'm not sure if step 4 succeed. But it is quite possible that linking binary for 11.1 with library built on 10.3 causes unpredictable trouble. So you should keep above steps anyway. --- Yasuhiro KIMURA ___ 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"
