Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

2018-06-04 Thread Konstantin Belousov
On Mon, Jun 04, 2018 at 12:46:32AM +0200, Michael Gmelin wrote: > > > On Sun, 3 Jun 2018 23:53:40 +0300 > Konstantin Belousov wrote: > > > On Sun, Jun 03, 2018 at 09:50:20PM +0200, Michael Gmelin wrote: > > > > > > > > > On Sun, 3 Jun 2018 18:04:23 +0300 > > > Konstantin Belousov wrote: > >

Re: how to deal with variable set but not used warnings?

2018-06-04 Thread Rick Macklem
Matthew Macy wrote: >On Sun, Jun 3, 2018 at 2:40 PM, Theron wrote: >>> 4. Disable the stupid warning in the Makefile / build system. If you don't >>> care, and there's a good reason for what you are doing (sounds like there >>> is), better to just disable the warning as so much useless noise. >>>

Re: Error build nvidia-driver with r334555

2018-06-04 Thread Tomoaki AOKI
On Sun, 3 Jun 2018 15:20:24 +0200 Mateusz Guzik wrote: > On Sun, Jun 3, 2018 at 2:42 PM, Tomoaki AOKI > wrote: > > > This is caused by r334533 and/or r334534 (memset-related changes). > > sysutils/lsof is also affected. > > > > You should revert r334533 and r334534 temporarily until nvidia-driv

Re: Can't seem to use 5GHz APs with Intel wireless

2018-06-04 Thread Adam
On Sun, Jun 3, 2018 at 9:50 PM, Dhananjay Balan wrote: > On Sun, Jun 03, 2018 at 07:33:30PM +0200, Christoph Moench-Tegeder wrote: > > > Is the regdomain/country setting correct for your area and matches your > > AP? Especially in the 5GHz band there are some "gaps" - not all channels > > may be

error building libpmc_events.c

2018-06-04 Thread Claude Buisson
Hi, During a buildworld of head on amd64, from 332518 to 334590, the build stops with: --- all_subdir_lib/libpmc --- ===> lib/libpmc (all) --- libpmc_events.c --- ./pmu-events/jevents "x86" /home/src/lib/libpmc/pmu-events/arch libpmc_events.c sh: ./pmu-events/jevents: not found *** [libpmc_e

RE: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted

2018-06-04 Thread Martin.Ambroz
> Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 memstick > images on various hardware? Note, this is not a request to install 12.0- > CURRENT, only a boot-test with various system knobs tweaked. > > The most recent images are available at: > https://download.freebsd

Re: Error build nvidia-driver with r334555

2018-06-04 Thread Alexey Dokuchaev
On Sun, Jun 03, 2018 at 09:42:22PM +0900, Tomoaki AOKI wrote: > This is caused by r334533 and/or r334534 (memset-related changes). > sysutils/lsof is also affected. > > You should revert r334533 and r334534 temporarily until nvidia-driver > support this change. nVidia driver port was fixed as of

Re: Error build nvidia-driver with r334555

2018-06-04 Thread Alex V. Petrov
Спасибо Алексей! Thank you! 05.06.2018 00:46, Alexey Dokuchaev пишет: > On Sun, Jun 03, 2018 at 09:42:22PM +0900, Tomoaki AOKI wrote: >> This is caused by r334533 and/or r334534 (memset-related changes). >> sysutils/lsof is also affected. >> >> You should revert r334533 and r334534 temporarily un

Re: [RFC] Deprecation and removal of the drm2 driver

2018-06-04 Thread Adrian Chadd
Hi, As a driver/framework developer - no, don't do that. It's worked mostly great for the video side of things because your touch points are "the VM system" and "linuxkpi". And they're all in one big driver pull from Linux. For wifi as an example - it has a bunch of userland components, a kernel

Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted

2018-06-04 Thread Ian FREISLICH
On 05/30/2018 11:50 AM, Glen Barber wrote: Hi, Could folks please help boot-test the most recent 12.0-CURRENT amd64 memstick images on various hardware? Note, this is not a request to install 12.0-CURRENT, only a boot-test with various system knobs tweaked. The most recent images are available

Re: [RFC] Deprecation and removal of the drm2 driver

2018-06-04 Thread Matthew Macy
On Mon, Jun 4, 2018 at 12:03 PM, Adrian Chadd wrote: > Hi, > > As a driver/framework developer - no, don't do that. > > It's worked mostly great for the video side of things because your > touch points are "the VM system" and "linuxkpi". And they're all in > one big driver pull from Linux. > > For

Re: Deadlocks / hangs in ZFS

2018-06-04 Thread Alexander Leidinger
Quoting Slawa Olhovchenkov (from Sun, 3 Jun 2018 22:28:14 +0300): On Sun, Jun 03, 2018 at 09:14:50PM +0200, Alexander Leidinger wrote: Quoting Alexander Leidinger (from Mon, 28 May 2018 09:02:01 +0200): > Quoting Slawa Olhovchenkov (from Mon, 28 May 2018 > 01:06:12 +0300): > >> On Sun, M

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

2018-06-04 Thread Michael Gmelin
On Mon, 4 Jun 2018 14:06:55 +0300 Konstantin Belousov wrote: > On Mon, Jun 04, 2018 at 12:46:32AM +0200, Michael Gmelin wrote: > > > > > > On Sun, 3 Jun 2018 23:53:40 +0300 > > Konstantin Belousov wrote: > > > > > On Sun, Jun 03, 2018 at 09:50:20PM +0200, Michael Gmelin wrote: > > > >

Re: [RFC] Deprecation and removal of the drm2 driver

2018-06-04 Thread Adrian Chadd
Hi, If there's an API that isn't being used then great, I'll go find it and fix up pieces in my spare time to use it. But the last drive by cut/paste didn't do that; it just changed the code in place. :-) -adrian ___ freebsd-current@freebsd.org mailin

Re: svn commit: r334626 - in head: . . . [brk_test fails to build for aarch64 and stops build: no brk or sbrk to test, so undefined symbols]

2018-06-04 Thread Mark Millard
>From ci.freebsd.org for a -r334626 + builds: --- brk_test.full --- cc -target aarch64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/arm64.aarch64/tmp -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin -O2 -pipe -g -std=iso9899:1999 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format