similar to: nouveau: refcount_t splat on 4.15-rc1 on nv50

I think you want kernel 4.10, or cherry-pick upstream commit 7dfee6827780d4228148263545af936d0cae8930. On Sun, Mar 12, 2017 at 11:27 AM, Marcelo Ribeiro <mbribeiro at gmail.com> wrote: > Hi, I am changing from proprietary nvidia drivers to Nouveau drivers in my > mediacenter. > > I run a Gentoo linux in this hardware and I am facing an out of signal > screen just after the

Hi, I am changing from proprietary nvidia drivers to Nouveau drivers in my mediacenter. I run a Gentoo linux in this hardware and I am facing an out of signal screen just after the boot (when the nouveau module is loaded). If I blacklist this module and modprobe it in the prompt, the screen gets out of signal in my 1080p TV in this moment. I tried recompile the kernel enabling and disabling a

Hi guys! I'm getting the following warn on 4.15-rc1, on GTX 560 Ti: [ 9.430433] nouveau 0000:01:00.0: NVIDIA GF114 (0ce000a1) ... [ 9.585172] nouveau 0000:01:00.0: bios: version 70.24.2e.00.02 ... [ 9.772204] nouveau 0000:01:00.0: fb: 1024 MiB GDDR5 [ 9.777342] ------------[ cut here ]------------ [ 9.782106] refcount_t: increment on 0; use-after-free. [ 9.787522] WARNING:

Hi, I have an Optimus-enabled laptop with a GTX 1060m. I never got it to fully work with Nouveau even after Pascal support was added. I need to run the kernel with nouveau.runpm=0 to get it to work. Unfortunately without proper power mangement support, my laptop will run out of battery after about 1h30, so I'd love to get Optimus working. What I can see is that when the extra GPU is not in

Hi all, I'm getting frequent system crashes (every few hours or so) and it seems that the nouveau driver is causing the issue (dmesg output below). I see it with both v5.2.8 and the v4.19 LTS kernel. Sometimes the system completely freezes and sometimes seemingly just the nouveau driver goes down. The screen freezes and colours stream across it. Often after I reboot the BIOS logo is mangled

On Fri, Jun 13, 2014 at 7:58 PM, Thomas Glanzmann <thomas at glanzmann.de> wrote: > Hello Ben, > commit Hey Thomas, Are you able to double-check that bisect? I'm not at all sure how that particular commit could trigger the issue you're seeing. Some of the others, certainly. It might be worth trying a couple of times before marking something as "good", in case

Hello Ben, commit (mini) [~/work/linux-2.6] git bisect bad 8777c5c11764d8336d8270f96778158c34c92108 is the first bad commit commit 8777c5c11764d8336d8270f96778158c34c92108 Author: Ben Skeggs <bskeggs at redhat.com> Date: Fri Jun 6 18:09:55 2014 +1000 drm/nouveau/dp: probe dpcd to determine connectedness Signed-off-by: Ben Skeggs <bskeggs at redhat.com> introduces a

https://bugs.freedesktop.org/show_bug.cgi?id=104161 Bug ID: 104161 Summary: refcount_t: increment on 0; use-after-free. Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau

we can't use nouveau_bo_ref here as no ttm object was allocated and nouveau_bo_ref mainly deals with that. Simply deallocate the object. Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nouveau_gem.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drm/nouveau/nouveau_gem.c b/drm/nouveau/nouveau_gem.c index e11303fbc..45582a8dc 100644 ---

From: Karol Herbst <kherbst at redhat.com> [ Upstream commit 925681454d7b557d404b5d28ef4469fac1b2e105 ] we can't use nouveau_bo_ref here as no ttm object was allocated and nouveau_bo_ref mainly deals with that. Simply deallocate the object. Signed-off-by: Karol Herbst <kherbst at redhat.com> Signed-off-by: Ben Skeggs <bskeggs at redhat.com> Signed-off-by: Sasha Levin

