similar to: [PATCH] drm/nouveau/falcon: fix a few indentation issues

The msgqueue pointer validity should be checked by its owner, not by the msgqueue code itself to avoid this situation. Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> Reported-by: Julia Lawall <julia.lawall at lip6.fr> --- drm/nouveau/nvkm/engine/sec2/base.c | 7 +++++++ drm/nouveau/nvkm/falcon/msgqueue.c | 5 ++--- drm/nouveau/nvkm/subdev/pmu/gm20b.c | 6 ++++++ 3 files

Thanks Tobias, I tried this but unfortunately the only effect was thta the boot was delayed by an additional 4 seconds :( The original timeout is at drivers/gpu/drm/nouveau/nvkm/subdev/secboot/ls_ucode_msgqueue.c I tried to increase that timeout, but it did not seem to make a difference either. I think I get this error less often when I have a cable plugged in the output of that card at boot,

Hi, the system fails to initialize your vbios using secureboot (i had a rare chance to on my system to witness it again), for now i traced it to acr_boot_falcon() in "linux/drivers/gpu/drm/nouveau/nvkm/falcon/msgqueue_0148cdec.c" where it throws -110 which is -ETIMEDOUT. You could try to increase the timeout and see if it helps something, similar to the following: diff --git

GP10B is the chip used in Tegra X2 SoCs. This patchset adds support for its base engines after reworking secboot a bit to accomodate its calling convention better. This patchset has been tested rendering simple off-screen buffers using Mesa and yielded the expected result. Alexandre Courbot (15): secboot: allow to boot multiple falcons secboot: pass instance to LS firmware loaders secboot:

Make the msgqueue_0148cdec_acr_func and msgqueue_0148cdec_func static to avoid the following sparse warnings: drivers/gpu/drm/nouveau/nvkm/falcon/msgqueue_0148cdec.c:230:1: warning: symbol 'msgqueue_0148cdec_acr_func' was not declared. Should it be static? drivers/gpu/drm/nouveau/nvkm/falcon/msgqueue_0148cdec.c:241:1: warning: symbol 'msgqueue_0148cdec_func' was not declared.

In preparation to enabling -Wvla, remove VLA. In this particular case directly use macro NVKM_MSGQUEUE_CMDLINE_SIZE instead of local variable cmdline_size. Also, remove cmdline_size as it is not actually useful anymore. The use of stack Variable Length Arrays needs to be avoided, as they can be a vector for stack exhaustion, which can be both a runtime bug or a security flaw. Also, in general, as

Hello Alexandre Courbot, This is a semi-automatic email about new static checker warnings. The patch 9b536e9d5251: "drm/nouveau/falcon: add msgqueue interface" from Jan 19, 2017, leads to the following Smatch complaint: drivers/gpu/drm/nouveau/nvkm/falcon/msgqueue.c:514 nvkm_msgqueue_recv() error: we previously assumed 'queue' could be null (see line 513)

Hi David, On 03/13/2018 11:10 AM, David Laight wrote: > From: Gustavo A. R. Silva >> Sent: 13 March 2018 14:48 >> In preparation to enabling -Wvla, remove VLA. In this particular >> case directly use macro NVKM_MSGQUEUE_CMDLINE_SIZE instead of local >> variable cmdline_size. Also, remove cmdline_size as it is not >> actually useful anymore. > ... >> diff

From: Gustavo A. R. Silva > Sent: 13 March 2018 14:48 > In preparation to enabling -Wvla, remove VLA. In this particular > case directly use macro NVKM_MSGQUEUE_CMDLINE_SIZE instead of local > variable cmdline_size. Also, remove cmdline_size as it is not > actually useful anymore. ... > diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/secboot/ls_ucode_msgqueue.c >

Hi Tobias, On Mon, Sep 11, 2017 at 8:49 PM, Tobias Klausmann < tobias.johannes.klausmann at mni.thm.de> wrote: > Hi, > > i remember seeing the same error with earlier firmware version with a > similar system (GP106) once in a while on boot, yet it does not happen > with newer versions. Maybe you could try to update the firmware to the > latest version from

In preparation to enabling -Wvla, remove VLA. In this particular case directly use macro NVKM_MSGQUEUE_CMDLINE_SIZE instead of local variable cmdline_size. Also, remove cmdline_size as it is not actually useful anymore. The use of stack Variable Length Arrays needs to be avoided, as they can be a vector for stack exhaustion, which can be both a runtime bug or a security flaw. Also, in general, as

Hi Philips, I have the same error after upgrade from dovecot 2.2 to dovecot 2.3, could be related to "service stats", try to grep in the dovecot.log for "reached" and look for an error like: dovecot: master: Warning: service(stats): client_limit (1000) reached, client connections are being dropped If you find it add to 10-master.conf: service stats { ? client_limit =

Hello, If it is on a (VMware) virtual machine, maybe the network capacity or cpu capacity might be consumed by other virtual machines ? Could there be a backup process running on the other machines ? Henk Van: Icecast [mailto:icecast-bounces at xiph.org] Namens Pedro M. Oliveira Verzonden: vrijdag 12 april 2019 21:32 Aan: icecast at xiph.org Onderwerp: [Icecast] Something not good.

[root at abc asterisk]# lsof -u 50771 | wc -l 0 BTW, I'm using CentOS 6.5 > > Date: Thu, 13 Oct 2016 10:20:19 -0400 >> From: Dovid Bender <dovid at telecurve.com> >> To: Asterisk Users Mailing List - Non-Commercial Discussion >> <asterisk-users at lists.digium.com> >> Subject: Re: [asterisk-users] Openfile Issue >> Message-ID:

Hello everyone, we have a huge problem with dovecot and IMAP connections. we got the following errors: 39665 today dovecot: imap-login: Error: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable (client-pid=29066, client-id=1755, rip=IP, created 562 msecs ago, received 0/4 bytes) we thinks this may be a problem with

Hello, I've a problem on my system with inotify. In the smbd logfile are shown a lot messages like this: [2015/06/10 11:15:21.644453, 0, pid=57030, effective(12700, 100), real(0, 0)] smbd/notify_inotify.c:297(inotify_setup) Failed to init inotify - Too many open files [2015/06/10 11:15:23.968497, 0, pid=57030, effective(12700, 100), real(0, 0)] smbd/notify_inotify.c:297(inotify_setup)

Everyone, I have a mail server running CentOS release 6.3 (Final) with 2.6.32-279.22.1.el6.i686 kernel that is reporting errors to me pertaining dovecot. I have appended the error message to this note. There is only one user that appears to generate this message, and it is generated to me by way of e-mail without a perceptible problem to the user which is not me. This particular user had an

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, First of all, thank you for the work the contributors are doing with Dovecot ! Dovecot is doing a great job ! I am encountering a problem with a configuration and, despite my search on the web, I do not find any solution for this problem. Dovecot seems to stop accepting new connection. The users : - - can not save sent messages to

Hello guys we have Dovecot 2.0.19 and we are getting those errors opening files of dovecot Too many open files, we?ve tried to increase limits in /etc/security/limits Wih ulimits ?a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 63735