dri-devel September 2014

dri-devel@lists.freedesktop.org

173 participants
1045 discussions

[Bug 60254] New: agd5f wip kernel Oops when provoking GPU lock.
by bugzilla-daemon＠freedesktop.org 30 Jul '15

30 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=60254 Priority: medium Bug ID: 60254 Assignee: dri-devel(a)lists.freedesktop.org Summary: agd5f wip kernel Oops when provoking GPU lock. Severity: normal Classification: Unclassified OS: All Reporter: lists(a)andyfurniss.entadsl.com Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI The GPU lock with Rv670 and openarena is nothing new - it seems to have been a feature for almost a year (I haven't used rv670 for most of that time). On noticing the new gpu reset code in drm-next-3.9-wip I decided to provoke it on my AGP box and got - Feb 3 20:46:56 nf7 kernel: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec Feb 3 20:46:56 nf7 kernel: radeon 0000:02:00.0: GPU lockup (waiting for 0x00000000000111c8 last fence id 0x00000000000111c6) Feb 3 20:46:56 nf7 kernel: radeon 0000:02:00.0: f51df600 unpin not necessary Feb 3 20:46:56 nf7 kernel: radeon 0000:02:00.0: Saved 217 dwords of commands on ring 0. Feb 3 20:46:56 nf7 kernel: BUG: unable to handle kernel paging request at f87aec0c Feb 3 20:46:56 nf7 kernel: IP: [<fa033a3e>] radeon_fence_process+0x7e/0x160 [radeon] Feb 3 20:46:56 nf7 kernel: *pde = 3702f067 *pte = 00000000 Feb 3 20:46:56 nf7 kernel: Oops: 0000 [#1] PREEMPT Feb 3 20:46:56 nf7 kernel: Modules linked in: radeon fbcon font bitblit ttm softcursor drm_kms_helper drm fb fbdev i2c_algo_bit i2c_core cfbcopyarea cfbimgblt cfbfillrect ehci_pci ehci_hcd nvidia_agp agpgart ohci_hcd usbhid usbcore usb_common snd_intel8x0 snd_ac97_codec ac97_bus forcedeth Feb 3 20:46:56 nf7 kernel: Pid: 2511, comm: openarena.i386 Not tainted 3.8.0-rc3-gc7fb5ff #1 /NF7-S/NF7 (nVidia-nForce2) Feb 3 20:46:56 nf7 kernel: EIP: 0060:[<fa033a3e>] EFLAGS: 00210246 CPU: 0 Feb 3 20:46:56 nf7 kernel: EIP is at radeon_fence_process+0x7e/0x160 [radeon] Feb 3 20:46:56 nf7 kernel: EAX: f87aec0c EBX: f73b2848 ECX: f73b2848 EDX: 00000000 Feb 3 20:46:56 nf7 kernel: ESI: 00000000 EDI: f73b2000 EBP: e4765d8c ESP: e4765d58 Feb 3 20:46:56 nf7 kernel: DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068 Feb 3 20:46:56 nf7 kernel: CR0: 8005003b CR2: f87aec0c CR3: 1e75f000 CR4: 000007d0 Feb 3 20:46:56 nf7 kernel: DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 Feb 3 20:46:56 nf7 kernel: DR6: ffff0ff0 DR7: 00000400 Feb 3 20:46:56 nf7 kernel: Process openarena.i386 (pid: 2511, ti=e4764000 task=f70ad2b0 task.ti=e4764000) Feb 3 20:46:56 nf7 kernel: Stack: Feb 3 20:46:56 nf7 kernel: c13d4e58 00765d7c 00000018 f73b2848 f73b2888 00000872 00000003 00000872 Feb 3 20:46:56 nf7 kernel: 00000000 0000000c 00000003 f73b2a5c e4765e0c e4765da4 fa034850 f73b2000 Feb 3 20:46:56 nf7 kernel: f73b2000 f73b2a5c e4765e0c e4765dc4 fa049bb8 f73b28e8 00000000 c12b06cd Feb 3 20:46:56 nf7 kernel: Call Trace: Feb 3 20:46:56 nf7 kernel: [<c13d4e58>] ? sub_preempt_count+0x8/0x80 Feb 3 20:46:56 nf7 kernel: [<fa034850>] radeon_fence_count_emitted+0x20/0x90 [radeon] Feb 3 20:46:56 nf7 kernel: [<fa049bb8>] radeon_ring_backup+0x38/0x100 [radeon] Feb 3 20:46:56 nf7 kernel: [<c12b06cd>] ? _dev_info+0x2d/0x30 Feb 3 20:46:56 nf7 kernel: [<fa020b22>] radeon_gpu_reset+0x62/0x1d0 [radeon] Feb 3 20:46:56 nf7 kernel: [<f8be99c6>] ? ttm_bo_unreserve+0x26/0x50 [ttm] Feb 3 20:46:56 nf7 kernel: [<fa04821d>] radeon_gem_handle_lockup.part.2+0xd/0x20 [radeon] Feb 3 20:46:56 nf7 kernel: [<fa048b13>] radeon_gem_wait_idle_ioctl+0xb3/0xd0 [radeon] Feb 3 20:46:56 nf7 kernel: [<fa048a60>] ? radeon_gem_busy_ioctl+0xf0/0xf0 [radeon] Feb 3 20:46:56 nf7 kernel: [<f8af9e82>] drm_ioctl+0x402/0x460 [drm] Feb 3 20:46:56 nf7 kernel: [<fa048a60>] ? radeon_gem_busy_ioctl+0xf0/0xf0 [radeon] Feb 3 20:46:56 nf7 kernel: [<c104f469>] ? ktime_add_safe+0x9/0x60 Feb 3 20:46:56 nf7 kernel: [<c104fe80>] ? hrtimer_forward+0xa0/0x190 Feb 3 20:46:56 nf7 kernel: [<f8af9a80>] ? drm_copy_field+0x80/0x80 [drm] Feb 3 20:46:56 nf7 kernel: [<c10eb65a>] do_vfs_ioctl+0x7a/0x590 Feb 3 20:46:56 nf7 kernel: [<c101ef0b>] ? lapic_next_event+0x1b/0x20 Feb 3 20:46:56 nf7 kernel: [<c106978d>] ? clockevents_program_event+0x9d/0x150 Feb 3 20:46:56 nf7 kernel: [<c106ab18>] ? tick_program_event+0x28/0x30 Feb 3 20:46:56 nf7 kernel: [<c1050612>] ? hrtimer_interrupt+0x182/0x2f0 Feb 3 20:46:56 nf7 kernel: [<c13d4e58>] ? sub_preempt_count+0x8/0x80 Feb 3 20:46:56 nf7 kernel: [<c1048cf9>] ? __rcu_read_unlock+0x9/0x60 Feb 3 20:46:56 nf7 kernel: [<c10f4bc7>] ? fget_light+0x77/0xd0 Feb 3 20:46:56 nf7 kernel: [<c10ebbac>] sys_ioctl+0x3c/0x70 Feb 3 20:46:56 nf7 kernel: [<c13d7ffa>] sysenter_do_call+0x12/0x22 Feb 3 20:46:56 nf7 kernel: Code: 8b 4d d4 8d 84 51 f0 00 00 00 8b 74 c7 08 89 75 e0 8b 74 c7 0c 8b 45 d8 83 c0 08 80 bf ec 0d 00 00 00 0f 84 bf 00 00 00 8b 40 0c <8b> 00 39 45 e8 8b 4d ec 89 c3 ba 01 00 00 00 0f 47 ce 39 f1 77 Feb 3 20:46:56 nf7 kernel: EIP: [<fa033a3e>] radeon_fence_process+0x7e/0x160 [radeon] SS:ESP 0068:e4765d58 Feb 3 20:46:56 nf7 kernel: CR2: 00000000f87aec0c Feb 3 20:46:56 nf7 kernel: ---[ end trace 457588a7cbc40235 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 70227] New: OpenCL reaper-prime app crashes due to atomic_or unimplemented
by bugzilla-daemon＠freedesktop.org 29 Jul '15

29 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=70227 Priority: medium Bug ID: 70227 Assignee: dri-devel(a)lists.freedesktop.org Summary: OpenCL reaper-prime app crashes due to atomic_or unimplemented Severity: normal Classification: Unclassified OS: All Reporter: alexxy(a)gentoo.org Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Miner app https://github.com/arnuschky/primecoin-reaper.git crashes with ./reaper \|||||||||||||||||||||/ - Reaper v13 64-bit - - PRIME BETA 2 - - coded by mtrlt - /|||||||||||||||||||||\ Warning: unknown property "use_gpu" in configuration file. I'm now mining primecoin! Share thread started GeneratePrimeTable() : setting nSievePercentage = 1, nSieveSize = 100000 GeneratePrimeTable() : prime table [1, 100000] generated with 9592 primes Available CPU mining algorithms: hp7 Using default: hp7 Creating 1 CPU thread. 1...Warning: can't set thread priority done List of platforms: 0 Default Using platform number 0 Using device 0 OpenCL device 0........ Compiling kernel... this could take up to 2 minutes. 2 warnings generated. Building kernel CalculateMultipliers Building kernel Sieve Building kernel Combine Building kernel Fermat done Compiling kernel... this could take up to 2 minutes. 2 warnings generated. Building kernel CalculateMultipliers Building kernel Sieve Building kernel Combine Building kernel Fermat 0x7f735cdadd00: i32 = GlobalAddress<i32 (...)* @atomic_or> 0 [ORD=104] Stack dump: 0. Running pass 'Function Pass Manager' on module 'radeon'. 1. Running pass 'AMDGPU DAG->DAG Pattern Instruction Selection' on function '@Sieve' Segmentation fault -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 33399] New: No HDMI PCM mutichannel audio
by bugzilla-daemon＠freedesktop.org 14 Jul '15

14 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=33399 Summary: No HDMI PCM mutichannel audio Product: DRI Version: XOrg CVS Platform: All OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: xavier.bestel(a)free.fr Hi, using a HD 2600, audio over HDMI is stereo-only. The only mean to have multichannel (e.g. 5.1) is to use passthrough, but true multichannel (e.g. 8 channels PCM) isn't supported by the driver, although it should be supported by the HDMI standard. Here's the excerpt from alsa-info.sh concerning the card: Codec: ATI R6xx HDMI Address: 0 AFG Function Id: 0x1 (unsol 0) Vendor Id: 0x1002aa01 Subsystem Id: 0x00aa0100 Revision Id: 0x100000 No Modem Function Group found Default PCM: rates [0x40]: 48000 bits [0x2]: 16 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A GPIO: io=0, o=0, i=0, unsolicited=0, wake=0 Node 0x02 [Audio Output] wcaps 0x201: Stereo Digital Control: name="IEC958 Playback Con Mask", index=0, device=0 Control: name="IEC958 Playback Pro Mask", index=0, device=0 Control: name="IEC958 Playback Default", index=0, device=0 Control: name="IEC958 Playback Switch", index=0, device=0 Device: name="HDMI 0", type="HDMI", device=3 Converter: stream=1, channel=0 Digital: Enabled GenLevel Digital category: 0x2 Node 0x03 [Pin Complex] wcaps 0x400381: Stereo Digital Pincap 0x00000094: OUT Detect HDMI Pin Default 0x18560010: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0x1, Sequence = 0x0 Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Connection: 1 0x02 Full data is at http://www.alsa-project.org/db/?f=b3f67a0890f9878b7b3f345578e24eda0aaa59ac Thanks, Xav -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 6

[Bug 65730] New: no sound via HDMI for Radeon 6850 mesa driver
by bugzilla-daemon＠freedesktop.org 13 Jul '15

13 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=65730 Priority: medium Bug ID: 65730 Assignee: dri-devel(a)lists.freedesktop.org Summary: no sound via HDMI for Radeon 6850 mesa driver Severity: normal Classification: Unclassified OS: Linux (All) Reporter: jasontheparamedic(a)hotmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: Drivers/DRI/R600 Product: Mesa Greetings, this is my first bug report so I apologize if it is placed in the wrong section. I am unable to get sound via HDMI cable using the open source driver for my Radeon 6850. I have (X)ubuntu 13.04 32bit system, using mesa 9.2, as provided by the xorg-edgers ppa, using all appropriate updates as passed downstream by the ppa. Using the FGLRX driver does fix the sound issue along with providing a high level of hardware acceleration, but it does cripple me being able to play on some emulators due to the well-known buggy nature of the FGLRX driver. I already made a report on the askubuntu.com forums, but so far there has been no response. My motherboard's native sound card is broken, so currently I have my computer speakers plugged into the HD monitor, hence HDMI sound is my only choice at this time. Here is a link to my askubuntu question (so as to avoid duplication of effort with providing info). http://askubuntu.com/questions/306196/no-sound-via-hdmi-using-xubuntu-13-04… Thanks in advance for any assistance. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 70689] New: Periodic system freezes on Linux 3.11-rc4 and later
by bugzilla-daemon＠freedesktop.org 13 Jul '15

13 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=70689 Priority: medium Bug ID: 70689 Assignee: dri-devel(a)lists.freedesktop.org Summary: Periodic system freezes on Linux 3.11-rc4 and later Severity: normal Classification: Unclassified OS: All Reporter: krejzi(a)email.com Hardware: Other Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Ever since Linux 3.11-rc4 (still present in 3.12-rc6), when both Radeon and Intel GPUs are enabled on a hybrid graphics laptop, system freezes (well, the picture freezes) every minute or two, then unfreezes and so on, making system unusable. When I disable radeon graphics card via vgaswitcheroo, freezes stop. I have, however, discovered that when radeon driver gets loaded before i915 one, freezes happen. If i915 manages to get loaded before radeon, freezes don't happen. When both are built into kernel, radeon driver gets always loaded before i915. This behaviour wasn't present in 3.11-rc3 kernel. Discrete card is Radeon HD 6450M and integrated one is Intel HD 3000. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 71226] New: Colors occasionally broken on DCE5 Barts (HD69xx)
by bugzilla-daemon＠freedesktop.org 13 Jul '15

