Re: [Bug 240121] Serial console can eat a lot of CPU with low baudrate

On Mon, 26 Aug 2019 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240121 That effect is unexpected to me. I would expect opposite -- reduction of wait time, since code reduces number of buffer flushes and utilizes hardware FIFO. I may

Re: [Bug 238837] init: Remove P_SYSTEM flag from PID 1 to allow easier debugging of init(8)

On Sun, 14 Jul 2019, [UTF-8] ?~N~K?~X~J?~D? wrote: Thanks for share this. The followings are my suggestions. But debugging also requires normal signal handling, perhaps including core dumps, so my replacements for the bogus pid tests may be too strong. I think this could be fixed by

Re: [Bug 238837] init: Remove P_SYSTEM flag from PID 1 to allow easier debugging of init(8)

On Sat, 13 Jul 2019 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238837 --- Comment #3 from WHR --- (In reply to Conrad Meyer from comment #2) I knwon that ptrace(2) can't be used to debug any kernel processes, allowing that would hang

Re: Miscommunication when changing media interface

On Wed, 29 May 2019, [UTF-8] Andr?? S. Almeida wrote: When the network interface media "em0" is changed the communication stops working. To reproduce the problem simply execute: ifconfig em0 media autoselect If you change "autoselect" to any other media, the same problem happens. I am using

Re: [Bug 202712] [cam] [ata] System doesn't recognize older hdd after boot

On Mon, 22 Apr 2019 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712 --- Comment #21 from Andriy Gapon --- (In reply to Domagoj Hranjec from comment #20) And my point is that I am not sure if you have actually tested reading from the

Re: [Bug 202712] [cam] [ata] System doesn't recognize older hdd after boot

On Sun, 21 Apr 2019 a bug that doesn't want repl...@freebsd.org wrote: Created attachment 203861 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203861=edit dmesg log with 8.4 livefs disk I've booted the FreeBSD 8.4 livefs disk. Disk is correctly configured: ad3: FAILURE -

