[Bug 99353] Kaveri 7400K shows random colored noise instead of GUI in X or Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=99353 --- Comment #50 from Bong Cosca --- Will we see this patch/commit on the stable kernel too? -- You are receiving this mail because: You are the assignee for the bug.___

[Bug 104193] [radeonsi] The Witcher 3 freezes the system with no attachments calls & transform feedback Wine patch

https://bugs.freedesktop.org/show_bug.cgi?id=104193 --- Comment #7 from Shmerl --- Actually, scrap that. I've just got another freeze even without znver1. -- You are receiving this mail because: You are the assignee for the

[Bug 104193] [radeonsi] The Witcher 3 freezes the system with no attachments calls & transform feedback Wine patch

https://bugs.freedesktop.org/show_bug.cgi?id=104193 --- Comment #6 from Shmerl --- I managed to narrow it down to building Wine with -march=znver1 that I used for AMD Ryzen. Without that, it's not freezing. -- You are receiving this mail because: You are the assignee for

[Bug 104082] amdgpu 0000:07:00.0: swiotlb buffer is full (sz: 2097152 bytes)

https://bugs.freedesktop.org/show_bug.cgi?id=104082 --- Comment #35 from Nick Lee --- The same on NVIDIA Corporation C79 [GeForce 9300 / nForce 730i] (rev b1). This happens when high disk IO load. For example - copy foles from HDD to USB. [30790.063300] nouveau :03:00.0:

[Bug 105273] [r350] missing background, transparency not working & other glitches in ETR (AGP, ppc, mesa-18.0.0_rc4)

https://bugs.freedesktop.org/show_bug.cgi?id=105273 --- Comment #5 from erhar...@mailbox.org --- Just tried software rendering for comparison. Using softpipe ETR runs like on amd64 without any glitches. Albeith unuseable slow on a G5. $ glxinfo | grep -i opengl OpenGL vendor string: VMware, Inc.

[Bug 198985] BUG: KASAN: use-after-free in amdgpu_job_free_cb+0x26/0xb0 [amdgpu]

https://bugzilla.kernel.org/show_bug.cgi?id=198985 --- Comment #1 from Fredrik (fred...@planet-express.se) --- mesa3d 17.3.6-1 CONFIG_DRM_AMDGPU=m CONFIG_DRM_AMD_DC=y CONFIG_DRM_AMD_DC_PRE_VEGA=y -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 198985] New: BUG: KASAN: use-after-free in amdgpu_job_free_cb+0x26/0xb0 [amdgpu]

https://bugzilla.kernel.org/show_bug.cgi?id=198985 Bug ID: 198985 Summary: BUG: KASAN: use-after-free in amdgpu_job_free_cb+0x26/0xb0 [amdgpu] Product: Drivers Version: 2.5 Kernel Version: 4.15.7 Hardware: x86-64

[Bug 105333] [gallium-nine] missing geometry after commit ac: replace ac_build_kill with ac_build_kill_if_false

https://bugs.freedesktop.org/show_bug.cgi?id=105333 --- Comment #2 from had...@gmx.de --- Created attachment 137767 --> https://bugs.freedesktop.org/attachment.cgi?id=137767=edit screenshot with mesa git -- You are receiving this mail because: You are the assignee for the

[Bug 105333] [gallium-nine] missing geometry after commit ac: replace ac_build_kill with ac_build_kill_if_false

https://bugs.freedesktop.org/show_bug.cgi?id=105333 --- Comment #1 from had...@gmx.de --- Created attachment 137766 --> https://bugs.freedesktop.org/attachment.cgi?id=137766=edit screenshot with mesa 17.3 -- You are receiving this mail because: You are the assignee for the

[Bug 105333] [gallium-nine] missing geometry after commit ac: replace ac_build_kill with ac_build_kill_if_false

https://bugs.freedesktop.org/show_bug.cgi?id=105333 Bug ID: 105333 Summary: [gallium-nine] missing geometry after commit ac: replace ac_build_kill with ac_build_kill_if_false Product: Mesa Version: git Hardware: x86-64

[Bug 105083] Random blinking display

https://bugs.freedesktop.org/show_bug.cgi?id=105083 --- Comment #12 from denisgolo...@yandex.ru --- Disabling amdgpu.dc under drm-next-4.17-wip works fine though. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel

[Bug 105083] Random blinking display

https://bugs.freedesktop.org/show_bug.cgi?id=105083 --- Comment #11 from denisgolo...@yandex.ru --- (In reply to Harry Wentland from comment #10) > We have some patches that rework our gamma programming in our staging trees. > Would you be able to try amd-staging-drm-next or drm-next-4.17-wip

[Bug 102553] Venus PRO R9 M265X amdgpu: Kernel OOPS si_dpm_set_power_state unable to handle kernel NULL pointer dereference