13 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=71226 Priority: medium Bug ID: 71226 Assignee: dri-devel(a)lists.freedesktop.org Summary: Colors occasionally broken on DCE5 Barts (HD69xx) Severity: normal Classification: Unclassified OS: All Reporter: zajec5(a)gmail.com Hardware: Other Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI >From time to time colors on my displays appear broken. It happens randomly and is pretty hard to reproduce. -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 78221] New: 3.16 RC1: AMD R9 270 GPU locks up on some heavy 2D activity - GPU VM fault occurs. (possibly DMA copying issue strikes back?)
by bugzilla-daemon＠bugzilla.kernel.org 10 Jul '15

10 Jul '15

https://bugzilla.kernel.org/show_bug.cgi?id=78221 Bug ID: 78221 Summary: 3.16 RC1: AMD R9 270 GPU locks up on some heavy 2D activity - GPU VM fault occurs. (possibly DMA copying issue strikes back?) Product: Drivers Version: 2.5 Kernel Version: 3.16-rc1 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: t3st3r(a)mail.ru Regression: No Configuration: AMD R9 270 with 3.16-rc1 kernel. Ubuntu 14.04 + oibaf PPA used as recent opensource graphics stack (MESA 10.3 git). XFCE used as DE, compositing is off. To reproduce: Intermittent bug. R9 270 GPU can sometimes lock up on some heavy 2D-based loads. Known way to toggle bug is to install Battle for Wesnoth game from ubuntu repos and allow game to display some map with many units/heavy animations when running in windowed mode (BfW is SDL-based, 2D-only game, it does not makes GL calls, etc). In random intervals, usually in range of 30 minutes, GPU could lose stability and could lock up. Special considerations: 1) GPU recovery often succeeds in this case. Yet its bad to have 20 seconds of black screen and sometimes it can fail to recover after multiple GPU crashes. 2) Kernels prior 3.15 had similar issue. Kernel 3.15 (release version but not -RCs) has been rock solid and never crashed GPU to the best of my knowledge, no matter what I attempted. Now 3.16-rc1 crashes again. 3) Taking 2) into account and such verioning I suspect it could have something to do with commit b5be1a839a33634393394e4782edaa37a4bc1a1e or somewhere around. Possibly its what reintroduced lockups in 3.16 again. Maybe underlying reasons of deadlocks were not fixed for R9 270? 4) GPU seems to be stable under 3D loads I've attempted - it does not crashes even after hours of quite demanding 3D loads like games, etc. Only some specific 2D loads can cause such issues. Crash details are looking like this: ===CUT=== Jun 18 03:10:01 localhost kernel: [26125.102351] radeon 0000:01:00.0: ring 0 stalled for more than 10263msec Jun 18 03:10:01 localhost kernel: [26125.102362] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000445274 last fence id 0x0000000000445273 on ring 0) Jun 18 03:10:01 localhost kernel: [26125.102370] radeon 0000:01:00.0: failed to get a new IB (-35) Jun 18 03:10:01 localhost kernel: [26125.671219] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0018 address=0x00000000803dae00 flags=0x0000] Jun 18 03:10:01 localhost kernel: [26125.671232] AMD-Vi: Event logged [ Jun 18 03:10:01 localhost kernel: [26125.671232] radeon 0000:01:00.0: Saved 23200 dwords of commands on ring 0. Jun 18 03:10:01 localhost kernel: [26125.671240] IO_PAGE_FAULT device=01:00.0 domain=0x0018 address=0x00000000803dae30 flags=0x0020] Jun 18 03:10:01 localhost kernel: [26125.671243] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0018 address=0x0000000080000100 flags=0x0020] Jun 18 03:10:01 localhost kernel: [26125.671248] AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0018 address=0x00000000803dad00 flags=0x0000] Jun 18 03:10:01 localhost kernel: [26125.671361] radeon 0000:01:00.0: GPU softreset: 0x0000006C Jun 18 03:10:01 localhost kernel: [26125.671365] radeon 0000:01:00.0: GRBM_STATUS = 0xA0003028 Jun 18 03:10:01 localhost kernel: [26125.671367] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 Jun 18 03:10:01 localhost kernel: [26125.671370] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 Jun 18 03:10:01 localhost kernel: [26125.671372] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 Jun 18 03:10:01 localhost kernel: [26125.671483] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 Jun 18 03:10:01 localhost kernel: [26125.671485] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jun 18 03:10:01 localhost kernel: [26125.671487] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00010000 Jun 18 03:10:01 localhost kernel: [26125.671489] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000002 Jun 18 03:10:01 localhost kernel: [26125.671492] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80010243 Jun 18 03:10:01 localhost kernel: [26125.671494] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44483146 Jun 18 03:10:01 localhost kernel: [26125.671496] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C84246 Jun 18 03:10:01 localhost kernel: [26125.671499] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jun 18 03:10:01 localhost kernel: [26125.671501] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jun 18 03:10:02 localhost kernel: [26126.218193] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF Jun 18 03:10:02 localhost kernel: [26126.218247] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100140 Jun 18 03:10:02 localhost kernel: [26126.219404] radeon 0000:01:00.0: GRBM_STATUS = 0x00003028 Jun 18 03:10:02 localhost kernel: [26126.219407] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 Jun 18 03:10:02 localhost kernel: [26126.219409] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 Jun 18 03:10:02 localhost kernel: [26126.219411] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 Jun 18 03:10:02 localhost kernel: [26126.219522] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 Jun 18 03:10:02 localhost kernel: [26126.219524] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jun 18 03:10:02 localhost kernel: [26126.219526] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 Jun 18 03:10:02 localhost kernel: [26126.219528] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 Jun 18 03:10:02 localhost kernel: [26126.219530] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 Jun 18 03:10:02 localhost kernel: [26126.219533] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Jun 18 03:10:02 localhost kernel: [26126.219535] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 Jun 18 03:10:02 localhost kernel: [26126.219780] radeon 0000:01:00.0: GPU reset succeeded, trying to resume Jun 18 03:10:02 localhost kernel: [26126.246602] [drm] probing gen 2 caps for device 1002:5a16 = 31cd02/0 Jun 18 03:10:02 localhost kernel: [26126.246606] [drm] PCIE gen 2 link speeds already enabled Jun 18 03:10:02 localhost kernel: [26126.250269] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000). Jun 18 03:10:02 localhost kernel: [26126.250405] radeon 0000:01:00.0: WB enabled Jun 18 03:10:02 localhost kernel: [26126.250408] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff88041651fc00 Jun 18 03:10:02 localhost kernel: [26126.250411] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff88041651fc04 Jun 18 03:10:02 localhost kernel: [26126.250413] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff88041651fc08 Jun 18 03:10:02 localhost kernel: [26126.250415] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff88041651fc0c Jun 18 03:10:02 localhost kernel: [26126.250417] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff88041651fc10 Jun 18 03:10:02 localhost kernel: [26126.251393] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90011db5a18 Jun 18 03:10:02 localhost kernel: [26126.436426] [drm] ring test on 0 succeeded in 3 usecs Jun 18 03:10:02 localhost kernel: [26126.436432] [drm] ring test on 1 succeeded in 1 usecs Jun 18 03:10:02 localhost kernel: [26126.436437] [drm] ring test on 2 succeeded in 1 usecs Jun 18 03:10:02 localhost kernel: [26126.436500] [drm] ring test on 3 succeeded in 2 usecs Jun 18 03:10:02 localhost kernel: [26126.436510] [drm] ring test on 4 succeeded in 1 usecs Jun 18 03:10:02 localhost kernel: [26126.613588] [drm] ring test on 5 succeeded in 2 usecs Jun 18 03:10:02 localhost kernel: [26126.613595] [drm] UVD initialized successfully. Jun 18 03:10:04 localhost kernel: [26128.294193] SysRq : Emergency Sync Jun 18 03:10:04 localhost kernel: [26128.309427] Emergency Sync complete Jun 18 03:10:12 localhost kernel: [26136.610250] radeon 0000:01:00.0: ring 0 stalled for more than 10001msec Jun 18 03:10:12 localhost kernel: [26136.610260] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000445396 last fence id 0x0000000000445273 on ring 0) Jun 18 03:10:12 localhost kernel: [26136.610266] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). Jun 18 03:10:12 localhost kernel: [26136.610273] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). Jun 18 03:10:12 localhost kernel: [26136.610278] radeon 0000:01:00.0: ib ring test failed (-35). Jun 18 03:10:13 localhost kernel: [26137.083011] SysRq : Emergency Sync Jun 18 03:10:13 localhost kernel: [26137.098644] Emergency Sync complete Jun 18 03:10:13 localhost kernel: [26137.164779] radeon 0000:01:00.0: GPU softreset: 0x00000048 Jun 18 03:10:13 localhost kernel: [26137.164782] radeon 0000:01:00.0: GRBM_STATUS = 0xA0003028 Jun 18 03:10:13 localhost kernel: [26137.164785] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 Jun 18 03:10:13 localhost kernel: [26137.164787] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 Jun 18 03:10:13 localhost kernel: [26137.164789] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 Jun 18 03:10:13 localhost kernel: [26137.164911] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 Jun 18 03:10:13 localhost kernel: [26137.164913] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jun 18 03:10:13 localhost kernel: [26137.164918] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00010000 Jun 18 03:10:13 localhost kernel: [26137.164925] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000002 Jun 18 03:10:13 localhost kernel: [26137.164930] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80010243 Jun 18 03:10:13 localhost kernel: [26137.164933] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Jun 18 03:10:13 localhost kernel: [26137.164935] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 Jun 18 03:10:13 localhost kernel: [26137.164937] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jun 18 03:10:13 localhost kernel: [26137.164940] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jun 18 03:10:13 localhost kernel: [26137.709342] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF Jun 18 03:10:13 localhost kernel: [26137.709397] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 Jun 18 03:10:13 localhost kernel: [26137.710554] radeon 0000:01:00.0: GRBM_STATUS = 0x00003028 Jun 18 03:10:13 localhost kernel: [26137.710556] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 Jun 18 03:10:13 localhost kernel: [26137.710558] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 Jun 18 03:10:13 localhost kernel: [26137.710560] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 Jun 18 03:10:13 localhost kernel: [26137.710681] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 Jun 18 03:10:13 localhost kernel: [26137.710683] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jun 18 03:10:13 localhost kernel: [26137.710685] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 Jun 18 03:10:13 localhost kernel: [26137.710687] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 Jun 18 03:10:13 localhost kernel: [26137.710689] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 Jun 18 03:10:13 localhost kernel: [26137.710695] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Jun 18 03:10:13 localhost kernel: [26137.710706] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 Jun 18 03:10:13 localhost kernel: [26137.710960] radeon 0000:01:00.0: GPU reset succeeded, trying to resume Jun 18 03:10:13 localhost kernel: [26137.724290] [drm] probing gen 2 caps for device 1002:5a16 = 31cd02/0 Jun 18 03:10:13 localhost kernel: [26137.724294] [drm] PCIE gen 2 link speeds already enabled Jun 18 03:10:13 localhost kernel: [26137.728012] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000). Jun 18 03:10:13 localhost kernel: [26137.728147] radeon 0000:01:00.0: WB enabled Jun 18 03:10:13 localhost kernel: [26137.728150] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff88041651fc00 Jun 18 03:10:13 localhost kernel: [26137.728152] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff88041651fc04 Jun 18 03:10:13 localhost kernel: [26137.728154] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff88041651fc08 Jun 18 03:10:13 localhost kernel: [26137.728156] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff88041651fc0c Jun 18 03:10:13 localhost kernel: [26137.728158] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff88041651fc10 Jun 18 03:10:13 localhost kernel: [26137.729140] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90011db5a18 Jun 18 03:10:14 localhost kernel: [26137.914127] [drm] ring test on 0 succeeded in 3 usecs Jun 18 03:10:14 localhost kernel: [26137.914133] [drm] ring test on 1 succeeded in 1 usecs Jun 18 03:10:14 localhost kernel: [26137.914138] [drm] ring test on 2 succeeded in 1 usecs Jun 18 03:10:14 localhost kernel: [26137.914202] [drm] ring test on 3 succeeded in 2 usecs Jun 18 03:10:14 localhost kernel: [26137.914211] [drm] ring test on 4 succeeded in 1 usecs Jun 18 03:10:14 localhost kernel: [26138.091289] [drm] ring test on 5 succeeded in 2 usecs Jun 18 03:10:14 localhost kernel: [26138.091296] [drm] UVD initialized successfully. Jun 18 03:10:14 localhost kernel: [26138.091385] [drm] ib test on ring 0 succeeded in 0 usecs Jun 18 03:10:14 localhost kernel: [26138.091475] [drm] ib test on ring 1 succeeded in 0 usecs Jun 18 03:10:14 localhost kernel: [26138.091601] [drm] ib test on ring 2 succeeded in 0 usecs Jun 18 03:10:14 localhost kernel: [26138.091644] [drm] ib test on ring 3 succeeded in 0 usecs Jun 18 03:10:14 localhost kernel: [26138.091679] [drm] ib test on ring 4 succeeded in 0 usecs Jun 18 03:10:16 localhost kernel: [26140.121922] SysRq : Keyboard mode set to system default Jun 18 03:10:18 localhost kernel: [26141.841306] SysRq : Emergency Sync Jun 18 03:10:18 localhost kernel: [26141.866011] Emergency Sync complete Jun 18 03:10:18 localhost kernel: [26142.361117] SysRq : Emergency Sync Jun 18 03:10:18 localhost kernel: [26142.383541] Emergency Sync complete Jun 18 03:10:24 localhost kernel: [26148.238943] radeon 0000:01:00.0: ring 5 stalled for more than 10000msec Jun 18 03:10:24 localhost kernel: [26148.238952] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000004 last fence id 0x0000000000000002 on ring 5) Jun 18 03:10:24 localhost kernel: [26148.238958] [drm:uvd_v1_0_ib_test] *ERROR* radeon: fence wait failed (-35). Jun 18 03:10:24 localhost kernel: [26148.238966] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-35). Jun 18 03:10:24 localhost kernel: [26148.238995] [drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed Jun 18 03:10:24 localhost kernel: [26148.262523] radeon 0000:01:00.0: GPU fault detected: 146 0x05428804 Jun 18 03:10:24 localhost kernel: [26148.262534] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0000A1AA Jun 18 03:10:24 localhost kernel: [26148.262539] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02088004 Jun 18 03:10:24 localhost kernel: [26148.262544] VM fault (0x04, vmid 1) at page 41386, read from TC (136) Jun 18 03:10:24 localhost kernel: [26148.262552] radeon 0000:01:00.0: GPU fault detected: 146 0x06824804 Jun 18 03:10:24 localhost kernel: [26148.262556] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jun 18 03:10:24 localhost kernel: [26148.262559] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jun 18 03:10:24 localhost kernel: [26148.262563] VM fault (0x00, vmid 0) at page 0, read from unknown (0) Jun 18 03:10:24 localhost kernel: [26148.262570] radeon 0000:01:00.0: GPU fault detected: 146 0x05428404 Jun 18 03:10:24 localhost kernel: [26148.262573] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jun 18 03:10:24 localhost kernel: [26148.262577] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jun 18 03:10:24 localhost kernel: [26148.262580] VM fault (0x00, vmid 0) at page 0, read from unknown (0) Jun 18 03:10:24 localhost kernel: [26148.262586] radeon 0000:01:00.0: GPU fault detected: 146 0x06c24404 Jun 18 03:10:24 localhost kernel: [26148.262590] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jun 18 03:10:24 localhost kernel: [26148.262593] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jun 18 03:10:24 localhost kernel: [26148.262597] VM fault (0x00, vmid 0) at page 0, read from unknown (0) Jun 18 03:10:24 localhost kernel: [26148.262603] radeon 0000:01:00.0: GPU fault detected: 146 0x06228804 Jun 18 03:10:24 localhost kernel: [26148.262606] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jun 18 03:10:24 localhost kernel: [26148.262610] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jun 18 03:10:24 localhost kernel: [26148.262613] VM fault (0x00, vmid 0) at page 0, read from unknown (0) Jun 18 03:10:24 localhost kernel: [26148.262619] radeon 0000:01:00.0: GPU fault detected: 146 0x07024804 Jun 18 03:10:24 localhost kernel: [26148.262623] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jun 18 03:10:24 localhost kernel: [26148.262626] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jun 18 03:10:24 localhost kernel: [26148.262629] VM fault (0x00, vmid 0) at page 0, read from unknown (0) Jun 18 03:10:24 localhost kernel: [26148.262635] radeon 0000:01:00.0: GPU fault detected: 146 0x0802c804 Jun 18 03:10:24 localhost kernel: [26148.262639] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jun 18 03:10:24 localhost kernel: [26148.262642] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jun 18 03:10:24 localhost kernel: [26148.262646] VM fault (0x00, vmid 0) at page 0, read from unknown (0) Jun 18 03:10:24 localhost kernel: [26148.262652] radeon 0000:01:00.0: GPU fault detected: 146 0x0882c404 Jun 18 03:10:24 localhost kernel: [26148.262655] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jun 18 03:10:24 localhost kernel: [26148.262659] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 ===CUT=== (message about VM fault repeats several thousands times, some messages omitted as they make full log about 3.5Mb). -- You are receiving this mail because: You are watching the assignee of the bug.

