ipe call failed: Cannot allocate memory
I also have a bunch of these on the console:
negative pipecnt for uid = 0
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
ds me to suspect
that you don't actually need them and would be better off disabling them
than fiddling with PXE and Forth.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
void writes:
> The arm64 device is headless and i connect to it via serial.
> I noticed the beastie menu come up with the option Video for
> console. Cycled it to Serial, booted, all fine. [...]
man boot.config
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
ot increase fragmentation, but it uses
up memory from a much more limited pool than loading them later.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
"Poul-Henning Kamp" writes:
> Dag-Erling Smørgrav writes:
> > There is very little difference between options and devices in kernel
> > configuration files, but for what it's worth, filemon is a device, not
> > an option.
> Apart from the internals of
Miroslav Lachman <000.f...@quip.cz> writes:
> Dag-Erling Smørgrav writes:
> > This does cause the module to be loaded at boot time, but it's slower
> > than loading it later, and it increases memory fragmentation.
> Does this also apply today? I recently read from som
void writes:
> How would I go about remedying the issue that usage/examples
> are not present in manpages for either the device line in kernel
> config or filemon.ko ?
https://reviews.freebsd.org/D46184
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
etc/rc.conf
or /etc/rc.conf.d/kld. For instance,
% cat /etc/rc.conf.d/kld/filemon
kld_list="${kld_list} filemon"
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Marcin Cieslak writes:
> Dag-Erling Smørgrav writes:
> > Marcin Cieslak writes:
> > > I think this (useful) change should go into the future release
> > > notes as a new feature.
> > Which change?
> https://reviews.freebsd.org/D32306 Import _FORTIFY_SOURC
Marcin Cieslak writes:
> I think this (useful) change should go into the future release notes
> as a new feature.
Which change?
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
issue of _forward_ compatibility, which we've never promised.
Besides, an entry in UPDATING wouldn't have helped you since your source
tree predated the change that would have added it.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
> > }
> > You realize this diff does nothing at all, right?
> Yeap, i also said it worked in 14-current old code only ,and has more
> than 2 years already
No, I mean all this does is add a comment. It has no effect on the
code.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
t_quirk(&sc->sc_hw, HQ_HID_IGNORE))
> return (ENXIO);
> +// return (BUS_PROBE_GENERIC + 1);
> return (BUS_PROBE_DEFAULT + 1);
> }
You realize this diff does nothing at all, right?
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
gnificantly slower and should only be done for
modules which are required to boot or mount the root filesystem, such as
zfs.
> But IMHO it some regression.
I agree, and 6437872c1d66 should be reverted until devmatch is capable
of loading uhid.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Renato Botelho writes:
> I'm not sure about a good way to test it on a running system instead.
Update your source tree, build and install world, run `sudo bsdconfig`,
scroll down and select “Network Management”, then select “Wireless
Networks”.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
ls due to a failed sccache start [...]
Using `ktrace -tcnpstuy` instead of just `ktrace` should greatly reduce
the size of the trace file.
(remind me to modify ktrace and kdump so this can be written as `-t-i`
or `-tI` instead...)
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
bob prohaska writes:
> Apr 20 22:14:37 www su[30398]: in prompt_tty(): caught signal 2
This means someone ran `su` and pressed Ctrl-C instead of entering a
password when prompted.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
> Here is the best part: after doing the above, going back to mere
> "timeout 2 sleep 10" (without truss!) no longer works
Neither is this.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
ld
> always read options instead of option.
It's not a typo, both spellings work, cf. config(5).
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
ave nightly scripts which would trigger
atime updates even with relatime.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
fixed in 14 and 15:
https://cgit.freebsd.org/src/commit/?id=75411d157232ee3b4789b92c9205453e7d59a3d2
It was too late for 13.2, but I'll make sure it's merged before 13.3.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
No, this is definitely something we want to support.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
ms to give a retval of 1 inside
> certctl.
This only happens if a certificate is listed as both trusted and
untrusted, and I'm pretty sure the previous version would return 1 in
that case as well. Can you check?
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Warner Losh writes:
> Do we support any compression on top of that? Has support for
> poudriere been added for it?
Yes (zstd) and no.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
le (of which there are 30k in the
ports tree) is only 200-250 bytes long, but it occupies 512 bytes on an
FFS filesystem, 1 kB in a tarball, and 4 kB on a typical ZFS filesystem.
Note that if the target system is FreeBSD 14 or newer, you can simply
mount the tarball (`sudo mount -rt t
Mark Millard writes:
> I'm not aware of there being other documentation for what
> is appropriate for setting up such for kyua runs.
https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/build-test_image-head.sh#L69-L84
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
ng memcmp()
with a bogus length invokes UB.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
he buildenv before building libc. If that still
fails, just run buildworld; it will fail in libmagic as before but it
will have built libc before failing, and you can install libc and
restart the build.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
nd run
$ sudo make -C lib/libc install
then buildworld as usual.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
ms to be a recent issue (less than 5 days).
> Hundreds of configure scripts now fail to run on 15-current due to
> this sed failure: [...]
Try adding ARCHLEVEL=scalar to CONFIGURE_ENV on one of these. If that
helps, yell at fuz@ :)
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Rainer Hurling writes:
> If I try to build world from todays c1b26df2972d with 15.0-CURRENT
> (main-n265063-e0752f431b01), it aborts with an error.
Either update your source tree or apply aca3bd160257, then build and
install libc before attempting buildworld.
DES
--
Dag-Erling Smørgr
le) to fail.
This was fixed in aca3bd160257.
> I am trying to manually compile a working mkmagic and restart the
> build to get unstuck.
mkmagic is fine, just build and install libc.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Dag-Erling Smørgrav writes:
> c47116e909 with cd25b0f740 and 28d2e3b5de reverted deadlocks, see
> attached ddb.txt. I'm going to see if reverting only 28d2e3b5de but not
> cd25b0f740 changes anything.
c47116e909 with only 28d2e3b5de reverted also deadlocked, but in both
case
Dag-Erling Smørgrav writes:
> Plot twist: c47116e909 _without_ the patches also appears to be working
> fine. The last kernel I know for sure deadlocks is b36f469a15, so I'm
> going to test cd25b0f740 and 28d2e3b5de.
c47116e909 with cd25b0f740 and 28d2e3b5de reverted deadlocks
Dag-Erling Smørgrav writes:
> A kernel built from c47116e909 plus these two patches has so far built
> 2,285 packages without a hitch, whereas normally it would have
> deadlocked after well before reaching 500 packages. I'll do another run
> without the patches tomorrow just
se two patches has so far built
2,285 packages without a hitch, whereas normally it would have
deadlocked after well before reaching 500 packages. I'll do another run
without the patches tomorrow just to be sure.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
t.
Do you have a FreeBSD branch with your patch applied?
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
The attached script successfully deadlocks 9228ac3a69c4.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
#!/bin/sh
: ${n:=$(nproc)}
: ${pool:=zroot}
basefs="${pool}/zfsdl"
set -eu
zfs destroy -r "${basefs}" >/dev/null 2>&1 || true
zfs create -o com.sun:auto-snap
om victim
> and whatever the real culprit is deeper.
We already know the real culprit, see upthread.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Mateusz Guzik writes:
> Given that the custom reproducer failed I think the most prudent
> course of action is to reproduce again with poudriere, but this time
> arrange to have all stacktraces dumped.
Why? What more information do you need?
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Dag-Erling Smørgrav writes:
> I managed to geat a deadlock with 4e8d558c9d1c. Its predecessor
> 5ca7f02946 appears to be working. I'm going to try to come up with a
> more efficient way to reproduce the deadlock than running poudriere.
I wrote a script that creates multip
Dag-Erling Smørgrav writes:
> Trying to narrow this range down, I did not get a deadlock with
> 4e8d558c9d1c (10 June) but I did with b7198dcfc039 (16 June) [...]
> Perhaps I should try 4e8d558c9d1c again.
I managed to geat a deadlock with 4e8d558c9d1c. Its predecessor
5ca7f02946 appe
Dag-Erling Smørgrav writes:
> At some point between 42d088299c (4 May) and f0c9703301 (26 June), a
> deadlock was introduced in ZFS.
Trying to narrow this range down, I did not get a deadlock with
4e8d558c9d1c (10 June) but I did with b7198dcfc039 (16 June), albeit
after building ~1800 pa
Tomoaki AOKI writes:
> This can help new installation using release tarballs (official or
> locally built) or upgrading with overwriting using said tarballs, but
> how does freebsd-update?
freebsd-update uses the same release process.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Tomoaki AOKI writes:
> Yes. But if bsdinstall and freebsd-update automatically bootstrap
> etcupdate if not yet done, newbies and casual users wouldn't be bitten.
https://cgit.freebsd.org/src/commit/?id=e9120a256075543376496fbd75949eed1f13a887
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Alan Somers writes:
> Do you have ZFS block cloning enabled on your pool? There were a lot
> of bugs associated with that feature. I think that was merged on
> 3-April.
No, and this deadlock did not appear until May.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
am pull request merges:
#14987 Fix memory leak in zil_parse()
Obtained from: OpenZFS
OpenZFS commit: 8e8acabdcaeb831c777f71361722f4235b698a8d
We can't ship 14.0 with this deadlock.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Michael Grimm writes:
> I'm currently in the process to prepare for upcoming 14-STABLE. Thus,
> I upgraded one of my sytems from 13-STABLE to 14-CURRENT.
Did you run etcupdate?
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
uld I run 'make installkernel' a 2nd time?
'make reinstallkernel' is more appropriate in this case.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
assword” upstream (and presumably in the port), while
PermitEmptyPasswords defaults to “no” both in FreeBSD and upstream,
cf. crypto/openssh/servconf.c (search for “permit_root” and
“permit_empty”).
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
FreeBSD User writes:
> I tried to put the option
>
> WITHOUT_MODULE="an"
it's spelled WITHOUT_MODULES, cf. make.conf(5).
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
(security/opie). You will have to manually add back the
pam_opie and pam_opieaccess lines in the relevant PAM policies.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
money, and
> those devices all have different threat/failure/admin models
> than simple paper.
Neither HOTP nor TOTP require dedicated devices. HOTP codes are
sequential and can be pre-generated and printed if that's what you
prefer.
DES
--
Dag-Erling Smørgrav - d...@des.no
I will be removing OPIE from the main branch within the next few days.
It has long outlived its usefulness. Anyone still using it should look
into OATH HOTP / TOTP instead (cf. security/pam_google_authenticator).
https://reviews.freebsd.org/D36592
DES
--
Dag-Erling Smørgrav - d...@des.no
Baptiste Daroussin writes:
> Dag-Erling Smørgrav writes:
> > [...] does not have a default domain setting, so it cannot handle
> > email from cron, periodic etc. where the recipient is just a user
> > name (usually “root”) [...]
> This has been fixed since. (not by me)
domain setting, so it cannot handle email from cron,
periodic etc. where the recipient is just a user name (usually “root”),
and the devs were not willing to add that feature. I have email as far
back as 2015 on the subject.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Yuri Pankov writes:
> There's apparently a bug in VMware Workstation NAT implementation,
> [...] The patch itself is attached.
Could you please open a differential and add me as reviewer?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
free
ike Red Hat does. Advise the customer to use a workaround
> until the other vendor fixes their code.
With respect, that's not your decision. It's mine.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
h
not be a viable piece
of software. Wishing they weren't needed is a waste of time and energy.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubs
it
> in src.conf.
Then it's useless.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
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"
all that
devd's aware of. The only way to find out if it's supported is to call
the driver's identify method, which checks the cpuid and creates a
device instance for each reported sensor.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
free
Rebecca Cran writes:
> After installing 12.0-BETA1, on the first boot I noticed a warning
> about $local_unbound_tls not being set properly.
Ah, I should probably have added it to /etc/defaults/rc.conf. Can you
do that (just set it to “no”) and let me know if it helps?
DES
--
Dag-
; share ?
# pkg install -y misc/compat9x misc/compat10x misc/compat11x
DES
--
Dag-Erling Smørgrav - d...@des.no
___
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"
Jung-uk Kim writes:
> I forgot to patch one more file, i.e., Makefile.inc1. Please try the
> attached patch instead.
Thanks, I missed that too.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
ur installed system. It may delete
files which have been obsoleted by changes you haven't yet built and
installed, to the point where you may be unable to build and install
those changes. In this particular case, it will, at the very least,
tem expert is needed here.
(and libldns probably needs a version bump, but that won't affect this)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To
just i386. The quick fix is
to replace size_t with u_int64_t in sshbuf_get_passwd(), on line 513 of
sshbuf-getput-basic.c (with my previous patch applied). I have a full
patch in the pipeline.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd
Please try the attached patch. I expect it to fix i386. If it also
fixes arm32, all the better, although I don't quite see why it would.
DES
--
Dag-Erling Smørgrav - d...@des.no
Index: crypto/openssh/sshbuf-getput-ba
t's the cause, as
it shouldn't break arm32, where time_t *is* 64 bits wide, but it still
needs fixing. Are you getting the exact same error message as Michael?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing
blubee blubeeme writes:
> You seem to miss the point where the you avoid breaking the system for
> any users not on the bleeding edge.
You seem to miss the point where nobody is interested in anything you
have to say any more.
DES
--
Dag-Erling Smørgrav - d...@
t partition contains the code that loads the loader and
should not need updating.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
Johannes,
Niclas, Warner and others with a century of combined experience will be
thrilled to see you succeed where they, by your account, have failed.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.
opers, our friends, most of us want nothing to do with you. If
can't live with that, I'm sure you can figure out how to install Linux.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.fr
has 934 packages installed. It's been running for ten minutes and has
printed over 90,000 lines, with no end in sight.)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinf
ndencies:
# pkg query -e '%#r == 0' %n-%v
DES
--
Dag-Erling Smørgrav - d...@des.no
___
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"
the bug before it affected you. No hard feelings?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-
Slawa Olhovchenkov writes:
> Dag-Erling Smørgrav writes:
> > In the meantime, you can try something like this in .bashrc or
> > whatever:
> Imposible. For accessing .bashrc on kerberoized NFS need correct
> /tmp/krb5cc_.
/etc/profile, then.
DES
--
Dag-Erling S
en
if mv "${KRB5CCNAME}" "${krb5ccuid}" ; then
export KRB5CCNAME="${krb5ccuid}"
else
echo "Unable to rename krb5 credential cache" >&2
fi
fi
unset krb5ccuid
DES
--
Dag-Erling Smørgrav -
Kevin Oberman writes:
> Dag-Erling Smørgrav writes:
> > Julian Elischer writes:
> > > what is the internal window size in the new ssh?
> > 64 kB.
> Are you sure of this?
Sorry, I was thinking of 6.6 (in stable/10). The buffer code in 7.1
supports dynamically-sized b
Julian Elischer writes:
> what is the internal window size in the new ssh?
64 kB.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, s
intended to reduce the impact of upstream
changes on existing systems.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "fr
Konstantin Belousov writes:
> Dag-Erling Smørgrav writes:
> > Maxim Sobolev writes:
> > > Hi, while working on some unrelated feature I've noticed that at least
> > > those two system calls are not returning proper value (-1) on error.
> > > Instea
NVAL.
That's how syscalls work.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
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"
e developers in
> question are being paid to work on other things, there is no real
> timeline for the release.
Given this state of affairs, it might not be unreasonable to consider
switching back for 11. There should be enough time, provided our
Kerberos maintainers have some spare cycles.
H and apply the output of that workflow to the source
tree instead of working entirely within the source tree.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd
We switched from MIT to Heimdal at some point in the past for some
reason I don't remember. MIT and Heimdal are *not* interchangeable at
the source or binary level, so switching back is not trivial.
DES
--
Dag-Erling Smørgrav - d...@des.no
__
l
haven't upgraded OpenSSH, but to the best of my knowledge, it is far
less intrusive than HPN.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubsc
ed HPN
and lack the CPU power to perform encryption at line speed.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to &q
noticed this thread.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
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"
Julian Elischer writes:
> Bob Bishop writes:
> > Is removing HPN going to impact the performance of tunnelled X
> > connexions?
> yes if your rtt is greater than about 85 mSec
With an RTT of 85 ms, X is unusable with or without HPN.
DES
--
Dag-Erling Smør
HPN is so important to you, is there a reason
why you can't use the port?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
side code (IIRC, one place where it printed only the
hardcoded version instead of the variable string). I'll try again.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/li
as so old it didn't
> have AESNI and would soon be retired, using the NONE cipher sped up
> the transfer significantly.
In that scenario, you don't need ssh at all. Just set up rsyncd on the
backup server.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
Willem Jan Withagen writes:
> "Dag-Erling Smørgrav" writes:
> > Willem Jan Withagen writes:
> > > Are they still willing to accept changes to the old version that
> > > is currently in base?
> > No, why would they do that?
> Exactly my question...
ktop at work and
FreeBSD 10 desktop at home).
DES
--
Dag-Erling Smørgrav - d...@des.no
___
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"
to the old version that is
> currently in base?
No, why would they do that?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mai
resses instead of hostnames? Just turn off
UseDNS. It is off by default since 6.8.
If you mean adding IP addresses or hostnames to messages that don't
already have them, try suggesting it on the openssh-portable mailing
list (openssh-unix-...@mindrot.org).
DES
--
Dag-Erling
them to the openssh-portable port, which has
them as a default option. I would also like to remove the NONE cipher
patch, which is also available in the port (off by default, just like in
base).
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-cu
y have to include
some of the other recent commits to the vm_map.c, which seem (at a quick
glance) to be related.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-c
NGie Cooper writes:
> Dag-Erling Smørgrav writes:
> > David Wolfskill writes:
> > > pid 544 (ntpd), uid 0: exited on signal 11 (core dumped)
> > Did you find a solution? [...]
> https://svnweb.freebsd.org/changeset/base/287591 ?
Are you certain? The commit messag
1 - 100 of 430 matches
Mail list logo
