chromium-80.0.3987.163_1 FreeBSD 11.3-STABLE #0 r356413: Mon Jan 6 23:59:20 CET 2020 > grep sign-extension /var/log/messages | awk ' { print $5, $6, $9, $10, $11, $12, $13, $14 } ' | sort -u kernel: WARNING (chrome): ioctl sign-extension ioctl ffffffff80045612 kernel: WARNING (chrome): ioctl sign-extension ioctl ffffffff80045613 kernel: WARNING (chrome): ioctl sign-extension ioctl ffffffffc008561b kernel: WARNING (chrome): ioctl sign-extension ioctl ffffffffc008561c kernel: WARNING (chrome): ioctl sign-extension ioctl ffffffffc0145608 kernel: WARNING (chrome): ioctl sign-extension ioctl ffffffffc0205648 kernel: WARNING (chrome): ioctl sign-extension ioctl ffffffffc02c564a kernel: WARNING (chrome): ioctl sign-extension ioctl ffffffffc034564b kernel: WARNING (chrome): ioctl sign-extension ioctl ffffffffc0405602 kernel: WARNING (chrome): ioctl sign-extension ioctl ffffffffc0445624 kernel: WARNING (chrome): ioctl sign-extension ioctl ffffffffc0585609 kernel: WARNING (chrome): ioctl sign-extension ioctl ffffffffc058560f kernel: WARNING (chrome): ioctl sign-extension ioctl ffffffffc0585611 kernel: WARNING (chrome): ioctl sign-extension ioctl ffffffffc0cc5615 kernel: WARNING (chrome): ioctl sign-extension ioctl ffffffffc0cc5616 kernel: WARNING (chrome): ioctl sign-extension ioctl ffffffffc0d05605 Trying to participate in a Zoom teleconference with "computer audio". The microphone is detected but no audio can be heard on the other side, maybe those warnings are related.
probably fixed in base r359968
@Samy How does this depend on bug 250126
(In reply to Mikael Urankar from comment #1) @hselasky Is there something the www/chromium port can do in the meantime to address the warning?
I think chromium uses its own IOCTL definitions. You'll need to find those and change them to use unsigned integer format. BTW: The kernel warning is harmless, because the kernel will always cast the cmd argument to 32-bit. It should not affect audio. Try to install "sndio" and run "service sndiod onestart" if there is no audio in chrome. --HPS
(In reply to Kubilay Kocak from comment #2) Hi all, @Kubilay Kocak Without much knowledge and before base r359968 I thought I would attempt to debug this by my own. Then I got blocked by the issue of bug 250126. I now realize that more knowledgeable people can resolve this issue irrespective of bug 250126: I had no intention to be egocentric :-)