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

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

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: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

2018-01-29 Thread John Nielsen
[ resending from correct email address ] > On Jan 29, 2018, at 6:05 AM, Maurizio Vairani wrote: > > I am running > # uname > -a > > FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 04:48:52 > UTC 2018 >

Re: Error compiling isboot-kmod

2018-01-29 Thread John Nielsen
> On Jan 27, 2018, at 9:20 AM, Ian Lepore <i...@freebsd.org> wrote: > > On Fri, 2018-01-26 at 23:20 -0700, John Nielsen wrote: >>> >>> On Jan 26, 2018, at 9:42 PM, John Nielsen <li...@jnielsen.net> wrote: >>> >>>> >>>> [

Re: Error compiling isboot-kmod

2018-01-27 Thread John Nielsen
> On Jan 26, 2018, at 9:42 PM, John Nielsen <li...@jnielsen.net> wrote: > >> On Jan 26, 2018, at 10:35 AM, Ian Lepore <i...@freebsd.org> wrote: >> >> On Fri, 2018-01-26 at 10:00 -0700, John Nielsen wrote: >>>> >>>> On Jan 26, 2018

Re: Error compiling isboot-kmod

2018-01-26 Thread John Nielsen
> On Jan 26, 2018, at 10:35 AM, Ian Lepore <i...@freebsd.org> wrote: > > On Fri, 2018-01-26 at 10:00 -0700, John Nielsen wrote: >>> >>> On Jan 26, 2018, at 3:37 AM, Maurizio Vairani <maurizio1018@gmail.c >>> om> wrote: >>> &g

Re: Error compiling isboot-kmod

2018-01-26 Thread John Nielsen
> On Jan 26, 2018, at 3:37 AM, Maurizio Vairani wrote: > > 2018-01-24 17:19 GMT+01:00 Warner Losh : > > > On Wed, Jan 24, 2018 at 3:12 AM, Maurizio Vairani > wrote: > On this CURRENT snapshot > # uname -a > FreeBSD freebsd12

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: vlans + bridging is "interesting"

2017-11-24 Thread John-Mark Gurney
all the mac addresses, but this is just a > guess. I finally figured this out w/ tcpdump, as tcpdump was showing the packets going out em0.14 (in my case), but the reply was never making it back to em0.14. I was seeing it on em0 w/ "tcpdump -i em0 vlan 14", and then, when I ran &qu

vlans + bridging is "interesting"

2017-11-24 Thread John-Mark Gurney
, it should work w/ original configuration), I'll test and commit the patch. Otherwise, please submit another fix. Thanks. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have

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.

Re: TSC as timecounter makes system lag