1 24

[PATCH 0/3] drm/ttm: hard to swim in an empty pool
by Jérôme Glisse 08 Jul '15

08 Jul '15

So it seems there was several issue with the various ttm pool. The obvious one is fixed in patch 2 where the always empty pool syndrom is addressed. However the pool size are kind of crazy and because before some pool were never actualy fill we might never have experience the hill effect of the crazy maximum limit. This is what is addressed by first patch. Last patch cook it up further so that under memory pressure the pool size is divided by 2 each time a shrinker is run on a pool. There is a timeout to restore the pool size on next allocation. Idea here is that memory should not last and if it last then shrinker will keep minimize the pool size and anyway thing are probably already sluggish once we it the shrinker path. Of course because this fix thing in ttm memory allocation this need careful testing. So before pushing anything i would like to see more people testing this. Cheers, Jérôme

10 28

[Bug 36563] New: Unity locks up with latest xorg/mesa/dri/drm
by bugzilla-daemon＠freedesktop.org 07 Jul '15

07 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=36563 Summary: Unity locks up with latest xorg/mesa/dri/drm Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: General AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: ernstp(a)gmail.com #0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:136 #1 0x00007f643c9615b4 in _L_lock_944 () from /lib/x86_64-linux-gnu/libpthread.so.0 #2 0x00007f643c9613ca in __pthread_mutex_lock (mutex=0xf09a68) at pthread_mutex_lock.c:61 #3 0x00007f6432d91f9d in radeon_bo (radeon=0xf09a10, handle=21, size=0, alignment=0) at radeon_bo.c:78 #4 0x00007f6432d8d612 in r600_bo_handle (radeon=0xf09a10, handle=21, array_mode=0x7fff0d9888ec) at r600_bo.c:83 #5 0x00007f6432d7770d in r600_texture_from_handle (screen=0xf09bd0, templ=0x7fff0d988990, whandle=0x7fff0d9889d0) at r600_texture.c:484 #6 0x00007f6432d8b29a in dri2_drawable_process_buffers (drawable=0x7f6434095e20, statts=<value optimized out>, count=228100616) at dri2.c:253 #7 dri2_allocate_textures (drawable=0x7f6434095e20, statts=<value optimized out>, count=228100616) at dri2.c:363 #8 0x00007f6432d8c1f7 in dri_st_framebuffer_validate (stfbi=<value optimized out>, statts=0x7fff0d988a80, count=1, out=0x0) at dri_drawable.c:73 #9 0x00007f6432d8c370 in dri_drawable_validate_att (pDRICtx=<value optimized out>, target=3553, format=8410, dPriv=<value optimized out>) at dri_drawable.c:185 #10 dri_set_tex_buffer2 (pDRICtx=<value optimized out>, target=3553, format=8410, dPriv=<value optimized out>) at dri_drawable.c:199 #11 0x00007f6433bc41fe in TfpTexture::bindPixmapToTexture(unsigned long, int, int, int) () from /usr/lib/compiz/libopengl.so #12 0x00007f6433bc9cf4 in boost::detail::function::function_invoker4<GLTexture::List (*)(unsigned long, int, int, int), GLTexture::List, unsigned long, int, int, int>::invoke(boost::detail::function::function_buffer&, unsigned long, int, int, int) () from /usr/lib/compiz/libopengl.so #13 0x00007f6433bc3cb4 in GLTexture::bindPixmapToTexture(unsigned long, int, int, int) () from /usr/lib/compiz/libopengl.so #14 0x00007f643072ff79 in DecorTexture::DecorTexture(unsigned long) () from /usr/lib/compiz/libdecor.so #15 0x00007f6430730095 in DecorScreen::getTexture(unsigned long) () from /usr/lib/compiz/libdecor.so #16 0x00007f6430730678 in Decoration::create(unsigned long, unsigned long) () from /usr/lib/compiz/libdecor.so #17 0x00007f6430730704 in DecorWindow::updateDecoration() () from /usr/lib/compiz/libdecor.so #18 0x00007f6430733593 in DecorScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libdecor.so #19 0x000000000044e9a3 in CompScreen::handleEvent(_XEvent*) () #20 0x000000000044e9a3 in CompScreen::handleEvent(_XEvent*) () #21 0x00007f642fef44bf in RegexScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libregex.so #22 0x000000000044e9a3 in CompScreen::handleEvent(_XEvent*) () #23 0x000000000044e9a3 in CompScreen::handleEvent(_XEvent*) () #24 0x00007f642f3c97bc in MoveScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libmove.so #25 0x000000000044e9a3 in CompScreen::handleEvent(_XEvent*) () #26 0x000000000044e9a3 in CompScreen::handleEvent(_XEvent*) () #27 0x000000000044e9a3 in CompScreen::handleEvent(_XEvent*) () #28 0x00007f642d2bb1ad in WorkaroundsScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libworkarounds.so #29 0x000000000044e9a3 in CompScreen::handleEvent(_XEvent*) () #30 0x00007f642ce7c396 in ResizeScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libresize.so #31 0x000000000044e9a3 in CompScreen::handleEvent(_XEvent*) () #32 0x00007f642cc626c1 in FadeScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libfade.so #33 0x000000000044e9a3 in CompScreen::handleEvent(_XEvent*) () #34 0x00007f642ca4d0cb in UnityMTGrabHandlesScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libunitymtgrabhandles.so #35 0x000000000044e9a3 in CompScreen::handleEvent(_XEvent*) () #36 0x00007f642c62a3c7 in PrivateScaleScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libscale.so #37 0x000000000044e9a3 in CompScreen::handleEvent(_XEvent*) () #38 0x00007f642c40f3c0 in SessionScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libsession.so #39 0x000000000044e9a3 in CompScreen::handleEvent(_XEvent*) () #40 0x00007f642c174829 in UnityScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libunityshell.so #41 0x000000000044e9a3 in CompScreen::handleEvent(_XEvent*) () #42 0x000000000042e59b in PrivateScreen::processEvents() () #43 0x0000000000455958 in CompEventSource::callback() () #44 0x00007f643db83daf in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/libglibmm-2.4.so.1 #45 0x00007f643d032bcd in g_main_dispatch (context=0xea3f30) at /build/buildd/glib2.0-2.28.6/./glib/gmain.c:2440 #46 g_main_context_dispatch (context=0xea3f30) at /build/buildd/glib2.0-2.28.6/./glib/gmain.c:3013 #47 0x00007f643d0333a8 in g_main_context_iterate (context=0xea3f30, block=<value optimized out>, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.28.6/./glib/gmain.c:3091 #48 0x00007f643d0339f2 in g_main_loop_run (loop=0xee5620) at /build/buildd/glib2.0-2.28.6/./glib/gmain.c:3299 #49 0x000000000042a2ea in CompScreen::eventLoop() () #50 0x0000000000423160 in main () -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 9

