similar to: [Bug 99968] New: [NV4C] System crashes reliably with glxinfo

https://bugs.freedesktop.org/show_bug.cgi?id=91992 Bug ID: 91992 Summary: [NV4C] computer hangs after few minutes of use Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/nouveau

Several users have, over time, reported issues with MSI on these IGPs. They're old, rarely available, and MSI doesn't provide such huge advantages on them. Just disable. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=87361 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=74492 Fixes: fa8c9ac72fe ("drm/nv4c/mc: nv4x igp's have a different msi rearm register")

See https://bugs.freedesktop.org/show_bug.cgi?id=74492 Reported-by: Ronald <ronald645 at gmail.com> Suggested-by: Marcin Ko?cielnicki <koriakin at 0x04.net> Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- drivers/gpu/drm/nouveau/Makefile | 1 + drivers/gpu/drm/nouveau/core/engine/device/nv40.c | 10 ++---

MSI interrupts appear to not work for nv46 based cards. Change the mc subdev oclass for these cards from nv44 to nv4c, the nv4c mc code is identical to the nv44 mc code except that it does not use msi (it does not define a msi_rearm callback). BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=90435 Signed-off-by: Hans de Goede <hdegoede at redhat.com> ---

https://bugs.freedesktop.org/show_bug.cgi?id=87361 Bug ID: 87361 Summary: [NV4C] Kernel lock-up after booting to desktop in Fedora 20 & 21 (Nvidia Geforce 6100 IGP) Product: Mesa Version: 10.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker

https://bugs.freedesktop.org/show_bug.cgi?id=33668 Summary: [regression] [nv4c] Screen corruption Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Hi, On 24-07-15 04:32, Ben Skeggs wrote: > On 24 July 2015 at 01:20, Hans de Goede <hdegoede at redhat.com> wrote: >> MSI interrupts appear to not work for nv46 based cards. Change the mc >> subdev oclass for these cards from nv44 to nv4c, the nv4c mc code is >> identical to the nv44 mc code except that it does not use msi >> (it does not define a msi_rearm

https://bugs.freedesktop.org/show_bug.cgi?id=61321 Priority: medium Bug ID: 61321 Keywords: regression Assignee: nouveau at lists.freedesktop.org Summary: [regression][NV4c] System hang while loading gdm on 3.7 kernel (works on 3.6) QA Contact: xorg-team at lists.x.org Severity: major Classification:

Hi folks, I''m having trouble getting gems to install rails. It just keeps asking me which version of thin I want to install. Until I choose skip or cancel, in which case I''m told that something has gone wrong. Any advice? Thanks kindly, Tommy PS: Gems is 0.94. --------------------------------------------------------------------- tommy@tommy-laptop:~/www/blog$ sudo gem

Hi, I need to know what the implications are to make use of the hosts.allow file on a FreeBSD Production Server (ISP Setup)? The reason I'm asking, is that I've recently decommisioned a Linux SendMail Server to a FreeBSD Exim Server, but with no Firewall (IPTABLES) yet. Besides the fact that it only runs EXIM and Apache, is it necessary to Configure rc.Firewall? or can I only make use of

Dear Centos Users We are running centos on our HPC. Indeed, we have a problem with running some software using X11 server such as pymol. For your information, we are using cygwin to access to the hpc (using ssh -X -Y username at xxx.xxx.xxx.xxx) When we are testing glxinfo on my desktop, it gives us the following error: [username at hpc ~]# glxinfo name of display: localhost:10.0 X Error of

http://bugs.freedesktop.org/show_bug.cgi?id=11038 Summary: nouveau and NV17: glxinfo, glxgears and other gl-apps crash Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo:

https://bugs.freedesktop.org/show_bug.cgi?id=28570 Francisco Jerez <currojerez at riseup.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Component|Server/general

Hi, Just to say that this report may well seem a little sparse, but I really don't know what exactly to look for so if anybody needs extra information just shout and I will get it for you ASAP. When I check the X.org log file, it says direct rendering: enabled on my graphics device (it attaches its i810 driver to the kernel's i915 DRM device). This would appear to me to suggest that

https://bugs.freedesktop.org/show_bug.cgi?id=71172 Priority: medium Bug ID: 71172 Assignee: nouveau at lists.freedesktop.org Summary: Segfault when running glxinfo. NV25GL [Quadro4 900 XGL] Severity: normal Classification: Unclassified OS: All Reporter: simon at mungewell.org Hardware:

On Tue, Jan 19, 2016 at 5:22 AM, Jiri Slaby <jslaby at suse.cz> wrote: > Hi, > > On 01/17/2016, 08:28 PM, Ilia Mirkin wrote: >> I'd like to recommend backporting this commit: >> >> commit 0a363e85cdafbceeee6a49b91c604d0d4d070dc7 >> Author: Hans de Goede <hdegoede at redhat.com> >> Date: Thu Jul 23 17:20:12 2015 +0200 >> >>

https://bugs.freedesktop.org/show_bug.cgi?id=70212 Priority: medium Bug ID: 70212 Assignee: nouveau at lists.freedesktop.org Summary: glxinfo triggers assert in cso_release_all after 3f0627c2ad6 Severity: normal Classification: Unclassified OS: All Reporter: awatry at gmail.com

Hi, On 01/17/2016, 08:28 PM, Ilia Mirkin wrote: > I'd like to recommend backporting this commit: > > commit 0a363e85cdafbceeee6a49b91c604d0d4d070dc7 > Author: Hans de Goede <hdegoede at redhat.com> > Date: Thu Jul 23 17:20:12 2015 +0200 > > drm/nouveau/nv46: Change mc subdev oclass from nv44 to nv4c > > This disables MSI by default on G72 (NV46)

First, I hope that this message is not considered flame bait. As someone who has used FreeBSD for for 5+ years now, I have a genuine interest in the integrity of our source code. Second, I hope that this message is not taken as any form of insult or finger pointing. Software without bugs does not exist, and I think we all know that. Acknowledging that point and working to mitigate the risks

I've had ipf working on a few 5.3 servers for quite awhile. Not too long ago some developers had to do some coding work and were coming from dynamic IP's. I (reluctantly) opened up SSH to the world. Immediately I started seeing the attacks where bots of some sort would try to break in with a variety of different users. So, I (thought) I closed it up again and told the developers to use a