Re: How to hotplug a PCI device (such as VF) on FreeBSD

2019-03-25 Thread John Baldwin
n' to force a rescan of a PCI bus as Ian noted. For native PCI-express hotplug you should not need to do manual rescans (though FreeBSD does not support PCI-e hotplug via Thunderbolt). -- John Baldwin ___ freebsd-current@freebsd.org mailing list https

Re: Optimization bug with floating-point?

2019-03-14 Thread John Baldwin
have max ULP of 2.9 (the > desired result); with the latter you have a max ULP of 23.xxx. > I have observed a 6 billion ULP issue when running my testsuite. > As pointed out by John Baldwin, GCC is aware of the FPU setting. > The problem with clang is that it seems to unconditiona

Re: Optimization bug with floating-point?

2019-03-14 Thread John Baldwin
t is gcc doing different than clang in this case. I assume neither GCC _nor_ clang are adjusting the FPU in compiler-generated code, and in fact as Steve's earlier tests shows, the precision is set to PD by default when a clang-built binary is run. -- John Baldwin

Re: Optimization bug with floating-point?

2019-03-13 Thread John Baldwin
On 3/13/19 9:40 AM, Steve Kargl wrote: > On Wed, Mar 13, 2019 at 09:32:57AM -0700, John Baldwin wrote: >> On 3/13/19 8:16 AM, Steve Kargl wrote: >>> On Tue, Mar 12, 2019 at 07:45:41PM -0700, Steve Kargl wrote: >>>> >>>> gcc8 --version >>>> gcc

Re: Optimization bug with floating-point?

2019-03-13 Thread John Baldwin
nt >> main(void) >> { >>double re, im, u, ur, ui; >>float complex f; >>float x, y; > > this line to "volatile float x, y". So it seems to be a regression in clang 7 vs clang 6? -- John Baldwin __

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

2019-03-01 Thread John Baldwin
, not > just core deciding what is or is not a tier 1 and/or how to fix our > tier 1 situation with i386 (which I do agree needs to change, but > to what I have not a solid idea.) As you are well aware, core@ has talked to some stakeholders already (including you) which has already resulted in

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

2019-02-28 Thread John Baldwin
removing per my other mail. While there is some cruft in a few files for older CPUs (mostly just initcpu.c and identcpu.c) it is quite small and in code that doesn't change. To effect any type of substantial "win" in reducing code complexity for i38

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

2019-02-28 Thread John Baldwin
; thinking of removing the workarounds like F00F. Are there any processors that > are still vulnerable to this? We have only removed support for 386 since it didn't support cmpxchg. We still nominally support 486s. I don't know how well FreeBS

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

2019-02-28 Thread John Baldwin
On 2/28/19 10:32 AM, Steve Kargl wrote: > On Thu, Feb 28, 2019 at 09:09:38AM -0800, John Baldwin wrote: >> You can do all your tests directly on amd64 by just adding >> "-m32" to compile i386 binaries against the libraries in /usr/lib32 >> and you will generate t

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

2019-02-28 Thread John Baldwin
for testing i386 things. I also run i386 VMs under bhyve on amd64 hosts. I'm not sure your laptop's CPU can run i386 VMs though, and you don't need a VM to test userland-only changes (I'm usually trying to test kernel changes). However, an amd64 kernel is going to

Re: Panic in sys_fstatat()

2019-02-14 Thread John Baldwin
On 2/14/19 12:38 PM, Steve Kargl wrote: > On Thu, Feb 14, 2019 at 12:26:01PM -0800, John Baldwin wrote: >> On 2/13/19 6:47 PM, Steve Kargl wrote: >>> #16 0x00ff58bb in trap (frame=0x2e7b6880) at >>> /usr/src/sys/i386/i386/trap.c:519 >>> #17 0xffc0315d in ?? ()

Re: Panic in sys_fstatat()

2019-02-14 Thread John Baldwin
24 syscall (frame=0x2e7b6ce8) at /usr/src/sys/i386/i386/trap.c:1144 > #25 0xffc033a7 in ?? () > #26 0x2e7b6ce8 in ?? () > Backtrace stopped: Cannot access memory at address 0xfbafbbbc > (kgdb) Frame 18 is probably the root problem, though it doesn't look like kgdb is able t

Re: kernel config question

2019-01-04 Thread John Baldwin
On 1/3/19 10:40 PM, Kevin Oberman wrote: > On Wed, Jan 2, 2019 at 5:02 PM Robert Huff wrote: > >> >> John Baldwin writes: >> >>> -[8] In order to have a kernel that can run the 4.x binaries needed >> to >>> -do an installwo

Re: kernel config question

