Re: Cannot set CPU frequency for 8th gen CPU
On Wed, 18 Jul 2018, at 8:31 PM, Dave Green wrote: > If I disable 5 of the 6 > cores in the BIOS then setting frequency as above is successful. Further, when setting: # sysctl debug.cpufreq.verbose=1 A different 11.1 amd64 system with a 2nd gen 4 core processor reports: cpufreq: setting abs freq 2500 on est0 (cpu 0) cpufreq: setting abs freq 2500 on est1 (cpu 1) cpufreq: setting abs freq 2500 on est2 (cpu 2) cpufreq: setting abs freq 2500 on est3 (cpu 3) Whereas the 11.2 amd64 system with the 8th gen 6 core reports: cpufreq: setting abs freq 2800 on est0 (cpu 1) cpufreq: setting abs freq 2800 on est1 (cpu 2) cpufreq: setting abs freq 2800 on est2 (cpu 3) cpufreq: setting abs freq 2800 on est3 (cpu 4) cpufreq: setting abs freq 2800 on est3 (cpu 5) For the second (faulty) system cpu0 is conspicuously missing and may explain why frequency can only be set on that machine with all but one core disabled? ___ 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"
Cannot set CPU frequency for 8th gen CPU
I have an 8th gen (i5-8400) processor installed in motherboard using the H370 chipset (Gigabyte H370 HD3) with factory default BIOS configuration running FreeBSD 11.2 amd64. Although the correct number of cores (6) and available frequencies are correctly detected only the lowest frequency is usable: # sysctl dev.cpu.0.freq_levels dev.cpu.0.freq_levels: 2801/65000 2800/65000 2700/61690 2500/55888 2400/52759 2200/47301 2100/44946 1900/39204 1800/37000 1700/34277 1500/29546 1400/27531 1200/22557 1100/20688 900/16549 800/14296 # sysctl dev.cpu.0.freq=2800 dev.cpu.0.freq: 800 -> 800 Accordingly powerd continues to try and raise the frequency in response to high system load but is unable to do so. If I disable 5 of the 6 cores in the BIOS then setting frequency as above is successful. Has this been reproduced and/or what are the next steps I should take to investigate? Attached is the obligatory dmesg which contains some complaints about ACPI firmware of unknown relevance? -- CPU: Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz (2808.23-MHz K8-class CPU) Origin="GenuineIntel" Id=0x906ea Family=0x6 Model=0x9e Stepping=10 Features=0xbfebfbff Features2=0x7ffafbbf AMD Features=0x2c100800 AMD Features2=0x121 Structured Extended Features=0x29c67af Structured Extended Features2=0x4000 Structured Extended Features3=0xc00 XSAVE Features=0xf VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory = 17179869184 (16384 MB) avail memory = 16386461696 (15627 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 6 CPUs FreeBSD/SMP: 1 package(s) x 6 core(s) ioapic0 irqs 0-119 on motherboard SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #4 Launched! Timecounter "TSC-low" frequency 1404113625 Hz quality 1000 random: entropy device external interface kbd1 at kbdmux0 netmap: loaded module module_register_init: MOD_LOAD (vesa, 0x80ff4550, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" nexus0 cryptosoft0: on motherboard aesni0: on motherboard acpi0: on motherboard ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x33CCD (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x33CD6 (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x343C1 (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x343CA (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x34AB5 (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x34ABE (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x351AA (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x351B3 (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x3589F (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x358A8 (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x35C52 (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x35C5B (20171214/psloop-344) Firmware Error (ACPI): Failure looking up [\134_SB.PCI0.RP04.PXSX._SB.PCI0.RP05.PXSX], AE_NOT_FOUND (20171214/dswload2-312) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20171214/psobject-371) ACPI Error: Method parse/execution failed \134_SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20171214/psparse-677) Firmware Error (ACPI): Failure looking up [\134_SB.PCI0.RP08.PXSX._SB.PCI0.RP09.PXSX], AE_NOT_FOUND (20171214/dswload2-312) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20171214/psobject-371) ACPI Error: Method parse/execution failed \134_SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20171214/psparse-677) Firmware Error (ACPI): Failure looking up [\134_SB.PCI0.RP12.PXSX._SB.PCI0.RP13.PXSX], AE_NOT_FOUND (20171214/dswload2-312) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20171214/psobject-371) ACPI Error: Method parse/execution failed \134_SB.PCI0.RP12.PXSX, AE_NOT_FOUND (20171214/psparse-677) Firmware Error (ACPI): Failure looking up [\134_SB.PCI0.RP05.PXSX.WIST], AE_NOT_FOUND (20171214/psargs-503) ACPI Error: Method parse/execution failed \134CNDP, AE_NOT_FOUND (20171214/psparse-677) ACPI Error: Method parse/execution failed \134, AE_NOT_FOUND (20171214/psparse-677) acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 2400 Hz quality 950 Event timer
Re: [FreeBSD-Stable] svn commit: r296462 - in stable/9: crypto/openssl/crypto/bio crypto/openssl/crypto/bn crypto/openssl/doc/apps crypto/openssl/ssl secure/usr.bin/openssl/man
On 2016-03-09 5:19 PM, Mike Tancsa wrote: On 3/9/2016 5:06 PM, Dimitry Andric wrote: Can you please try the attached patch, which I also attached to PR 207783? I think this will solve the crashes. It should be enough to rebuild secure/lib/libcrypto, and install it. Hi, Yes it allows sshd to not crash on my one test case (secureCRT client) so far! Thanks. Looks to work as well on the second server here that SSH was crashing on. Thanks. :-) Craig. -- ___ 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-Stable] svn commit: r296462 - in stable/9: crypto/openssl/crypto/bio crypto/openssl/crypto/bn crypto/openssl/doc/apps crypto/openssl/ssl secure/usr.bin/openssl/man
On 2016-03-08 7:45 AM, Mike Tancsa wrote: Hi, I tried on 2 separate boxes, and sshd segfaults when this rev is applied ---Mike Just adding some debug logs showing a couple places where sshd exited. Encryption algorithm, kex and hmac didn't seem to matter. Craig. -- Mar 7 16:59:53 smtp1 sshd[40348]: debug1: rexec start in 5 out 5 newsock 5 pipe 7 sock 8 Mar 7 16:59:53 smtp1 sshd[40348]: debug1: inetd sockets after dupping: 3, 3 Mar 7 16:59:53 smtp1 sshd[40348]: debug1: res_init() Mar 7 16:59:53 smtp1 sshd[40348]: debug1: HPN Disabled: 0, HPN Buffer Size: 65536 Mar 7 16:59:53 smtp1 sshd[40348]: debug1: Client protocol version 2.0; client software version SecureCRT_6.6.1 (x64 build 289) SecureCRT Mar 7 16:59:53 smtp1 sshd[40348]: debug1: no match: SecureCRT_6.6.1 (x64 build 289) SecureCRT Mar 7 16:59:53 smtp1 sshd[40348]: debug1: Enabling compatibility mode for protocol 2.0 Mar 7 16:59:53 smtp1 sshd[40348]: debug1: Local version string SSH-2.0-OpenSSH_6.6.1_hpn13v11 FreeBSD-20140420 Mar 7 16:59:53 smtp1 sshd[40348]: debug1: list_hostkey_types: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ssh-ed25519 Mar 7 16:59:53 smtp1 sshd[40348]: debug1: SSH2_MSG_KEXINIT sent Mar 7 16:59:53 smtp1 sshd[40348]: debug1: SSH2_MSG_KEXINIT received Mar 7 16:59:53 smtp1 sshd[40348]: debug1: kex: client->server aes256-ctr hmac-sha1 none Mar 7 16:59:53 smtp1 sshd[40348]: debug1: kex: server->client aes256-ctr hmac-sha1 none Mar 7 16:59:53 smtp1 kernel: pid 40348 (sshd), uid 0: exited on signal 11 Mar 7 17:01:39 smtp1 sshd[46204]: debug1: rexec start in 5 out 5 newsock 5 pipe 7 sock 8 Mar 7 17:01:39 smtp1 sshd[46204]: debug1: inetd sockets after dupping: 3, 3 Mar 7 17:01:39 smtp1 sshd[46204]: debug1: res_init() Mar 7 17:01:39 smtp1 sshd[46204]: debug1: HPN Disabled: 0, HPN Buffer Size: 65536 Mar 7 17:01:39 smtp1 sshd[46204]: debug1: Client protocol version 2.0; client software version OpenSSH_6.1_hpn13v11 FreeBSD-20120901 Mar 7 17:01:39 smtp1 sshd[46204]: debug1: match: OpenSSH_6.1_hpn13v11 FreeBSD-20120901 pat OpenSSH* compat 0x0400 Mar 7 17:01:39 smtp1 sshd[46204]: debug1: Enabling compatibility mode for protocol 2.0 Mar 7 17:01:39 smtp1 sshd[46204]: debug1: Local version string SSH-2.0-OpenSSH_6.6.1_hpn13v11 FreeBSD-20140420 Mar 7 17:01:39 smtp1 sshd[46204]: debug1: list_hostkey_types: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ssh-ed25519 Mar 7 17:01:39 smtp1 sshd[46204]: debug1: SSH2_MSG_KEXINIT sent Mar 7 17:01:39 smtp1 sshd[46204]: debug1: SSH2_MSG_KEXINIT received Mar 7 17:01:39 smtp1 sshd[46204]: debug1: kex: client->server aes128-ctr hmac-md5 none Mar 7 17:01:39 smtp1 sshd[46204]: debug1: kex: server->client aes128-ctr hmac-md5 none Mar 7 17:01:39 smtp1 sshd[46204]: debug1: expecting SSH2_MSG_KEX_ECDH_INIT Mar 7 17:01:40 smtp1 kernel: pid 46204 (sshd), uid 0: exited on signal 11 Mar 7 17:02:01 smtp1 sshd[47350]: debug1: rexec start in 5 out 5 newsock 5 pipe 7 sock 8 Mar 7 17:02:01 smtp1 sshd[47350]: debug1: inetd sockets after dupping: 3, 3 Mar 7 17:02:01 smtp1 sshd[47350]: debug1: res_init() Mar 7 17:02:01 smtp1 sshd[47350]: debug1: HPN Disabled: 0, HPN Buffer Size: 65536 Mar 7 17:02:01 smtp1 sshd[47350]: debug1: Client protocol version 2.0; client software version OpenSSH_6.1_hpn13v11 FreeBSD-20120901 Mar 7 17:02:01 smtp1 sshd[47350]: debug1: match: OpenSSH_6.1_hpn13v11 FreeBSD-20120901 pat OpenSSH* compat 0x0400 Mar 7 17:02:01 smtp1 sshd[47350]: debug1: Enabling compatibility mode for protocol 2.0 Mar 7 17:02:01 smtp1 sshd[47350]: debug1: Local version string SSH-2.0-OpenSSH_6.6.1_hpn13v11 FreeBSD-20140420 Mar 7 17:02:01 smtp1 sshd[47350]: debug1: list_hostkey_types: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ssh-ed25519 Mar 7 17:02:01 smtp1 sshd[47350]: debug1: SSH2_MSG_KEXINIT sent Mar 7 17:02:01 smtp1 sshd[47350]: debug1: SSH2_MSG_KEXINIT received Mar 7 17:02:01 smtp1 sshd[47350]: debug1: kex: client->server aes128-ctr hmac-md5 none Mar 7 17:02:01 smtp1 sshd[47350]: debug1: kex: server->client aes128-ctr hmac-md5 none Mar 7 17:02:01 smtp1 sshd[47350]: debug1: expecting SSH2_MSG_KEX_ECDH_INIT Mar 7 17:02:01 smtp1 kernel: pid 47350 (sshd), uid 0: exited on signal 11 Mar 7 18:52:36 smtp1 sshd[1127]: debug1: rexec start in 5 out 5 newsock 5 pipe 7 sock 8 Mar 7 18:52:36 smtp1 sshd[1127]: debug1: inetd sockets after dupping: 3, 3 Mar 7 18:52:36 smtp1 sshd[1127]: debug1: res_init() Mar 7 18:52:36 smtp1 sshd[1127]: debug1: HPN Disabled: 0, HPN Buffer Size: 65536 Mar 7 18:52:36 smtp1 sshd[1127]: debug1: Client protocol version 2.0; client software version PuTTY_Release_0.60 Mar 7 18:52:36 smtp1 sshd[1127]: debug1: no match: PuTTY_Release_0.60 Mar 7 18:52:36 smtp1 sshd[1127]: debug1: Enabling compatibility mode for protocol 2.0 Mar 7 18:52:36 smtp1 sshd[1127]: debug1: Local version string SSH-2.0-OpenSSH_6.6.1_hpn13v11 FreeBSD-20140420 Mar 7 18:52:36 smtp1 sshd[1127]: debug1: list_hostkey_types:
Re: Skylake Loader Performance 10.3-BETA3
On 2016-03-07 17:24, Steven Hartland wrote: On 07/03/2016 16:43, Will Green wrote: On 4 Mar 2016, at 18:49, Mark Dixon <mnd...@hotmail.com> wrote: Will Green sundivenetworks.com> writes: I am happy to test patches and/or current on this server if that helps. If you want more details on the motherboard/system I have started a post on it at http://buildwithbsd.org/hw/skylake_xeon_server.html I've made the UEFI switch which worked fine, but I'm also happy to help out with testing if anyone looks at this. Are you booting from ZFS? Unless I’ve missed something this isn’t yet supported by the installer, but it is possible to get working manually. Pretty sure you missed something and those changes where merged, imp should be able to confirm. You're right: that was an error on my part. I've now got ZFS boot working with UEFI. :) I booted the Skylake motherboard with FreeBSD-10.3-RC1-amd64-uefi-memstick.img and it successfully installed to ZFS *and* loaded at normal speed. Looks like UEFI is the way to go on Skylake systems. All tests have gone well so far. Thanks ___ 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: Skylake Loader Performance 10.3-BETA3
> On 4 Mar 2016, at 18:49, Mark Dixon <mnd...@hotmail.com> wrote: > > Will Green sundivenetworks.com> writes: > >> I am happy to test patches and/or current on this server if that helps. If > you want more details on the >> motherboard/system I have started a post on it at > http://buildwithbsd.org/hw/skylake_xeon_server.html >> > > I've made the UEFI switch which worked fine, but I'm also happy to help out > with testing if anyone looks at this. Are you booting from ZFS? Unless I’ve missed something this isn’t yet supported by the installer, but it is possible to get working manually. Will ___ 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"
Skylake Loader Performance 10.3-BETA3
Hello, I’ve been testing a new Skylake E3 Xeon server with 10.3-BETA3. The slow loader issue described on the forums https://forums.freebsd.org/threads/53511/ is still present. On my Supermicro X11SSH-LN4F motherboard with E3-1260L v5 it takes over ten minutes to get to kernel boot. After that performance seems normal (though I’m still testing). This issue occurs when booting the installer from a USB stick or when booting the installed OS over SATA. I understand using UEFI resolves this issue, although I only have one Skylake motherboard model on which to confirm this. I know this issue is unlikely to be fixed for 10.3 release, but I think it should be noted in the release and/or hardware notes. Skylake systems are going to be increasing numerous this year, especially now Skylake Xeons are starting to ship in volume. I am happy to test patches and/or current on this server if that helps. If you want more details on the motherboard/system I have started a post on it at http://buildwithbsd.org/hw/skylake_xeon_server.html TIA Will ___ 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: Problems adding Intel 750 to zfs pool
I wonder if this is connected to NVMe? Our SATA Intel DC S3500 drives (which are not that different to the 750s) TRIM much more quickly. What does camcontrol think the secure erase time should be? For a 600GB S3500 camcontrol accurately gives the secure erase time as 4 minutes: # camcontrol security ada0 erase time4 min enhanced erase time 4 min Trimming drives before addition to a system is definitely worthwhile. Will On 20 Jul 2015, at 10:28, Steven Hartland kill...@multiplay.co.uk wrote: This will almost certainly be due to slow TRIM support on the device. Try setting the sysctl vfs.zfs.vdev.trim_on_init to 0 before adding the devices. On 18/07/2015 05:35, dy...@techtangents.com wrote: Hi, I've installed an Intel 750 400GB NVMe PCIe SSD in a Dell R320 running FreeBSD 10.2-beta-1... not STABLE, but not far behind, I think. Apologies if this is the wrong mailing list, or if this has been fixed in STABLE since the beta. Anyway, I've gparted it into 2 partitions - 16GB for slog/zil and 357GB for l2arc. Adding the slog partition to the pool takes about 2 minutes - machine seems hung during that time. Ping works, but I can't open another ssh session. Adding the l2arc doesn't seem to complete - it's been going 10 minutes now and nothing. Ping works, but I can't log in to the local console or another ssh session. I'm adding the partitions using their gpt names. i.e. zpool add zroot log gpt/slog zpool add zroot cache gpt/l2arc The system BIOS is up-to-date. The OS was a fresh 10.1 install, then freebsd-update to 10.2-beta2. 10.1 exhibited the same symptoms. Root is on zfs. Device was tested to be working on Windows 8.1 on a Dell T1700 workstation. Any ideas? Cheers, Dylan Just ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Xeon D-1540 Support
Hello, Has anyone had any success running FreeBSD 10.1 on the Xeon D-1540 [1]? It’s a 8-core Broadwell-based Xeon SOC with integrated GigE or 10GigE. The combination of low power and support for 128 GB of ram makes them quite attractive. An example motherboard with this CPU is the Supermicro X10SDV-F [2]. The Supermicro web site shows support for FreeBSD 10.1 [3], but I haven’t seen any use in the wild. I will try to get hold of a board to test, but any advance information on support would be useful. Thanks, Will [1] http://ark.intel.com/products/87039/Intel-Xeon-Processor-D-1540-12M-Cache-2_00-GHz [2] http://www.supermicro.co.uk/products/motherboard/Xeon/D/X10SDV-F.cfm [3] http://www.supermicro.co.uk/support/resources/OS/Broadwell-DE.cfm ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: File-Backed ZFS Kernel Panic still in 10.1-RELEASE (PR 195061)
Thanks Steven. I’ll hold off releasing the updated tutorials for now. On 21 Apr 2015, at 17:45, Steven Hartland kill...@multiplay.co.uk wrote: I did actually request this back in November, but I don't seem to have had a reply so I'll chase. On 21/04/2015 16:23, Will Green wrote: Hello, I have been updating my ZFS tutorials for use on FreeBSD 10.1. To allow users to experiment with ZFS I use file-backed ZFS pools. On FreeBSD 10.1 they cause a kernel panic. For example a simple command like the following causes a panic: zpool create /tmp/zfstut/disk1 This issue was identified in PR 195061: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195061 And fixed in r274619 (2014-11-17): https://svnweb.freebsd.org/base?view=revisionrevision=274619 However, even on 10.1-RELEASE-p9 the kernel panic still occurs (but doesn’t on 11-CURRENT). Are there any plans to patch this in 10.1? I note it’s not in the errata. My tutorials are not the only ones that use file-backed ZFS: new users experimenting with ZFS on FreeBSD are likely to encounter this issue. Thanks, Will ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
File-Backed ZFS Kernel Panic still in 10.1-RELEASE (PR 195061)
Hello, I have been updating my ZFS tutorials for use on FreeBSD 10.1. To allow users to experiment with ZFS I use file-backed ZFS pools. On FreeBSD 10.1 they cause a kernel panic. For example a simple command like the following causes a panic: zpool create /tmp/zfstut/disk1 This issue was identified in PR 195061: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195061 And fixed in r274619 (2014-11-17): https://svnweb.freebsd.org/base?view=revisionrevision=274619 However, even on 10.1-RELEASE-p9 the kernel panic still occurs (but doesn’t on 11-CURRENT). Are there any plans to patch this in 10.1? I note it’s not in the errata. My tutorials are not the only ones that use file-backed ZFS: new users experimenting with ZFS on FreeBSD are likely to encounter this issue. Thanks, Will ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Mergemaster [was: Re: Ifconfig config of gif tunnels]
Matthew Dillon wrote about mergemaster: - I also like the idea someone posted in regards to having a list of files 'typically never modified by the sysop', e.g. /etc/defaults/*, /etc/rc*, and so forth, though with the patches I have so far that particular problem is not so big a deal any more (at least not for me). - Mergemaster automatically updating the various default files, displaying to the admin only the files the admin actually might want to see during a normal upgrade, would be quite desirable to me. What would also be helpful, though this may be diff's fault, would be if there were less tendency for mergemaster to combine changes the admin likely wants to make (adding a new user the OS requires) with changes the admin does not want to make (removing surrounding entries out of master.passwd), requiring the admin to make a note of mergemaster's suggestions followed by editing the file by hand. Thanks, --Lucky Green To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Ssh problems and more after update
I ran what into what, at first glance, sounds like similar problems with ssh as some others on this list after updating a few days ago to 4.6.1-RELEASE-p10 from 4.6.1-RELEASE as of 2002-07-21. I followed the usual sequence: buildworld, buildkernel, installkernel, installworld, mergemaster. After reboot, I could ping the machine, but all services, including sshd (from ports), smtpd (postfix), and httpd (Apache) were down. Syslog was useless. The closest guess that I can come up with is that for whatever reason, the OS failed to read rc.conf and rc.d after boot. After a few reboots and some voodoo that may or may not have had any impact (moving the sshd startup script from rc.conf to rc.d), the services started by both rc.conf and the services started via rc.d are now again operational. The problem that remains is that I have no idea what caused the failure. Since I don't have physical access to the box - until I know what happened - I will be rather apprehensive rebooting the machine once the next security flaw needs to be patched in what has turned out to be a Summer of exploits. If you have seen anything similar during a recent update, please let me know. Thanks, --Lucky Green To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
