dri-devel January 2016

dri-devel@lists.freedesktop.org

194 participants
1200 discussions

[Bug 93534] Issues with color and rendering through OpenGL composited desktops on ATI FirePro v4800
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=93534 Bug ID: 93534 Summary: Issues with color and rendering through OpenGL composited desktops on ATI FirePro v4800 Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: sawyerbergeron(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 120728 --> https://bugs.freedesktop.org/attachment.cgi?id=120728&action=edit Screenshot taken depicting issues experienced I experienced this bug in Arch Linux starting approximately two or three weeks ago, and am experiencing it under Ubuntu 14.04 LTS as of today. This bug appears on any DE or program that uses OpenGL for compositing and is persistent through multiple power cycles, occurs with any number of monitors connected, and what appears to bypass these issues is (on desktops that allow doing so, such as Plasma) the use of Xrender or CPU rendering. If any additional information is required I can add it. Thanks in advance for any help. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 93466] [r600g] Emulate fp64 OpenCL operations using integer arithmetic
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=93466 Bug ID: 93466 Summary: [r600g] Emulate fp64 OpenCL operations using integer arithmetic Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: enhancement Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: rivanvx(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org For teaching and demonstration purposes it would be cool to have emulated fp64 arithmetic on low-end Evergreen and Northern Islands chips which don't support it (e.g. Caicos). However slow it might end up being, it would be really useful to have it at least for teaching GPU computing. glennk, iive and others discussed this in #radeon on 2015-09-13: http://people.freedesktop.org/~cbrill/dri-log/?channel=radeon&highlight_nam… -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 93370] [r600g] OpenCL atomic_cmpxchg() segmentation fault on Caicos
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=93370 Bug ID: 93370 Summary: [r600g] OpenCL atomic_cmpxchg() segmentation fault on Caicos Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: rivanvx(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 120495 --> https://bugs.freedesktop.org/attachment.cgi?id=120495&action=edit Program that segfaults I'm using mesa 8b52fa71ac3d706f27ccbddcb050aae4965839e9 and llvm svn revision 255468. The code that segfaults is attached. Debugging with gdb gives: Starting program: /home/vedranm/atomic [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff034b700 (LWP 20619)] [New Thread 0x7fffef912700 (LWP 20620)] [New Thread 0x7fffef111700 (LWP 20621)] [Thread 0x7fffef111700 (LWP 20621) exited] [Thread 0x7fffef912700 (LWP 20620) exited] Program received signal SIGSEGV, Segmentation fault. 0x00007ffff0a4480d in radeon_lookup_buffer (csc=csc@entry=0x7ffff7f31028, bo=bo@entry=0xf103c0) at radeon_drm_cs.c:230 230 if (i == -1 || csc->relocs_bo[i].bo == bo) (gdb) backtrace #0 0x00007ffff0a4480d in radeon_lookup_buffer (csc=csc@entry=0x7ffff7f31028, bo=bo@entry=0xf103c0) at radeon_drm_cs.c:230 #1 0x00007ffff0a44931 in radeon_add_buffer (added_domains=<synthetic pointer>, priority=29, domains=<optimized out>, usage=<optimized out>, bo=0xf103c0, cs=0x7ffff7f31010) at radeon_drm_cs.c:269 #2 radeon_drm_cs_add_buffer (rcs=0x7ffff7f31010, buf=0xf103c0, usage=<optimized out>, domains=<optimized out>, priority=RADEON_PRIO_VERTEX_BUFFER) at radeon_drm_cs.c:333 #3 0x00007ffff0a65a79 in radeon_add_to_buffer_list (rctx=0x65c260, ring=0x65c580, rbo=<optimized out>, rbo=<optimized out>, priority=RADEON_PRIO_VERTEX_BUFFER, usage=RADEON_USAGE_READ) at ../../../../src/gallium/drivers/radeon/r600_cs.h:53 #4 evergreen_emit_vertex_buffers (rctx=0x65c260, state=0x65ef00, resource_offset=816, pkt_flags=<optimized out>) at evergreen_state.c:1917 #5 0x00007ffff0a62467 in r600_emit_atom (atom=0x65ef00, rctx=0x65c260) at r600_pipe.h:578 #6 compute_emit_cs (grid_layout=0xf26950, block_layout=0xf26c10, ctx=0x65c260) at evergreen_compute.c:489 #7 evergreen_launch_grid (ctx_=0x65c260, block_layout=0xf26c10, grid_layout=grid_layout@entry=0xf26950, pc=pc@entry=0, input=input@entry=0xe68850) at evergreen_compute.c:631 #8 0x00007ffff58167ac in clover::kernel::launch (this=0xf24790, q=..., grid_offset=..., grid_size=std::vector of length 1, capacity 1 = {...}, block_size=std::vector of length 1, capacity 1 = {...}) at core/kernel.cpp:81 #9 0x00007ffff5811626 in std::function<void (clover::event&)>::operator()(clover::event&) const (__args#0=..., this=0xf26820) at /usr/include/c++/5/functional:2271 #10 clover::event::trigger (this=this@entry=0xf267e0) at core/event.cpp:55 #11 0x00007ffff58124f8 in clover::hard_event::hard_event(clover::command_queue&, unsigned int, clover::ref_vector<clover::event> const&, std::function<void (clover::event&)>) (this=0xf267e0, q=..., command=<optimized out>, deps=..., action=...) at core/event.cpp:126 #12 0x00007ffff57f8ae8 in clover::create<clover::hard_event, clover::command_queue&, int, clover::ref_vector<clover::event>&, clEnqueueNDRangeKernel(cl_command_queue, cl_kernel, cl_uint, const size_t*, const size_t*, const size_t*, cl_uint, _cl_event* const*, _cl_event**)::<lambda(clover::event&)> > () at ./util/pointer.hpp:230 #13 clEnqueueNDRangeKernel (d_q=0x63d328, d_kern=0xf24798, dims=<optimized out>, d_grid_offset=<optimized out>, d_grid_size=<optimized out>, d_block_size=0x7fffffffc430, num_deps=0, d_deps=0x0, rd_ev=0x0) at api/kernel.cpp:293 #14 0x00000000004014a8 in main () (gdb) -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 93364] texture bo too small ((899 721) (1 1) 0 26 0 -> 2592716 have 4096)
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=93364 Bug ID: 93364 Summary: texture bo too small ((899 721) (1 1) 0 26 0 -> 2592716 have 4096) Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: bjourne(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org I'm getting the following errors in dmesg: [947174.086041] radeon 0000:01:05.0: alignments 64 1 1 1 [947174.086071] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! [947185.227119] radeon 0000:01:05.0: texture bo too small ((899 721) (1 1) 0 26 0 -> 2592716 have 4096) [947185.227132] radeon 0000:01:05.0: alignments 64 1 1 1 [947185.227197] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! [947197.584009] radeon 0000:01:05.0: texture bo too small ((899 721) (1 1) 0 26 0 -> 2592716 have 4096) [947197.584016] radeon 0000:01:05.0: alignments 64 1 1 1 [947197.584056] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! [947243.179560] radeon 0000:01:05.0: texture bo too small ((899 721) (1 1) 0 26 0 -> 2592716 have 4096) [947243.179567] radeon 0000:01:05.0: alignments 64 1 1 1 [947243.179605] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! When tooltips are shown in Chromium, their windows contain garbled and uninitialized pixels. No idea if that is relevant. I'm using Ubuntu 15.10 with KDE. There were other bugs referencing the "texture bo too small" message, but they are all very old or marked fixed so I don't think this bug is a dupe. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 93353] GRID Autosport crash on loading screen with an HD 6950
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=93353 Bug ID: 93353 Summary: GRID Autosport crash on loading screen with an HD 6950 Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: serge.yquel(a)laposte.net QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 120465 --> https://bugs.freedesktop.org/attachment.cgi?id=120465&action=edit GRID Autosport crash report Hello, On loading screen just before starting a race, the game crash to the desktop with this on the terminal: EE r600_shader.c:182 r600_pipe_shader_create - translation from TGSI failed ! EE r600_state_common.c:826 r600_shader_select - Failed to build shader variant (type=1) -1 i added a crash report from the game .dmp, if it can help. it was working on low setting with a previous version of mesa, i don't know the exact version number but it was just before r600 add full support for OpenGL 4.1 and probably the tesselation. Here are the information about the version i currently use and make the game crash just before the race start: VGA: Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO [Radeon HD 6950] Driver: r600 direct rendering: Yes OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD CAYMAN (DRM 2.43.0, LLVM 3.8.0) OpenGL core profile version string: 4.1 (Core Profile) Mesa 11.2.0-devel (git-369afdb) OpenGL core profile shading language version string: 4.10 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile GL_ARB_direct_state_access, GL_ARB_draw_buffers, GL_ARB_draw_indirect, GL_ARB_draw_instanced, GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multi_draw_indirect, OpenGL version string: 3.0 Mesa 11.2.0-devel (git-369afdb) OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.2.0-devel (git-369afdb) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 93292] "Thea: The Awakening" world map textures not rendered (blue background)
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=93292 Bug ID: 93292 Summary: "Thea: The Awakening" world map textures not rendered (blue background) Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: glogow(a)fbihome.de QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 120410 --> https://bugs.freedesktop.org/attachment.cgi?id=120410&action=edit Thea with interface only world map The problematic game can be downloaded from the link in the first message in the following steam thread or via the steam beta channel (DRM free, free for Linux): https://steamcommunity.com/app/378720/discussions/0/490125737485986607?fp=2… Someone else with older AMD hardware reported the same problem in the linked communty thread. My hardware is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v] When starting the actual gameplay, only the interface is rendered but not the games world map, basically rendering the game unplayable (see attached image). I'm on Ubuntu Trusty 14.04, 3.13 kernel. This happens with stock Mesa from the Ubuntu release and with the git release from the oibaf PPA: https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers The apitrace is too large to upload for me (1.5 GB), but doesn't show a particular error, except for an early glClear without a context; even the trimmed one is 1,25GB. xz compressed is still 620MB. The game renders correctly when started with "LIBGL_ALWAYS_SOFTWARE=1". I confirmed this by also rendering the apitrace in software. imirkin told me on IRC, that this actually is a bug in the r600 driver. I've compiled Mesa git packages with "--enable-debug" and can test a patch, if needed. I'm jmux on freenode and will be lingering around in the channel for some time and normally can be found in the libreoffice-dev channel. -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 93162] playing video while suspending results in screen corruption at resume
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=93162 Bug ID: 93162 Summary: playing video while suspending results in screen corruption at resume Product: Mesa Version: 11.0 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: serafean(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Smplayer was playing a movie, the PC suspended. At resume, all screens looked like analog noise, and the playing movie was stuck looping on a few frames. Closing smplayer and starting the movie again worked fine though. In dmesg, the only relevant lines during suspend are : [27911.777744] sd 6:0:1:0: [sdc] Stopping disk [27912.215648] radeon 0000:01:00.0: couldn't schedule ib [27912.215672] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD (-22)! [27912.387056] PM: suspend of devices complete after 651.111 msecs And during resume : [27912.467612] [drm] PCIE GART of 1024M enabled (table at 0x0000000000274000). [27912.467683] radeon 0000:01:00.0: WB enabled [27912.467685] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff88012a3d8c00 [27912.468456] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc90001032118 [27912.468457] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff88012a3d8c04 [27912.468459] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff88012a3d8c08 [27912.468461] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff88012a3d8c0c [27912.468462] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff88012a3d8c10 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 93039] [APITRACE] Google earth bad colors when tilted
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=93039 Bug ID: 93039 Summary: [APITRACE] Google earth bad colors when tilted Product: Mesa Version: 11.0 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: egore(a)gmx.de QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 119982 --> https://bugs.freedesktop.org/attachment.cgi?id=119982&action=edit Screenshot of the problem When tilting the view in Google Maps the color turn yellow and red. Work for non-tilted and slightly tilted. Also works on i965. APITRACE can be found at: https://drive.google.com/file/d/0BxAIK4wsKm_YNXgzbXRObDdveE0/view?usp=shari… -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 92755] Shadow of Mordor locks up R600
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=92755 Bug ID: 92755 Summary: Shadow of Mordor locks up R600 Product: Mesa Version: 11.0 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: egore(a)gmx.de QA Contact: dri-devel(a)lists.freedesktop.org Shadow of Mordor locks up when entering the game. The following can be found in journalctl: Okt 31 15:53:48 hostname kernel: radeon 0000:01:00.0: ring 0 stalled for more than 10493msec Okt 31 15:53:48 hostname kernel: radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000017f8e last fence id 0x0000000000017fa0 on ring 0) Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: Saved 567 dwords of commands on ring 0. Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: GPU softreset: 0x00000019 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: GRBM_STATUS = 0xA00309A0 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000001 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: SRBM_STATUS = 0x20000AC0 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x01000000 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00011000 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00028506 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: R_008680_CP_STAT = 0x80838647 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: GPU reset succeeded, trying to resume Okt 31 15:53:49 hostname kernel: [drm] PCIE gen 2 link speeds already enabled Okt 31 15:53:49 hostname kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000000025E000). Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: WB enabled Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8800cf42cc00 Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8800cf42cc0c Okt 31 15:53:49 hostname kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr 0xffffc90001c1c418 Okt 31 15:53:49 hostname kernel: [drm] ring test on 0 succeeded in 1 usecs Okt 31 15:53:49 hostname kernel: [drm] ring test on 3 succeeded in 2 usecs Okt 31 15:53:50 hostname kernel: [drm] ring test on 5 succeeded in 1 usecs Okt 31 15:53:50 hostname kernel: [drm] UVD initialized successfully. Okt 31 15:53:50 hostname kernel: ------------[ cut here ]------------ Okt 31 15:53:50 hostname kernel: WARNING: CPU: 3 PID: 124 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x66/0x80() Okt 31 15:53:50 hostname kernel: sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:02.0/0000:01:00.0/power_dpm_state' Okt 31 15:53:50 hostname kernel: Modules linked in: bnep bluetooth rfkill fuse hwmon_vid ext4 crc16 mbcache jbd2 gspca_ov519 gspca_main joydev snd_hda_codec_realtek mousedev snd_hda_codec_hdmi videodev media input_leds led_class wacom snd_hda_codec_generic snd_hda_intel evdev snd_hda_codec kvm_amd snd_hda_core mac_hid kvm psmouse snd_hwdep snd_pcm r8169 edac_core pcspkr serio_raw edac_mce_amd snd_timer mii k10temp sp5100_tco snd wmi acpi_cpufreq asus_atk0110 i2c_piix4 button shpchp soundcore processor sch_fq_codel vboxnetflt(O) pci_stub vboxpci(O) vboxdrv(O) ip_tables x_tables crc32c_generic btrfs xor hid_generic raid6_pq usbhid hid sr_mod cdrom sd_mod ata_generic pata_acpi atkbd libps2 pata_atiixp ahci libahci firewire_ohci pata_via ehci_pci xhci_pci ohci_pci ohci_hcd xhci_hcd ehci_hcd libata usbcore usb_common scsi_mod Okt 31 15:53:50 hostname kernel: firewire_core crc_itu_t i8042 serio radeon i2c_algo_bit drm_kms_helper ttm drm Okt 31 15:53:50 hostname kernel: CPU: 3 PID: 124 Comm: kworker/u12:3 Tainted: G O 4.2.5-1-ARCH #1 Okt 31 15:53:50 hostname kernel: Hardware name: System manufacturer System Product Name/M4A88TD-V EVO/USB3, BIOS 1601 09/08/2010 Okt 31 15:53:50 hostname kernel: Workqueue: radeon-crtc radeon_flip_work_func [radeon] Okt 31 15:53:50 hostname kernel: 0000000000000000 00000000d93e9885 ffff8800cf75fb58 ffffffff81570d0a Okt 31 15:53:50 hostname kernel: 0000000000000000 ffff8800cf75fbb0 ffff8800cf75fb98 ffffffff810748a6 Okt 31 15:53:50 hostname kernel: 000059d6cf75fb98 ffff88010045c000 ffffffffa01ee5a8 ffff880225d15960 Okt 31 15:53:50 hostname kernel: Call Trace: Okt 31 15:53:50 hostname kernel: [<ffffffff81570d0a>] dump_stack+0x4c/0x6e Okt 31 15:53:50 hostname kernel: [<ffffffff810748a6>] warn_slowpath_common+0x86/0xc0 Okt 31 15:53:50 hostname kernel: [<ffffffff81074935>] warn_slowpath_fmt+0x55/0x70 Okt 31 15:53:50 hostname kernel: [<ffffffff81245808>] ? kernfs_path+0x48/0x60 Okt 31 15:53:50 hostname kernel: [<ffffffff81248df6>] sysfs_warn_dup+0x66/0x80 Okt 31 15:53:50 hostname kernel: [<ffffffff81248b07>] sysfs_add_file_mode_ns+0x127/0x180 Okt 31 15:53:50 hostname kernel: [<ffffffff81248b8a>] sysfs_create_file_ns+0x2a/0x30 Okt 31 15:53:50 hostname kernel: [<ffffffff813cf532>] device_create_file+0x42/0x90 Okt 31 15:53:50 hostname kernel: [<ffffffffa011d976>] radeon_pm_late_init+0x76/0x1a0 [radeon] Okt 31 15:53:50 hostname kernel: [<ffffffffa00b9e1a>] radeon_gpu_reset+0x26a/0x330 [radeon] Okt 31 15:53:50 hostname kernel: [<ffffffff810b4c80>] ? wake_atomic_t_function+0x60/0x60 Okt 31 15:53:50 hostname kernel: [<ffffffffa00e1190>] radeon_flip_work_func+0x130/0x170 [radeon] Okt 31 15:53:50 hostname kernel: [<ffffffff8108c5db>] process_one_work+0x14b/0x440 Okt 31 15:53:50 hostname kernel: [<ffffffff8108c918>] worker_thread+0x48/0x4a0 Okt 31 15:53:50 hostname kernel: [<ffffffff8108c8d0>] ? process_one_work+0x440/0x440 Okt 31 15:53:50 hostname kernel: [<ffffffff8108c8d0>] ? process_one_work+0x440/0x440 Okt 31 15:53:50 hostname kernel: [<ffffffff81092578>] kthread+0xd8/0xf0 Okt 31 15:53:50 hostname kernel: [<ffffffff810924a0>] ? kthread_worker_fn+0x170/0x170 Okt 31 15:53:50 hostname kernel: [<ffffffff8157665f>] ret_from_fork+0x3f/0x70 Okt 31 15:53:50 hostname kernel: [<ffffffff810924a0>] ? kthread_worker_fn+0x170/0x170 Okt 31 15:53:50 hostname kernel: ---[ end trace 9a616c8d3f7ec6d9 ]--- Okt 31 15:53:50 hostname kernel: [drm:radeon_pm_late_init [radeon]] *ERROR* failed to create device file for dpm state Okt 31 15:53:50 hostname kernel: ------------[ cut here ]------------ -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 92555] GPU lockup crashing the system on Cayman
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=92555 Bug ID: 92555 Summary: GPU lockup crashing the system on Cayman Product: Mesa Version: 11.0 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: v10lator(a)myway.de QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 119002 --> https://bugs.freedesktop.org/attachment.cgi?id=119002&action=edit dmesg part 1 (png file) Reproduced with Left 4 Dead 2, Distance and Metro 2033 Redux. First the screen either freezes (Distance) or shows garbage, looks like many small brown rectangles on the screen (Left 4 Dead 2, Metro 2033 Redux), then, after around 30 seconds, the whole system freezes (keyboard/mouse doesn't react, ssh connections drop, finally watchdog kicks in and reboots the system). In between the 30 seconds I was able to grab some data via ssh. Screenshots attached. This is on a HD 6950. -- You are receiving this mail because: You are the assignee for the bug.

1 12

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2016