Re: devd in r329188M don't start

2018-02-15 Thread Rainer Hurling

Am 16.02.2018 um 07:17 schrieb Warner Losh:



On Thu, Feb 15, 2018 at 11:12 PM, Rainer Hurling > wrote:


Am 13.02.2018 um 13:50 schrieb Hans Petter Selasky:

On 02/13/18 10:47, Jakob Alvermark wrote:

+1

My USB mouse was working fine before the switch to devmatch.
Now I have to 'kldload ums' manually.

Same for USB audio, snd_uaudio.ko was loaded by devd before.


Hi,

This is a known issue.

Can you try the attached patch?

Rebuild devmatch(8) and reinstall /etc/devd/devmatch.conf and
/etc/rc.d/devmatch only.

--HPS



Is there any chance to get this committed into base in the near future?


Yes.

Warner


Nice, thanks :)
___
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: devd in r329188M don't start

2018-02-15 Thread Warner Losh
On Thu, Feb 15, 2018 at 11:12 PM, Rainer Hurling  wrote:

> Am 13.02.2018 um 13:50 schrieb Hans Petter Selasky:
>
>> On 02/13/18 10:47, Jakob Alvermark wrote:
>>
>>> +1
>>>
>>> My USB mouse was working fine before the switch to devmatch. Now I have
>>> to 'kldload ums' manually.
>>>
>>> Same for USB audio, snd_uaudio.ko was loaded by devd before.
>>>
>>>
>> Hi,
>>
>> This is a known issue.
>>
>> Can you try the attached patch?
>>
>> Rebuild devmatch(8) and reinstall /etc/devd/devmatch.conf and
>> /etc/rc.d/devmatch only.
>>
>> --HPS
>>
>
>
> Is there any chance to get this committed into base in the near future?
>

Yes.

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"


Re: devd in r329188M don't start

2018-02-15 Thread Rainer Hurling

Am 13.02.2018 um 13:50 schrieb Hans Petter Selasky:

On 02/13/18 10:47, Jakob Alvermark wrote:

+1

My USB mouse was working fine before the switch to devmatch. Now I 
have to 'kldload ums' manually.


Same for USB audio, snd_uaudio.ko was loaded by devd before.



Hi,

This is a known issue.

Can you try the attached patch?

Rebuild devmatch(8) and reinstall /etc/devd/devmatch.conf and 
/etc/rc.d/devmatch only.


--HPS



Is there any chance to get this committed into base in the near future?

Thanks for any answer,
Rainer Hurling
___
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: devd in r329188M don't start

2018-02-15 Thread Lawrence Stewart
On 13/02/2018 23:50, Hans Petter Selasky wrote:
> On 02/13/18 10:47, Jakob Alvermark wrote:
>> +1
>>
>> My USB mouse was working fine before the switch to devmatch. Now I
>> have to 'kldload ums' manually.
>>
>> Same for USB audio, snd_uaudio.ko was loaded by devd before.
>>
> 
> Hi,
> 
> This is a known issue.
> 
> Can you try the attached patch?
> 
> Rebuild devmatch(8) and reinstall /etc/devd/devmatch.conf and
> /etc/rc.d/devmatch only.

+1 for ums mouse breakage on recent upgrade from head 20180201 (Git
9e57d147a97) to head 20180215 (Git 81891e10182). Will build and test
patch on the weekend, but given the 2 success reports already, I presume
it will fix things for me too. I won't follow up to this thread again
unless the patch doesn't work for me. Thanks Hans.

Cheers,
Lawrence
___
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: New ACPI Errors

