similar to: [Bug 107069] New: trace in kernel.log on boot

The warning you included happens when we're trying to execute a VBIOS script as part of DP training. Can you include your vbios? It should be available at /sys/kernel/debug/dri/0/vbios.rom Also, can you confirm how your monitors are connected to the card (and e.g. what resolution they are, anything else "funny" about them)? Finally, this warning might not have anything to do with

I have a Nvidia NVS310 installed in my Linux computer for a few years. It works well with the Nvidia driver, and not so well with the Linux nouveau driver. The Nvidia NVS310 has never worked well with Linux. In the beginning (many years ago) I decided to install Nvidia proprietary drivers, but every kernel upgrade would require an additional effort to have the driver working. That was enough

I have two monitors connected to the PC. One is an AOC 23" (1920 x 1080) and the other is a BenQ 27" (2560 x 1440). Nothing special about them. BenQ has a display port and the AOC uses some sort of DVI adapter. I have this event many times and I captured dmesg twice. At least at one time I captured dmesg my computer was under high load: it had about 15 to 20 windows opened

Using the ARRAY_SIZE macro improves the readability of the code. Also, it is useless to re-invent it. Found with Coccinelle with the following semantic patch: @r depends on (org || report)@ type T; T[] E; position p; @@ ( (sizeof(E)@p /sizeof(*E)) | (sizeof(E)@p /sizeof(E[...])) | (sizeof(E)@p /sizeof(T)) ) Reviewed-by: Thierry Reding <treding at nvidia.com> Signed-off-by: Jérémy

Dear list, I have a question concerning the above mentioned methods in the pls package with respect to the loadings matrix produced by the call. In some work I am doing I have found that the values produced are nearly of the same magnitude but of opposite sign. When I use the example data (sensory) I find this result reproduced. I am prepared to work this through but I have a feeling that

Fixes broken dp on GF119: Call Trace: ? nvkm_dp_train_drive+0x183/0x2c0 [nouveau] nvkm_dp_acquire+0x4f3/0xcd0 [nouveau] nv50_disp_super_2_2+0x5d/0x470 [nouveau] ? nvkm_devinit_pll_set+0xf/0x20 [nouveau] gf119_disp_super+0x19c/0x2f0 [nouveau] process_one_work+0x193/0x3c0 worker_thread+0x35/0x3b0 kthread+0x125/0x140 ? process_one_work+0x3c0/0x3c0 ?

Using the ARRAY_SIZE macro improves the readability of the code. Also, it is not always useful to use a variable to store this constant calculated at compile time nor to re-invent the ARRAY_SIZE macro. Found with Coccinelle with the following semantic patch: @r depends on (org || report)@ type T; T[] E; position p; @@ ( (sizeof(E)@p /sizeof(*E)) | (sizeof(E)@p /sizeof(E[...])) | (sizeof(E)@p

https://bugs.freedesktop.org/show_bug.cgi?id=105977 Bug ID: 105977 Summary: Samsung screen replacement in a Dell laptop brings corrupted display Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium

Use ARRAY_SIZE macro, rather than explicitly coding some variant of it yourself. Found with: find -type f -name "*.c" -o -name "*.h" | xargs perl -p -i -e 's/\bsizeof\s*\(\s*(\w+)\s*\)\s*\ /\s*sizeof\s*\(\s*\1\s*\[\s*0\s*\]\s*\) /ARRAY_SIZE(\1)/g' and manual check/verification. Signed-off-by: Thomas Meyer <thomas at m3y3r.de> --- diff --git

In the interests of full disclosure, here's the glossy press release (with html as well ! :-). Jeremy. --------------------------------------------------------------------- Samba 2.2.0 - Powering the next generation of Network Attached -------------------------------------------------------------- Storage. -------- 17

Hi, We recently purchased some HP Gen8 servers with Broadcom BCM57810 NIC controllers. I am running CentOS 6.2 on these servers configured as KVM hosts. Has anyone gotten the Broadcom chips to run with SR-IOV on CentOS 6.2? Any clues on how to get it working? I see from the Broadcom glossy marketing docs that this chip supports SR-IOV, but I cannot find a procedure for configuring it. The

Hello! :) Explanation of the problem: For several years now it is impossible to render "shiny" (glossy, vertex shaders), effects on ships, planets and generally metallic surfaces in Haegemonia. The problem is that newer graphics drivers on Windows systems changed/lack a feature the game exploited to get these effects. Way back when I was mailing the developers of the game, I was told

hi guys.. i got a little problem - i installed photoshop cs4 in wine, and it works fine - except for the UI font. seems like it didn't install. i checked in the windows/fonts folder, and there's nothing in it. take a look: [Image: http://img32.picoodle.com/img/img32/3/2/24/t_pscs4m_930ebff.png ] (http://www.picoodle.com/view.php?img=/3/2/24/f_pscs4m_930ebff.png&srv=img32) of course

It is interesting how things have changed -- 5 weeks later, I review materials collected at the JSM, and notice that Springer-Verlag's glossy statistics catalog has 3 of 9 books on the front page directly or indirectly related to R (Peter D's intro book, MASS, and Parmigiani et.al's book with a number of Bioconductor-related chapters). (one could argue that 8 of 9 could use it -- it

On 7/11/2017 3:58 PM, Fred Smith wrote: > I faced the same issue some years ago, and found a low-priced mono > laser that lated me quite a few years. no color, but few thing I > wanted to print actually demanded color. my last two laser printers have been Brother black&white all-in-ones ("MFC"). *VERY* cheap per page printing costs, even if you use Brother brand toner

https://bugs.freedesktop.org/show_bug.cgi?id=72943 Priority: medium Bug ID: 72943 Assignee: nouveau at lists.freedesktop.org Summary: NV98 [GeForce 9300 gs m] hangs on boot- all linux kernel versions > 3.2 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS:

Il 15/06/2015 12:41, Daniel Helgenberger ha scritto: > Hello Sandro, > > frist thanks for the great news! > > On 15.06.2015 10:28, Sandro Bonazzola wrote: >> Hi, >> today oVirt 3.5.3 has been released[1] >> VDSM 4.16.20 and its dependencies has been tagged as release as well within the Virt SIG build repositories for CentOS Linux 7. >> In order to enable

On 21.03.19 18:12, Jerome Glisse wrote: > On Thu, Mar 21, 2019 at 04:59:14PM +0100, Tobias Klausmann wrote: >> Hi, >> >> just for your information and maybe for some help: with 5.1rc1 and SVM >> enabled i see the following backtrace [1] when the nouveau card (reverse >> prime) goes to sleep, for now i have papered over with [2] which leaves me >> with

Hello, 5.1.0-next-20190517 I'm looking at quite a lot of kmemleak reports coming from drm/nouveau/core/memory, all of which are: unreferenced object 0xffff8deec27c4ac0 (size 16): comm "Web Content", pid 5309, jiffies 4309675011 (age 68.076s) hex dump (first 16 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace:

Hi Halil, When swiotlb full is hit for virtio_blk, there is below warning for once (the warning is not by this patch set). Is this expected or just false positive? [ 54.767257] virtio-pci 0000:00:04.0: swiotlb buffer is full (sz: 16 bytes), total 32768 (slots), used 258 (slots) [ 54.767260] virtio-pci 0000:00:04.0: overflow 0x0000000075770110+16 of DMA mask ffffffffffffffff bus limit 0 [