[Bug 75357] New: Barts (HD6850): Failure in evergreen_surface_check_2d
by bugzilla-daemon＠freedesktop.org 06 Jul '15

06 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=75357 Priority: medium Bug ID: 75357 Assignee: dri-devel(a)lists.freedesktop.org Summary: Barts (HD6850): Failure in evergreen_surface_check_2d Severity: major Classification: Unclassified OS: Linux (All) Reporter: oogway.droid(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 94554 --> https://bugs.freedesktop.org/attachment.cgi?id=94554&action=edit dmesg radeon 6850 I'm running Fedora 20 with the latest distro kernel (3.13.3). I'm running Gnome shell and see very frequent hangs. Its usually observed when the system has been inactive for a while and the monitor goes into powersave mode. When I try to activate the system via keyboard/mouse I get a black screen. I cannot switch to a VT as well. SSH still works and the system is responsive via ssh. DPM is not enabled. However I did switch the card to "low" power profile after boot. echo "low" > /sys/class/drm/card0/device/power_profile cat /sys/kernel/debug/dri/0/radeon_pm_info default engine clock: 775000 kHz current engine clock: 99990 kHz default memory clock: 1000000 kHz current memory clock: 150000 kHz voltage: 950 mV PCIE lanes: 16 dmesg shows the following: [ 8443.493242] radeon 0000:01:00.0: evergreen_surface_check_2d:277 texture pitch 1920 invalid must be aligned with 512 [ 8443.493249] radeon 0000:01:00.0: evergreen_cs_track_validate_texture:826 texture invalid 0x1dfc3bc1 0x40000437 0x060a0000 0x00000000 0x80000000 0x800304da [ 8443.493251] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! [ 8455.699835] radeon 0000:01:00.0: evergreen_surface_check_2d:277 texture pitch 1920 invalid must be aligned with 512 [ 8455.699841] radeon 0000:01:00.0: evergreen_cs_track_validate_texture:826 texture invalid 0x1dfc3bc1 0x40000437 0x060a0000 0x00000000 0x80000000 0x800304da [ 8455.699844] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! [ 8456.748217] radeon 0000:01:00.0: evergreen_surface_check_2d:277 texture pitch 1920 invalid must be aligned with 512 [ 8456.748223] radeon 0000:01:00.0: evergreen_cs_track_validate_texture:826 texture invalid 0x1dfc3bc1 0x40000437 0x060a0000 0x00000000 0x80000000 0x800304da [ 8456.748226] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! [ 8605.668059] radeon 0000:01:00.0: evergreen_surface_check_2d:277 texture pitch 1920 invalid must be aligned with 512 [ 8605.668066] radeon 0000:01:00.0: evergreen_cs_track_validate_texture:826 texture invalid 0x1dfc3bc1 0x40000437 0x060a0000 0x00000000 0x80000000 0x800304da [ 8605.668068] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream ! -- You are receiving this mail because: You are the assignee for the bug.

1 14

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2014