2018-02-15 Thread Jung-uk Kim
On 02/13/2018 17:34, Claude Buisson wrote:
> On 02/13/2018 22:49, Pete Wright wrote:
>> Hello,
>> I have started seeing a lot of these messages spam my system log:
>>
>> ACPI Error: No pointer back to namespace node in package
>> 0xf8000f79a080 (20180209/dsargs-472)
>> ACPI Error: Method parse/execution failed \134_SB.AC.ADJP,
>> AE_AML_INTERNAL (20180209/psparse-677)
>> ACPI Error: Method parse/execution failed \134_SB.AC._PSR,
>> AE_AML_INTERNAL (20180209/psparse-677)
>>
>> I noticed this starting from a CURRENT build i installed two weeks
>> ago, and still see it from a world/kernel i built last night.  two
>> questions:
>> 1) has anyone else noticed this?
>> 2) is this something to worry about?
>>
>> i can help debug the issue but am not sure where to start poking.
>>
>> thanks!
>> -pete
>>
> Here I have
> 
> ACPI Error: No pointer back to namespace node in package
> 0xf8000171f700 (20180209/dsargs-472)
> ACPI Error: AE_AML_INTERNAL, While resolving operands for [OpcodeName
> unavailable] (20180209/dswexec-606)
> ACPI Error: Method parse/execution failed
> \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677)
> 
> with svn 329142 on a Lenovo ThinkCentre M83
> ACPI APIC Table: 
> 
> Claude Buisson

I believe you can silence the errors with the attached patch.  Please
try it and let me know.

Jung-uk Kim
Index: sys/contrib/dev/acpica/include/platform/acfreebsd.h
===
--- sys/contrib/dev/acpica/include/platform/acfreebsd.h	(revision 329340)
+++ sys/contrib/dev/acpica/include/platform/acfreebsd.h	(working copy)
@@ -166,6 +166,7 @@
 
 #define ACPI_UINTPTR_T  uintptr_t
 
+#define ACPI_IGNORE_PACKAGE_RESOLUTION_ERRORS
 #define ACPI_USE_DO_WHILE_0
 #define ACPI_USE_LOCAL_CACHE
 #define ACPI_USE_NATIVE_DIVIDE


signature.asc
Description: OpenPGP digital signature


Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

2018-02-15 Thread Ian FREISLICH
On 02/14/18 03:42, Vladimir Zakharov wrote:
> On Tue, Feb 13, 2018, Bryan Drewery wrote:
>> On 2/13/2018 1:48 AM, Vladimir Zakharov wrote:
>>> On Mon, Feb 12, 2018, Bryan Drewery wrote:
 On 2/12/2018 6:54 AM, Vladimir Zakharov wrote:
> Hello, Bryan!
>
> On Fri, Feb 09, 2018, Bryan Drewery wrote:
>> On 2/1/2018 1:10 AM, Vladimir Zakharov wrote:
>>> Hello!
>>>
>>> For some time (about a week) building and installing kernel fails with
>>> the error "Variable OBJTOP is recursive." when going to build/install
>>> module from ports.
>>>
>>> Last successful build was at r328426. Next build at r328527 failed and
>>> still broken at r328649.
>>>
>>> Without PORTS_MODULES building and installing kernel succeeds. Another
>>> workaround: ignore error and build/install module directly from ports.
>>> ...
>> For some reason I cannot recreate this issue.
> It seems, setting WITH_AUTO_OBJ in /etc/src-env.conf causes an error.
> At least, removing it fixes build for me.
>
> Build successful with the following settings:
> # cat /etc/src-env.conf
> WITH_META_MODE=
> #WITH_AUTO_OBJ=
>
 Please try this patch (requires a buildkernel).

 https://people.freebsd.org/~bdrewery/patches/kernel-portsmodules.diff

>>> Fixed partly:
>>> | buildkernel  | installkernel |
>>> r329196 | OK   | FAIL(*)   |
>>> r329169 + patch | OK   | OK|
>>> r329196 + WITH_AUTO_OBJ | FAIL |   |
>>> r329169 + WITH_AUTO_OBJ + patch | FAIL |   |
>>>
>>> (*) - same error "Variable OBJTOP is recursive".
>>>
>> Thanks, r329232 should fix it.
> Not yet. 'installkernel' still fails (see below). Can be fixed either by
> explicit setting WITHOUT_AUTO_OBJ in /etc/src-env.conf or by applying
> previous patch (s/build/stage/ in kern.post.mk:89).
>
> # svn info
> Path: .
> Working Copy Root Path: /usr/src
> URL: https://svn.freebsd.org/base/head
> Relative URL: ^/head
> Repository Root: https://svn.freebsd.org/base
> Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
> Revision: 329259
> Node Kind: directory
> Schedule: normal
> Last Changed Author: eadler
> Last Changed Rev: 329259
> Last Changed Date: 2018-02-14 10:59:30 +0300 (Wed, 14 Feb 2018)
>
> # cat /etc/src-env.conf
> WITH_META_MODE=
> #WITH_AUTO_OBJ=
>
> # env | grep MAKE
> MAKEOBJDIRPREFIX=/home/obj
>
> # make -j 4 buildkernel && make installkernel
> ...
> ===> Ports module graphics/drm-next-kmod (all)
> cd ${PORTSDIR:-/usr/ports}/graphics/drm-next-kmod; env  -u CC  -u CXX  -u CPP 
>  -u MAKESYSPATH  -u MAKEOBJDIR  MAKEFLAGS="-j 4 -J 15,16 -j 4 -J 15,16 -D 
> NO_MODULES_OBJ .MAKE.LEVEL.ENV=MAKELEVEL KERNEL=kernel TARGET=amd64 
> TARGET_ARCH=amd64"  SYSDIR=/usr/src/sys  
> PATH=/home/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/home/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/home/obj/usr/src/amd64.amd64/tmp/legacy/bin:/home/obj/usr/src/amd64.amd64/tmp/usr/sbin:/home/obj/usr/src/amd64.amd64/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin
>   SRC_BASE=/usr/src  OSVERSION=1200058  
> WRKDIRPREFIX=/home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG make -B clean 
> build
> ===>  Cleaning for drm-next-kmod-g20180117
> ===>  License BSD2CLAUSE MIT GPLv2 accepted by the user
> ===>   drm-next-kmod-g20180117 depends on file: /usr/local/sbin/pkg - found
> ===> Fetching all distfiles required by drm-next-kmod-g20180117 for building
> ===>  Extracting for drm-next-kmod-g20180117
> => SHA256 Checksum OK for FreeBSDDesktop-kms-drm-g20180117-622fdd1_GH0.tar.gz.
> ===>  Patching for drm-next-kmod-g20180117
> ===>   drm-next-kmod-g20180117 depends on file: /usr/local/bin/ccache - found
> ===>  Configuring for drm-next-kmod-g20180117
> ===>  Building for drm-next-kmod-g20180117
> [Creating objdir obj...]
> ...
> --
 Kernel build for GENERIC-NODEBUG completed on Wed Feb 14 11:09:45 MSK 2018
> --
> --
 Installing kernel GENERIC-NODEBUG on Wed Feb 14 11:09:45 MSK 2018
> --
> ...
> kldxref /boot/kernel
> ===> Ports module graphics/drm-next-kmod (install)
> cd ${PORTSDIR:-/usr/ports}/graphics/drm-next-kmod; env  -u CC  -u CXX  -u CPP 
>  -u MAKESYSPATH  -u MAKEOBJDIR  MAKEFLAGS=".MAKE.LEVEL.ENV=MAKELEVEL 
> KERNEL=kernel MK_AUTO_OBJ=no TARGET=amd64 TARGET_ARCH=amd64"  
> SYSDIR=/usr/src/sys  
> PATH=/home/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/home/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/home/obj/usr/src/amd64.amd64/tmp/legacy/bin:/home/obj/usr/src/amd64.amd64/tmp/usr/sbin:/home/obj/usr/src/amd64.amd64/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin
>   SRC_BASE