2017-02-24 Thread John Baldwin
if (cpu_deepest_sleep >= 2 && cpu_vendor_id == CPU_VENDOR_INTEL && > >> + if (cpu_vendor_id == CPU_VENDOR_INTEL && > >> is enough to fix the issue ? If yes, we can remove the cpu_deepest_sleep > >> variable. This is John' observation, I think he

Re: TSC as timecounter makes system lag

2017-02-23 Thread John Baldwin
arly. > > > > Just moving order of init_TSC_tc() would not help, since tsc checks smp > > consistency, which requires started APs. Try this for now, but might > > be John has better idea how to handle the issue. You might need to add > > some extern declarations f

Re: r311568 makes freerdp very slow

2017-01-18 Thread John Baldwin
On Tuesday, January 17, 2017 01:46:31 PM Jakob Alvermark wrote: > On Fri, January 13, 2017 22:46, Jakob Alvermark wrote: > > On Fri, January 13, 2017 19:44, John Baldwin wrote: > > > >> On Friday, January 13, 2017 09:58:01 AM Jakob Alvermark wrote: > >> > >

Re: Strange issue after early AP startup

2017-01-18 Thread John Baldwin
On Wednesday, January 18, 2017 09:00:52 AM Hans Petter Selasky wrote: > On 01/18/17 02:18, John Baldwin wrote: > > You might still want to adjust 'nextevent' to schedule the next interrupt > > to be sooner than 'timerperiod' though. You could just set 'nextevent' to > > 'now'

Re: Strange issue after early AP startup

2017-01-17 Thread John Baldwin
On Tuesday, January 17, 2017 05:08:58 PM Cy Schubert wrote: > In message <1492450.xzfnz8z...@ralph.baldwin.cx>, John Baldwin writes: > > On Tuesday, January 17, 2017 12:53:19 PM Cy Schubert wrote: > > > In message <b9c53237-4b1a-a140-f692-bf5837060...@selasky.org>,

Re: Strange issue after early AP startup

2017-01-17 Thread John Baldwin
update of these fields? Can they be > written simultaneously by configtimer() and cpu_new_callout()? Both functions do ET_HW_LOCK() of DPCPU_PTR(timerstate). -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/ma

Re: Strange issue after early AP startup

2017-01-17 Thread John Baldwin
*/ > + state->nextcall = SBT_MAX; > + state->nextcallopt = now + 1; > hardclock_sync(cpu); > } > busy = 0; > > > Then there is no problem

Re: Strange issue after early AP startup

2017-01-17 Thread John Baldwin
irs have no problem however my laptop will reboot > repeatedly at: > > Jan 17 11:55:16 slippy kernel: cd0: Attempt to query device size failed: > NOT READY, Medium not present - tray closed So it panics and reboots after this? -- 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: Strange issue after early AP startup

2017-01-17 Thread John Baldwin
On Tuesday, January 17, 2017 08:31:28 PM Hans Petter Selasky wrote: > Hi, > > On 01/17/17 20:00, John Baldwin wrote: > >> > >> Does this matter for the first tick? How often is configtimer() called? > > > > As I said, it is called at runtime when profc

Re: Strange issue after early AP startup

2017-01-17 Thread John Baldwin
On Tuesday, January 17, 2017 07:04:15 PM Hans Petter Selasky wrote: > On 01/17/17 16:50, John Baldwin wrote: > > On Monday, January 16, 2017 10:10:16 PM Hans Petter Selasky wrote: > >> On 01/16/17 20:31, John Baldwin wrote: > >>> On Monday, January 16, 2017 04:51:4

Re: Strange issue after early AP startup

2017-01-17 Thread John Baldwin
On Monday, January 16, 2017 10:10:16 PM Hans Petter Selasky wrote: > On 01/16/17 20:31, John Baldwin wrote: > > On Monday, January 16, 2017 04:51:42 PM Hans Petter Selasky wrote: > >> Hi, > >> > >> When booting I observe an additional 30-second delay after this

Re: Strange issue after early AP startup

2017-01-16 Thread John Baldwin
48477898 483209 > > Trying to add delays and/or prints around the Timecounters printout > makes the issue go away. Any ideas for debugging? I have generally used KTR tracing to trace what is happening during boot to debug EARLY_AP_STARTUP issues. -- John Baldwin __

Re: r311568 makes freerdp very slow

2017-01-13 Thread John Baldwin
On Friday, January 13, 2017 09:58:01 AM Jakob Alvermark wrote: > On Thu, January 12, 2017 19:26, John Baldwin wrote: > > On Thursday, January 12, 2017 12:42:11 PM Shawn Webb wrote: > > > >> On Thu, Jan 12, 2017 at 06:05:08PM +0100, Jakob Alvermark wrote: > >> &g

Re: r311568 makes freerdp very slow

2017-01-12 Thread John Baldwin
gle packet). However, it should not affect an application just calling aio_write() on a socket once. -- 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: SVN r311568 breaks build

2017-01-07 Thread John Baldwin
On Friday, January 06, 2017 08:33:19 PM Michael Butler wrote: > With the introduction of MSG_MORETOCOME, the build of libsysdecode is > broken. > > Was the following patch the intended but missed fix? Yes, this is the correct fix. Thanks! --

Re: How many CPU cores does FreeBSD support?

