<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Kernel Oops when starting X nv50_dma_push" href="https://bugs.freedesktop.org/show_bug.cgi?id=100758#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Kernel Oops when starting X nv50_dma_push" href="https://bugs.freedesktop.org/show_bug.cgi?id=100758">bug 100758</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to Kevin Winchester from <a href="show_bug.cgi?id=100758#c5">comment #5</a>) > After this crash, I rebooted and I'm currently running sway on wayland and > things seem to work well, but I've been having trouble with X for weeks now. > > I first noticed issues when the following messages started appearing in my > boot logs: > > nouveau 0000:01:00.0: bios: OOB 1 015f1901 015f1901 > nouveau 0000:01:00.0: bios: OOB 1 b90900b8 b90900b8 > nouveau 0000:01:00.0: bios: OOB 1 b90900b8 b90900b8 > nouveau 0000:01:00.0: bios: OOB 1 b90900b8 b90900b8 Those are "normal". By which I mean harmless. Should go away in some updated kernel. > > I have a dual monitor setup and I was always running with no specific > xorg.config files, just the following in my .xinitrc file: > > xrandr --output LVDS-1 --preferred > xrandr --output HDMI-1 --preferred --primary --left-of LVDS-1 > > But suddenly after some updates, that was resulting in the same content > being displayed on both screens, but I can still move my mouse cursor over > onto the second screen. > > I put in the xorg.conf file that I used to use (already pasted in) and it > seemed to improve the situation, but there were still issues. The same > content would still appear on both screens, but once I let the xfce power > management shut off the monitors and then woke the computer back up, the > screens would work correctly again. > > Then this I installed a new kernel and nouveau driver, and after starting X > everything froze and I found the Oops in my logs. Looks like your crash happened with 4.10.11. 4.10.12 includes a backport of a very important fix, <a href="https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=2efa4bd3b644f115befbd225f45fce936e19cf2c">https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=2efa4bd3b644f115befbd225f45fce936e19cf2c</a> , which I believe accounts for the crash that you saw.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>