Re: [Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware

On Thu, 4 Apr 2019 a bug that dpesnt want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 --- Comment #5 from longw...@incore.de --- Created attachment 203384 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203384=edit Output serial console of full

Re: [Bug 236702] KERN_UPTIME not updated after resume

On Thu, 21 Mar 2019 bugzilla-nore...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236702 Bug ID: 236702 Summary: KERN_UPTIME not updated after resume ... Reporter: tr...@freebsd.org It seems the time returned by clock_gettime(CLOCK_UPTIME)

Re: [Bug 236096] top shows WCPU numbers greater than 100 percent when using SCHED_BSD

On Thu, 28 Feb 2019 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236096 After switching from SCHED_ULE to SCHED_4BSD I immediately noticed that top Congratulations on the switch. SCHED_ULE is slightly better, but I use my version

Re: [Bug 236065] TimeStamp Overflow 2106 year

On Tue, 26 Feb 2019 bugzilla-nore...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236065 I work doing tests, and I found one possible in a decentralized system that is used worldwide. I want to simulate a specific date in the 22nd century; however when I define the

Re: [Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1

On Fri, 8 Feb 2019, Bruce Evans wrote: On Thu, 7 Feb 2019 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 [syncing sc with i915kms, fixing lost video, and fixing corrupt i915kms] On a Haswell desktop: - first load of i915kms

Re: [Bug 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1

On Thu, 7 Feb 2019 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #30 from Pavel Minaev --- To use X, you'll need to kldload drm_next_kmod. If you do that with sc driver in effect, your screen will go blank the moment

Re: [Bug 230757] [syscons] random wrong color for kernel messages

On Mon, 10 Sep 2018, Koro wrote: In FreeBSD-11: - for boot messages, configure SC_KERNEL_CONS_ATTR to anything except its default of FG_WHITE (0xf). - after booting, use the hw.syscons.kattr sysctl to change the array of MAXCPU kernel attributes to whatever you want (all FG_WHITE to get

Re: [Bug 230757] [syscons] random wrong color for kernel messages

On Sun, 19 Aug 2018 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230757 --- Comment #2 from k...@kzxiv.net --- I confirm, it stops happening when I set the VM to only have one CPU, and inversely, I get more colors if I add more CPUs.

Re: [Bug 201685] top(1) with -m io produces garbage output for first update

On Sun, 24 Jun 2018 a bug that does't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201685 --- Comment #4 from cstde...@ctgameinfo.com --- I encountered this error because I was trying to log periodic snapshots of top output as part of tracking down some

Re: [Bug 228755] libvgl under syscons causes system reboot (via SDL 1.2)

On Wed, 6 Jun 2018, Bruce Evans wrote: On Tue, 5 Jun 2018, Mahmoud Al-Qudsi wrote: On Tue, Jun 5, 2018 at 7:32 AM, Bruce Evans wrote: ... 1920x1080x8. I use this fix: ... - if (offset > adp->va_window_size - PAGE_SIZE) + if (offset > trunc

Re: [Bug 228755] libvgl under syscons causes system reboot (via SDL 1.2)

On Tue, 5 Jun 2018, Mahmoud Al-Qudsi wrote: On Tue, Jun 5, 2018 at 7:32 AM, Bruce Evans wrote: This is the driver getting the check wrong for all frame buffer sizes that are not a multiple of PAGE_SIZE. The frame buffer size is not a multiple of PAGE SIZE mainly for the interesting

Re: [Bug 228755] libvgl under syscons causes system reboot (via SDL 1.2)

On Tue, 5 Jun 2018, Bruce Evans wrote: On Mon, 4 Jun 2018 a bug that doesn't want replies (especially to the reporter)@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228755 Bug ID: 228755 Summary: libvgl under syscons causes system reboot (via SDL

Re: [Bug 228755] libvgl under syscons causes system reboot (via SDL 1.2)

On Mon, 4 Jun 2018 a bug that doesn't want replies (especially to the reporter)@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228755 Bug ID: 228755 Summary: libvgl under syscons causes system reboot (via SDL 1.2) ... I was

RE: [Bug 227404] UP FreeBSD VM always hangs on reboot since 20180329-r331740

On Tue, 10 Apr 2018, Dexuan Cui wrote: From: Bruce Evans Sent: Tuesday, April 10, 2018 00:45 On Tue, 10 Apr 2018 a bug that doesn't want repl...@freebsd.org wrote: (The bug didn't even Cc freebsd-bugs for this followup.) Thanks for the reminder! I Cc'd bugs@ just now. --- Comment #4 from

Re: [Bug 227404] UP FreeBSD VM always hangs on reboot since 20180329-r331740

On Tue, 10 Apr 2018 a bug that doesn't want repl...@freebsd.org wrote: (The bug didn't even Cc freebsd-bugs for this followup.) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227404 --- Comment #4 from Dexuan Cui --- I think the first bad patch is this one:

Re: [Bug 227404] UP FreeBSD VM always hangs on reboot since 20180329-r331740

On Tue, 10 Apr 2018 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227404 ... --- Comment #1 from Dexuan Cui --- When the issue happens, the cpu utilization of the UP VM is 100%. While we're trying to find the first

Re: [Bug 226553] kbdcontrol doesn't map function keys

On Wed, 28 Mar 2018 a bug that doesn't want repl...@freebsd.org wrote: --- Comment #2 from Sergey --- (In reply to Arshan Khanifar from comment #1) Hello Arshan, There are patches suggested for several files in this thread:

Re: [Bug 225626] r325865 malloc vs bzero

On Sat, 3 Feb 2018, Conrad Meyer wrote: On Sat, Feb 3, 2018 at 3:52 AM, Bruce Evans <b...@optusnet.com.au> wrote: On Fri, 2 Feb 2018 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225626 --- Comment #1 from Brooks Davi

Re: [Bug 225626] r325865 malloc vs bzero

On Fri, 2 Feb 2018 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225626 --- Comment #1 from Brooks Davis --- I'd agree it's pointless, but there's seriously nothing wrong with the fix other than making a path that

Re: [Bug 225265] Lack of monotonic clock prolongs the default sudo 5 minutes password caching as long as suspend lasts

On Wed, 17 Jan 2018 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225265 Bug ID: 225265 Summary: Lack of monotonic clock prolongs the default sudo 5 minutes password caching as long as suspend lasts

Re: [Bug 203129] syslogd: /dev/console: Interrupted system call

On Wed, 20 Dec 2017 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203129 --- Comment #10 from h...@shrubbery.net --- I have noticed another regressive behavior from this: Local system status: 3:01AM up 36 days, 7 hrs, 3 users, load

Re: [Bug 224069] (Fix included) Use of uninitalized register value in vesa.ko, causing X, text console and suspend/resume to fail

On Mon, 4 Dec 2017 a bug that doesn't want reple...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224069 --- Comment #9 from Jung-uk Kim --- ... In the FreeBSD forums, there are constant complaints regarding Nvidia cards. ... So I have the strong

Re: [Bug 224069] (Fix included) Use of uninitalized register value in vesa.ko, causing X, text console and suspend/resume to fail

On Mon, 4 Dec 2017, Bruce Evans wrote: On Mon, 4 Dec 2017 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224069 ... I spent days looking for bugs near here. Unfortunately, removing the commenting out doesn't fix them, since it has

Re: [Bug 224069] (Fix included) Use of uninitalized register value in vesa.ko, causing X, text console and suspend/resume to fail

On Mon, 4 Dec 2017 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224069 Mark Linimon changed: What|Removed |Added

Re: [Bug 221501] [msdosfs] panic 11.0-RELEASE by mounting a malformed msdosfs image

On Mon, 14 Aug 2017 a big that doesn't want repl...@freebsd.org wrote: It is possible to panic 11.0-RELEASE by mounting a malformed msdosfs image. Did you check it with fsck before mounting? Otherwise the problem is probably uninteresting. No file system in FreeBSD except possibly zfs does

Re: [Bug 221418] FreeBSD 10.4-PRERELEASE fails to build on systems using 32 bit time_t since r322315.

On Fri, 11 Aug 2017 a bug that doesn't want repl...@freebsd.org wrote: --- Comment #1 from Conrad Meyer --- Truncated INT64_MIN should be INT32_MIN on 2's complement, not 0. Seems like we just lack a (time_t) cast on the value. Truncated INT64_MIN should be and is, 0 in

Re: [Bug 220779] getgroups result is affected by setegid

On Sun, 16 Jul 2017 a bug that doesn't want repl...@freebsd.org wrote: ... Summary: getgroups result is affected by setegid ... Reporter: muh.muh...@gmail.com On FreeBSD, the groups applicable to a process are stored in an array with the egid in [0] and and zero or more (not

Re: Fix cp not to give chflags error on NFS

On Sat, 1 Apr 2017, Eitan Adler wrote: +freebsd-standards for folks that know more than I do On 1 April 2017 at 08:54, Lewis Donzis wrote: It's fairly annoying that cp has no way to suppress the chflags error when the destination file is on an NFS mount. A bigger problem

Re: [Bug 217512] boot2 is unable to load kernel directly

On Fri, 3 Mar 2017 "a bug that doesn't want replies"@freebsd.org wrote: --- Comment #2 from Mark Willson --- As I understand the theory of boot0/boot1/boot2/loader operations, boot2 should have all the registers, bios calls, and setup correct for direct execution of the

Re: [Bug 211965] [patch] fmodl not properly aliased on architectures where LDBL_PREC == 53 (arm, mips, powerpc)

On Tue, 30 Aug 2016 a bug that doesn't want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211965 Kyle Evans changed: What|Removed |Added

Re: [Bug 211884] IPKVM cannot reliably enter text under 11.0-RC2

On Mon, 15 Aug 2016 "a bug that doesn't want replies"@freebsd.org wrote: Updated from 11.0-ALPHA to 11.0-RC2 this afternoon on a test machine and ran into a really odd problem. The system in question has an encrypted root ZFS pool, which results in a prompt for the GELI password during the

Re: [Bug 211304] 11.0 -r303168 buildkernel via devel/amd64-gcc fails for: dev/cxgbe/common/t4_hw.c warning: overflow in implicit constant conversion; more

On Sat, 23 Jul 2016 a bug that doesn't want replies wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211304 --- Comment #3 from Mark Millard --- (In reply to Mark Millard from comment #0) The code in question for the overflow in an implicit constant conversion is

Re: [Bug 205398] [regression] [tty] tty_drain() kernel function lacks timeout support it had before

On Fri, 18 Dec 2015 a bug system that doesn't want replies wrote: Revision 181905 by e...@freebsd.org brought the new MPSAFE TTY layer and removed "drainwain" timeout support. Now applications working with serial port can hang forever on close() system call: It brought many other bugs. About

Re: [Bug 205398] [regression] [tty] tty_drain() kernel function lacks timeout support it had before

On Fri, 18 Dec 2015, Eugene Grosbein wrote: 18.12.2015 23:05, Bruce Evans ??: ... There is a hack for last-close that is supposed to give a hard-coded timeout of 1 second. Not sure why this doesn't work for you. My quick fix that restores the timeout uses slightly different logic

Re: [Bug 204671] clang floating point wrong around Inf (i386)

On Sun, 22 Nov 2015 a bug that doesn't want replies wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204671 --- Comment #3 from ne...@segfault.kiev.ua --- (In reply to Jilles Tjoelker from comment #2) Jilles, thanks for the excellent explanation. This exposes I have lost some

Re: [Bug 204671] clang floating point wrong around Inf (i386)

On Sat, 21 Nov 2015 a bug that supreesses replies in mail wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204671 Jilles Tjoelker changed: What|Removed |Added

Re: [Bug 2137] [vm] systat(1) total vm statistics are b

On Tue, 10 Nov 2015 a bug that doesn't want a reply wrote: --- Comment #4 from NGie Cooper --- This is still sadly valid on 11-CURRENT -- please note that the amount of memory shown is negative ~2GB :(... This affects many people because... having this much memory is

Re: [Bug 204376] Cavium ThunderX system heavily loaded while at db> prompt

On Sun, 8 Nov 2015 comment-igno...@freebsd.org wrote: --- Comment #1 from NGie Cooper --- It's not just arm64; amd64 does/did a horrible job at yielding when in the debugger (part of the reason why we have a script which goes and suspends test VMs at $work if/when they

Re: [Bug 204049] vmtotal() loading is high when memory utilization is high

On Tue, 27 Oct 2015 bugzilla-nore...@freebsd.org wrote: Bugzilla doesn't want replies, so I shouldn't reply. I didn't reply to it. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204049 Dmitry Sivachenko changed: What|Removed |Added

Re: [Bug 204049] vmtotal() loading is high when memory utilization is high

On Thu, 29 Oct 2015, Bruce Evans wrote: ... There ar many bugs in the implementation of clock_gettime() family. Some of the related ones are: - none of the above unportable clock ids is documented - CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID are bogusly named. The '_ID

Re: [Bug 173541] load average 0.60 at 100% idle

On Tue, 27 Oct 2015 bugzilla-nore...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173541 --- Comment #9 from Alexander Motin --- I don't know whether it is the only cause of such behavior, but I have one logical explanation. The problem goes from the

Re: [Bug 202933] unwanted behaviour change when writing to revoked terminals

On Sun, 6 Sep 2015 bugzilla-nore...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202933 When a terminal is revoked, writing to it sets errno to: - ENXIO until FreeBSD 10.1 kernel - EIO with FreeBSD 10.2 kernel The following program can be used to see this behaviour

Re: [Bug 200493] Killing pid 11 (idle) wedges the disk IO

On Fri, 29 May 2015 bugzilla-nore...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200493 --- Comment #5 from Konstantin Belousov k...@freebsd.org --- (In reply to Edward Tomasz Napierala from comment #4) Great, you nailed it down. Look at the tdsigwakeup(), which is

Re: [Bug 199587] libc strncmp() performance

On Tue, 21 Apr 2015 bugzilla-nore...@freebsd.org wrote: I've been tinkering with the code, out of curiosity, and I've reimplemented strncmp() to check the performance. Here are my results and the benchmark code: 42359800221 cycles -- FreeBSD strncmp() 42113090043 cycles --

Re: [Bug 199422] fmodl not fully defined on architectures where LDBL_PREC == 53 (arm, mips, powerpc)

On Mon, 13 Apr 2015 bugzilla-nore...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199422 I testing out a change to build lib/msun/tests on all architectures, and I lib/msun/tests/fmod_test failed to compile on MACHINE == {arm,mips,powerpc} with the following error:

Re: [Bug 198377] libc: Invalid size check in load_msgcat()

On Fri, 6 Mar 2015 bugzilla-nore...@freebsd.org wrote: According to coverity 1193663, the following check always yields a false result: 405if (st.st_size SIZE_T_MAX) { 406_close(fd); 407SAVEFAIL(name, lang, EFBIG); 408NLRETERR(EFBIG); 409} _

Re: [Bug 197336] find command cannot see more than 32765 subdirectories when using ZFS

On Wed, 4 Feb 2015 bugzilla-nore...@freebsd.org wrote: Created attachment 152566 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=152566action=edit python script to generate a bunch of subdirectories with files in them This may be considered a feature -- it detected a bad script that

Re: [Bug 191674] New: [tests] printf(%tu, (intmax_t)-1) returns UINT64_MAX on i386, not UINT32_MAX

On Sun, 6 Jul 2014 bugzilla-nore...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191674 ... One of the testcases in tools/regression/lib/libc/stdio/test-printbasic.t tests out %tu with -1 and it fails because the testcase is correctly expecting UINT32_MAX, not

Re: kern/189941: getgroups(2) implements first argument as unsigned int

On Mon, 19 May 2014, Peter Holm wrote: Description: Passing -1 as gidsetlen is not detected. Discovered by ATF. Caught on Ubuntu and OS/X. A typical error from abusing an unsigned variable as a counter. This doesn't even match the API. This bug was in 4.4BSD. The fix seems to be almost

Re: kern/188952: read after revoke giving error not eof

On Thu, 24 Apr 2014, Justin Cormack wrote: Description: I have this ktrace of revoking a pty device: ... 43214 luajit-2.0.2 CALL revoke(0xfebc8) 43214 luajit-2.0.2 NAMI /dev/pts/1 43214 luajit-2.0.2 RET revoke 0 43214 luajit-2.0.2 CALL read(0x4,0xa4170,0x1000) 43214 luajit-2.0.2 RET

Re: kern/188952: read after revoke giving error not eof

The following reply was made to PR kern/188952; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Justin Cormack jus...@specialbusservice.com Cc: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: kern/188952: read after revoke giving error not eof Date

Re: kern/181155: [libc] [patch] *access*(2) does not handle invalid amodes properly

On Fri, 18 Apr 2014, Garrett Cooper wrote: And one more thing: fixing this will make FreeBSD more POSIX compliant with this system call ( http://pubs.opengroup.org/onlinepubs/009695299/functions/access.html ), will match the behavior on Linux and NetBSD at least: The access() function may

Re: bin/188715: int64 not handled right as arg on badsect(8), possible other issues lurking

On Thu, 17 Apr 2014, Dirk-Willem van Gulik wrote: Description: Was trying to map out some bad blocks prior to temporarily read/empty 4 Tbyte volume using ?badsect(8)? - and returing it. Was expecting to be able to put the sector # into badsect (e.g. 3432631424 from below FSCK output). This

Re: bin/188715: int64 not handled right as arg on badsect(8), possible other issues lurking

The following reply was made to PR bin/188715; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Dirk-Willem van Gulik di...@webweaving.org Cc: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: bin/188715: int64 not handled right as arg on badsect(8

Re: kern/188247: [PATCH] include/rpcsvc/yp_prot.h: remove typedef of bool.

On Fri, 4 Apr 2014, Yasuhiro KIMURA wrote: Description: There have been typedef of bool in rpcsvc/yp_prot.h since it is added to source tree in August 1994. But there is also definition of bool in stdbool.h, and they conflict when both headers are used. An

Re: kern/188247: [PATCH] include/rpcsvc/yp_prot.h: remove typedef of bool.

The following reply was made to PR kern/188247; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Yasuhiro KIMURA y...@utahime.org Cc: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: kern/188247: [PATCH] include/rpcsvc/yp_prot.h: remove typedef

Re: misc/186699: ddb on i386 and amd64 should be enhanced to show MSR values (enhancement)

On Wed, 12 Feb 2014, Justin Hibbits wrote: Description: On x86 it would be very useful to be able to show MSR values using rdmsr in the debugger. All inline functions in machine/cpufunc.h should be backed by extern functions, as for machine/atomic.h on x86 (this too is broken on other

Re: misc/186699: ddb on i386 and amd64 should be enhanced to show MSR values (enhancement)

The following reply was made to PR misc/186699; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Justin Hibbits jhibb...@freebsd.org Cc: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: misc/186699: ddb on i386 and amd64 should be enhanced to show MSR

Re: misc/184340: PATH_MAX not interoperable with Linux

On Wed, 27 Nov 2013, Brooks Davis wrote: On Wed, Nov 27, 2013 at 11:03:31PM +, David Cundiff wrote: Change PATH_MAX in kernel to 4096 from 1024. Should be harmless and will fix the issue in any program that uses PATH_MAX from the kernel headers. Also would allow longer 32-bit unicode

Re: kern/181439: [headers] sys/wait.h is not enough to use waitid(), but kind of should be.

On Wed, 21 Aug 2013, Jilles Tjoelker wrote: In PR kern/181439, you wrote: [sys/wait.h does not define siginfo_t] POSIX says that sys/wait.h shall define siginfo_t and may make visible all symbols from signal.h. This was even in the 2001 version (under an XSI extension) (waitid was there

Re: kern/181416: socket timeout rounding issue

On Tue, 20 Aug 2013, Vitja Makarov wrote: Description: Recently I was playing with small socket timeouts. setsockopt(2) SO_RCVTIMEO and found a problem with it: if timeout is small enough read(2) may return before timeout is actually expired. I was unable to reproduce this on linux box. I

Re: kern/181416: socket timeout rounding issue

The following reply was made to PR kern/181416; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Vitja Makarov vitja.maka...@gmail.com Cc: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/181416: socket timeout rounding issue Date: Tue, 20 Aug

Re: kern/181127: [PATCH] set{domain, host}name doesn't permit NUL terminated strings that are MAXHOSTNAMELEN long

On Thu, 8 Aug 2013, Garrett Cooper wrote: Synopsis: [PATCH] set{domain,host}name doesn't permit NUL terminated strings that are MAXHOSTNAMELEN long ... Description: The noted link/patch fixes POSIX and generic requirement compliance for set{domain,host}name per the manpages by

Re: kern/181127: [PATCH] set{domain, host}name doesn't permit NUL terminated strings that are MAXHOSTNAMELEN long

The following reply was made to PR kern/181127; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Garrett Cooper yaneurab...@gmail.com Cc: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: kern/181127: [PATCH] set{domain, host}name doesn't permit NUL

Re: kern/181127: [PATCH] set{domain, host}name doesn't permit NUL terminated strings that are MAXHOSTNAMELEN long

On Thu, 8 Aug 2013, Garrett Cooper wrote: On Aug 8, 2013, at 4:35 AM, Bruce Evans wrote: On Thu, 8 Aug 2013, Garrett Cooper wrote: Synopsis: [PATCH] set{domain,host}name doesn't permit NUL terminated strings that are MAXHOSTNAMELEN long ... Description: The noted link/patch fixes

Re: kern/181127: [PATCH] set{domain, host}name doesn't permit NUL terminated strings that are MAXHOSTNAMELEN long

The following reply was made to PR kern/181127; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Garrett Cooper yaneurab...@gmail.com Cc: Bruce Evans b...@optusnet.com.au, freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: kern/181127: [PATCH] set

Re: kern/178997: Heavy disk I/O may hang system

The following reply was made to PR kern/178997; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Klaus Weber fbsd-bugs-201...@unix-admin.de Cc: freebsd-gnats-sub...@freebsd.org Subject: Re: kern/178997: Heavy disk I/O may hang system Date: Mon, 10 Jun 2013 11:00:29 +1000

Re: kern/178997: Heavy disk I/O may hang system

On Fri, 31 May 2013, Klaus Weber wrote: Sorry for the late reply, testing took longer than expected. This is very interesting. It will take me a long time to complete testing and replying too. Maybe more later. (I have combined your replies from separate mails into one, and reordered some

Re: kern/178997: Heavy disk I/O may hang system

The following reply was made to PR kern/178997; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Klaus Weber fbsd-bugs-201...@unix-admin.de Cc: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: kern/178997: Heavy disk I/O may hang system Date: Tue, 4

Re: kern/178997: Heavy disk I/O may hang system

On Mon, 27 May 2013, Klaus Weber wrote: On Mon, May 27, 2013 at 03:57:56PM +1000, Bruce Evans wrote: On Sun, 26 May 2013, Klaus Weber wrote: Description: During heavy disk I/O (two bonnie++ processes working on the same disk simultaneously) causes an extreme degradation in disk throughput

Re: kern/178997: Heavy disk I/O may hang system

The following reply was made to PR kern/178997; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Klaus Weber fbsd-bugs-201...@unix-admin.de Cc: Bruce Evans b...@optusnet.com.au, freebsd-gnats-sub...@freebsd.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/178997: Heavy

Re: kern/178997: Heavy disk I/O may hang system

The following reply was made to PR kern/178997; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Klaus Weber fbsd-bugs-201...@unix-admin.de Cc: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/178997: Heavy disk I/O may hang system Date: Mon, 27

Re: kern/178997: Heavy disk I/O may hang system

On Sun, 26 May 2013, Klaus Weber wrote: Environment: FreeBSD filepile 9.1-STABLE FreeBSD 9.1-STABLE #5 r250475: Sun May 12 19:14:21 CEST 2013 root@filepile:/usr/obj/usr/src/sys/FILEPILE amd64 (Kernel config has some drivers removed and debugging options added. Tested with GENERIC as

Re: bin/178664: truss(1) may kill process

On Sun, 19 May 2013, Jilles Tjoelker wrote: The following reply was made to PR bin/178664; it has been noted by GNATS. From: Jilles Tjoelker jil...@stack.nl To: bug-follo...@freebsd.org, kwia...@panic.pl Cc: Subject: Re: bin/178664: truss(1) may kill process Date: Sun, 19 May 2013 14:09:32

Re: misc/177624: Swapcontext can get compiled incorrectly

On Thu, 4 Apr 2013, Brian Demsky wrote: Description: Here is the code for swap context: int swapcontext(ucontext_t *oucp, const ucontext_t *ucp) { int ret; if ((oucp == NULL) || (ucp == NULL)) { errno = EINVAL; return (-1); } oucp-uc_flags =

Re: misc/177624: Swapcontext can get compiled incorrectly

The following reply was made to PR misc/177624; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Brian Demsky bdem...@uci.edu Cc: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@FreeBSD.org Subject: Re: misc/177624: Swapcontext can get compiled incorrectly Date: Fri, 5 Apr

Re: misc/177624: Swapcontext can get compiled incorrectly

The following reply was made to PR misc/177624; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Bruce Evans b...@optusnet.com.au Cc: Brian Demsky bdem...@uci.edu, freebsd-bugs@freebsd.org, freebsd-gnats-sub...@freebsd.org Subject: Re: misc/177624: Swapcontext can

Re: misc/177624: Swapcontext can get compiled incorrectly

On Thu, 4 Apr 2013, Brian Demsky wrote: On Apr 4, 2013, at 8:16 AM, Bruce Evans wrote: On Fri, 5 Apr 2013, Bruce Evans wrote: On Thu, 4 Apr 2013, Brian Demsky wrote: Description: Here is the code for swap context: int swapcontext(ucontext_t *oucp, const ucontext_t *ucp) { int ret

Re: misc/177624: Swapcontext can get compiled incorrectly

The following reply was made to PR misc/177624; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Brian Demsky bdem...@uci.edu Cc: Bruce Evans b...@optusnet.com.au, freebsd-bugs@FreeBSD.org, freebsd-gnats-sub...@freebsd.org Subject: Re: misc/177624: Swapcontext can

Re: bin/176746: Document a bug (unusual 2K block media) with src/sbin/fsck_msdosfs/

On Fri, 8 Mar 2013, Julian H. Stacey wrote: Description: Document a 2K block media bug to src/sbin/fsck_msdosfs/fsck_msdosfs.8 How-To-Repeat: Analysis here http://www.berklix.com/~jhs/txt/sigmatel/#bsd2k Fix: Apply patch (appended) ---

Re: bin/176746: Document a bug (unusual 2K block media) with src/sbin/fsck_msdosfs/

The following reply was made to PR bin/176746; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Julian H. Stacey j...@berklix.com Cc: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/176746: Document a bug (unusual 2K block media) with src/sbin

Re: misc/176628: [stdint.h] use safer way of definint __WORDSIZE

On Mon, 4 Mar 2013, Dmitry Marakasov wrote: Description: r228529 introduced __WORDSIZE macro: --- sys/sys/stdint.h +#if defined(UINTPTR_MAX) defined(UINT64_MAX) (UINTPTR_MAX == UINT64_MAX) +#define__WORDSIZE 64 +#else +#define__WORDSIZE 32 +#endif

Re: misc/176628: [stdint.h] use safer way of definint __WORDSIZE

The following reply was made to PR kern/176628; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Dmitry Marakasov amd...@freebsd.org Cc: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@FreeBSD.org Subject: Re: misc/176628: [stdint.h] use safer way of definint __WORDSIZE Date

Re: kern/175759: Correct data types for fields of struct qm_trace{} from sys/queue.h

On Tue, 5 Feb 2013, Gleb Smirnoff wrote: On Tue, Feb 05, 2013 at 03:23:44AM +1100, Bruce Evans wrote: B On Mon, 4 Feb 2013, Gleb Smirnoff wrote: B Bany additional comments for the attached patch. Is it ok from your B viewpoint? B B Index: queue.h B

Re: kern/175759: Correct data types for fields of struct qm_trace{} from sys/queue.h

On Mon, 4 Feb 2013, Gleb Smirnoff wrote: any additional comments for the attached patch. Is it ok from your viewpoint? Index: queue.h === --- queue.h (revision 245741) +++ queue.h (working copy) @@ -105,13 +105,14 @@

Re: kern/175674: sem_open() should use O_EXLOCK with open() instead of a separate flock() call

On Sun, 3 Feb 2013, Giorgos Keramidas wrote: For a reason unknown to me, open(2) does not restart but always returns [EINTR] when a signal is caught. This is not POSIX-compliant. Actually, it is restarting that would be POSIX-non-compliant. From an old POSIX draft: @ 27392 ERRORS @ 27393

Re: kern/175674: sem_open() should use O_EXLOCK with open() instead of a separate flock() call

On Sun, 3 Feb 2013, Eitan Adler wrote: On 3 February 2013 16:00, Giorgos Keramidas keram...@freebsd.org wrote: The following reply was made to PR kern/175674; it has been noted by GNATS. The best way to fix this is in kern_openat() in the kernel but this might cause compatibility issues.

Re: kern/174440: [patch][syscons] panic: mutex Giant not owned at kern/tty_ttydisc.c:1089

On Fri, 14 Dec 2012, Mark Johnston wrote: Description: Last night the kernel on my laptop panicked, apparently while printing a LOR warning. The cause was a failed mutex assert: (kgdb) bt #0 doadump (textdump=1) at /usr/home/mark/src/freebsd/sys/kern/kern_shutdown.c:263 #1

Re: kern/174440: [patch][syscons] panic: mutex Giant not owned at kern/tty_ttydisc.c:1089

The following reply was made to PR kern/174440; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Mark Johnston mark...@gmail.com Cc: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: kern/174440: [patch][syscons] panic: mutex Giant not owned at kern

Re: bin/173977: pw(8) does not do range-checking on UIDs/GUIs from user's input, passwd DB becomes inconsistent

On Fri, 30 Nov 2012, Eitan Adler wrote: On 28 November 2012 13:41, Nikos Vassiliadis nv...@gmx.com wrote: Index: usr.sbin/pw/pw_group.c === --- usr.sbin/pw/pw_group.c (revision 243652) +++ usr.sbin/pw/pw_group.c

Re: Possible non-conformance to POSIX

On Wed, 28 Nov 2012, Martin Sustrik wrote: On 28/11/12 06:21, Martin Sustrik wrote: On 27/11/12 23:39, Bruce Evans wrote: #include netinet/in.h INADDR_ANY; The above results in 'u_int32_t undefined' error, which it shouldn't according to POSIX. netinet/in.h is careful to only declare

Re: bin/173977: pw(8) does not do range-checking on UIDs/GUIs from user's input, passwd DB becomes inconsistent

On Wed, 28 Nov 2012, Nikos Vassiliadis wrote: Description: pw(8) command does not do any range checking on the uid and gid input, resulting in inconsistencies in the password database. ... Fix: Patch attached with submission follows: Index: usr.sbin/pw/pw_group.c

Re: Possible non-conformance to POSIX

On Tue, 27 Nov 2012, Martin Sustrik wrote: I've just noted the following: #include netinet/in.h INADDR_ANY; The above results in 'u_int32_t undefined' error, which it shouldn't according to POSIX. netinet/in.h is careful to only declare uint32_t, but then it is broken and uses u_int32_t

Re: bin/170206: complex arcsinh, log, etc.

On Sat, 28 Jul 2012, Stephen Montgomery-Smith wrote: On 07/28/2012 11:15 AM, Stephen Montgomery-Smith wrote: On 07/28/2012 10:46 AM, Stephen Montgomery-Smith wrote: OK. This clog really seems to work. x*x + y*y - 1 is computed with a ULP less than 0.8. The rest of the errors seem to be due

  1   2   >