From: Karol Herbst <kherbst at redhat.com> [ Upstream commit 925681454d7b557d404b5d28ef4469fac1b2e105 ] we can't use nouveau_bo_ref here as no ttm object was allocated and nouveau_bo_ref mainly deals with that. Simply deallocate the object. Signed-off-by: Karol Herbst <kherbst at redhat.com> Signed-off-by: Ben Skeggs <bskeggs at redhat.com> Signed-off-by: Sasha Levin

From: Karol Herbst <kherbst at redhat.com> [ Upstream commit 925681454d7b557d404b5d28ef4469fac1b2e105 ] we can't use nouveau_bo_ref here as no ttm object was allocated and nouveau_bo_ref mainly deals with that. Simply deallocate the object. Signed-off-by: Karol Herbst <kherbst at redhat.com> Signed-off-by: Ben Skeggs <bskeggs at redhat.com> Signed-off-by: Sasha Levin

Hello, [ 4.762826] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 5.025098] udevd[441]: starting version 175 [ 5.134411] i2c i2c-0: nForce2 SMBus adapter at 0x2140 [ 5.134585] i2c i2c-1: nForce2 SMBus adapter at 0x2100 [ 5.137320] ACPI: bus type USB registered [ 5.137444] usbcore: registered new interface driver usbfs [ 5.137535] usbcore: registered

Am 25.12.2015 um 18:43 schrieb Pierre Moreau: > Hello, > > Maybe my e-mail client is messing with me, but I couldn't find any dmesg output > attached to your e-mail. Could you please try to attach it again? > > By the way, since you have a Kepler, you should try booting with > "nouveau.War00C800_0=1". That workaround is enabled by default in 4.4-rc5 > (IIRC),

Hey, This patch causes a regression on my display-less nvd7. Commenting out the aux, aux_stat and aux_mask members in nvd0_i2c_oclass fixes boot, and makes things work normally again. broken dmesg: [ 40.314470] ACPI Warning: \_SB_.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 40.314729] ACPI Warning: \_SB_.PCI0.GFX0._DSM:

https://bugs.freedesktop.org/show_bug.cgi?id=105173 Pierre Moreau <pierre.morrow at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|With kernel >=4.15 nouveau |[MCP79][Regression] |- artefacts and freezes |Unhandled NULL pointer

https://bugs.freedesktop.org/show_bug.cgi?id=105173 --- Comment #12 from Nick Lee <nvlbox at gmail.com> --- > The NULL pointer dereference, or the “trapped read at 0080000000 on channel 1 > [0fbb0000 DRM] engine 00 [PGRAPH] client 03 [DISPATCH] subclient 04 [M2M_IN] > reason 00000006 [NULL_DMAOBJ]” one? "NULL pointer dereference" AND "trapped read" after

https://bugs.freedesktop.org/show_bug.cgi?id=83271 Priority: medium Bug ID: 83271 Assignee: nouveau at lists.freedesktop.org Summary: Windowed mode causes framebuffer not to refresh with PRIME on optimus/kepler discrete GPU QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified

I built a v4.11-rc1 kernel, and booted it in a KVM guest and got this oops during startup. My config is attached: [ 2.386786] virtio-pci 0000:00:07.0: virtio_pci: leaving for legacy driver [ 2.395650] BUG: unable to handle kernel paging request at ffff97a3ec5f4000 [ 2.396005] IP: string+0x43/0x80 [ 2.396005] PGD 2d25b067 [ 2.396005] PUD 2d25f067 [ 2.396005] PMD 12c696063 [

I built a v4.11-rc1 kernel, and booted it in a KVM guest and got this oops during startup. My config is attached: [ 2.386786] virtio-pci 0000:00:07.0: virtio_pci: leaving for legacy driver [ 2.395650] BUG: unable to handle kernel paging request at ffff97a3ec5f4000 [ 2.396005] IP: string+0x43/0x80 [ 2.396005] PGD 2d25b067 [ 2.396005] PUD 2d25f067 [ 2.396005] PMD 12c696063 [