awk: can't open file /sys/param.h
Probably innocent, but reporting just in case:
$ poudriere version
3.3.4
$ freebsd-version
12.2-RC1
# poudriere jail -c -j 122amd64-srv -v 12.2-RC1
[00:00:00] Creating 122amd64-srv fs at
/data0/poudriere/jails/122amd64-srv... done
[00:00:01] Using
I just updated my laptop from source, and somewhere along the way
the key-codes Xorg sees changed.
Indeed. This doesn't just affect -CURRENT: it happened to me on
-STABLE last week, so I'm copying that list too.
And a "Down" key now opens and closes a KDE "Application Launcher",
2019-12-10 16:35, Marc Branchaud wrote:
On 2019-12-10 9:18 a.m., Mark Martinec wrote:
Commenting on a thread from 2018-12 and from 2019-09-20, with my
solution
to the boot problem at the end, in case anyone is still interested.
Thank you very much for this. A couple of questions:
(1) Why
reboot, and re-insert the data disks after the boot is finished.
|[...]
|No gpart on the bck pool, raw drives.
2019-09-20 17:27, Mark Martinec wrote:
Subject: Re: Lockdown adaX numbers to allow booting ?
This sounds very much like my experience:
2018-11-29, Boot loader stuck a
On 15/11/2019 3:27 am, Mark Martinec wrote:
Running 12.1-RELEASE-p1 on AMD Ryzen 5 3600X cpu,
but I don't see any temperatures reported in sysctl,
even though amdtemp.ko and amdsmn.ko are loaded
and they don't produce any complaints on loading.
2019-11-15 03:01, Kubilay Kocak wrote:
Resolver
Running 12.1-RELEASE-p1 on AMD Ryzen 5 3600X cpu,
but I don't see any temperatures reported in sysctl,
even though amdtemp.ko and amdsmn.ko are loaded
and they don't produce any complaints on loading.
$ kldstat | fgrep amd
271 0x82f3 1458 amdtemp.ko
281
20.00.02.00 (and ZFS can't cope with that),
but is stable with 20.00.07.00.
Mark
2018-12-17 16:52, je Mark Martinec napisal
One of our servers that was upgraded from 11.2 to 12.0 (to RC2
initially, then to RC3
and lastly to a 12.0-RELEASE) is suffering severe instability of a
disk controller
One of our servers that was upgraded from 11.2 to 12.0 (to RC2
initially, then to RC3
and lastly to a 12.0-RELEASE) is suffering severe instability of a disk
controller,
resetting itself a couple of times a day, usually associated with high
disk usage
(like poudriere buils or zfs scrub or
2018-12-13 16:59, Warner Losh wrote:
Do you have any encrypted disks?
Indeed I do, both pools are encrypted.
(although I haven't seen such messages with 11.2, as far as I can tell)
Mark
On Thu, Dec 13, 2018, 6:19 AM Mark Martinec
wrote:
On one of my hosts (now running 12.0-RELEASE
On one of my hosts (now running 12.0-RELEASE) the zfsboot shows
this weird negative number, which sounds suspicious:
Verifying DMI pool Data .
Shortening read at 3907029152 from 16 to 15
Shortening read at 7435283708 from 16 to -479991569
BTX loader 1.0 BTX version is 1.02
to regain control.
Mark
On 29 Nov 2018, at 17:01, Mark Martinec
wrote:
After successfully upgraded three hosts from 11.2-p4 to 12.0-RC2
(amd64,
zfs, bios), I tried my luck with one of our production hosts, and
ended up
with a stuck loader after rebooting with a new kernel (after the
first
me problem?
Mark
On 29 Nov 2018, at 17:01, Mark Martinec
wrote:
After successfully upgraded three hosts from 11.2-p4 to 12.0-RC2
(amd64,
zfs, bios), I tried my luck with one of our production hosts, and
ended up
with a stuck loader after rebooting with a new kernel (after the first
stage
After successfully upgraded three hosts from 11.2-p4 to 12.0-RC2 (amd64,
zfs, bios), I tried my luck with one of our production hosts, and ended
up
with a stuck loader after rebooting with a new kernel (after the first
stage of upgrade).
These were the steps, and all went smoothly and normally
On 07/08/2018 15:58, Mark Martinec wrote:
Collected, here it is:
https://www.ijs.si/usr/mark/tmp/dtrace-cmd.out.bz2
2018-08-14 11:18, Andriy Gapon wrote:
I see one memory leak, not sure if it's the only one.
It looks like vdev_geom_read_config() leaks all parsed vdev nvlist-s
2018-08-13 21:48, Volodymyr Kostyrko wrote:
I've been in the same situation. ZFS, only pool, no ZFS errors.
I think the problem is rather between swapping and ZFS ARC. This host
has different load, sometimes it needs more active memory, somtimes
less... This means that active zone can expand
t/{@allocs[stack(), args[3]] = count()}
dtmalloc::solaris:free
/pid == $target/{@frees[stack(), args[3]] = count();}'
This will record all allocations and frees from a single instance of
"zpool list".
2018-08-07 14:58, Mark Martinec wrote:
Collected,
On Sat, Aug 04, 2018 at 08:38:04PM +0200, Mark Martinec wrote:
2018-08-04 19:01, Mark Johnston wrote:
> I think running "zpool list" is adding a lot of noise to the output.
> Could you retry without doing that?
No, like I said previously, the "zpool list"
grows steadily.
This leak was introduced sometime between 10.3 and 11.1R-p11,
and is still there with 11.2.
Mark
On Fri, Aug 03, 2018 at 09:11:42PM +0200, Mark Martinec wrote:
More attempts at tracking this down. The suggested dtrace command does
usually abort with:
Assertion failed: (buf-&
138
Thanks in advance for looking into it,
Mark
2018-08-01 09:12, myself wrote:
On Tue, Jul 31, 2018 at 11:54:29PM +0200, Mark Martinec wrote:
I have now upgraded this host from 11.1-RELEASE-p11 to 11.2-RELEASE
and the situation has not improved. Also turned off all services.
Z
On Tue, Jul 31, 2018 at 11:54:29PM +0200, Mark Martinec wrote:
I have now upgraded this host from 11.1-RELEASE-p11 to 11.2-RELEASE
and the situation has not improved. Also turned off all services.
ZFS is still leaking memory about 30 MB per hour, until the host
runs out of memory and swap space
I have now upgraded this host from 11.1-RELEASE-p11 to 11.2-RELEASE
and the situation has not improved. Also turned off all services.
ZFS is still leaking memory about 30 MB per hour, until the host
runs out of memory and swap space and crashes, unless I reboot it
first every four days.
Any
After upgrading an older AMD host from FreeBSD 10.3 to 11.1-RELEASE-p11
(amd64), ZFS is gradually eating up all memory, so that it crashes every
few days when the memory is completely exhausted (after swapping heavily
for a couple of hours).
This machine has only 4 GB of memory. After capping up
with which you're
able
to reproduce the hang during boot, and remove "options
EARLY_AP_STARTUP".
2017-07-20 15:45, Mark Martinec wrote:
Done. And it avoids the problem altogether! Thanks.
Tried a reboot several times and it succeeds every time.
Here is all that I had in a config file fo
Should patch releases to stable 11.1 (errata) include fixes for kernel
crashes?
Referring to:
Bug 59 - 11.1-R crashing in sendfile syscall, as used by a uwsgi
process
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=59
https://svnweb.freebsd.org/base?view=revision=323634
2017-09-12 15:46, Steven Hartland wrote:
Could you post the decoded crash info from /var/crash/...
Using crashinfo(8) I suppose?
I would also create a bug report:
https://bugs.freebsd.org/bugzilla/enter_bug.cgi?product=Base%20System
Done (with additional info):
Bug 59 - 11.1-R
A couple of days ago I have upgraded an Intel box from FreeBSD 10.3 to
11.1-RELEASE-p1, and reinstalled all the packages, built on the same OS
version.
This host is running nginx web server with an uwsgi as a backend.
The file system is ZFS (recent as of 10.3, zpool not yet upgraded
to new 11.1
Could somebody please check why the new 'include' 11.1 feature of
syslogd
does not work when given more than one file to include...
Any chance of fixing this as a patch release to 11.1 ?
The 11.1 release brought a very desirable feature to syslogd:
$ man syslog.conf :
A special include
But this is all for 11.0, on 11.1 it hangs and I cannot look it up:
Does it also hang if you choose 'Safe mode" in the loader dialog?
Mark
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
2017-07-24 18:25, Ken Merry wrote:
It is possible that the change I MFCed today (r321207 in head, r321415
in stable/11) is related, but Mark will have to boot his machine with
the fix to see if it makes any difference.
What happened in my case on one particular machine (not on most
machines in
Thanks! Tried it, and the message (or a backtrace) does not show
during a boot of a generic (patched) kernel, at least not in
the last 40-lines screen before the hang occurs.
(It also does not show during a "Safe mode" successful boot.)
Btw (may or may not be relevant): after the above
2017-07-24 04:15, Mark Johnston wrote:
Could you try re-enabling EARLY_AP_STARTUP, applying the patch at the
end of this email, and see if the message "sleeping before eventtimer
init" appears in the boot output? If it does, it'll be followed by a
backtrace that might be useful for tracking down
2017-07-20 02:03, Mark Johnston wrote:
One thing to try at this point would be to disable EARLY_AP_STARTUP in
the kernel config. That is, take a configuration with which you're able
to reproduce the hang during boot, and remove "options
EARLY_AP_STARTUP".
Done. And it avoids the problem
ark
2017-07-19 01:18, Mark Martinec wrote:
2017-07-18 01:24, Mark Johnston wrote:
Are you able to break into the debugger at this point? Try setting
debug.kdb.break_to_debugger=1 and debug.kdb.alt_break_to_debugger=1 at
the loader prompt, and hit the break key, or the key sequence
~ ctrl-b
t, and only then the ada
disks - and even within the group of disks on the same
controller their order has been shuffled - no idea what could
have caused it - and it may have avoided the problem by doing so.
Will play some more with this tomorrow...
Mark
On Tue, Jul 18, 2017 at 01:01:16AM +0200, M
Upgrading 11.0-RELEASE-p11 to 11.1-RC3 using the usual freebsd-update
upgrade
method I ended up with a system which gets stuck while trying to attach
the second set of disks. This happened already after the first phase of
the upgrade procedure (installing and re-booting with a new kernel).
The
2017-02-06 18:04, Eric van Gyzen wrote:
On 02/06/2017 10:19, Mark Martinec wrote:
Hope the fix finds its way into 11.1 (or better yet, as a patch level
in 10.0). Should I open a bug report?
It will quite likely get into 11.1. As for a 10.x patch, you would
have
to ask re@ (I think
After experiencing an unexplained restart on one host (11.0-RELEASE-p7),
which could be tied to a problem with a swap device (swap on a dedicated
gpt partition), I'm investigating options for adding some checksuming
to swap storage.
I understand that swap on ZFS is not a way to go, and that a
On 2017-02-02 12:55, Mark Martinec wrote:
11.0-RELEASE-p7, net.inet.udp.log_in_vain=1
The following syslog entries seem to indicate some buffer overruns
in the reporting code (not all log lines are broken, just some).
(the actual failed connection attempts were indeed there,
it's just
11.0-RELEASE-p7, net.inet.udp.log_in_vain=1
The following syslog entries seem to indicate some buffer overruns
in the reporting code (not all log lines are broken, just some).
(the actual failed connection attempts were indeed there,
it's just that the reported IP address is highly suspicious)
I have recently upgraded two hosts with identical nvidia boards (GeForce
GT 730,
fresh driver nvidia-driver-375.26 from ports), one has been following
11-STABLE
every now and then, the other was on 10.3. So they are now at
11.0-RELEASE-p7
or on a recent 11-STABLE respectively.
The problem now
Thanks to all who responded, makes perfect sense now.
Paul Mather wrote:
The only thing you need on the host is to have the linux kernel module
loaded.
(You don't need to have any Linux packages installed there.) The
default setting
in /usr/local/etc/poudriere.conf is to have NOLINUX=yes
When building packages under poudriere on 11.0-RELEASE-p7 (from a
command
line in a terminal window) I'm noticing occasional streams of
diagnostic:
ELF binary type "3" not known.
which seem to be related to building some linux packages (example below,
parallel builds). Poudriere still
asn't been merged is
because it can't (yet) be made to work correctly on the develop branch
of iocage. But it works fine on the master branch.
https://github.com/iocage/iocage/pull/370
-Alan
Superb, appreciated!
Mark
On Tue, Dec 13, 2016 at 8:08 AM, Mark Martinec
<mark.martinec+free...@
2016-12-12 20:38, Christian Schwarz wrote:
With the new jail parameters, new namespaces for SysV IPC are possible
on FreeBSD 11.
For those ezjail users, add something like this to the jail's config
after creating it using 'ezjail-admin create':
export jail_postgres_parameters="sysvmsg=new
Regarding installation of PostgreSQL in a FreeBSD jail, the web hold
plenty of
warnings/advice that each postgres instance should have a unique UID,
otherwise
they stumble across each other's feet:
| allow.sysvipc
| A process within the jail has access to System V IPC primitives. In
the
|
2016-11-06 22:49, Stefan Bethke wrote:
So what do I set my LANG and LC variables to? I do want UTF-8, but I
do also want my scripts to continue to work. Clearly, en_US.UTF-8 is
not what I want. Is it C.UTF-8?
Or do I set LANG=en_US.UTF-8 and LC_COLLATE=C?
Yes, that is the safest bet.
2016-11-06 12:07, Baptiste Daroussin wrote:
Yes A-Z only means uppercase in an ASCII only world in a unicode world
it means
AaBb... Z because there are way more characters that simple A-Z. In
FreeBSD 11
we have a unicode collation instead of falling back in on LC_COLLATE=C
which
means ascii
On 10/28/16 14:15, Tomasz CEDRO wrote:
Just for the curious. I am testing on VirtualBox (Version 5.1.8
r111374 (Qt5.5.1), macOS 10.12.1 host). Cannot bootstrap PKG on a host
with NAT enabled.I have noticed this problem occurs only when NAT is
enabled in VBox. When I use Bridged interface there
, Mark Martinec wrote:
Whatever you did, it started to work now normally. Thank you!
(no changes at our side)
Mark
2016-10-12 16:29, Mark Martinec wrote:
Trying to upgrade a couple of hosts (11.0-RC2, 11.0-RC3,
10.3-RELEASE-p10)
to 11.0 (using: freebsd-update upgrade -r 11.0-RELEASE
Whatever you did, it started to work now normally. Thank you!
(no changes at our side)
Mark
2016-10-12 16:29, Mark Martinec wrote:
Trying to upgrade a couple of hosts (11.0-RC2, 11.0-RC3,
10.3-RELEASE-p10)
to 11.0 (using: freebsd-update upgrade -r 11.0-RELEASE), and it seems
the fetch(1
Trying to upgrade a couple of hosts (11.0-RC2, 11.0-RC3,
10.3-RELEASE-p10)
to 11.0 (using: freebsd-update upgrade -r 11.0-RELEASE), and it seems
the fetch(1) always fails with a timeout. Even a simple (freebsd-update
fetch)
in an attempt to bump a 10.3-RELEASE-p9 to 10.3-RELEASE-p10 now fails
I prefer to have a /var/run file system reside on a tmpfs
as its contents is small and ephemeral in its nature (like
pid files, lock files, sockets), need not be preserved across
reboots, and should not have to depend on any physical disk.
The problem is that some programs/services/ports like to
ITH_TESTS="yes" from
/etc/make.conf avoids the problem - although this was not necessary
in 10.2-RELEASE, as far as I can tell.
Mark
On 1/14/2016 7:42 AM, Mark Martinec wrote:
Prompted by recent security advisories I did a 'make buildworld'
on a fresh svn checkout, only to find out
be clearly documented in release notes.
Mark
On 2015-12-07 16:35, Mark Martinec wrote:
So, is this a new state of affairs that /usr/src file system
needs to be mounted exec in order for buildworld to succeed,
or is this an unintended change and I should file a bug report?
Mark
On 2015-11
So, is this a new state of affairs that /usr/src file system
needs to be mounted exec in order for buildworld to succeed,
or is this an unintended change and I should file a bug report?
Mark
On 2015-11-26 19:44, Miroslav Lachman wrote:
Mark Martinec wrote on 11/26/2015 19:31:
Up to about
Up to about a week ago building world on FreeBSD 10.2-STABLE went
just fine. Today after svn update the build fails:
# make buildworld
[...]
CC='cc ' mkdep -f .depend.getprotoent_test -a
-I/usr/src/lib/libc/tests/net -I/usr/src/lib/libnetbsd
-I/usr/src/contrib/netbsd-tests -std=gnu99
Upgrading 10.2-RELEASE-p6 to 10.2-RELEASE-p7 now solved ntpd crashes
(apparently fixed by: FreeBSD Errata Notice FreeBSD-EN-15:20.vm).
Thanks!!!
Mark
On 2015-11-01 10:31, Andre Albsmeier wrote:
On Fri, 30-Oct-2015 at 19:47:59 +0100, Mark Martinec wrote:
Not sure if it's the same issue
Not sure if it's the same issue, but it sure looks like it is.
I have upgraded a couple of hosts (amd64) from 10.2-RELEASE-p5
to 10.2-RELEASE-p6, i.e. the freebsd-upgrade essentially just
replaced the /usr/sbin/ntpd with a new one; then I restarted
the ntpd.
On all host but one this was
2015-10-01 10:32, Marko Cupać wrote:
what is the recommended poudriere jail version for building ports? So
far I was trying to be on latest binary patchlevel for every minor
version for both base system, poudriere jails and clients, but I ended
up with three jails just for amd64 (9.3, 10.1 and
Pete French wrote:
I updated to stable yesterday, plus updated all my porst to
the latest pecompiled packages, but I am now seeing odd problems
with bash on exit. Sometimes it quits, but leaves a zombie
process... e.g
PID TT STATTIME COMMAND
44308 v0 IW 0:00.00 -bash (bash)
44312 v0
On Sun, 16 Aug 2015, Kimmo Paasiala wrote:
It could be the classic fall back to TCP on SRV records problem on
your upstream DNS forwarder if you're using one:
http://lists.freebsd.org/pipermail/freebsd-ports/2012-May/074801.html
The cure would be to use your own caching DNS resolver (configured
On Sun, 16 Aug 2015, Kimmo Paasiala wrote:
It could be the classic fall back to TCP on SRV records problem on
your upstream DNS forwarder if you're using one:
http://lists.freebsd.org/pipermail/freebsd-ports/2012-May/074801.html
The cure would be to use your own caching DNS resolver (configured
62 matches
Mail list logo
