search for: msgqueue

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...

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) drivers/gpu/drm/nouveau/nvkm/falcon/msgqueue.c 512 { 513 if (!que...

...result. Alexandre Courbot (15): secboot: allow to boot multiple falcons secboot: pass instance to LS firmware loaders secboot: let LS post_run hooks return error secboot: start LS firmware in post-run hook secboot/gm20b: specify MC base address as argument secboot: add GP10B support msgqueue: support for GP10B PMU firmware fifo: add GP10B support fb: add GP10B support mc: add GP10B support ibus: add GP10B support gr: support for GP10B platform: make VDD regulator optional platform: support for probing GP10B core: recognise GP10B chipset drm/nouveau/include/nvkm/core/m...

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 a/drivers/gpu/drm/nouveau/nvkm/falcon/msgqueue.c b/drivers/gpu/drm/nouveau/nvkm/falcon/msgqueue.c index 77273b53672c..fc0cb187d80d 1...

From: Colin Ian King <colin.king at canonical.com> There are a few statements that are indented incorrectly. Fix these. Signed-off-by: Colin Ian King <colin.king at canonical.com> --- drivers/gpu/drm/nouveau/nvkm/falcon/msgqueue.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/falcon/msgqueue.c b/drivers/gpu/drm/nouveau/nvkm/falcon/msgqueue.c index 771e16a16267..a8bee1e046aa 100644 --- a/drivers/gpu/drm/nouveau/nvkm/falcon/msgqueue.c +++ b/drivers/gpu/drm/nouveau/nvkm...

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, whereas I always get this error when I boot without a monitor attached to the card. On Wed, Sep 13, 2017 at 2:28...

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

...x locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 64053 64053 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us ulimit -n 1024 dovecot --version 2.3.4.1 (f79e8e7e4) protocols =...

...65536 >> bytes >> > Max address space unlimited unlimited >> bytes >> > Max file locks unlimited unlimited >> locks >> > Max pending signals 256389 256389 >> signals >> > Max msgqueue size 819200 819200 >> bytes >> > Max nice priority 0 0 >> > Max realtime priority 0 0 >> > Max realtime timeout unlimited unlimited us >> > >> > &gt...

...x locked memory 65536 262144 bytes Max address space 57559531520 unlimited bytes Max file locks unlimited unlimited locks Max pending signals 516081 516081 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us Tracing the syscall inotify_init() via ftrace is not possible, beca...

...535??????????????? files > Max locked memory???????? 65536 65536??????????????? bytes > Max address space???????? unlimited unlimited??????????? bytes > Max file locks??????????? unlimited unlimited??????????? locks > Max pending signals?????? 64053 64053??????????????? signals > Max msgqueue size???????? 819200 819200?????????????? bytes > Max nice priority???????? 0??????????????????? 0 > Max realtime priority???? 0??????????????????? 0 > Max realtime timeout????? unlimited unlimited??????????? us > > ulimit -n > 1024 > > > dovecot --version > 2.3.4.1 (f7...

...; 4096 files Max locked memory 65536 > 65536 bytes Max address space 268435456 > 268435456 bytes Max file locks unlimited > unlimited locks Max pending signals 257157 > 257157 signals Max msgqueue size 819200 > 819200 bytes Max nice priority 0 > 0 Max realtime priority 0 0 > Max realtime timeout unlimited unlimited > us If it may help, dovecot is running inside an lxc container. I would really appreciate any...

...65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 63065 63065 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us Can some...

Is there a way I can prevent processes from taking up all the ram then swap until the box crashes/freezes? I'm using IEs4Linux and the wineserver seems to start taking up RAM until my box dies, it happens slowly. I am able to kill the sucker now, but I'd like to not have to worry about that. sar -r 01:00:01 PM kbmemfree kbmemused %memused kbbuffers kbcached kbswpfree kbswpused

...4096 files :Max locked memory 65536 65536 bytes :Max address space unlimited unlimited bytes :Max file locks unlimited unlimited locks :Max pending signals 19090 19090 signals :Max msgqueue size 819200 819200 bytes :Max nice priority 0 0 :Max realtime priority 0 0 :Max realtime timeout unlimited unlimited us maps: :001ec000-001f8000 r-xp 0000000...

Hi, perhaps this? > with new debian9: > open files (-n) 1024 Regards Urban Am 16.09.20 um 12:57 schrieb Maciej Milaszewski: > Hi > Limits: > > Where all working fine: > > core file size????????? (blocks, -c) 0 > data seg size?????????? (kbytes, -d) unlimited > scheduling priority???????????? (-e) 0 > file size?????????????? (blocks,

...1024 4096 files :Max locked memory 65536 65536 bytes :Max address space unlimited unlimited bytes :Max file locks unlimited unlimited locks :Max pending signals 579817 579817 signals :Max msgqueue size 819200 819200 bytes :Max nice priority 0 0 :Max realtime priority 0 0 :Max realtime timeout unlimited unlimited us maps: :7ffc17ffd000-7ffc1802f000 r-xp 00000000 fd:05 664017 /usr/lib64/libustr-1.0.so....

...x locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 63735 63735 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us I am still getting 1024 limit The only warning that we get is dovec...

Hi all, I am running Xen 4.1.2 with ubuntu Dom0. I have essentially got 1000 Modified Mini-OS DomU''s running at the same time. When i try and access the 1000th domain console: xm console DOM1000 xenconsole: could not read tty from store: No such file or directory The domain is alive and running according to xentop, and has been for some time. I can successfully access the first 338