https://bugs.freedesktop.org/show_bug.cgi?id=102553 --- Comment #4 from mercuriete --- Searching in internet I found somebody hitting my same problem. https://patchwork.kernel.org/patch/8731311/ maybe lane with calculations leads on a kernel oops in amdgpu and a warning in

[Bug 102553] Venus PRO R9 M265X amdgpu: Kernel OOPS si_dpm_set_power_state unable to handle kernel NULL pointer dereference

https://bugs.freedesktop.org/show_bug.cgi?id=102553 --- Comment #3 from mercuriete --- Only for give more information: When using radeon DRM driver this is output in dmesg [ 82.490643] [drm:si_dpm_set_power_state] *ERROR* invalid pcie lane request: 7 But there are no

[PATCH v2 6/7] vga_switcheroo: Let HDA autosuspend on mux change

When switching the display on muxed machines, we currently force the HDA controller into runtime suspend on the previously used GPU and into runtime active state on the newly used GPU. That's unnecessary if the GPU uses driver power control, we can just let the audio device autosuspend or

[PATCH v2 7/7] drm/nouveau: Runtime suspend despite HDA being unbound

Commit 5addcf0a5f0f ("nouveau: add runtime PM support (v0.9)") prevents runtime suspend of the GPU if its integrated HDA controller is not bound to a driver. The rationale appears to be that probing the HDA fails if the GPU is in D3cold. However we now use a device link to ensure that the GPU is

[PATCH v2 4/7] vga_switcheroo: Deduplicate power state tracking

If DRM drivers use runtime PM, they currently notify vga_switcheroo whenever they ->runtime_suspend or ->runtime_resume to update vga_switcheroo's internal power state tracking. That's essentially a duplication of a functionality performed by the PM core as it already tracks the GPU's power state

[PATCH v2 5/7] vga_switcheroo: Use device link for HDA controller

Back in 2013, runtime PM for GPUs with integrated HDA controller was introduced with commits 0d69704ae348 ("gpu/vga_switcheroo: add driver control power feature. (v3)") and 246efa4a072f ("snd/hda: add runtime suspend/resume on optimus support (v4)"). Briefly, the idea was that the HDA controller

[PATCH v2 2/7] PCI: Make pci_wakeup_bus() & pci_bus_set_current_state() public

There are PCI devices which are power-manageable by a nonstandard means, such as a custom ACPI method. One example are discrete GPUs in hybrid graphics laptops, another are Thunderbolt controllers in Macs. Such devices can't be put into D3cold with pci_set_power_state() because

[PATCH v2 3/7] vga_switcheroo: Update PCI current_state on power change

When cutting power to a GPU and its integrated HDA controller, their cached current_state should be updated to D3cold to reflect reality. We currently rely on the DRM and HDA drivers to do that, however: - The HDA driver updates the current_state in azx_vs_set_state(), which will no longer be

[PATCH v2 1/7] PCI: Restore config space on runtime resume despite being unbound

From: Rafael J. Wysocki We leave PCI devices not bound to a driver in D0 during runtime suspend. But they may have a parent which is bound and can be transitioned to D3cold at runtime. Once the parent goes to D3cold, the unbound child may go to D3cold as well. When the

[PATCH v2 0/7] Modernize vga_switcheroo by using device link for HDA

Modernize vga_switcheroo by using a device link to enforce a runtime PM dependency from an HDA controller to the GPU it's integrated into, v2. Changes since v1: - Replace patch [1/7] to use pci_save_state() / pci_restore_state() for consistency between runtime PM code path of bound and unbound

[Bug 102553] Venus PRO R9 M265X amdgpu: Kernel OOPS si_dpm_set_power_state unable to handle kernel NULL pointer dereference

https://bugs.freedesktop.org/show_bug.cgi?id=102553 --- Comment #2 from mercuriete --- Still happening on uname -a Linux localhost.localdomain 4.14.23-gentoo #2 SMP PREEMPT Sat Mar 3 10:31:54 CET 2018 x86_64 Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz GenuineIntel GNU/Linux

Re: [Intel-gfx] [PATCH 1/1] intel: align reuse buffer's size on page size instead

Quoting James Xiong (2018-03-02 17:53:04) > From: "Xiong, James" > > With gem_reuse enabled, when a buffer size is different than > the sizes of buckets, it is aligned to the next bucket's size, > which means about 25% more memory than the requested is allocated > in the

[Bug 105317] The GPU Vega 56 was hang while try to pass #GraphicsFuzz shader15 test

https://bugs.freedesktop.org/show_bug.cgi?id=105317 --- Comment #2 from mikhail.v.gavri...@gmail.com --- (In reply to Emil Velikov from comment #1) > Mikhail one suggestion to consider for the future: > > Do mention version numbers (or sha if using a git checkout), for the > different components