2019-01-02 Thread John Baldwin
On 1/2/19 1:31 PM, Robert Huff wrote: > > John Baldwin writes: > >> >> [8] In order to have a kernel that can run the 4.x binaries >> >> needed to do an installworld, you must include the >> >> COMPAT_FREEBSD4 option in your kernel. [...] >

Re: kernel config question

2019-01-02 Thread John Baldwin
; No, COMPAT_FREEBSD4 is not needed. Maybe COMPAT_FREEBSD11 is needed. Yes, that text needs to be made more generic to say that you will need COMPAT_FREEBSD. Though we've also had so

Re: buildworld falure: truncated or malformed archive

2019-01-02 Thread John Baldwin
ng (and llvm) with stripped down debug symbols by default. If you don't put any DEBUG_* foo in src.conf you will get debug symbols for all of the world including the limited ones for clang. (We use -gline-tables-only or some such fo

Re: 12.0 - (zpool upgrade ) /bootpool/boot/* new location for /boot/* ?

2018-12-17 Thread John Baldwin
n all of the devices.) I have a fresh install of 12.0-RC3 here that still has the files in /boot and doesn't have a /bootpool directory at all. -- John Baldwin ___ freebsd-current

Re: Composite PCI devices in FreeBSD (mfd in Linux)

2018-12-10 Thread John Baldwin
On 12/10/18 12:19 PM, Ian Lepore wrote: > On Mon, 2018-12-10 at 14:42 -0500, Anthony Jenkins wrote: >> On 12/10/18 1:26 PM, John Baldwin wrote: >>> >>> On 12/10/18 9:00 AM, Anthony Jenkins wrote: >>>> >>>> Hi all, >>>> >>>>

Re: Composite PCI devices in FreeBSD (mfd in Linux)

2018-12-10 Thread John Baldwin
e BAR. If you want to enforce exclusivity (once a device allocates part of a BAR then other children shouldn't be permitted to do so), then you will need a more complicated solution. Hopefully that gives you a starting point? -- John Baldwin

Re: maxswzone NOT used correctly and defaults incorrect?

2018-11-24 Thread John-Mark Gurney
Konstantin Belousov wrote this message on Sat, Nov 24, 2018 at 12:40 +0200: > On Sat, Nov 24, 2018 at 01:04:29AM -0800, John-Mark Gurney wrote: > > I have an BeagleBoard Black. I'm running a recent snapshot: > > FreeBSD generic 13.0-CURRENT FreeBSD 13.0-CURRENT r340239 GENERIC a

maxswzone NOT used correctly and defaults incorrect?

2018-11-24 Thread John-Mark Gurney
for the zones did not increase at ALL: swpctrie:48, 62084, 0, 0, 0, 0, 0 swblk: 72, 62040, 0, 0, 0, 0, 0 Thoughts? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has

Re: axp288 on Intel HW

2018-11-16 Thread John Baldwin
ry devices work? Maybe your battery devices don't have a _STA method and you need the change in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191? -- John Baldwin ___ freeb

Re: Has anything changed from 11.2 to 12.0 in PCI MSI/MSIX path?

2018-11-01 Thread John Baldwin
On 10/30/18 1:22 AM, Rajesh Kumar wrote: > Hi John, > > Thanks for your updates.  I assume you are talking about having a unified > intr_machdep.h compared to having seperate amd64 and i386 versions. > > Can you please update this thread once all changes are MFC

Re: Has anything changed from 11.2 to 12.0 in PCI MSI/MSIX path?

2018-10-29 Thread John Baldwin
On 10/25/18 10:24 AM, Rajesh Kumar wrote: > Hi John, > > Thanks a lot. It helps. I backported the changes to 11.2 and tried booting in > my board with success without any need for the said tunables. > > I see those changes are marked for MFC after 2 Weeks. But I don't

Re: UFS panics

2018-10-27 Thread John-Mark Gurney
to ask the following: is it expected for > kernel panics to happen when there are errors in the file system? Have you unmounted the file system, and tried to do a fsck on it? That you're getting a bad file descriptor sounds like it might be a directory entry pointing to a bad inode. -- John-Mar

Re: savecore: BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276

2018-10-25 Thread John Baldwin
On 10/25/18 2:14 AM, Marcin Cieslak wrote: > On Wed, 24 Oct 2018, John Baldwin wrote: > >> On 10/23/18 10:58 AM, Marcin Cieslak wrote: >>> This GDB was configured as "amd64-marcel-freebsd"...BFD: >>> /boot/kernel/kernel: invalid relocation type 37 &

Re: Has anything changed from 11.2 to 12.0 in PCI MSI/MSIX path?

2018-10-24 Thread John Baldwin
h my observations about the issue on > 11.1/11.2 in the following thread > https://forums.freebsd.org/threads/freebsd-11-1-installation-fails-and-rebooting.65814/ > > Let me know if you need any details. I believe this was fixed by r338360. -- John Baldwin __

Re: savecore: BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276

2018-10-24 Thread John Baldwin
Is this something that matters at all? It is not something that is likely to be fixed. If you pkg install gdb from ports, is the kgdb it includes able to examine the crash dump? -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://l

Re: which way to update export_args structure?

2018-10-23 Thread John-Mark Gurney
zeof oexport_args... It zeros out the remaining of the buffer.. > > + memcpy(, bufp, len); -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." signature.asc Description: PGP signature

problems on lists.freebsd.org error 503 backend fetch failed

2018-10-01 Thread John
Hi, if there's a better place to report this then please advise It seems the web-mail-list software for FreeBSD has failed partially (mostly?) For example, these work, to display the subjects of messages https://lists.freebsd.org/pipermail/freebsd-ports/2018-September/thread.html

Re: Speed problems with both system openssl and security/openssl-devel

2018-09-22 Thread John-Mark Gurney
cm's in 3.01s > Doing aes-256-gcm for 3s on 1024 size blocks: 587396 aes-256-gcm's in 3.01s > Doing aes-256-gcm for 3s on 8192 size blocks: 75806 aes-256-gcm's in 3.03s > ... > aes-256-gcm 62590.75k 135047.68k 181245.26k 199977.06k 204866.89k -- John-Mark Gurney

Re: intr_machdep.c:176:2: error: use of undeclared identifier 'interrupt_sorted'

2018-09-17 Thread John Baldwin
On 9/17/18 11:32 AM, Michael Butler wrote: > On 9/10/18 1:20 PM, John Baldwin wrote: >> On 9/8/18 1:44 PM, Michael Butler wrote: >>> On 9/8/18 3:43 PM, Konstantin Belousov wrote: >>>> On Sat, Sep 08, 2018 at 02:07:41PM -0400, Michael Butler wrote: >>>>

Re: devd on head -r338675 on aarch64 (Pine64+ 2GB example) gets during booting: "sh: /usr/libexec/hyperv/hyperv_vfattach: not found"

2018-09-14 Thread John Baldwin
error booting FreeBSD/riscv in qemu. -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send

Re: Speed problems with both system openssl and security/openssl-devel

2018-09-13 Thread John Baldwin
it doesn't I'd check for a BIOS option disabling it). -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubsc

Re: Enabling the WITH_REPRODUCIBLE_BUILD knob for 12.0-REL

2018-09-10 Thread John Baldwin
2 users would have hassles getting kgdb to work? No, this means that if you turn this option on in HEAD and leave it always on (as I read your mail to say), then it would be a hassle for developers on head. On stable branches it would be nice to keep the info if people are building kernel

Re: intr_machdep.c:176:2: error: use of undeclared identifier 'interrupt_sorted'

2018-09-10 Thread John Baldwin
er/firewall with few actual applications running. >>> >>> As another data point, I manually reversed both SVN r338360 and r338415 >>> (a related change) and it is now stable running at SVN r338520, >> >&g

Re: Enabling the WITH_REPRODUCIBLE_BUILD knob for 12.0-REL

2018-09-10 Thread John Baldwin
tree the extra info is useful to have. For better or worse, kgdb also parses the path to try to find kernel.full (used by e.g. 'kgdb -n last'), so if you remove the path it won't be able to find the matching kernel using its current logic. crashinfo uses

Re: Failing to retrieve source tarballs for anything.

2018-09-01 Thread John Kennedy
On Sun, Sep 02, 2018 at 07:58:16AM +1200, Jonathan Chen wrote: > On 2 September 2018 at 05:25, Alex McKeever > wrote: > > After compiling PKG, when I go to ports to compile anything (my eMac can > > run FreeBSD but not modern Linux due to the version of the Radeon GPU) it > > fails to retrieve

Re: intr_machdep.c:176:2: error: use of undeclared identifier 'interrupt_sorted'

2018-08-29 Thread John Baldwin
interrupt_sorted), Probably just needs #ifdef SMP around the mallocarray(). I'll test locallyon a UP kernel config. -- John Baldwin ___ freebsd-current@freebsd.org mailing list h

Re: x11/nvidia-driver no longer works under -current (r338323)

2018-08-26 Thread John
Hi, On Sun, 26 Aug 2018, at 13:02, Tomoaki AOKI wrote: > Hi, John. > It's broken again by r338318. (Previously broken by r338107.) > > If your previous src rev is older, you could be bitten by these. > If so, update ports tree at latest rev and try the latest single patch > be

Re: x11/nvidia-driver no longer works under -current (r338323)

2018-08-26 Thread John
Hello, On Sun, 26 Aug 2018, at 12:12, Kubilay Kocak wrote: > On 26/08/2018 9:07 pm, John wrote: > > Hello lists, > > > > x11/nvidia-driver is broken again. > > > > Context: FreeBSD-12-ALPHA3 r338323 / ports 478102 / amd64. > > > > Tried to bui

x11/nvidia-driver no longer works under -current (r338323)

2018-08-26 Thread John
Hello lists, x11/nvidia-driver is broken again. Context: FreeBSD-12-ALPHA3 r338323 / ports 478102 / amd64. Tried to build with make distclean clean rmconfig && make MAKE_JOBS_UNSAFE=yes It fails here: =kernel -Wno-sign-compare -Wno-format-extra-args -UDEBUG -U_DEBUG -DNDEBUG -Werror=undef

Re: svn commit: r338204 - in head: etc etc/defaults sbin/devfs

2018-08-23 Thread John Baldwin
longer mimic the layout on the host, such as syslog.d being "flattened".) -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Newly upgraded -CURRENT box does not boot

2018-08-21 Thread John Baldwin
o that maybe Brett has a chance to upgrade > to 12.0, unless this sounds familiar to someone and the cause is > obvious. =) I would start with bisecting the changes to libi386/biosdisk.c. Also, comparing 'lsdev -v' output between old and new loaders might be a useful step before starting on the bisecting. -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: buildworld failure: Do not include ${SRCTOP}/sys when building bootstrap tools

2018-08-21 Thread John Baldwin
e/rescue >> [...] >> >> >> This problem occured during today's source updates since I was able to build >> the NanoBSD >> image I intend to build yesterday ~ r338060. >> >> What is going wrong? > > It seems the problem has been intr

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread John Baldwin
loader, >> or is this a change with the recent default switch? >> >> And to be clear, you expect the host's file to be used for this, not the VM >> filesystem? >> > > (CC'ing jhb@ and tychon@, who might have better insight) > > If

Re: kernel build failure

2018-08-19 Thread John Baldwin
think of no sound reason that you should be >>> forced to use modules. >> I thought that ZFS was required to be a module because of the licensing >> terms (they didn't want any CDDL code in the core kernel)? >> > > It can't be in _GENERIC_ for that reason. Ther

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

2018-08-17 Thread John Baldwin
On 8/17/18 9:54 AM, Michael Gmelin wrote: > > >> On 17. Aug 2018, at 08:17, John Baldwin wrote: >> >>> On 8/16/18 1:58 PM, Michael Gmelin wrote: >>> >>> >>>> On 15. Aug 2018, at 15:55, Konstantin Belousov >>> <mailto:kosti

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

2018-08-17 Thread John Baldwin
t - so the previous fix just worked due to a bug it seems. > > Is there an easy way to output the content of physmap at that point > (debug.late_console=0 doesn’t work) - like an existing buffer I could use, or > would this be more elaborate (I did something complicated last time b

buffer device_printf...

2018-08-16 Thread John-Mark Gurney
failed to set bus width Instruction Set Attributes 1 = <> Processor Features 0 = Comments? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." _

Re: programs like gdb core dump

2018-08-09 Thread John Baldwin
> Revision: Revision: 337343 The core dumps don't really do me any good unfortunately without a binary, but if you can open fortune.core under gdb for example, just getting the stack trace along with 'info reg' is probably sufficient. > Erich > > > On Wed, 8 Aug 2018 08:57:06 -

Re: Early kernel boot log?

2018-08-09 Thread John Baldwin
ically due to an exception occuring before > IDT is set up and trap machinery operational. Double-check that > there is no any early framebuffer access, as a drastic measure remove > all framebuffer drivers from your kernel config. > > I

Re: programs like gdb core dump

2018-08-08 Thread John Baldwin
On 8/7/18 7:00 PM, Erich Dollansky wrote: > Hi, > > On Tue, 7 Aug 2018 11:59:11 -0700 > John Baldwin wrote: > >> On 8/6/18 8:11 PM, Erich Dollansky wrote: >>> On Mon, 6 Aug 2018 15:57:53 -0700 >>> John Baldwin wrote: >>> >>>> On

Re: programs like gdb core dump

2018-08-07 Thread John Baldwin
On 8/6/18 8:11 PM, Erich Dollansky wrote: > Hi, > > On Mon, 6 Aug 2018 15:57:53 -0700 > John Baldwin wrote: > >> On 8/4/18 4:38 PM, Erich Dollansky wrote: >>> Hi, >>> >>> I compiled me yesterday this system: >>> >>> 12.0-CURREN

Re: install: auto_master: No such file or directory

2018-08-07 Thread John-Mark Gurney
t; Lars Schotte > > > Mudro??ova 13 > > > 92101 Pieany > > > ___ > > > freebsd-current@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscr

Re: programs like gdb core dump

2018-08-06 Thread John Baldwin
; > Bad system call (core dumped) > > Trying to install ports results in the same effect. > > Erich Did you upgrade from stable/11 with a world that is still stable/11? If so, did you make sure your kernel config includes COMPAT_FREEBSD11?

Re: head -r336568 and -r336570 appears to have made ci.freebsg.org's FreeBSD-head-amd64-gcc fail either than it had been (error: operand type 'struct *' is incompatible with argument 1 of

2018-08-03 Thread John Baldwin
I decided that it was better to fix our stdatomic.h, so I have a review to do that at https://reviews.freebsd.org/D16585 -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current

Re: head -r336568 and -r336570 appears to have made ci.freebsg.org's FreeBSD-head-amd64-gcc fail either than it had been (error: operand type 'struct *' is incompatible with argument 1 of

2018-07-27 Thread John Baldwin
ight be to fix sys/cdefs.h and sys/stdatomic.h to actually work with modern GCC by having them not use the struct for the _GCC_ATOMICS case, only for the _SYNC case. I think that would fix all of the cases. -- John Baldwin ___ freebsd-current@free

Re: head -r335782 (?) broke ci.freebsd.org's FreeBSD-head-amd64-gcc build (lib32 part of build)

2018-07-26 Thread John Baldwin
der for the > directories for now. I finally got the approval 2 days ago to remove float.h from amd64-gcc so you shouldn't need this reverted anymore once the OFED thing is straightened out. -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: head -r336568 and -r336570 appears to have made ci.freebsg.org's FreeBSD-head-amd64-gcc fail either than it had been (error: operand type 'struct *' is incompatible with argument 1 of

2018-07-26 Thread John Baldwin
On 7/26/18 10:55 AM, Mark Millard wrote: > > > On 2018-Jul-26, at 10:21 AM, John Baldwin wrote: > >> On 7/25/18 6:52 PM, Mark Millard wrote: >>> >>> >>> On 2018-Jul-25, at 2:10 PM, Mark Millard wrote: >>> >>> >>> >>

Re: head -r336568 and -r336570 appears to have made ci.freebsg.org's FreeBSD-head-amd64-gcc fail either than it had been (error: operand type 'struct *' is incompatible with argument 1 of

2018-07-26 Thread John Baldwin
On 7/25/18 6:52 PM, Mark Millard wrote: > > > On 2018-Jul-25, at 2:10 PM, Mark Millard wrote: > > > >> On 2018-Jul-25, at 10:09 AM, Mark Millard wrote: >> >>> On 2018-Jul-25, at 8:39 AM, John Baldwin wrote: >>> >>>> On 7/24/18 11:

Re: head -r336568 and -r336570 appears to have made ci.freebsg.org's FreeBSD-head-amd64-gcc fail either than it had been (error: operand type 'struct *' is incompatible with argument 1 of

2018-07-25 Thread John Baldwin
On 7/25/18 10:09 AM, Mark Millard wrote: > > > On 2018-Jul-25, at 8:39 AM, John Baldwin wrote: > >> On 7/24/18 11:39 PM, Mark Millard wrote: >>> On 2018-Jul-24, at 10:32 PM, Mark Millard wrote: >>> >>>> https://ci.freebsd.org/job/FreeBSD-hea

Re: head -r336568 and -r336570 appears to have made ci.freebsg.org's FreeBSD-head-amd64-gcc fail either than it had been (error: operand type 'struct *' is incompatible with argument 1 of

2018-07-25 Thread John Baldwin
mpiler-provided headers since they are a part of the language (and the system stdatomic.h simply attempts to mimic the compiler-provided header in case it is missing). Simple standalone tests of _Atomic(int) with GCC don't trigger those failures when using its stdatomic.h, so there is probably somethin

Re: atomic changes break drm-next-kmod?

2018-07-05 Thread John Baldwin
On 7/5/18 12:36 PM, Konstantin Belousov wrote: > On Thu, Jul 05, 2018 at 09:12:24PM +0200, Hans Petter Selasky wrote: >> On 07/05/18 20:59, Hans Petter Selasky wrote: >>> On 07/05/18 19:48, Pete Wright wrote: >>>> >>>> >>>> On 07/05/2018 10

Re: atomic changes break drm-next-kmod?

2018-07-05 Thread John Baldwin
On 7/3/18 5:10 PM, Pete Wright wrote: > > > On 07/03/2018 15:56, John Baldwin wrote: >> On 7/3/18 3:34 PM, Pete Wright wrote: >>> >>> On 07/03/2018 15:29, John Baldwin wrote: >>>> That seems like kgdb is looking at the wrong CPU. Can you use >>

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread John Baldwin
. You could also try using just 'r' to always force the use of a register. It would be less optimal than "er" but should function correctly. > On Tue, Jul 3, 2018 at 15:38 Pete Wright <mailto:p...@nomadlogic.org>> wrote: > > > > On 07/03/2018 15:29, Joh

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread John Baldwin
On 7/3/18 3:34 PM, Pete Wright wrote: > > > On 07/03/2018 15:29, John Baldwin wrote: >> That seems like kgdb is looking at the wrong CPU. Can you use >> 'info threads' and look for threads not stopped in 'sched_switch' >> and get their backtraces? You could also just

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread John Baldwin
On 7/3/18 3:20 PM, Pete Wright wrote: > > > On 07/03/2018 15:12, Pete Wright wrote: >> >> >> On 07/03/2018 14:17, Pete Wright wrote: >>> >>> >>> On 07/03/2018 12:02, John Baldwin wrote: >>>> On 7/3/18 11:28 AM, Niclas Zeising wr

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread John Baldwin
quot;, "ir", v); -ATOMIC_ASM(set, long, "orq %1,%0", "ir", v); -ATOMIC_ASM(clear,long, "andq %1,%0", "ir", ~v); -ATOMIC_ASM(add, long, "addq %1,%0", "ir", v); -ATOMIC_ASM(subtract, long, "subq %1,%0", "ir", v); +ATOMIC_ASM(set, long, "orq %1,%0", "er", v); +ATOMIC_ASM(clear,long, "andq %1,%0", "er", ~v); +ATOMIC_ASM(add, long, "addq %1,%0", "er", v); +ATOMIC_ASM(subtract, long, "subq %1,%0", "er", v); #defineATOMIC_LOADSTORE(TYPE) \ ATOMIC_LOAD(TYPE); \ -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: head -r335782 (?) broke ci.freebsd.org's FreeBSD-head-amd64-gcc build (lib32 part of build)

2018-06-30 Thread John Baldwin
On 6/30/18 10:19 AM, Mark Millard wrote: > > > On 2018-Jun-30, at 10:04 AM, Mark Millard wrote: > >> On 2018-Jun-30, at 9:29 AM, John Baldwin wrote: >> >>> On 6/30/18 9:17 AM, Mark Millard wrote: >>>> On 2018-Jun-30, at 7:51 AM, John Baldwin wrote

Re: head -r335782 (?) broke ci.freebsd.org's FreeBSD-head-amd64-gcc build (lib32 part of build)

2018-06-30 Thread John Baldwin
On 6/30/18 9:17 AM, Mark Millard wrote: > On 2018-Jun-30, at 7:51 AM, John Baldwin wrote: > >> On 6/29/18 2:37 PM, Mark Millard wrote: >>> [I expect this is more than just amd64-gcc related but that is all >>> that ci.freebsd.org normally builds via a devel/*-g

Re: head -r335782 (?) broke ci.freebsd.org's FreeBSD-head-amd64-gcc build (lib32 part of build)

2018-06-30 Thread John Baldwin
eement on LDBL_MANT_DIG. -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: head -r335782 (?) broke ci.freebsd.org's FreeBSD-head-amd64-gcc build (lib32 part of build)

2018-06-29 Thread John Baldwin
when at all possible. It's not clear to me if amd64 should be using the compiler provided values of things like LDBL_MIN/MAX either btw. -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: head -r335782 (?) broke ci.freebsd.org's FreeBSD-head-amd64-gcc build (lib32 part of build)

2018-06-29 Thread John Baldwin
amd64-binutils: 2.30_3,1 > > and amd64-gcc being 6.4.0 (via powerpc64-gcc) is from -r466834 > (via looking up in https://svnweb.freebsd.org/ports/head/devel/ ). > > This indicates that -r465416 and -r466701 did not cause: > > --sysroot=/workspace/obj/workspace/src/amd64.amd64

Re: TSC calibration in virtual machines

2018-06-27 Thread John Baldwin
different > timecounter: > https://lists.freebsd.org/pipermail/freebsd-cloud/2017-January/80.html I suspect you are probably right that we should just "trust" TSC frequencies provided by a hypervisor. We could perhaps choose to whitelist hypervisors known to provide accurate valu

Re: Resume without drm driver results in black screen

2018-06-15 Thread John Baldwin
of driver for the GPU that knows how to turn the display back on. That isn't a portable thing, it's GPU-specific. You could perhaps write smaller drivers that only support resume and not graphics acceleration, but that doesn't seem trivial. -- John Baldwin __

Re: kgdb crashing on a vmcore with dumptid = 0

2018-06-15 Thread John Baldwin
> old_chain = 0x804431820 > ti = 0x7fffd550 > kt = 0x0 > nkvm = 0x804363800 > temp = 0x8047f33b0 "/home/eax/crashes/aes_gpault_crash/vmcore.2" > kernel = 0x8043dec80 "/home/eax/crashes/aes_gpault_crash/kernel/kernel" > filename = 0x8047f33b0 "/home

Re: Current panic on boot on H11DSI motherboard with epyc cpu (nexus_add_irq: failed)

2018-04-18 Thread John Baldwin
ns on I/O APICs, so IRQ 256 is already reserved for use by one of those interrupt pins. The real fix is that I need to make FIRST_MSI_INT dynamic instead of a constant and just define it as the first free IRQ after the I/O APICs have probed. -- John Baldwin ___

Re: Current panic on boot on H11DSI motherboard with epyc cpu (nexus_add_irq: failed)

2018-04-17 Thread John Baldwin
On Tuesday, April 17, 2018 10:15:53 PM Vitalij Satanivskij wrote: > Dear John > > I'm try patch with no success > > http://hell.ukr.net/panic/recorder_patch165.webm > > Also I'm enable verbose boot and record boot process (hpet was disabled so > crash in anot

panic: VM object not locked in vm_page_ps_test()

2018-04-17 Thread John Baldwin
My laptop running recent head panicked this morning, apparently from hitting a key to stop the screensaver (at which point xscreensaver prompts for a password to unlock). -- John Baldwin ___ freebsd-current@freebsd.org mailing list https

Re: panic: VM object not locked in vm_page_ps_test()

2018-04-17 Thread John Baldwin
On Tuesday, April 17, 2018 10:01:41 AM John Baldwin wrote: > My laptop running recent head panicked this morning, apparently from hitting > a key to stop the screensaver (at which point xscreensaver prompts for a > password to unlock). (Sorry, buggy mail client sent this early) panic

Re: Current panic on boot on H11DSI motherboard with epyc cpu (nexus_add_irq: failed)

2018-04-17 Thread John Baldwin
f this parameters not set as described system not boot ^( Please try the patch from here https://reviews.freebsd.org/P165 -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Duplicate free in of file caps data

2018-04-09 Thread John Baldwin
am using a patched bhyve that uses cap_ioctls_limit() on a listen socket (so the caps will be copied to the new socket during accept()). I'll see if I can't come up with a simpler program to reproduce this. -- John Baldwin ___ freebsd-current@freebsd.

Re: "Could not allocate I/O space" and "intsmb0 attach returned 6" in a under-Hyper-V context on Ryzen Threadripper: Is this expected?

2018-04-09 Thread John Baldwin
yper-V? That seems like an odd device to have for an AMD machine. I suspect that this has never worked and the module started auto-loading due to devmatch. -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailm

Re: Can't load linux64.ko module

2018-04-09 Thread John Baldwin
s probably to have linux_vdso32.c and linux_vdso64.c that #include linux_vdso.c after setting ELF_WORD_SIZE similar to how sys/kern/imgact_elf.c works. Then the COMPAT_LINUX and linux64.ko modules would include linux_vdso64.c and COMPAT_LINUX32 and linux32.ko modules (and linux.ko on i386) would inclu

Re: problem with [intr{swi4: clock (0)}]

2018-03-23 Thread John Baldwin
er 6700 kernel`usb_power_wdog 7341 kernel`pfslowtimo 19607 kernel`tcp_timer_delack 20273 dtrace.ko`dtrace_state_deadman 32262 kernel`sleepq_timeout You can use this to figure out which timer events are using CPU in the softclock thread/process. -- John Baldwin

best settings for usb2 and attached disks, and sdcards

2018-03-06 Thread John
svnlite stops bailing out. When newfs was written, I passed -t to it to enable trim, which seems to make a difference on this for deletes but not writes. Can anyone please suggest anything I can so to speed up disk i/o? And is async being applied or ignored? thanks, -- John tech-l

FreeBSD has a politics problem

2018-03-03 Thread John Darrah
FreeBSD recently introduced an updated Code of Conduct that developers and members must adhere to. There has been much backlash online about it and about introducing identity politics into a technical OS project in general. The Code of Conduct was adopted from the "Geek Feminism" wiki's version,

Re: pkg does not recognize correct kernel version

2018-03-02 Thread John Baldwin
On Thursday, March 01, 2018 02:02:58 PM Konstantin Belousov wrote: > On Wed, Feb 28, 2018 at 03:32:43PM -0800, John Baldwin wrote: > > On Wednesday, February 28, 2018 09:45:47 PM Konstantin Belousov wrote: > > > On Wed, Feb 28, 2018 at 10:57:53AM -0800, John Baldwin wrote:

Re: pkg does not recognize correct kernel version

2018-02-28 Thread John Baldwin
On Wednesday, February 28, 2018 09:45:47 PM Konstantin Belousov wrote: > On Wed, Feb 28, 2018 at 10:57:53AM -0800, John Baldwin wrote: > > On Tuesday, February 20, 2018 10:19:02 AM Conrad Meyer wrote: > > > On Mon, Feb 19, 2018 at 2:38 PM, Ronald Klop <ronald-li...@klop.ws&g

Re: pkg does not recognize correct kernel version

2018-02-28 Thread John Baldwin
tly (or even having it depend on to force relinking of everything when changes). This matters for more than just pkg as the kernel also looks at the embedded __FreeBSD_version in binaries to make decisions about compat shims to enable (grep for P_OSREL in sys/). -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: make installworld broke / how to recover

2018-02-22 Thread John
stopped in /storage/usr/src 1 error make[2]: stopped in /storage/usr/src *** [_bootstrap-tools] Error code 2 make[1]: stopped in /storage/usr/src 1 error make[1]: stopped in /storage/usr/src *** [buildworld] Error code 2 make: stopped in /storage/usr/src 1 error make: stopped i

make installworld broke / how to recover

2018-02-22 Thread John
: stopped in /storage/usr/src # thanks, -- John tech-li...@zyxst.net ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: LUA boot loader coming very soon

2018-02-12 Thread John Baldwin
On Monday, February 12, 2018 02:31:46 PM Warner Losh wrote: > On Mon, Feb 12, 2018 at 10:12 AM, John Baldwin <j...@freebsd.org> wrote: > > > On Monday, February 12, 2018 08:27:27 AM Warner Losh wrote: > > > Greetings, > > > > > > As you may know, the

Re: posix_fallocate on ZFS

2018-02-12 Thread John Baldwin
u are still requiring writes to allocate blocks, and the second seems a bit fraught with peril as well if the application is expecting the non-COW'd file to be in sync with other files in the system since presumably non-COW'd files couldn't be snapshotted, etc. -- John Baldwin

Re: LUA boot loader coming very soon

2018-02-12 Thread John Baldwin
0xa000 for the text/data/bss and stack (in some cases like PXE booting the top can be lower than 0xa). I'm not sure if we have any other platforms with similar memory constraints. -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

2018-02-07 Thread John Nielsen
> On Feb 7, 2018, at 6:07 AM, Maurizio Vairani <maurizio1...@gmail.com> wrote: > > 2018-02-06 23:02 GMT+01:00 John Nielsen <li...@jnielsen.net>: > > On Feb 6, 2018, at 11:50 AM, Ian Lepore <i...@freebsd.org> wrote: > > > > On Tue,

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

2018-02-06 Thread John Nielsen
> On Feb 6, 2018, at 11:50 AM, Ian Lepore <i...@freebsd.org> wrote: > > On Tue, 2018-02-06 at 11:33 -0700, John Nielsen wrote: >> >> Apparently sending a NULL socket pointer to ifioctl hasn't worked >> since this commit in 2011: >> https://svnweb.freebsd.

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

2018-02-06 Thread John Nielsen
> On Feb 6, 2018, at 10:54 AM, John Nielsen <li...@jnielsen.net> wrote: > >> >> On Feb 4, 2018, at 2:50 AM, Maurizio Vairani <maurizio1...@gmail.com> wrote: >> >> 2018-01-29 18:38 GMT+01:00 John Nielsen <li...@jnielsen.net>: >> [ resendin

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

2018-02-06 Thread John Nielsen
> On Feb 4, 2018, at 2:50 AM, Maurizio Vairani <maurizio1...@gmail.com> wrote: > > 2018-01-29 18:38 GMT+01:00 John Nielsen <li...@jnielsen.net>: > [ resending from correct email address ] > >> On Jan 29, 2018, at 6:05 AM, Maurizio Vairani <maurizio1...@g

  1   2   3   4   5   6   7   8   9   10   >