search for: nvmsi

...d 3.13.0-rc6 is up and > running. > > If necessary I can go back to the GT 560 Ti to gather dmesg and Xorg log > information. Having a dmesg would be nice. One thing I can think of off-hand is that 3.13-rc has MSI turned on by default. You can turn it off by adding "nouveau.config=NvMSI=0" to your kernel cmdline. If that doesn't help, a bisect restricted to drivers/gpu/drm/nouveau should show the offending commit fairly quickly. -ilia

...; running. >> >> If necessary I can go back to the GT 560 Ti to gather dmesg and Xorg log >> information. > Having a dmesg would be nice. One thing I can think of off-hand is > that 3.13-rc has MSI turned on by default. You can turn it off by > adding "nouveau.config=NvMSI=0" to your kernel cmdline. If that > doesn't help, a bisect restricted to drivers/gpu/drm/nouveau should > show the offending commit fairly quickly. > > -ilia > Adding "nouveau.config=NvMSI=0" to the command line fixed the problem. So it looks like commit 049ffa...

...necessary I can go back to the GT 560 Ti to gather dmesg and Xorg log >>>> information. >>> Having a dmesg would be nice. One thing I can think of off-hand is >>> that 3.13-rc has MSI turned on by default. You can turn it off by >>> adding "nouveau.config=NvMSI=0" to your kernel cmdline. If that >>> doesn't help, a bisect restricted to drivers/gpu/drm/nouveau should >>> show the offending commit fairly quickly. >>> >>> -ilia >>> >> Adding "nouveau.config=NvMSI=0" to the command line...

...>>> wrote: >>>> On 31/12/13 10:36, Ilia Mirkin wrote: >>>>> Having a dmesg would be nice. One thing I can think of off-hand is >>>>> that 3.13-rc has MSI turned on by default. You can turn it off by >>>>> adding "nouveau.config=NvMSI=0" to your kernel cmdline. If that >>>>> doesn't help, a bisect restricted to drivers/gpu/drm/nouveau should >>>>> show the offending commit fairly quickly. >>>>> >>>>> -ilia >>>>> >>>> Adding &quot...

https://bugs.freedesktop.org/show_bug.cgi?id=69982 Priority: medium Bug ID: 69982 Assignee: nouveau at lists.freedesktop.org Summary: GPU+system crash with nouveau and kernel 3.12-rc3 QA Contact: xorg-team at lists.x.org Severity: major Classification: Unclassified OS: Linux (All) Reporter: mike.cloaked at

...croll by [they wipe out some scrambled area > when scrolling by]. > > Unfortunately it will be rather hard to bisect because sometimes it does not > happen. > Adding drm-nouveau-next on top of rc2/rc3 does no apparent difference. A shot in the dark -- try booting with nouveau.config=NvMSI=0. We already disable MSI for NVAA, perhaps we should do it for NVAC as well. Although the blob drivers have it enabled... but we could be doing something wrong. -ilia

...it's the first bad commit for these nasty corruptions recoded >> and uploaded to YouTube. >> >> 4) 3.14-rc1 >> No changes since c21eb21cb50d58e7cbdcb8b9e7ff68b85cfa5095. No pink >> lines, but display corruptions happening. > > Can you boot with nouveau.config=NvMSI=0 ? If that helps, there are > some patches on the nouveau/dri-devel lists (search for "nv4c") that > may help you. Unfortunately this config parameter doesn't help :( -- Rafa?

...scrolling by]. >> > >> > Unfortunately it will be rather hard to bisect because sometimes it does not >> > happen. >> > Adding drm-nouveau-next on top of rc2/rc3 does no apparent difference. >> >> A shot in the dark -- try booting with nouveau.config=NvMSI=0. We >> already disable MSI for NVAA, perhaps we should do it for NVAC as >> well. Although the blob drivers have it enabled... but we could be >> doing something wrong. > > Hi Ilia, > > FWIW a Fedora user got those messages on stock 3.13-rc6 with and without the >...

...tion would be nice. See > http://nouveau.freedesktop.org/wiki/Bugs/ for the sort of information > that's generally useful. I should also mention that rebooting allows firefox to open. It seems to crash if it is opened after the system has been running for awhile. I tried nouveau.config=NvMSI=0 but it didn't help. - Grant

...ktop.org/wiki/Bugs/ for the sort of information >>> that's generally useful. >> >> I should also mention that rebooting allows firefox to open. It seems >> to crash if it is opened after the system has been running for awhile. >> >> I tried nouveau.config=NvMSI=0 but it didn't help. >> >> - Grant > > Can anyone help me out here? This has been really disruptive to my > organization. Unchecking "Use hardware acceleration when available" > in firefox also doesn't seem to fix it. Anything else I could try? Launch...

https://bugs.freedesktop.org/show_bug.cgi?id=78441 Priority: medium Bug ID: 78441 Assignee: nouveau at lists.freedesktop.org Summary: X does not start under kernel 3.13.x QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: aebenjam at opentext.com

It appears that MSI does not work on either G5 PPC nor on a E5500-based platform, where other hardware is reported to work fine with MSI. Both tests were conducted with NV4x hardware, so perhaps other (or even this) hardware can be made to work. It's still possible to force-enable with config=NvMSI=1 on load. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: stable at vger.kernel.org --- drm/nouveau/nvkm/subdev/pci/base.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/drm/nouveau/nvkm/subdev/pci/base.c b/drm/nouveau/nvkm/subdev/pci/base.c index eb9b2781..a4cb8249 10064...

https://bugs.freedesktop.org/show_bug.cgi?id=69876 --- Comment #8 from Mike <michele.cane at gmail.com> --- (In reply to comment #6) > Had a typo previously, the correct argument is > nouveau.config=NvMSI=0 The behaviour remain the same with nouveau.config=NvMSI=0 -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20131008/af7d56fb/at...

...gt; If necessary I can go back to the GT 560 Ti to gather dmesg and Xorg log >>> information. >> >> Having a dmesg would be nice. One thing I can think of off-hand is >> that 3.13-rc has MSI turned on by default. You can turn it off by >> adding "nouveau.config=NvMSI=0" to your kernel cmdline. If that >> doesn't help, a bisect restricted to drivers/gpu/drm/nouveau should >> show the offending commit fairly quickly. >> >> -ilia >> > Adding "nouveau.config=NvMSI=0" to the command line fixed the problem. >...

....uk> >> wrote: >>> >>> On 31/12/13 10:36, Ilia Mirkin wrote: >>>> Having a dmesg would be nice. One thing I can think of off-hand is >>>> that 3.13-rc has MSI turned on by default. You can turn it off by >>>> adding "nouveau.config=NvMSI=0" to your kernel cmdline. If that >>>> doesn't help, a bisect restricted to drivers/gpu/drm/nouveau should >>>> show the offending commit fairly quickly. >>>> >>>> -ilia >>>> >>> Adding "nouveau.config=NvMSI=0&q...

https://bugs.freedesktop.org/show_bug.cgi?id=69928 Priority: medium Bug ID: 69928 Assignee: nouveau at lists.freedesktop.org Summary: [NVAA] Boot of linux kernel 3.12-rc2 hangs QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: dirkneukirchen at

...On 31/12/13 10:36, Ilia Mirkin wrote: >>>>>> >>>>>> Having a dmesg would be nice. One thing I can think of off-hand is >>>>>> that 3.13-rc has MSI turned on by default. You can turn it off by >>>>>> adding "nouveau.config=NvMSI=0" to your kernel cmdline. If that >>>>>> doesn't help, a bisect restricted to drivers/gpu/drm/nouveau should >>>>>> show the offending commit fairly quickly. >>>>>> >>>>>> -ilia >>>>>> >>&...

...ly small corruption (10 %) which changes over time somewhat slightly - disk writes only happen in periodic spurs with long pauses (SysRQ + S) did not help Eventually I'm dumped to terminal with an oops, but I don't see anything nouveau related in there. Attaching it anyway. nouveau.config=NvMSI=0 'fixes' it. Or let me put it this way: It never occurred while using this parameter. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouvea...

Hi guys, With a GeForce 320M GPU running linux 3.13.2 and Xorg 1.15.0, I'm seeing significant graphical corruption and later unrecoverable GPU lockup, accompanied by thousands of ILLEGAL_MTHD or related kernel messages [1]. I see similar issues on 3.12 also. Is there any debugging or testing I can do to help diagnose this? Many thanks, Daniel --- [1] http://quora.org/nouveau-dmesg.txt

https://bugs.freedesktop.org/show_bug.cgi?id=89775 Bug ID: 89775 Summary: Grpahics card G72 [GeForce 7200 GS / 7300 SE] 3d does not work Product: Mesa Version: unspecified Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: