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: 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
complete or tag me > in necessary place? So that I can give a try in my board once it's ready. I just committed r340016 which merges r338360 along with followup fixes to stable/11. > On Mon, Oct 29, 2018 at 11:08 PM John Baldwin <mailto:j...@freebsd.org>> wrote: > > On 10/25/18 1

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

2018-10-29 Thread John Baldwin
tr_machdep.h as a precursor to MFC'ing this change. > On Thu, Oct 25, 2018 at 1:17 AM John Baldwin <mailto:j...@freebsd.org>> wrote: > > On 10/24/18 3:40 AM, Rajesh Kumar wrote: > > Hi, > > > > I have a amd64 based board. When I tried to

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: 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: 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: 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

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: 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
} > root@test:/usr/src > > If you need any aditional information please tell me about. Can you perhaps turn off the stack trace on boot to not lose the panic messages (remove KDB_TRACE from kernel config) and maybe modify the panic message to include the IRQ number pas

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

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: 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: Kernel build error rev.328485

2018-01-29 Thread John Baldwin
bsd/freebsd32.h) -- 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: witness_lock_list_get: witness exhausted

2018-01-08 Thread John Baldwin
2048 threads * will hold LOCK_NCHILDREN locks. We handle failure ok, and we should * probably be safe for the most part, but it's still a SWAG. */ #define LOCK_NCHILDREN 5 #define LOCK_CHILDCOUNT 2048 Probably the '2048' (max number of concurrent threads) needs to scale

Re: Breakage with sys.kern.ptrace_test.{ptrace__parent_sees_exit_after_child_debugger, parent_sees_exit_after_unrelated_debugger} after r325719:325721

2017-11-16 Thread John Baldwin
ng forever. I could fix the tests to check for the status in the kinfo_proc. I've no idea if there are other programs aside from tests that depend on this behavior that are also broken though. I feel like I copied that approach from some other bit of code when writing these

Re: Okular or any pdf reader

2017-10-28 Thread John Baldwin
rnel structures are changing, which means NVIDIA needs to recompile > their binary blob aswell! The blob does not generally use FreeBSD-specific structures. Part of the driver is source and that interfaces with FreeBSD's APIs to implement shims for the

Re: VM images for 12.0-CURRENT showing checksum failed messages

2017-10-18 Thread John Baldwin
On Wednesday, October 18, 2017 04:40:22 PM Glen Barber wrote: > On Wed, Oct 18, 2017 at 09:28:40AM -0700, John Baldwin wrote: > > On Wednesday, October 18, 2017 03:01:55 PM Glen Barber wrote: > > > On Wed, Oct 18, 2017 at 07:49:00AM -0700, John Baldwin wrote: > > > >

Re: VM images for 12.0-CURRENT showing checksum failed messages

2017-10-18 Thread John Baldwin
On Wednesday, October 18, 2017 03:01:55 PM Glen Barber wrote: > On Wed, Oct 18, 2017 at 07:49:00AM -0700, John Baldwin wrote: > > On Tuesday, October 17, 2017 11:57:44 AM David Boyd wrote: > > > The FreeBSD-12.0-CURRENT-amd64-20171012-r324542.vmdk image displays > > > ma

Re: VM images for 12.0-CURRENT showing checksum failed messages

2017-10-18 Thread John Baldwin
ng the snapshot images wasn't updated to generate cg checksums when creating the initial filesystem. Glen, do you know which tool (makefs or something else?) is used to generate the UFS filesystem in VM images for snapshots? (In this case it appears to be a .vmdk image) -- John Baldwin ___

Re: LOR panic on mount -uw

2017-10-12 Thread John Baldwin
for a panic we really need the panic message in addition to the stack trace. -- 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: C++ in jemalloc

