similar to: [Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot

https://bugs.freedesktop.org/show_bug.cgi?id=101368 --- Comment #8 from Ben Skeggs <skeggsb at gmail.com> --- I investigated an issue a while back that I believe is likely the same as what you're experiencing. I'm, unfortunately, not able to reproduce properly (long story) on any hardware I own. I've identified a few issues that could result in what you're seeing, however,

https://bugs.freedesktop.org/show_bug.cgi?id=101368 --- Comment #9 from wilrikerDE+freedesktop at gmail.com --- I have the same issue on an Asus PL80Jt which has the same Nvidia Chip built in. Using modprobe.blacklist=nouveau let's me but just fine (except that PRIME won't be enabled and the card will not be disabled by vgaswitcheroo). Otherwise I experience what has been described here.

https://bugs.freedesktop.org/show_bug.cgi?id=101368 --- Comment #10 from Ben Steel <bhs_suse at precisionforesight.com> --- Thank you Mr. Coenen. I agree. Kernel 4.12.0-rc6 does not exhibit the problem on a Lenovo T510 either. Between a fix already in the pipeline and a modeset workaround in the meantime, I'm happy. Does anyone still need the bisection completed? -- You are receiving

https://bugs.freedesktop.org/show_bug.cgi?id=101368 Ben Steel <bhs_suse at precisionforesight.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED -- You are receiving this mail

https://bugs.freedesktop.org/show_bug.cgi?id=101368 --- Comment #11 from Ben Skeggs <skeggsb at gmail.com> --- (In reply to Ben Steel from comment #10) > Thank you Mr. Coenen. I agree. Kernel 4.12.0-rc6 does not exhibit the > problem on a Lenovo T510 either. > Between a fix already in the pipeline and a modeset workaround in the > meantime, I'm happy. Does anyone still need

https://bugs.freedesktop.org/show_bug.cgi?id=101368 --- Comment #12 from Ben Steel <bhs_suse at precisionforesight.com> --- Yikes. I only waited about 28 hours before completely restoring that machine from backup and putting it back in service. Food for thought: my greatest fear is that the problem may have been illuminated by the change to GCC 7, which doesn't like compiling 4.10

https://bugs.freedesktop.org/show_bug.cgi?id=101368 Daniel Otero <otero.o.daniel at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=101587 --

https://bugs.freedesktop.org/show_bug.cgi?id=96656 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|mesa-dev at lists.freedesktop. |nouveau at lists.freedesktop.o |org |rg QA

https://bugs.freedesktop.org/show_bug.cgi?id=77102 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|mesa-dev at lists.freedesktop. |nouveau at lists.freedesktop.o |org |rg Component|Other

https://bugs.freedesktop.org/show_bug.cgi?id=92971 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|DRM/other |Drivers/DRI/nouveau Version|XOrg git |unspecified Assignee|dri-devel at

https://bugs.freedesktop.org/show_bug.cgi?id=94627 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |Drivers/DRI/nouveau Assignee|mesa-dev at lists.freedesktop. |nouveau at lists.freedesktop.o

https://bugs.freedesktop.org/show_bug.cgi?id=99889 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Product|DRI |xorg QA Contact| |xorg-team at lists.x.org Assignee|dri-devel at

https://bugs.freedesktop.org/show_bug.cgi?id=99499 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|DRM/other |Driver/nouveau Product|DRI |xorg QA Contact|

https://bugs.freedesktop.org/show_bug.cgi?id=107729 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Product|DRI |xorg Version|XOrg git |unspecified Assignee|dri-devel at

Ilia Mirkin <imirkin at alum.mit.edu> writes: > mesa_texstore expects pixel data, not compressed data. For compressed > textures, we want to just copy the bits in without any conversion. > Any reason we cannot use _mesa_store_compressed_*image for this instead of rolling our own? > Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> > --- >

On Thu, Aug 22, 2013 at 10:10 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > The code expects non-VRAM mem nodes to have a pages list. If that's not > set, it will do a null deref down the line. Warn on that condition and > return an error. > > See https://bugs.freedesktop.org/show_bug.cgi?id=64774 > > Reported-by: Pasi K?rkk?inen <pasik at iki.fi> >

Ilia Mirkin <imirkin at alum.mit.edu> writes: > Fixes assertions when trying to attach textures to fbs with formats not > supported by the render engines. > > See https://bugs.freedesktop.org/show_bug.cgi?id=73459 > > Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> > --- Hi Ilia, > > In a perfect world I'd have separate callbacks for depth and

On Sun, Sep 14, 2014 at 3:37 AM, Francisco Jerez <currojerez at riseup.net> wrote: > Ilia Mirkin <imirkin at alum.mit.edu> writes: > >> mesa_texstore expects pixel data, not compressed data. For compressed >> textures, we want to just copy the bits in without any conversion. >> > > Any reason we cannot use _mesa_store_compressed_*image for this instead

On Mon, Feb 10, 2014 at 10:12 AM, Rafa? Mi?ecki <zajec5 at gmail.com> wrote: > 2014-02-09 23:12 GMT+01:00 Ilia Mirkin <imirkin at alum.mit.edu>: >> On Sun, Feb 9, 2014 at 5:08 PM, Rafa? Mi?ecki <zajec5 at gmail.com> wrote: >>> Last week I've switched from my old & good 3.4.63 to 3.14-rc1 and >>> noticed nasty display corruptions when using

On Mon, Oct 31, 2016 at 1:34 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > Hi Alex, > > As you're well-aware, your commit > 8539b37acef73949861a16808b60cb8b5b9b3bab (drm/nouveau/gr: use > NVIDIA-provided external firmwares) broke tons of existing setups for > people who were using extracted firmware files (stored in the > "nouveau" firmware directory)