2017-01-06 Thread John Baldwin
oblem? > > In sys/x86/acpica/madt.c file, function madt_add_cpu(), just remove > the block > if (apic_id > MAX_APIC_ID) { > printf("MADT: Ignoring local APIC ID %u (too high)\n", > apic_id); > return; >

Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending

2017-01-06 Thread John Baldwin
code to carry around, and seems a very small price to pay compared to the cost of breaking existing machines (and existing documentation, so now things have to document <= 11 and >= 12 differently, etc.). (FWIW, this approach is what cxgbe uses to have the same driver code manage cxgbe/cxl/c

Re: Revision 309657 to stack_machdep.c renders unbootable system

2016-12-16 Thread John Baldwin
odically when called during boot. So the hack in pause() is probably not as necessary now. In particular, I think we only need it for thread0, not for other threads. The patch below worked for me with SPEW's config: Index: kern_synch.c === --- kern_synch.c(revision 310128) +++ kern_synch.c(working copy) @@ -321,7 +321,8 @@ pause_sbt(const char *wmesg, sbintime_t sbt, sbint if (sbt == 0) sbt = tick_sbt; - if (cold || kdb_active || SCHEDULER_STOPPED()) { + if ((cold && curthread == ) || kdb_active || + SCHEDULER_STOPPED()) { /* * We delay one second at a time to avoid overflowing the * system specific DELAY() function(s): -- 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: best approximation of getcpu() ?

2016-12-16 Thread John Baldwin
The problem with using cli/sti in userland is that you might page fault and context switch during the fault handler (or get preempted in the fault handler which will run with interrupts enabled) and migrate. You could prevent this if you are able to mlock() all of the pages holding any code you will execute or data you will access to prevent faults, but you have to ensure you can do this for every potential page. -- 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: Enabling NUMA in BIOS stop booting FreeBSD

2016-12-16 Thread John Baldwin
karound this type of BIOS breakage. This is just the first time in over a decade that test has been relevant. -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any

Re: Please test EARLY_AP_STARTUP

2016-12-01 Thread John Baldwin
tered after the 30 seconds delay, though I press the > > break key when the delay started. > > I tried add VERBOSE_SYSINIT option in order to get a rough location of > this delay, but the system boots just fine w/ VERBOSE_SYSINIT option, > sigh. You could add KTR_PROC tracing

Re: boot fails on Table SSDT at 0x...

2016-11-29 Thread John Baldwin
On Tuesday, November 29, 2016 11:49:32 PM Julian H. Stacey wrote: > > Thanks for the Q. John, > > It hangs. > > I'm refining down which line of the custom config triggers the hang > > & will post when Ive found it. > > Sorry, after lots of kernel variants &

Re: Please test EARLY_AP_STARTUP

2016-11-28 Thread John Baldwin
On Monday, November 28, 2016 02:35:07 PM Sepherosa Ziehau wrote: > Hi John, > > fdc seems to cause panic on Hyper-V: > https://people.freebsd.org/~sephe/fdc_panic.png You shouldn't get this panic in latest HEAD (post-r309148). > I then commented out device fdc, and I fixed one p

Re: boot fails on Table SSDT at 0x...

2016-11-28 Thread John Baldwin
> > - device vr > > - device wb > > - device xl > > device wlan > > options IEEE80211_DEBUG > > options IEEE80211_AMPDU_AGE > > --- 109,116 > > *** > > *** 221,226 > > --- 135,143 > > device ral &g

Re: Please test EARLY_AP_STARTUP

2016-11-27 Thread John Baldwin
On Sunday, November 27, 2016 12:46:31 PM O. Hartmann wrote: > Am Fri, 25 Nov 2016 10:20:36 -0800 > John Baldwin <j...@freebsd.org> schrieb: > > > I plan to enable EARLY_AP_STARTUP on x86 in a week on HEAD. Some folks > > have been testing it for the last week o

Please test EARLY_AP_STARTUP

2016-11-25 Thread John Baldwin
this over the next few days before it is enabled by default. (To enable, add 'options EARLY_AP_STARTUP' to your kernel config.) Note that non-x86 platforms should eventually adopt this, but I don't think any of them are ready yet. -- John Baldwin

Re: stable/11 -r307797 on BPi-M3 (cortex-a7): truss gets segmentation fault for handling unknown system call

2016-10-28 Thread John Baldwin
eBSD ELF32" > > (gdb) print t->cs.number > $5 = 580828064 > > (gdb) print narg > $6 = 0 > > (that last is for context for the get_syscall arguments). > > FYI: 580828064 = 0x229EBBA0 I have a patchset I have tes

Re: pmcstat -T -P instructions -t $pid ==> NMI

2016-10-28 Thread John Baldwin
P:INT:3: reval=1 > 315427 01068994532643 MDP:INT:2: enabled=4194304 > 315426 01068994532390 MDP:INT:1: cpu=0 tf=0x81d769d0 um=1 > 315425 01068994508088 MDP:INT:3: reval=1 > 315424 01068994507167 MDP:INT:2: enabled=4194304 > 315423 0

Re: SM bus ioctls incorrect in FreeBSD 11

2016-10-14 Thread John Baldwin
was that breaking the ABI wasn't great, but that we could always fix it by adding compat handlers for the old ioctl values. If those are needed then they need to be restored. If the new API is useful then it needs to be fixed which I think is option

Re: Destroy GPT partition scheme absolutely, how?

2016-10-04 Thread John Baldwin
On Tuesday, October 04, 2016 06:23:26 AM Warren Block wrote: > On Mon, 26 Sep 2016, John Baldwin wrote: > > > On Tuesday, September 27, 2016 12:36:22 AM Ngie Cooper wrote: > >> > >>> On Sep 26, 2016, at 22:48, Ernie Luzar <luzar...@gmail.com> wrote: > >

Re: FreeBSD 11.0 i386 buildworld failure

2016-10-04 Thread John Baldwin
nto not installing the headers. Also, a build with an empty /usr/obj would be the next thing to try. -- 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: Destroy GPT partition scheme absolutely, how?

2016-09-29 Thread John Baldwin
e's arrived with some partition scheme on them from burn-in testing or the like and when trying to be reinstalled we could end up "exposing" the GPT when the MBR was destroyed or something like that. -- John Baldwin ___ freebsd-current

Re: Freeze during booting of ASUS F2A85-M motherboard with Coreboot

2016-09-27 Thread John Baldwin
On Tuesday, September 27, 2016 10:31:24 PM Piotr Kubaj wrote: > No, I get only messages about allocating window. > > On 09/26/16 22:48, John Baldwin wrote: > > On Wednesday, September 21, 2016 11:19:05 AM Piotr Kubaj wrote: > >> I'm trying to boot the ASUS F2A85-M board w

Re: Freeze during booting of ASUS F2A85-M motherboard with Coreboot

2016-09-26 Thread John Baldwin
1000-0x1fff Do you get this message in a verbose dmesg with the stock UEFI? -- 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: Destroy GPT partition scheme absolutely, how?

2016-09-26 Thread John Baldwin
expr $sectors - 2` > > count=2 > > done > > Why not just use "gpart destroy -F provider"? That doesn't always work. In particular, if a disk was partitioned with GPT and then you use normal MBR on it afterwards, the 'gpart destroy -F' of the MBR will leave most of th

Re: FreeBSD 11.0-RC1 boot prompt kernel load issue.

2016-09-26 Thread John Baldwin
rive at boot prompt, system > gets switched off. > > Could you please help? > > Regards/Ram > > -Original Message- > From: Murthy Bhat > Sent: Tuesday, August 30, 2016 8:03 PM > To: 'John Baldwin' <j...@freebsd.org> > Cc: freebsd-current@freebsd.org;

Re: 11.0-RC2 suspend/resume on thinkpad x201 kills poweroff

2016-09-12 Thread John Baldwin
e on console brings the screen back. It seems that vt(4) needs some sort of "repaint" call on resume. -- 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: kldload intpm

2016-09-07 Thread John Baldwin
ORDER_ANY); DRIVER_MODULE(miibus, xl, miibus_driver, miibus_devclass, NULL, NULL); DRIVER_MODULE() uses SI_ORDER_MIDDLE by default. This probably needs to be fixed in all of the smbus controller drivers. -- 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: 11.0-RELEASE status update

2016-09-06 Thread John Baldwin
ugh it was later removed from ObsoleteFiles so 'make delete-old' > would not remove it from users' systems in r282423. > > etcupdate removing it is the problem really being reported here. Mmm, etcupdate should not remove a modified file. However, etcupdate assumes that a file remove

Re: FreeBSD 11.0-RC1 boot prompt kernel load issue.

2016-08-29 Thread John Baldwin
I firmware on your machine (at least, reproducing the issue might be). > Regards/Murthy Bhat > > -Original Message- > From: John Baldwin [mailto:j...@freebsd.org] > Sent: Monday, August 29, 2016 10:52 PM > To: freebsd-current@freebsd.org > Cc: Murthy Bhat <m

Re: FreeBSD 11.0-RC1 boot prompt kernel load issue.

2016-08-29 Thread John Baldwin
crash messages? If it is not EFI, we probably crashed in the BIOS routines used to read data from the USB drive. It may be a BIOS bug (which isn't easily fixable), but we would need the register dump from the crash to figure anything out. -- John Baldwin

Re: Mosh regression between 10.x and 11-stable

2016-08-14 Thread john hood
On 8/13/16 4:30 AM, Peter Jeremy wrote: > Hi John, > > Sorry, I got side-tracked. > > On 2016-Aug-12 16:37:15 -0400, John Hood <cg...@glup.org> wrote: >> >Could I ask you to look at this a little further? On the one hand, it >> >sure looks

Re: Mosh regression between 10.x and 11-stable

2016-08-11 Thread John Hood
ECT...' at all, or if it's corrupted. You'll have to run mosh inside /usr/bin/script to capture that. regards, --jh On 08/11/16 03:53 PM, Peter Jeremy wrote: > On 2016-Aug-11 12:30:23 -0400, John Hood <cg...@glup.org> wrote: >> I still can't reproduce this on 3 different

Re: Mosh regression between 10.x and 11-stable

2016-08-11 Thread John Hood
>From 4c4d2193af37f4375d9f7d52c109bbcdb873d9fc Mon Sep 17 00:00:00 2001 From: John Hood <cg...@glup.org> Date: Thu, 11 Aug 2016 12:25:55 -0400 Subject: [PATCH] Ensure MOSH CONNECT message reaches sshd. --- src/frontend/mosh-server.cc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src

Re: Mosh regression between 10.x and 11-stable

2016-08-10 Thread john hood
On 8/10/16 4:18 AM, Peter Jeremy wrote: > I recently updated one of my VPS hosts from 10.3-RELEASE-p5 to 11.0-BETA4 > r303811 and mosh to that host from my Linux laptop stopped working. All > I get on the laptop is: > $ mosh remotehost > Connection to remotehost closed. > /usr/bin/mosh: Did not

Re: Mosh regression between 10.x and 11-stable

2016-08-10 Thread john hood
On 8/10/16 4:18 AM, Peter Jeremy wrote: > I recently updated one of my VPS hosts from 10.3-RELEASE-p5 to 11.0-BETA4 > r303811 and mosh to that host from my Linux laptop stopped working. All > I get on the laptop is: > $ mosh remotehost > Connection to remotehost closed. > /usr/bin/mosh: Did not

Re: kernel panic caused by virtualbox(?)

2016-08-08 Thread John Baldwin
re compiled with -mno-mmx -mno-sse > -msoft-float -mno-aes -mno-avx I suspect head packages are quite likely built against the a "wrong" KBI and are too fragile to use for kmods vs compiling from ports. :-/ I would try a built-from-ports kmod to see if the panics go away. -- John Baldwin ___

Re: EARLY_AP_STARTUP hangs during boot

2016-08-04 Thread John Baldwin
On Thursday, August 04, 2016 08:59:06 AM Gary Jennejohn wrote: > On Tue, 02 Aug 2016 10:41:23 -0700 > John Baldwin <j...@freebsd.org> wrote: > > > On Tuesday, August 02, 2016 09:03:10 AM Gary Jennejohn wrote: > > > On Mon, 01 Aug 2016 13:19:16 -0700 > > >

Re: EARLY_AP_STARTUP hangs during boot

2016-08-02 Thread John Baldwin
On Tuesday, August 02, 2016 09:03:10 AM Gary Jennejohn wrote: > On Mon, 01 Aug 2016 13:19:16 -0700 > John Baldwin <j...@freebsd.org> wrote: > > > On Monday, August 01, 2016 03:31:11 PM Gary Jennejohn wrote: > > > On Mon, 1 Aug 2016 09:34:34 +0200 > > > Gary

Re: EARLY_AP_STARTUP hangs during boot

2016-08-01 Thread John Baldwin
On Monday, August 01, 2016 03:31:11 PM Gary Jennejohn wrote: > On Mon, 1 Aug 2016 09:34:34 +0200 > Gary Jennejohn <gljennj...@gmail.com> wrote: > > > On Sun, 31 Jul 2016 14:22:35 -0700 > > John Baldwin <j...@freebsd.org> wrote: > > > > > On Sunday

Re: [PATCH] randomized delay in locking primitives, take 2

2016-08-01 Thread John Baldwin
On Monday, August 01, 2016 10:08:43 PM Mateusz Guzik wrote: > On Mon, Aug 01, 2016 at 11:37:50AM -0700, John Baldwin wrote: > > On Sunday, July 31, 2016 02:41:13 PM Mateusz Guzik wrote: > > > On Sun, Jul 31, 2016 at 01:49:28PM +0300, Konstantin Belousov wrote: > > >

Re: [PATCH] randomized delay in locking primitives, take 2

2016-08-01 Thread John Baldwin
about the overhead of the divide as you are only doing it when you are contesting (so you are already sort of hosed anyway). Long delays in checking the lock cookie can be bad (see my local APIC snafu which only polled once per microsecond). I don't really think a divide is

Re: EARLY_AP_STARTUP hangs during boot

2016-07-31 Thread John Baldwin
On Sunday, July 31, 2016 11:29:14 AM Gary Jennejohn wrote: > On Sat, 30 Jul 2016 12:03:59 -0700 > John Baldwin <j...@freebsd.org> wrote: > > > On Saturday, July 30, 2016 09:44:22 AM Gary Jennejohn wrote: > > > On Fri, 29 Jul 2016 13:17:42 -0700 > > >

<    1   2   3   4   5   6   7   8   9   10   >