FreeBSD 13.0-CURRENT r354423: Nice!

ugen1.2: at usbus1 drmn0: successfully loaded firmware image with name: amdgpu/polaris10_mc.bin Real Nice! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: Segmentation fault in netstat after r354373 -> r354373 update

+++ b/libxo/libxo.c @@ -8104,6 +8104,8 @@ xo_parse_args (int argc, char **argv) cp = strrchr(xo_program, '/'); if (cp) xo_program = ++cp; +else + cp = argv[0]; /* Reset to front of string */ /* GNU tools add an annoying ".test" as the program extension;

Re: Segmentation fault in netstat after r354373 -> r354373 update

On 7 Nov 2019, at 11:03, Arnaud Ysmal wrote: > Looks cleaner than the unconst. I've spun a new release (1.3.1) and am importing it now. Building... Thanks, Phil ___ freebsd-current@freebsd.org mailing list

Re: Segmentation fault in netstat after r354373 -> r354373 update

My bad. Will role a fix asap. Thanks, Phil On 7 Nov 2019, at 10:08, Arnaud Ysmal wrote: Hi, I just got the same issue, it happens when argv[0] does not contain a / (calling uptime segfault but calling /usr/bin/uptime works). In xo_parse_args there is no check whether cp is NULL before

Re: unkillable process consuming 100% cpu

On Thu, Nov 07, 2019 at 03:32:23PM -0500, Mark Johnston wrote: > On Thu, Nov 07, 2019 at 12:29:19PM -0800, Steve Kargl wrote: > > I haven't seen anyone post about an unkillable process > > (even by root), which consumes 100% cpu. > > > > last pid: 4592; load averages: 1.24, 1.08, 0.74 up

Re: CURRENT October images do not create a bootable install

> On 7. Nov 2019, at 21:07, Chris wrote: > > On Thu, 7 Nov 2019 20:09:12 +0200 Toomas Soome tso...@me.com > said > >> > On 7. Nov 2019, at 19:37, Chris.H wrote: >> > > On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tso...@me.com said >> > >> > On 7. Nov 2019, at

Re: unkillable process consuming 100% cpu

On Thu, Nov 07, 2019 at 12:29:19PM -0800, Steve Kargl wrote: > I haven't seen anyone post about an unkillable process > (even by root), which consumes 100% cpu. > > last pid: 4592; load averages: 1.24, 1.08, 0.74 up 13+20:21:20 > 12:26:29 > 68 processes: 2 running, 66 sleeping > CPU:

unkillable process consuming 100% cpu

I haven't seen anyone post about an unkillable process (even by root), which consumes 100% cpu. last pid: 4592; load averages: 1.24, 1.08, 0.74 up 13+20:21:20 12:26:29 68 processes: 2 running, 66 sleeping CPU: 0.1% user, 0.0% nice, 12.6% system, 0.0% interrupt, 87.2% idle Mem: 428M

Re: [PATCH] Typo in libm code

On Thu, Nov 07, 2019 at 10:45:43AM -0800, Steve Kargl wrote: > This patch > > https://cvsweb.openbsd.org/src/lib/libm/src/ld80/k_sincosl.h?sortby=date > > is applicable to FreeBSD. > > Index: src/k_sincosl.h > === > ---

No vmm.ko present.

Hello, Since 12.1R (I've not used bhyve on 12R) I can't load the vmm.ko module, and it isn't present in /boot/kernel. In a first moment I thought that was a consequence of some src.conf customizations I did but there is at least one separated case on forums. This system of mine without vmm.ko

Re: CURRENT October images do not create a bootable install

On Thu, 7 Nov 2019 20:09:12 +0200 Toomas Soome tso...@me.com said > On 7. Nov 2019, at 19:37, Chris.H wrote: > > On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tso...@me.com said > >> > On 7. Nov 2019, at 17:23, Daniel Nebdal wrote: >> > >> On Thu, 7 Nov 2019 09:49:52 +0100

[PATCH] Typo in libm code

This patch https://cvsweb.openbsd.org/src/lib/libm/src/ld80/k_sincosl.h?sortby=date is applicable to FreeBSD. Index: src/k_sincosl.h === --- src/k_sincosl.h (revision 353571) +++ src/k_sincosl.h (working copy) @@ -28,8

Re: CURRENT October images do not create a bootable install

> On 7. Nov 2019, at 19:37, Chris.H wrote: > > On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tso...@me.com said > >> > On 7. Nov 2019, at 17:23, Daniel Nebdal wrote: >> > >> On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said >> >> I chose GPT. >> > > Maybe whoever wrote the

Re: CURRENT October images do not create a bootable install

On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tso...@me.com said > On 7. Nov 2019, at 17:23, Daniel Nebdal wrote: > >> On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said >> I chose GPT. > > Maybe whoever wrote the EFI/BIOS code in your machine went all-in on > "Legacy", and it

Re: Segmentation fault in netstat after r354373 -> r354373 update

Looks cleaner than the unconst. Le 7 novembre 2019 16:40:04 GMT+01:00, Phil Shafer a écrit : >+++ b/libxo/libxo.c >@@ -8104,6 +8104,8 @@ xo_parse_args (int argc, char **argv) > cp = strrchr(xo_program, '/'); > if (cp) > xo_program = ++cp; >+else >+ cp = argv[0];

Re: CURRENT October images do not create a bootable install

> On 7. Nov 2019, at 17:23, Daniel Nebdal wrote: > >> On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said >> I chose GPT. > > Maybe whoever wrote the EFI/BIOS code in your machine went all-in on > "Legacy", and it only handles MBR disks (or disks < 2.2TB)? > After all, it seems like

Re: CURRENT October images do not create a bootable install

> On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said > I chose GPT. Maybe whoever wrote the EFI/BIOS code in your machine went all-in on "Legacy", and it only handles MBR disks (or disks < 2.2TB)? After all, it seems like "not booting" would be a standards-compliant way for a classic

Re: Segmentation fault in netstat after r354373 -> r354373 update

On Thu, Nov 07, 2019 at 04:08:28PM +0100, Arnaud Ysmal wrote: > Hi, > > I just got the same issue, it happens when argv[0] does not contain a / > (calling uptime segfault but calling /usr/bin/uptime works). > > In xo_parse_args there is no check whether cp is NULL before calling > xo_streq. >

re: Segmentation fault in netstat after r354373 -> r354373 update

Hi, I just got the same issue, it happens when argv[0] does not contain a / (calling uptime segfault but calling /usr/bin/uptime works). In xo_parse_args there is no check whether cp is NULL before calling xo_streq. I fixed it by changing this line: - cp = [len + 1 -

Segmentation fault in netstat after r354373 -> r354373 update

(I haven't started to look for a culprit yet; thought I'd let folks know about it first. -- dhw) g1-49(13.0-C)[1] uname -a FreeBSD g1-49.catwhisker.org 13.0-CURRENT FreeBSD 13.0-CURRENT #514 r354436M/354436: Thu Nov 7 04:15:23 PST 2019

Re: CURRENT October images do not create a bootable install

On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said On Thu, 07 Nov 2019 00:38:29 -0800 Chris wrote: > On Thu, 7 Nov 2019 10:15:49 +0200 Toomas Soome tso...@me.com said > > > > On 7. Nov 2019, at 10:05, Chris wrote: > > > > > On Thu, 7 Nov 2019 08:31:14 +0100 gljennj...@gmail.com

Re: CURRENT October images do not create a bootable install

> On 7. Nov 2019, at 10:38, Chris wrote: > > On Thu, 7 Nov 2019 10:15:49 +0200 Toomas Soome tso...@me.com > said > >> > On 7. Nov 2019, at 10:05, Chris wrote: >> > > On Thu, 7 Nov 2019 08:31:14 +0100 gljennj...@gmail.com said >> > >> On Wed, 06 Nov 2019 17:23:08

Re: CURRENT October images do not create a bootable install

On Thu, 07 Nov 2019 00:38:29 -0800 Chris wrote: > On Thu, 7 Nov 2019 10:15:49 +0200 Toomas Soome tso...@me.com said > > > > On 7. Nov 2019, at 10:05, Chris wrote: > > > > > On Thu, 7 Nov 2019 08:31:14 +0100 gljennj...@gmail.com said > > > > >> On Wed, 06 Nov 2019 17:23:08 -0800 > > >>

Re: CURRENT October images do not create a bootable install

On Thu, 7 Nov 2019 10:15:49 +0200 Toomas Soome tso...@me.com said > On 7. Nov 2019, at 10:05, Chris wrote: > > On Thu, 7 Nov 2019 08:31:14 +0100 gljennj...@gmail.com said > >> On Wed, 06 Nov 2019 17:23:08 -0800 >> Chris wrote: >> > I put a box together to test 13 about a mos ago. >> > It's

Re: CURRENT October images do not create a bootable install

> On 7. Nov 2019, at 10:05, Chris wrote: > > On Thu, 7 Nov 2019 08:31:14 +0100 gljennj...@gmail.com said > >> On Wed, 06 Nov 2019 17:23:08 -0800 >> Chris wrote: >> > I put a box together to test 13 about a mos ago. >> > It's a second gen core i3. But whether choosing automatic >> > disk

Re: CURRENT October images do not create a bootable install

On Thu, 7 Nov 2019 08:31:14 +0100 gljennj...@gmail.com said On Wed, 06 Nov 2019 17:23:08 -0800 Chris wrote: > I put a box together to test 13 about a mos ago. > It's a second gen core i3. But whether choosing automatic > disk layout, or choosing manual. When the install finishes, and > boots