2017-10-05 Thread John Baldwin
gement might work. For > >>> building > >>> > with external toolchains, it might also work. Some of the less popular > >>> > architectures may be a problem. > >>> > > >>> > Does that help? It isn't completely cut and dried, but it should be > >>> helpful > >>> > for you making a decision. > >>> > > >>> > Warner > >>> > >>> Wait a sec... we've been compiling C++ code with gcc 4.2 since like > >>> 2006. What am I missing here that keeps this answer from being a > >>> simple "go for it"? > >>> > >>> Just stay away from C++11 features and gcc 4.2 should work fine. (DTC > >>> may require C++11, but that was likely the author's choice given that > >>> there was no requirement for it to work on pre-clang versions of > >>> freebsd). > >>> > >> > >> It's the ubiquity of C++11 is why I didn't just say "Go for it". > >> > >> Warner > >> > > > > > ___ > 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" -- 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: panic: softdep_deallocate_dependencies: dangling deps

2017-09-28 Thread John Baldwin
.0 [GDB v8.0 for FreeBSD] > Copyright (C) 2017 Free Software Foundation, Inc. > Type "apropos word" to search for commands related to "word"... > Reading symbols from /usr/lib/debug/boot/kernel/kernel.debug...done. > ABI doesn't support a vmcore target &

Re: lldb unusable for regular user

2017-09-19 Thread John Baldwin
07fffdddf7000 in ?? () > Backtrace stopped: Cannot access memory at address 0x7fffddff7000 Your backtrace shows it crashed during thread exit inside of libthr, not in lldb itself. Also, it seems you are using libgcc_s from external gcc rather than the base system libgcc_s which is built from

Re: Panic: @r323525: iflib

2017-09-14 Thread John Baldwin
On Thursday, September 14, 2017 03:19:29 PM Stephen Hurd wrote: > John Baldwin wrote: > > igb0: <Intel(R) PRO/1000 PCI-Express Network Driver> port 0xe020-0xe03f mem > > 0xfb22-0xfb23,0xfb244000-0xfb247fff irq 43 at device 0.0 on pci6 > > igb0: attach_pre c

Re: Panic: @r323525: iflib

2017-09-14 Thread John Baldwin
igb0: trying 4 rx queues 4 tx queues igb0: Using MSIX interrupts with 9 vectors igb0: allocated for 4 tx_queues igb0: allocated for 4 rx_queues

Re: r323412: Panic on boot (slab->us_keg == keg)

2017-09-11 Thread John Baldwin
b50 > > mi_startup() at mi_startup+0x9c/frame 0x82193b70 > > btext() at btext+0x2c > > Uptime: 1s > > I bisected revisions, and the last working is r322988. > This machine is E5-2660 v4@ based. If you just revert r322988 on a newer tree does it work ok? -- John

Re: !EARLY_AP_STARTUP and -CURRENT

2017-08-31 Thread John Baldwin
ntainer lock: sched lock 0 (0xffff81c39800) > db> show lock 0x81c39800 > class: spin mutex > name: sched lock 0 > flags: {SPIN, RECURSE} > state: {OWNED} > owner: 0xf80128cdb560 (tid 100028, pid 11, "idle: cpu25") > > Regards, > Kevin -- 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: swapfile query

2017-08-20 Thread John Baldwin
swap, it won't be pulled back in until some thread or process actually needs it. If nothing needs the memory it doesn't hurt to just leave it out on swap. It might also mean that the memory freed up by your temporary memory pressure from your guests will now be available the next time you have memo

Re: Install FreeBSD from source into VM image

2017-08-16 Thread John Baldwin
he bhyve capsicum work. I've cc'd Allan and Peter who might be able to help track that down. It might be useful if you can run bhyve under ktrace, e.g.: sudo ktrace -i -t p sh /usr/share/examples/bhyve/vmrun.sh -d .raw vm- And then post the output of 'sudo kdump' -- 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: order of executing MOD_LOAD and registering module sysctl-s

2017-08-03 Thread John Baldwin
On Thursday, August 03, 2017 09:57:15 AM Andriy Gapon wrote: > On 02/08/2017 18:49, John Baldwin wrote: > > sysctl nodes are created explicitly via linker_file_register_sysctls, not > > via > > SYSINITs, so you can't order them with respect to other init functions. >

Re: order of executing MOD_LOAD and registering module sysctl-s

2017-08-02 Thread John Baldwin
On Wednesday, August 02, 2017 06:53:54 PM Hans Petter Selasky wrote: > On 08/02/17 17:49, John Baldwin wrote: > > On Wednesday, August 02, 2017 12:39:36 PM Hans Petter Selasky wrote: > >> On 08/02/17 12:13, Andriy Gapon wrote: > >>> > >>> As far as I

Re: zfs.ko no longer loads after r320156: unresolved symbol: abd_is_linear

2017-08-02 Thread John Baldwin
On Wednesday, August 02, 2017 10:14:01 AM Andriy Gapon wrote: > On 02/08/2017 04:00, Ngie Cooper (yaneurabeya) wrote: > > > >> On Aug 1, 2017, at 09:21, John Baldwin <j...@freebsd.org> wrote: > >> > >> On Tuesday, August 01, 2017 09:47:41 AM Andriy Ga

Re: order of executing MOD_LOAD and registering module sysctl-s

2017-08-02 Thread John Baldwin
via linker_file_register_sysctls, not via SYSINITs, so you can't order them with respect to other init functions. I think Andriy's suggestion of doing sysctls "inside" sysinits (so they are registered last and unregistered first) is probably better than the current state and is a simpler fix

Re: zfs.ko no longer loads after r320156: unresolved symbol: abd_is_linear

2017-08-01 Thread John Baldwin
the like. I forgot to send this to Andriy earlier, but here is the fix I'm using: https://github.com/freebsd/freebsd/commit/574dc95cf8272e16f6d44aff6cb4e08dede08886 -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/ma

Re: post ino64: lockd no runs?

2017-06-12 Thread John Baldwin
yscall is dying with EFAULT. The last argument is a pointer to an array of char * pointers, and the only way I can see it dying is if it fails to copyin() one of the strings pointed to by those pointers. You could try running rpc.lockd under gdb from ports and setting a breakpoint on 'nlm_syscall'

Re: [rfc] breaking out if_ath into ... lots of modules

2017-05-22 Thread John Baldwin
on't find your hardware. > > I realise this is a bit of a POLA change, but I'd like to get it into > -HEAD before FreeBSD-12 is cut. Why not have if_ath.ko just be a wrapper module that depends on everything like dtraceall.ko? That woul

Re: bootcode capable of booting both UFS and ZFS?

2017-05-08 Thread John Baldwin
dedicated blocks like boot2, > just that we can not use those blocks for more universal cases and eventually > those special cases will diminish. Yes, the BSD label stuff is stuck with a smaller size, but GPT should support unified bootstraps. -- John Baldwin _

Re: Add support for ACPI Module Device ACPI0004?

2017-05-01 Thread John Baldwin
On Sunday, April 30, 2017 09:02:30 AM Sepherosa Ziehau wrote: > On Sat, Apr 29, 2017 at 12:01 AM, John Baldwin <j...@freebsd.org> wrote: > > On Friday, April 28, 2017 05:38:32 PM Sepherosa Ziehau wrote: > >> On Thu, Apr 27, 2017 at 12:14 AM, John Baldwin

Re: Add support for ACPI Module Device ACPI0004?

2017-04-28 Thread John Baldwin
On Friday, April 28, 2017 05:38:32 PM Sepherosa Ziehau wrote: > On Thu, Apr 27, 2017 at 12:14 AM, John Baldwin <j...@freebsd.org> wrote: > > On Wednesday, April 26, 2017 09:18:48 AM Sepherosa Ziehau wrote: > >> On Wed, Apr 26, 2017 at 4:36 AM, John Baldwin

Re: Add support for ACPI Module Device ACPI0004?

2017-04-26 Thread John Baldwin
On Wednesday, April 26, 2017 09:18:48 AM Sepherosa Ziehau wrote: > On Wed, Apr 26, 2017 at 4:36 AM, John Baldwin <j...@freebsd.org> wrote: > > On Thursday, April 20, 2017 02:29:30 AM Dexuan Cui wrote: > >> > From: John Baldwin [mailto:j...@freebsd.org] > >> &g

Re: Add support for ACPI Module Device ACPI0004?

2017-04-25 Thread John Baldwin
On Thursday, April 20, 2017 02:29:30 AM Dexuan Cui wrote: > > From: John Baldwin [mailto:j...@freebsd.org] > > Sent: Thursday, April 20, 2017 02:34 > > > Can we add the support of "ACPI0004" with the below one-line change? > > > > > > acpi_sysr

Re: Add support for ACPI Module Device ACPI0004?

2017-04-19 Thread John Baldwin
the ACPI 6.1 spec it's not quite clear that ACPI0004 is like that? In particular, it seems that 004 should only allow direct children to suballocate? This change might work, but it will allow more devices to allocate the ranges in _CRS than otherwise. Do you have an acpidump from a guest system that con

Re: new problem?

2017-04-19 Thread John Baldwin
s.c:280 > vfs_bio.c:3500 > ufs_dirhash.c:281 > vfs_syscalls.c:3364 > > [some above also in dmesg, most in /var/log/messages... There are several known LORs in the VFS/UFS code that are either false positives or ones that have effectively been harmless. -- John Baldwin _

Re: bt full - included... kgdb 'script' output vmcore.8

2017-04-04 Thread John Baldwin
have_ia_ref = > ifp = > ia = > isbroadcast = > ---Type to continue, or q to quit--- > gw = The panic is in the LLE_FREE() here: /* * If there is a cached route, * check that it is

Re: info.0 dump good

2017-03-13 Thread John Baldwin
kdbg for a few > months anyway... Do you have a core.txt.0 file? If so it should contain a stack trace from kgdb which is the first thing that would be useful to obtain. -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freeb

Re: pkg output overflows line

2017-03-13 Thread John Baldwin
If I enlarge the terminal to 86 columns the output is correct again. > This happens in urxvt (my default), rxvt and in xterm. > > Some regression? I've noticed this same "feature" after the upgrade to 1.10. If possible please let it fit in 80 cols again. :) -- John Baldwin _

Re: SMBus driver

2017-03-13 Thread John Baldwin
is device is supported by the intpm(4) driver? -- 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: process killed: text file modification

2017-03-09 Thread John Baldwin
someone please take a look at it, with more > experience in the NFS code? -czg Can you print out the two mtimes? I wonder if what's happening is that your server uses different granularity (for example just seconds) than your client, so on the client we generate a timestamp with a non-zero nanoseconds bu

Re: confusing KTR_SCHED traces

2017-03-04 Thread John Baldwin
nd then > "running" states. > > I would like to fix that, but not sure how to do that best. > One idea is to move the mi_switch() trace closer to the cpu_switch() call > similarly to DTrace sched:cpu-off and sched:cpu-on probes. I think this is the right fix.

  1   2   3   4   5   6   7   8   9   10   >