similar to: [Bug 62035] New: [Regression kernel 3.8.0+] G86 GeForce 8400M GS 3D desktop effects does not work

https://bugs.freedesktop.org/show_bug.cgi?id=62835 Priority: medium Bug ID: 62835 Assignee: nouveau at lists.freedesktop.org Summary: Screen freezes after resume from s2ram QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: pontus.fuchs at gmail.com

On Wed, Jan 02, 2013 at 04:19:35PM +0100, Pontus Fuchs wrote: > Hi, > > Starting with 3.8rc1 I get a black screen when resuming after suspend. > The kernel is alive because I can switch to VT1 and reboot with > ctrl-alt-delete. > > I bisected the problem down to this commit: > > 186ecad21: drm/nv50/disp: move remaining interrupt handling into core > >

https://bugs.freedesktop.org/show_bug.cgi?id=59057 Priority: medium Bug ID: 59057 Assignee: nouveau at lists.freedesktop.org Summary: Black screen after resume from s2ram QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: pontus.fuchs at gmail.com

Hi, Using kernel 3.9.4, with openSUSE 12.1 (KDE 4.7.4 I think), I was running fine for a long time with no problems. Today with openSUSE 12.3 (KDE 4.10.3, Xorg 1.13.2, upgraded on Jun. 10), my machine hung completely. I believe the nouveau driver is at fault rather than KDE or X, so chose this list. I think it might have been triggered by the "Clock" ScreenLocker (screen saver). It

Hi! In commit da5e45e619b3f101420c38b3006a9ae4f3ad19b0: > drm/nouveau/mmu: ALIGN_DOWN correct variable > > 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

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]

The vblank on nvc0 was not working correctly and would freeze X, I managed to track it down and fix it with some help from m.b.lankhorst, see https://bugs.freedesktop.org/show_bug.cgi?id=56692 for details. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20121106/27ceb48e/attachment.html> --------------

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

On Wed, Apr 04, 2018 at 03:48:39PM +0300, Māris Nartišs wrote: > 2018-04-03 23:00 GMT+03:00, Adam Borowski <kilobyte at angband.pl>: > > In commit da5e45e619b3f101420c38b3006a9ae4f3ad19b0 > > > > yet it is still reproducible for me on 4.16-rc7 and 4.16.0, which already > > have your fix. I don't know about earlier versions -- my newer card went > > into

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #14 from torsten.stocklossa at gmail.com --- HI again, in addition some error messages Nov 29 11:21:47 torsten-LIFEBOOK-E8410 kernel: [ 66.215782] nouveau E[ PGRAPH][0000:01:00.0] ch 2 [0x0007b23000] subc 7 class 0x8297 mthd 0x15e0 data 0x00000000 Nov 29 11:21:47 torsten-LIFEBOOK-E8410 kernel: [ 66.304180] nouveau E[

https://bugs.freedesktop.org/show_bug.cgi?id=91373 Bug ID: 91373 Summary: Nouveau fills kern.log with gigabytes of data when molecule screensaver is ran Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium

Hello, I would like to report that WineASIO 0.7.4 compiles and runs well under 64studio on my Dell XPS m1330. I use it to run Pianoteq. On my integrated Intel HDA 2.0 card: If I don't have jack tweaked just right, it will degenerate into "pops and clicks" but seems stable if jack is given a little more "headroom" (higher latency) to work with. However, it completely

https://bugs.freedesktop.org/show_bug.cgi?id=56446 Priority: medium Bug ID: 56446 Assignee: nouveau at lists.freedesktop.org Summary: BUG: unable to handle kernel paging request at ffffc90014e00000 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All)

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- I made the assumption that showing the address is generally useful. Worst case, it won't make sense but still be displayed. Seems simpler than special-casing things. drivers/gpu/drm/nouveau/core/engine/graph/nv50.c | 117 ++++++++++++----------- 1 file changed, 63 insertions(+), 54 deletions(-) diff --git

Hi, while doing work, my luks encrypted btrfs home got a nice stacktrace i run a Debian testing and a kernel 3.4 vanilla % uname -a Linux Klappe2 3.4.0 #2 SMP Thu Jun 14 03:02:37 CEST 2012 x86_64 GNU/Linux the box is a dell xps m 1330 with about 4gb ram % btrfs fi show Label: ''home'' uuid: 9c1a77c9-3767-43aa-908d-0bae1ef4e534 Total devices 1 FS bytes used 198.25GB devid

Hi, there! Every once in a while / about once a day I have nouveau for a Quadro NVS 290 failing in my system from about kernel 3.10...up to now 3.14, so I finally decided to report this bug as it gets really annoying. After the bug appears, there are some (one per DATA_ERROR line) small 20x20 to 40x40 pixel sized odd shaped white block artefacts stuck on my (dual monitor) desktop. After a restart

https://bugs.freedesktop.org/show_bug.cgi?id=57837 Priority: medium Bug ID: 57837 Assignee: nouveau at lists.freedesktop.org Summary: nouveau invalid opcode for NVIDIA QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: yetist at gmail.com Hardware:

http://bugs.freedesktop.org/show_bug.cgi?id=23972 Summary: Nouveau KMS - kernel crash when loading drm on G86 [GeForce 8400M GS] Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: major Priority: high Component: Driver/nouveau

Thanks for the work so far. A quick scan through the first NVC4 trace at hand, using upstream demmio, reveals at least 20 writes to the BLCG registers of PGRAPH and a few in PXBAR prior to altering the value of register 0x20200 (see below). We know that these are related to the clock gating you enable. Are you 110% sure that fiddling with 0x20200 bits without first setting these values can