Re: ACPI Error: No handler for Region [ECOR]

[Samy Mahmoudi]

Same problem/output as Charlie Li, with a Lenovo T520.

I will post requested output files as soon as possible.
___
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: ACPI Error: No handler for Region [ECOR]

[Samy Mahmoudi]

Hi again,

Please find the requested files:

http://imp.ovh/18.2.0/acpidump_-dt_output
http://imp.ovh/18.2.0/acpi_ec_values
http://imp.ovh/18.2.0/dmesg_output

Best regards,
Samy

>
___
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: ACPI Error: No handler for Region [ECOR]

[Samy Mahmoudi]

Hi all,

"patch -p 1 < your_patch" gives me the following *.rej file:
@@ -362,7 +362,8 @@
ret = 0;

goto out;
-}
+} else
+   ecdt = 0;

 ret = ACPI_ID_PROBE(device_get_parent(dev), dev, ec_ids, NULL);
 if (ret > 0)
@@ -422,16 +434,6 @@
 /* Store the values we got from the namespace for attach. */
 acpi_set_private(dev, params);

-/*
- * Check for a duplicate probe. This can happen when a probe via ECDT
- * succeeded already. If this is a duplicate, disable this device.
- */
-peer = devclass_get_device(acpi_ec_devclass, params->uid);
-if (peer == NULL || !device_is_alive(peer))
-   ret = 0;
-else
-   device_disable(dev);
-
 if (buf.Pointer)
AcpiOsFree(buf.Pointer);
 out:

Reject of hunk 1 and hunk 3 may be due to indentation. Anyway, I manually
patched these two parts and I am now waiting for kernel build.
___
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: ACPI Error: No handler for Region [ECOR]

[Samy Mahmoudi]

With your patch applied, normal behavior seems back again.

"dmesg" output and other relevent files are availabe at:
http://imp.ovh/acpi

>
___
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"

Base committer requested for less evident error - Bug 232042 - [patch] handbook/firewalls: correct two errors related to Packet Filter

[Samy Mahmoudi]

Dear committers,

Could someone have a look at Bug 232042
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232042>?

Best regards,
Samy Mahmoudi
___
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"

Base committer requested for evident error - Bug 232031 - [patch] contrib/openresolv: fix a typo in resolvconf(8)

[Samy Mahmoudi]

Dear committers,

Could someone have a look at Bug 232031
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232031>?

Best regards,
Samy Mahmoudi
___
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"

awk manual

[Samy Mahmoudi]

Hello,

The awk manual seems out of date.

For example, the -V option is documented but is unknown at execution.
Reciprocally, --version is not documented but is functional at execution.
Under FreeBSD 12.0-CURRENT, the date at the end of the manual also seems
older than expected, as the FreeBSD Manual Pages indicates a newer date for
FreeBSD 11.2.

I could edit awk.1 and copy/paste a patch to solve these but reviewing the
whole manual may be better to eradicate other omissions. From the FreeBSD
Manual Pages, I have found out that options (including -V) were introduced
between 11.0 RELEASE and 11.1 RELEASE.

By the way, choosing the "FreeBSD 12-current" manual on that web page

actually gives the "FreeBSD 11.2" manual, seemingly.

Best regards,
Samy
___
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"

r336806: buildworld failed: emmintrin.h file not found

[Samy Mahmoudi]

 Basic/SourceManager.o 
/usr/src/contrib/llvm/tools/clang/lib/Basic/SourceManager.cpp:1175:10 fatal
error: 'emmintrin.h' file not found
#include 
  ^--
The file is located at
/usr/src/contrib/llvm/tools/clang/lib/Headers/emmintrin.h but I do not know
how to properly indicate this to the build suite.
___
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: r336806: buildworld failed: emmintrin.h file not found

[Samy Mahmoudi]

I found an answer in the last comment of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190669

2018-07-28 12:34 GMT+02:00 Samy Mahmoudi :

>  Basic/SourceManager.o 
> /usr/src/contrib/llvm/tools/clang/lib/Basic/SourceManager.cpp:1175:10
> fatal error: 'emmintrin.h' file not found
> #include 
>   ^--
> The file is located at 
> /usr/src/contrib/llvm/tools/clang/lib/Headers/emmintrin.h
> but I do not know how to properly indicate this to the build suite.
>
___
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: building LLVM threads gets killed

[Samy Mahmoudi]

> And probably running ZFS, which ate all your memory and
> put you in a memory contrained environment.

That's exactly why I keep the following in my /boot/loader.rc:

# vfs.zfs.arc_max=1073741824
vfs.zfs.arc_max=2147483648
# vfs.zfs.arc_max=4294967296
___
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: building LLVM threads gets killed

[Samy Mahmoudi]

> That's exactly why I keep the following in my /boot/loader.rc:

I meant "in my /boot/loader.conf"...
___
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: USB sound devices with FreeBSD-CURRENT

[Samy Mahmoudi]

Hi,

If reducing the audio buffer size in virtual_oss does not solve the issue
and you temporarily resort to use PulseAudio to achieve switching devices
on-the-fly (which does work very well with PulseAudio), you could indeed
'keep the devices connected' and use a variant of the following script:

#!/usr/local/bin/zsh
SINK_INDEX1=1
SINK_INDEX2=4
ACTIVE_SINK=$(pacmd list-sinks | grep '* index:' | /usr/local/bin/grep -o
'[0-9]*')
if [ "$ACTIVE_SINK" = $SINK_INDEX1 ] ; then
pacmd set-default-sink $SINK_INDEX2
pacmd list-sink-inputs | awk '/index:/{print $2}' | xargs -r -I{} pacmd
move-sink-input {} $SINK_INDEX2
else
pacmd set-default-sink $SINK_INDEX1
pacmd list-sink-inputs | awk '/index:/{print $2}' | xargs -r -I{} pacmd
move-sink-input {} $SINK_INDEX1
fi

In its current form, it allowed me to switch devices on-the-fly with a
keyboard shortcut.

The problem is I had to use a poudriere to build relevant ports with option
PULSEAUDIO (chromium, firefox, mpv, audacious, virtualbox, etc.) and there
may have been (I can not remember precisely) another problem if the USB
headset was either hot-plugged or hot-unplugged. Please let us know if you
manage to sort this out with virtual_oss.
___
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: Zpool doesn't boot anymore after FreeBSD 12.1

[Samy Mahmoudi]

Hi!

> That's why I have terribly outdated 13-CURRENT
on a bunch of servers and can't update them.

The way you're holding your head on your avatar looks
like you upgraded your servers' pools and now realize
your mistake! Fortunately, you did not ;-)
___
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: Building packages with poudriere fails after `zfs upgrade`

[Samy Mahmoudi]

Hi,

Have you tried to work around the issue by creating a new jail with
poudriere,
or even by changing the value of ZROOTFS in poudriere.conf ?

Best regards,
Samy Mahmoudi
___
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"