similar to: [Bug 74695] [NV86] GPU hangs on resume, causing X to crash

https://bugs.freedesktop.org/show_bug.cgi?id=74695 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|nouveau_exa_download_from_s |[NV86] GPU hangs on resume, |creen:299 leads to NULL |causing X to crash

https://bugs.freedesktop.org/show_bug.cgi?id=74695 --- Comment #3 from Carla sella <carla.sella at gmail.com> --- I am attaching dmesg after reboot. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=74695 --- Comment #4 from Carla sella <carla.sella at gmail.com> --- Created attachment 93634 --> https://bugs.freedesktop.org/attachment.cgi?id=93634&action=edit dmesg after reboot -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=74695 --- Comment #5 from Carla sella <carla.sella at gmail.com> --- I will also test this out with a fresh kernel and let you know. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=74695 --- Comment #7 from Carla sella <carla.sella at gmail.com> --- I started having Xorg server crashes from kernel 3.8.0-35 on wards. Up to kernel 3.7.10 I had ho crashes after suspension (that is until Ubuntu Quantal Quetzal no crashes, from Ubuntu Raring Ringtail I stared having crashes). Carla -- You are receiving this mail because: You

https://bugs.freedesktop.org/show_bug.cgi?id=74695 --- Comment #8 from Carla sella <carla.sella at gmail.com> --- This is the link with Ubuntu mainline kernels: http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D. I starded having crashes from v3.8-raring. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML

https://bugs.freedesktop.org/show_bug.cgi?id=74695 --- Comment #9 from Ilia Mirkin <imirkin at alum.mit.edu> --- Would you be able to do a bisect between 3.7 and 3.8? Another user identified commit 4f6029da58ba (in bug #67878) which came in between 3.7 and 3.8 -- perhaps you have the same issue? It's a different card, so might be different... a bunch of stuff changed between 3.7 and

https://bugs.freedesktop.org/show_bug.cgi?id=74695 --- Comment #10 from Carla sella <carla.sella at gmail.com> --- (In reply to comment #9) > Would you be able to do a bisect between 3.7 and 3.8? To be honest I never did a kernel bisect, but I can try. I will try and let you know. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part

https://bugs.freedesktop.org/show_bug.cgi?id=74695 --- Comment #11 from Carla sella <carla.sella at gmail.com> --- I started with compiling kernel v.3.8 19f949f from git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git. When I boot my PC with kernel 3.8 lightdm doesn't even start and I get a black screen, I am attaching dmesg from booting on kernel 3.8. After re-booting on

https://bugs.freedesktop.org/show_bug.cgi?id=74695 --- Comment #12 from Carla sella <carla.sella at gmail.com> --- Created attachment 93952 --> https://bugs.freedesktop.org/attachment.cgi?id=93952&action=edit dmesg from kernel 3.8 dmesg output after booting my PC with kernel v.3.8. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part

https://bugs.freedesktop.org/show_bug.cgi?id=74695 --- Comment #13 from Carla sella <carla.sella at gmail.com> --- I will continue testing previous kernels to v. 3.8. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=74695 --- Comment #14 from Carla sella <carla.sella at gmail.com> --- I started bisecting kernel from 3.7 to 3.8 this is the bisect log output: letozaf at letozaf-PC:~/Documents/linux$ git bisect log git bisect start # good: [29594404d7fe73cd80eaa4ee8c43dcc53970c60e] Linux 3.7 git bisect good 29594404d7fe73cd80eaa4ee8c43dcc53970c60e # bad:

https://bugs.freedesktop.org/show_bug.cgi?id=74695 Martin Peres <martin.peres at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED --- Comment #15 from Martin Peres

https://bugs.freedesktop.org/show_bug.cgi?id=105173 --- Comment #11 from Nick Lee <nvlbox at gmail.com> --- (In reply to Pierre Moreau from comment #10) > What exactly is reproducible? The artefacts I would assume, but which error > exactly? The NULL pointer dereference, or the “trapped read at 0080000000 on > channel 1 [0fbb0000 DRM] engine 00 [PGRAPH] client 03 [DISPATCH]

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

Commit 7110c89bb8852ff8b0f88ce05b332b3fe22bd11e ("mmu: swap out round for ALIGN") replaced two calls to round/rounddown with ALIGN/ALIGN_DOWN, but erroneously applied ALIGN_DOWN to a different variable (addr) and left intended variable (tail) not rounded/ALIGNed. As a result screen corruption, X lockups are observable. An example of kernel log of affected system with NV98 card where it

https://bugs.freedesktop.org/show_bug.cgi?id=105173 --- Comment #10 from Pierre Moreau <pierre.morrow at free.fr> --- (In reply to Nick Lee from comment #8) > Also tried: > > Vanilla kernel 4.15.4-300.vanilla.knurd.1.fc27.x86_64 > mesa-17.3.5 > wayland session > reproducible What exactly is reproducible? The artefacts I would assume, but which error exactly? The NULL

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #44 from Ilia Mirkin <imirkin at alum.mit.edu> --- Try commenting the same line out and see what happens... (i.e. the one with 0x74c1) FWIW I do remember seeing some PCRYPT-related (and PVP/PBSP-related) errors on start in the form of MMIO write failures in your log and thinking it odd: nouveau E[ PBUS][0000:01:00.0] MMIO

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #69 from Andreas Loew <awl1 at gmx.net> --- > Could you provide the output of > > nvapeek 154c > nvapeek 1540 > > Those registers specify which engines are there. I think we're ignoring them > in nouveau... OK - that might indeed explain the issues seen... Here you are: [aloew at aloew-lap nva]$ sudo

https://bugs.freedesktop.org/show_bug.cgi?id=62035 Priority: medium Bug ID: 62035 Assignee: nouveau at lists.freedesktop.org Summary: [Regression kernel 3.8.0+] G86 GeForce 8400M GS 3D desktop effects does not work QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified