Bug 103764 - 3D renering results in a distorted frame.
Summary: 3D renering results in a distorted frame.
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/nouveau (show other bugs)
Version: 17.0
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Nouveau Project
QA Contact: Nouveau Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-15 16:07 UTC by Ilya
Modified: 2019-09-18 20:46 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (33.48 KB, text/x-log)
2017-11-15 16:31 UTC, Ilya
Details
dmesg (65.46 KB, text/plain)
2017-11-15 16:32 UTC, Ilya
Details
glxinfo (21.57 KB, text/plain)
2017-11-15 16:37 UTC, Ilya
Details

Description Ilya 2017-11-15 16:07:13 UTC
Starting glxgears results in one static distorted frame. But the programs continues to run and outputs in the console, that the frames are drawn. No error reports occure.

Hardware:

01:00.0 VGA compatible controller: NVIDIA Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev a1)
Comment 1 Ilia Mirkin 2017-11-15 16:13:35 UTC
I know you said no errors, but I'd still like to see your xorg log and dmesg, which should provide additional info about the system if nothing else.
Comment 2 Ilya 2017-11-15 16:31:30 UTC
Created attachment 135494 [details]
Xorg.0.log
Comment 3 Ilya 2017-11-15 16:32:10 UTC
Created attachment 135495 [details]
dmesg
Comment 4 Ilya 2017-11-15 16:32:46 UTC
(In reply to Ilia Mirkin from comment #1)
> I know you said no errors, but I'd still like to see your xorg log and
> dmesg, which should provide additional info about the system if nothing else.

Have added it
Comment 5 Ilya 2017-11-15 16:37:28 UTC
Created attachment 135496 [details]
glxinfo
Comment 6 Ilia Mirkin 2017-11-15 16:45:26 UTC
Can you check if MSI is enabled (lspci -nn -vv -d 10de: )? Also see if interrupts are being properly delivered (cat /proc/interrupts)

NV46 had some issues with that, although they should have been fixed in 4.4, which you're running...
Comment 7 Ilya 2017-11-15 16:52:56 UTC
(In reply to Ilia Mirkin from comment #6)
> Can you check if MSI is enabled (lspci -nn -vv -d 10de: )? Also see if
> interrupts are being properly delivered (cat /proc/interrupts)
> 
> NV46 had some issues with that, although they should have been fixed in 4.4,
> which you're running...

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G72M [Quadro NVS 110M/GeForce Go 7300] [10de:01d7] (rev a1) (prog-if 00 [VGA controller])
	Subsystem: Lenovo G72M [Quadro NVS 110M/GeForce Go 7300] [17aa:3839]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 30
	Region 0: Memory at c9000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
	Region 3: Memory at ca000000 (64-bit, non-prefetchable) [size=16M]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: <access denied>
	Kernel driver in use: nouveau
	Kernel modules: nvidiafb, nouveau

The PCI-MSI counter (relative nvkm) is rapidly increasing, if glxgears are running. I tried to count, its about 120 interrupts per second, which seems to be ok, till vsync on 60Hz is enabled.
Comment 8 Ilya 2017-11-15 16:54:46 UTC
(In reply to Ilia Mirkin from comment #6)
> Can you check if MSI is enabled (lspci -nn -vv -d 10de: )? Also see if
> interrupts are being properly delivered (cat /proc/interrupts)
> 
> NV46 had some issues with that, although they should have been fixed in 4.4,
> which you're running...

Oh. O forgot to "suid" me :) Here is the right one:


01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G72M [Quadro NVS 110M/GeForce Go 7300] [10de:01d7] (rev a1) (prog-if 00 [VGA controller])
	Subsystem: Lenovo G72M [Quadro NVS 110M/GeForce Go 7300] [17aa:3839]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 30
	Region 0: Memory at c9000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
	Region 3: Memory at ca000000 (64-bit, non-prefetchable) [size=16M]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee0200c  Data: 41b2
	Capabilities: [78] Express (v1) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <1us, L1 <4us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
		LnkCtl:	ASPM Disabled; RCB 128 bytes Disabled- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
	Capabilities: [100 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=01
			Status:	NegoPending- InProgress-
	Capabilities: [128 v1] Power Budgeting <?>
	Kernel driver in use: nouveau
	Kernel modules: nvidiafb, nouveau
Comment 9 Ilya 2017-11-17 16:29:29 UTC
I seems to be a tuxonice-specific bug. I tried now the standard kernel and all seems to be ok (except the suspend and hibernation, which does not work since 5 years :(
Comment 10 Ilia Mirkin 2017-11-17 16:53:34 UTC
(In reply to Ilya from comment #9)
> I seems to be a tuxonice-specific bug. I tried now the standard kernel and
> all seems to be ok (except the suspend and hibernation, which does not work
> since 5 years :(

Perhaps they mess around with interrupts? Try disabling MSI anyways... nouveau.config=NvMSI=0
Comment 11 GitLab Migration User 2019-09-18 20:46:07 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1144.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.