<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NV34] [v3.14-rc1] nouveau: get 0x10000000 put 0x0000ed30 state 0xc0000000 (err: MEM_FAULT) push 0x00000000" href="https://bugs.freedesktop.org/show_bug.cgi?id=74613#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NV34] [v3.14-rc1] nouveau: get 0x10000000 put 0x0000ed30 state 0xc0000000 (err: MEM_FAULT) push 0x00000000" href="https://bugs.freedesktop.org/show_bug.cgi?id=74613">bug 74613</a> from <a class="email" href="mailto:ronald645@gmail.com" title="Ronald <ronald645@gmail.com>"> Ronald</a> <pre>@Ilia Mirkin: Ah, yes the next repo seems promising. Thank you. About the 'old' master repo: Say, for example, stable was v3.8 and then this machine would happily use it. Every week I would pull from this master branch the patches for v3.9 based on the v3.8 tree. These patches are localized in the nouveau driver, so I have quick rebuilds and thus quick bisects. Problems are narrowed down easily and most importantly: fast. Using Linux his tree sometimes means doing a lot more bisects since a lot of changes come in at once after two months. Furthermore, it's not just the nouveau driver that changes but the entire tree. So bisecting would imply also doing full rebuilds. However, drm-nouveau-next seems to fill the gap which master left behind. @Emil Velikov: Does not seem like it: [gebruiker@delta linux]$ pacman -Qi libdrm Naam : libdrm Versie : 2.4.52-1 Beschrijving : Userspace interface to kernel DRM services Architectuur : i686 ArchLinux is quick with it's updates. Which is really nice. Ow well, on to the bisect then =)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>