[Bug 238733] kvm disk i/o extremely slow
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238733 Bug ID: 238733 Summary: kvm disk i/o extremely slow Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: rai...@ultra-secure.de Hi, I've posted this on the forum: https://forums.freebsd.org/threads/is-kvm-virtio-really-that-slow-on-freebsd.71186/#post-430366 But I'll reiterate here. Basically, I'm running a FreeBSD 12 image created alongside this document: https://docs.openstack.org/image-guide/freebsd-image.html (plus swap) On a KVM host that is, TTBOMK, Ubuntu 18. Storage is Ceph Blockstorage, using pure NVMe SSDs - but I/O is capped at 2000 IOP/s. Using CentOS as a KVM guest, I basically get this: [root@centos ~]# dc3dd wipe=/dev/sdb dc3dd 7.1.614 started at 2019-06-20 07:54:22 + compiled options: command line: dc3dd wipe=/dev/sdb device size: 83886080 sectors (probed) sector size: 512 bytes (probed) 42949672960 bytes (40 G) copied (100%), 342.37 s, 120 M/s input results for pattern `00': 83886080 sectors in output results for device `/dev/sdb': 83886080 sectors out dc3dd completed at 2019-06-20 08:00:05 + Using FreeBSD, I get this: root@freebsd:~ # dc3dd wipe=/dev/vtbd2 dc3dd 7.2.646 started at 2019-06-20 09:37:10 +0200 compiled options: command line: dc3dd wipe=/dev/vtbd2 device size: 83886080 sectors (probed), 42,949,672,960 bytes sector size: 512 bytes (probed) 42949672960 bytes ( 40 G ) copied ( 100% ), 4585 s, 8.9 M/s input results for pattern `00': 83886080 sectors in output results for device `/dev/vtbd2': 83886080 sectors out dc3dd completed at 2019-06-20 10:53:35 +0200 The forum posting has fio-runs with the actual I/O numbers. Are the drivers really that bad? If this is the situation, FreeBSD is completely useless in the cloud. At least for us. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 237011] bsnmp fails to start with begemotSnmpdModulePath."pf"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237011 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: syrinx Date: Fri Jun 21 07:29:02 UTC 2019 New revision: 349264 URL: https://svnweb.freebsd.org/changeset/base/349264 Log: Unbreak snmp_pf(3) after the changes introduced in r338209 PR: 237011 Event:Vienna Hackathon 2019 MFC after:2 weeks Changes: head/usr.sbin/bsnmpd/modules/snmp_pf/pf_snmp.c head/usr.sbin/bsnmpd/modules/snmp_pf/pf_tree.def -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238735] New RC script to load binmisc activators
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238735 Bug ID: 238735 Summary: New RC script to load binmisc activators Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: msl023...@gmail.com Created attachment 205249 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205249&action=edit /etc/rc.d/binmisc Hello. I wrote a rc script that wraps binmiscctl(8) to load custom binmisc activators on boot time automatically. I think this script may be useful to others, if it could be included in base system. Usage: Put following into 'rc.conf': binmisc_enable="YES" binmisc_names=" [] [...]" binmisc__magic= binmisc__size="" binmisc__interpreter="" [binmisc__mask=] [binmisc__offset=""] Example: binmisc_enable="YES" binmisc_names="mono" binmisc_mono_magic='\x4d\x5a\x90\x00\x03\x00\x00\x00\x04\x00\x00\x00\xff\xff\x00\x00\xb8\x00\x00\x00' binmisc_mono_size="20" binmisc_mono_interpreter="/usr/local/bin/mono" -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233431] [bsnmpd] regression on 12-STABLE: crash on start
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233431 --- Comment #2 from commit-h...@freebsd.org --- A commit references this bug: Author: syrinx Date: Fri Jun 21 07:45:59 UTC 2019 New revision: 349265 URL: https://svnweb.freebsd.org/changeset/base/349265 Log: No need for each bsnmpd(1) module to open connection to syslog bsnmpd(1) main does that early on init and the connection is available to all loaded modules Event:Vienna Hackathon 2019 PR: 233431 , 221487 MFC after:2 weeks Changes: head/usr.sbin/bsnmpd/modules/snmp_lm75/snmp_lm75.c -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221487] [bsnmpd] crashes on startup with the enabled module begemotSnmpdModulePath."pf"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221487 --- Comment #5 from commit-h...@freebsd.org --- A commit references this bug: Author: syrinx Date: Fri Jun 21 07:45:59 UTC 2019 New revision: 349265 URL: https://svnweb.freebsd.org/changeset/base/349265 Log: No need for each bsnmpd(1) module to open connection to syslog bsnmpd(1) main does that early on init and the connection is available to all loaded modules Event:Vienna Hackathon 2019 PR: 233431 , 221487 MFC after:2 weeks Changes: head/usr.sbin/bsnmpd/modules/snmp_lm75/snmp_lm75.c -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238735] New RC script to load binmisc activators
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238735 WHR changed: What|Removed |Added CC||msl023...@gmail.com --- Comment #1 from WHR --- Created attachment 205251 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205251&action=edit binmisc.rc.diff Add a SVN diff file. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238733] kvm disk i/o extremely slow
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238733 rai...@ultra-secure.de changed: What|Removed |Added Hardware|Any |amd64 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238120] cron(8) doesn't set the HOME environment variable to users's home directory when command runs under regular user
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238120 WHR changed: What|Removed |Added CC||msl023...@gmail.com --- Comment #1 from WHR --- Can't reproduce on 12.0-STABLE r349024 GENERIC amd64. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 237368] /bin/df ; df on more than one unmounted device coredumps
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237368 WHR changed: What|Removed |Added CC||msl023...@gmail.com --- Comment #1 from WHR --- Seems also affecting 11.2-RELEASE. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238120] cron(8) doesn't set the HOME environment variable to users's home directory when command runs under regular user
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238120 --- Comment #2 from Yuri Victorovich --- On 12.0-STABLE r347548 GENERIC amd64 Add this line to /etc/crontab: > * * * * * yuri /home/yuri/cron-env-test.sh /home/yuri/cron-env-test.sh contains: > #!/bin/sh > echo "`date`: "$HOME >> /tmp/cron-env-test.txt It printed into /tmp/cron-env-test.txt: > Fri Jun 21 02:18:00 PDT 2019: /var/log -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238740] make buildworld fails in libc code at /usr/src/lib/libc/i386/gen/_ctx_start.S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238740 Bug ID: 238740 Summary: make buildworld fails in libc code at /usr/src/lib/libc/i386/gen/_ctx_start.S Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: o...@oz42.eu make buildworld fails at /usr/src/lib/libc/i386/gen/_ctx_start.S Building /usr/obj/usr/src/i386.i386/lib/libc/cancelpoints_sem.o Building /usr/obj/usr/src/i386.i386/lib/libc/cancelpoints_sem_new.o Building /usr/obj/usr/src/i386.i386/lib/libc/_ctx_start.o Building /usr/obj/usr/src/i386.i386/lib/libc/_setjmp.o Building /usr/obj/usr/src/i386.i386/lib/libc/_set_tp.o Building /usr/obj/usr/src/i386.i386/lib/libc/fabs.o --- _ctx_start.o --- /usr/src/lib/libc/i386/gen/_ctx_start.S:44:2: error: invalid instruction mnemonic 'pic_prologue' PIC_PROLOGUE ^~~~ *** [_ctx_start.o] Error code 1 make[4]: stopped in /usr/src/lib/libc -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238120] cron(8) doesn't set the HOME environment variable to users's home directory when command runs under regular user
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238120 Bob Bishop changed: What|Removed |Added CC||r...@gid.co.uk --- Comment #3 from Bob Bishop --- This bug refers to /etc/crontab. crontab(5) says "HOME [is] set from the /etc/passwd line of the crontab's owner", true for user crontabs but apparently not for /etc/crontab. This looks like a documentation problem. crontab(5) doesn't really describe /etc/crontab, cron(8) notwithstanding. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238741] RACK tcpip stack causes connections to hang
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238741 Bug ID: 238741 Summary: RACK tcpip stack causes connections to hang Product: Base System Version: 12.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: ad...@salesmanager.nl When using the RACK tcpip stack, fetch will hang and eventually generate a timeout. To reproduce the problem: # uname -a FreeBSD mail.xxx.yyy 12.0-RELEASE-p6 FreeBSD 12.0-RELEASE-p6 r349226 MAIL amd64 # kldload tcp_rack # sysctl net.inet.tcp.functions_default=rack # fetch https://cpan.metacpan.org/authors/id/I/IS/ISHIGAKI/JSON-PP-4.03.tar.gz When using wget, the same url can be retrieved without problems. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238741] RACK tcpip stack causes connections to hang
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238741 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238120] cron(8) doesn't set the HOME environment variable to users's home directory when command runs under regular user
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238120 --- Comment #4 from WHR --- (In reply to Yuri Victorovich from comment #2) The line I added in /etc/crontab is: * * * * * WHR /home/WHR/cron-env-test.sh cron-env-test.sh file is exactly same. The result is: [WHR@x ~]$ cat /tmp/cron-env-test Fri Jun 21 20:41:00 CST 2019: /usr/home/WHR Fri Jun 21 20:42:00 CST 2019: /usr/home/WHR Fri Jun 21 20:43:00 CST 2019: /usr/home/WHR Fri Jun 21 20:44:00 CST 2019: /usr/home/WHR Fri Jun 21 20:45:00 CST 2019: /usr/home/WHR Fri Jun 21 20:46:00 CST 2019: /usr/home/WHR [WHR@x ~]$ uname -a FreeBSD x 12.0-STABLE FreeBSD 12.0-STABLE r349024 GENERIC amd64 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238740] make buildworld fails in libc code at /usr/src/lib/libc/i386/gen/_ctx_start.S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238740 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #1 from Ed Maste --- CI is currently green so may be a local problem. https://ci.freebsd.org/tinderbox/ I suggest deleting all object files (under /usr/obj/...) and trying again, and if it still fails post to the freebsd-stable mailing list. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238725] Severe NFS exports(5) -maproot regression for :group definition
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238725 --- Comment #1 from Harald Schmalzbauer --- Found some time to falsify r346976 (MFCd in https://svnweb.freebsd.org/base?view=revision&revision=347340). Reverting that single commit restores full -maproot support. Will see if I can come up with a patch, but I guess more skilled hackers need much less time... Thanks, -harry -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238748] several race conditions in nandsim
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238748
Bug ID: 238748
Summary: several race conditions in nandsim
Product: Base System
Version: 12.0-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: ema...@freebsd.org
Reported to secteam (admbugs 795) but does not need to be treated as a security
issue because the NAND framework is not built by default, nandsim is not
intended for production use, and the device is root-only.
Reported by: Ilja Van Sprundel
the nandsim driver has a global variable called crtls. when it's used no locks
are held. this can cause race conditions in several places leading -among other
things- to:
- double free
- NULL deref
- memory leak
freebsd-master\sys\dev\nand\nandsim.c
static int
nandsim_create_chip(struct sim_chip *chip)
{
struct sim_chip *sim_chip;
nand_debug(NDBG_SIM,"create chip num:%d at ctrl:%d", chip->num,
chip->ctrl_num);
if (chip->ctrl_num >= MAX_SIM_DEV ||
chip->num >= MAX_CTRL_CS) {
return (EINVAL);
}
if (ctrls[chip->ctrl_num].chips[chip->num]) {
return (EEXIST);
}
sim_chip = malloc(sizeof(*sim_chip), M_NANDSIM,
M_WAITOK);
if (sim_chip == NULL) {
return (ENOMEM);
}
memcpy(sim_chip, chip, sizeof(*sim_chip));
ctrls[chip->ctrl_num].chips[chip->num] = sim_chip; <-- <-- no ctrls lock held,
this can leak
sim_chip->created = 1;
return (0);
}
static int
nandsim_destroy_chip(struct sim_ctrl_chip *chip)
{
struct sim_ctrl_conf *ctrl_conf;
nand_debug(NDBG_SIM,"destroy chip num:%d at ctrl:%d", chip->chip_num,
chip->ctrl_num);
if (chip->ctrl_num >= MAX_SIM_DEV ||
chip->chip_num >= MAX_CTRL_CS)
return (EINVAL);
ctrl_conf = &ctrls[chip->ctrl_num];
if (!ctrl_conf->created || !ctrl_conf->chips[chip->chip_num])
return (ENODEV);
if (ctrl_conf->running)
return (EBUSY);
free(ctrl_conf->chips[chip->chip_num], M_NANDSIM); <-- no ctrls lock held, this
could double free
ctrl_conf->chips[chip->chip_num] = NULL;
return (0);
}
static int
nandsim_modify(struct sim_mod *mod)
{
struct sim_chip *sim_conf = NULL;
struct nandsim_chip *sim_chip = NULL;
nand_debug(NDBG_SIM,"modify ctlr %d chip %d", mod->ctrl_num,
mod->chip_num);
if (mod->field != SIM_MOD_LOG_LEVEL) {
if (mod->ctrl_num >= MAX_SIM_DEV ||
mod->chip_num >= MAX_CTRL_CS)
return (EINVAL);
sim_conf = ctrls[mod->ctrl_num].chips[mod->chip_num]; <-- can be NULL!
sim_chip = get_nandsim_chip(mod->ctrl_num, mod->chip_num); <-- can be NULL!
}
switch (mod->field) {
case SIM_MOD_LOG_LEVEL:
nandsim_log_level = mod->new_value; <-- NULL deref
break;
case SIM_MOD_ERASE_TIME:
sim_conf->erase_time = sim_chip->erase_delay = mod->new_value; <-- NULL deref
break;
case SIM_MOD_PROG_TIME:
sim_conf->prog_time = sim_chip->prog_delay = mod->new_value; <-- NULL deref
break;
case SIM_MOD_READ_TIME:
sim_conf->read_time = sim_chip->read_delay = mod->new_value; <-- NULL deref
break;
case SIM_MOD_ERROR_RATIO:
sim_conf->error_ratio = mod->new_value; <-- NULL deref
sim_chip->error_ratio = mod->new_value;
break;
default:
break;
}
return (0);
}
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 237368] /bin/df ; df on more than one unmounted device coredumps
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237368 Jamie Landeg-Jones changed: What|Removed |Added CC||ja...@catflap.org Severity|Affects Only Me |Affects Some People --- Comment #2 from Jamie Landeg-Jones --- Cheers, WHR. Anyone listening? I'll provide a patch to fix or remove this depracted code if required. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238725] Severe NFS exports(5) -maproot regression for :group definition
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238725 Harald Schmalzbauer changed: What|Removed |Added Version|12.0-STABLE |11.3-RELEASE -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238725] Severe NFS exports(5) -maproot regression for :group definition
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238725 Harald Schmalzbauer changed: What|Removed |Added Component|kern|bin -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238749] startup error in boot/lua/loader.lua
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238749 Bug ID: 238749 Summary: startup error in boot/lua/loader.lua Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: omen...@ya.ru Дано: при прочих равных условиях: 12_0_RELEASE_AMD64_DVD -- устанавливается без проблем. следующие релизы: 12_0_RELEASE_AMD64 --- не устанавливается. 13_0_AMD64 --- не устанавливается. дают ошибку --- startup error in boot/lua/loader.lua прим. релиз 13_0_AMD64 --- декабрь 2018 ставился без проблем. 1. неужели авторы косяка до сих пор не знают об этой проблеме. 2. когда будет исправлен этот косяк. omen...@ya.ru александр -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238749] startup error in boot/lua/loader.lua
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238749 --- Comment #1 from Conrad Meyer --- Можете ли вы предоставить скриншот? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238324] Add XG-C100C/AQtion AQC107 10GbE NIC driver
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238324 --- Comment #1 from Anda --- The driver is now publicly available via there website. https://www.aquantia.com/support/driver-download/ -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238725] Severe NFS exports(5) -maproot regression for :group definition
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238725 --- Comment #2 from Harald Schmalzbauer --- Sorry for the bad reproduction info. The choosen values are nonsense and inconsistent in the example... But I guess that doesn't matter much. Here's the breaking part: Index: usr.sbin/mountd/mountd.c === --- usr.sbin/mountd/mountd.c(Revision 349275) +++ usr.sbin/mountd/mountd.c(Arbeitskopie) @@ -2958,8 +2958,8 @@ /* * Get the user's password table entry. */ - names = namelist; - name = strsep_quote(&names, ":"); + names = strsep_quote(&namelist, " \t\n"); + name = strsep(&names, ":"); /* Bug? name could be NULL here */ if (isdigit(*name) || *name == '-') pw = getpwuid(atoi(name)); This reverse-diff restores working state. I have no idea what the intention was. At least dlim seems to be unintentionally changed? Thanks, -harry P.S.: Like mentioned, I consider this as severe surprise for useres updating to 11.3 and wondering why NFS doesn't work as before... -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238349] Fresh install will not boot under some circumstances
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238349 --- Comment #2 from Ronald F. Guilmette --- I can only tell you what I *believe* I did, obviously, since I wasn't videoing myself as I did this. (Maybe I will next time! :-) I'm not sure that any of this info will help though, as I believe that I did all of the exact same manual partitioning actions the second time around, i.e. *after* I had *also* done: 1) gpart destroy -F ada0 2) dd if=/dev/zero of=/dev/ada0 bs=1M count=10 However on this second install attempt everything worked, no problem. Anyway, what I did, to the best of my recollection was this: I started out, of course, selecting GPT as the partitioning scheme. I created a 1 GiB / (root) partition... type freebsd-ufs of course. I created a 16 GiB swap partition (freebsd-swap). The rest is as you can see here, which is the "df -k" output from my (now running) system: /dev/ada0p2 101494023175670199225%/ devfs 1 1 0 100%/dev /dev/ada0p4 3044988 1174092 162730042%/var /dev/ada0p5 2031132 16444 1852200 1%/var/ftp /dev/ada0p6 101532439242854167242%/tmp /dev/ada0p7 16233660 8574620 636034857%/usr /dev/ada0p8 32487548 22888624 62477%/home /dev/ada0p9400156276 258842812 10930096470%/v /dev/ada0p10 473796804 32808 435860252 0%/w procfs 4 4 0 100%/proc I hope and trust that this answers your question. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238407] lpd(8) man page -- missing operational detail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238407 --- Comment #2 from Ronald F. Guilmette --- (In reply to Rodney W. Grimes from comment #1) Sorry. Yes. That was just a very unfortunate typo... or more accurately, two of them. The man page at issue here is the lpd(8) one. My bad. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238753] /etc/rc.d/local_unbound fails to honor configuration directory setting pre-start
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238753 Bug ID: 238753 Summary: /etc/rc.d/local_unbound fails to honor configuration directory setting pre-start Product: Base System Version: 12.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: conf Assignee: b...@freebsd.org Reporter: k...@denninger.net Created attachment 205269 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205269&action=edit Address missing "-c" flag on the control command /etc/rc.d/local_unbound starts the local "unbound" nameserver. The script assumes the working directory is in /var/unbound, which is valid for most users. However, in an embedded environment /var is frequently on a ramdisk and not saved (that is, it's volatile), which means you need to move this directory for those environments since otherwise you will be regenerating the configuration on each boot -- and that is probably not desirable. The base RC script is intended to honor local_unbound_workdir in /etc/rc.conf, but the "local_unbound_poststart()" function makes a call to the "-control" software without specifying the config directory explicitly with "-c". If the working directory is not in the default location this results in that command failing; this is not fatal since the test gives up after five tries, but it should honor the config directive and thus know when the startup has completed successfully. The attached patch adds the "-c" flag to the control command and resolves the issue. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238753] /etc/rc.d/local_unbound fails to honor configuration directory setting post-start
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238753 k...@denninger.net changed: What|Removed |Added Summary|/etc/rc.d/local_unbound |/etc/rc.d/local_unbound |fails to honor |fails to honor |configuration directory |configuration directory |setting pre-start |setting post-start -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238753] /etc/rc.d/local_unbound fails to honor configuration directory setting post-start
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238753 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|r...@freebsd.org Keywords||patch -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238730] r349241 on ppc64 IBM 970 instant panic in vm_mem_init(0)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238730 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org --- Comment #1 from Mark Johnston --- Have you booted FreeBSD successfully on this hardware in the past? segind 91 is way bigger the VM_PHYSSEG_MAX for powerpc (16), which suggests that vm_page_startup() is adding uninitialized page structures to the physical memory allocator. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238729] head -r347549 on aorus gaming 7 F12e BIOS (Threadripper 1950X): boot attempts hang (but boots for fedora/Windows 10 Pro)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238729 --- Comment #9 from Mark Millard --- Created attachment 205272 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205272&action=edit gzip holding *.dsl files from iasl -d (not including dsdt) The *.dat files were from fedora (which boots the machine). I used the FreeBSD iasl command (via Hyper-V use). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238729] head -r347549 on aorus gaming 7 F12e BIOS (Threadripper 1950X): boot attempts hang (but boots for fedora/Windows 10 Pro)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238729 --- Comment #10 from Mark Millard --- (In reply to Mark Millard from comment #9) Among other things, ssddt5.dsl seems odd (truncated). But ssdt5.dat was only 36 bytes long in the first place, much shorter than any other ssdt*.dat . -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 238729] head -r347549 on aorus gaming 7 F12e BIOS (Threadripper 1950X): boot attempts hang (but boots for fedora/Windows 10 Pro)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238729 --- Comment #11 from Mark Millard --- (In reply to Mark Millard from comment #10) Using: options ACPI_DEBUG and: hw.acpi.verbose=1 debug.acpi.layer="ACPI_ALL_COMPONENTS ACPI_ALL_DRIVERS" debug.acpi.level="ACPI_LV_ALL_EXCEPTIONS" The output stopped with (typed from a screen picture): exregion-0323 ExSystemMemorySpaceHan: System-Memory (width 8) R/W 0 Address=771ED01F The earlier part of the screen was similar, with Address varying. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
The problem with the work of micro-sd card in FreeBSD
Good afternoon, dear FreeBSD technical support! I have the following problem: my small computer with FreeBSD 12 installed on it cannot work with the built-in card reader. Help, please solve this problem! ( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238570 ) Error messages: /var/log/messages Jun 14 16:00:00 dc newsyslog[3194]: logfile turned over due to size>1000K Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD24 arg 0x71d2e flags 0x35 data 512 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6814e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x68b280 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a550 flags 0x35 data 4096 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD24 arg 0x71d2f flags 0x35 data 512 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6814e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a9a8 flags 0x35 data 8192 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data 32768 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x69a9a8 flags 0x35 data 8192 Jun 14 16:00:00 dc kernel: mmc1: REQUEST: CMD25 arg 0x6815e8 flags 0x35 data ... Jun 14 16:00:00 dc kernel: mmc1: R
