dri-devel March 2014

dri-devel@lists.freedesktop.org

144 participants
926 discussions

[Bug 29842] New: Radeon runs very hot
by bugzilla-daemon＠bugzilla.kernel.org 19 Feb '15

19 Feb '15

https://bugzilla.kernel.org/show_bug.cgi?id=29842 Summary: Radeon runs very hot Product: Drivers Version: 2.5 Kernel Version: 2.6.38-rc6 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: psusi(a)cfl.rr.com Regression: No The newer kernels read the temperature of my Radeon card, and report that it is running at around 80 C on an idle desktop. For comparison, my CPU is only 34 C. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

6 26

[Bug 76487] New: [PIGLIT,radeonsi] spec/{EXT_texture_array/fbo-generatemipmap-array, ARB_framebuffer_object/fbo-generatemipmap-3d} RGB9_E5 crashes
by bugzilla-daemon＠freedesktop.org 19 Feb '15

19 Feb '15

https://bugs.freedesktop.org/show_bug.cgi?id=76487 Priority: medium Bug ID: 76487 Assignee: dri-devel(a)lists.freedesktop.org Summary: [PIGLIT,radeonsi] spec/{EXT_texture_array/fbo-generatemipmap-array,ARB_f ramebuffer_object/fbo-generatemipmap-3d} RGB9_E5 crashes Severity: normal Classification: Unclassified OS: Linux (All) Reporter: kai(a)dev.carbon-project.org Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 96212 --> https://bugs.freedesktop.org/attachment.cgi?id=96212&action=edit GDB backtrace and register info of the crash For the first time ever, since I'm having a PITCAIRN GPU I was able to run a full Piglit quick test without crashing my X (hooray for that). During the test I came across two similar crashes in "spec/EXT_texture_array/fbo-generatemipmap-array RGB9_E5" and "spec/ARB_framebuffer_object/fbo-generatemipmap-3d RGB9_E5" (see the attached GDB backtrace; the backtrace is for spec/EXT_texture_array/fbo-generatemipmap-array RGB9_E5", but the second crashed in the same function on the same line and as it's the same format, that is tested, I guess, these are related, if not, I'm happy to provide a backtrace for the second case as well and split the bugs). I can't tell whether this is a regression or not, since this was the first time I was able to run Piglit on this machine without getting a corrupted results file, due to the crash of the X server. My graphics stack is: GPU: "PITCAIRN" (ChipID = 0x6819) Linux: 3.13.6 libdrm: 2.4.52-1 LLVM: SVN:trunk/r204517 libclc: Git:master/1e278a7b04 Mesa: Git:master/4c79f088c0 GLAMOR: Git:master/a4fbc7732a (Standalone) DDX: Git:master/ea6d0affe5 X: 1.15.0-2 Let me know if you need further information. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 60639] New: RV635: Kernel displays black screen when monitor is connect via DisplayPort
by bugzilla-daemon＠bugzilla.kernel.org 17 Feb '15

17 Feb '15

https://bugzilla.kernel.org/show_bug.cgi?id=60639 Bug ID: 60639 Summary: RV635: Kernel displays black screen when monitor is connect via DisplayPort Product: Drivers Version: 2.5 Kernel Version: 3.10.3 (and earlier) Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: kernspam(a)schreib-doch-mal-wieder.de Regression: No When the monitor is connected via DisplayPort I can see grub but once the kernel takes over, the screen goes black. When the same monitor is connected via DVI everything works. Adding the kernel option "video=DP-1:1920x1200@75" makes at least the kernel messages and virtual consoles work. However, when X starts the screen goes black again. This might be related to the bug reported here: https://bugzilla.novell.com/show_bug.cgi?id=752593 Modeline from EDID: Detailed mode: Clock 154.000 MHz, 518 mm x 324 mm 1920 1968 2000 2080 hborder 0 1200 1203 1209 1235 vborder 0 +hsync -vsync Monitor ranges (GTF): 50-61Hz V, 30-83kHz H, max dotclock 170MHz Kernel 3.10.3 (but also tested with 3.9.x and 3.8.x) Graphic chip: ATI Mobility FireGL V5700 (the second intel chip should be disabled) -- You are receiving this mail because: You are watching the assignee of the bug.

1 24

[Bug 64471] New: Radeon HD6570 lockup in Brütal Legend
by bugzilla-daemon＠freedesktop.org 07 Feb '15

07 Feb '15

https://bugs.freedesktop.org/show_bug.cgi?id=64471 Priority: medium Bug ID: 64471 Assignee: dri-devel(a)lists.freedesktop.org Summary: Radeon HD6570 lockup in Brütal Legend Severity: major Classification: Unclassified OS: Linux (All) Reporter: zboszor(a)pr.hu Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 79165 --> https://bugs.freedesktop.org/attachment.cgi?id=79165&action=edit Lockup from "new game" I tried Brütal Legend on Fedora 18/x86_64, the game itself if i386. The system has these newer-than-Fedora18 components: kernel 3.9+ (commit 51a26ae7a14b85c99c9be470c2d28eeeba0f26a3) libdrm 2.4.44 from 2.4.44-2.fc20 SRPM from Koji recompiled on F18 llvm-3.3 from May 7, before branching to 3.3 was done mesa 9.2 from May 7, commit was around 03ef60681e61a52dee7fa3285618c313cf13f50c compiled into an RPM with float textures enabled: $ rpm -q mesa-libGL mesa-libGL-9.2-0.1.fc18.x86_64 mesa-libGL-9.2-0.1.fc18.i686 The game makes the Radeon chip lock up, reliably at the same point, which is when the game starts after the long cutscene. Attached are two dmesgs, showing the same lockup. The first occurred when I started a new game and watched through the cutscene. The second occurred when I tried to continue the auto-saved game. -- You are receiving this mail because: You are the assignee for the bug.

1 33

[Bug 75005] New: "Upvoid" segfault in radeonsi/llvm
by bugzilla-daemon＠freedesktop.org 06 Feb '15

06 Feb '15

https://bugs.freedesktop.org/show_bug.cgi?id=75005 Priority: medium Bug ID: 75005 Assignee: dri-devel(a)lists.freedesktop.org Summary: "Upvoid" segfault in radeonsi/llvm Severity: normal Classification: Unclassified OS: All Reporter: haagch.christoph(a)googlemail.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 94105 --> https://bugs.freedesktop.org/attachment.cgi?id=94105&action=edit gdb "bt full" of the segfault Software: Latest mesa git etc. The program causing it is closed source: https://upvoid.com/ On intel ivy bridge it works. On radeonsi it segfaults every time when starting the game. full gdb backtrace with at least most debug information is attached. -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 75211] New: radeonsi/llvm SIGABRT in Antichamber (UDK)
by bugzilla-daemon＠freedesktop.org 06 Feb '15

06 Feb '15

https://bugs.freedesktop.org/show_bug.cgi?id=75211 Priority: medium Bug ID: 75211 Assignee: dri-devel(a)lists.freedesktop.org Summary: radeonsi/llvm SIGABRT in Antichamber (UDK) Severity: normal Classification: Unclassified OS: All Reporter: haagch.christoph(a)googlemail.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 94363 --> https://bugs.freedesktop.org/attachment.cgi?id=94363&action=edit backtrace without debug symbols HD 7970M, mesa recent git, llvm 3.5 recent svn. Antichamber based on Unreal Engine is available in the latest Humble Bundle. The crash doesn't seem to happen deterministically, I produced such a crash two times now by playing the game for a few minutes and then it randomly crashed. UDKGame-Linux: /build/lib32-llvm-svn/src/llvm/include/llvm/CodeGen/SlotIndexes.h:417: llvm::SlotIndex llvm::SlotIndexes::getInstructionIndex(const llvm::MachineInstr*) const: Assertion `itr != mi2iMap.end() && "Instruction not found in maps."' failed. Program received signal SIGABRT, Aborted. 0xf7fdb430 in __kernel_vsyscall () The backtrace I attached is without debug symbols so maybe isn't too informative. Later I will compile with debug symbols and provide a better one if needed. -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 75361] New: freeze in Mass Effect 3 (wine)
by bugzilla-daemon＠freedesktop.org 06 Feb '15

06 Feb '15

https://bugs.freedesktop.org/show_bug.cgi?id=75361 Priority: medium Bug ID: 75361 Assignee: dri-devel(a)lists.freedesktop.org Summary: freeze in Mass Effect 3 (wine) Severity: normal Classification: Unclassified OS: Linux (All) Reporter: idd997733t(a)gmail.com Hardware: x86 (IA32) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 94560 --> https://bugs.freedesktop.org/attachment.cgi?id=94560&action=edit R600_DEBUG=fs,vs,gs,ps,cs dump Kernel:3.13.1/3.14_rc2 libdrm:git (21 february) mesa:git (21 february) llvm:svn (21 february) card: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz Edition] R600_DEBUG=hyperz and R600_DEBUG=nohyperz no effect Freeze in game. If use another video card (GF8800 on nouveau git) - work fine. Need dump apitrace? Let me know if you need further information. -- You are receiving this mail because: You are the assignee for the bug.

1 30

[Bug 73320] New: [radeonsi] LLVM runs out of registers during register allocation in Painkiller Hell & Damnation
by bugzilla-daemon＠freedesktop.org 06 Feb '15

06 Feb '15

https://bugs.freedesktop.org/show_bug.cgi?id=73320 Priority: medium Bug ID: 73320 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeonsi] LLVM runs out of registers during register allocation in Painkiller Hell & Damnation Severity: major Classification: Unclassified OS: Linux (All) Reporter: freedesktop.org(a)inequation.org Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa (this is possibly a duplicate of bug #72228) First of all, this report is based on a user's report - I do not have the software/hardware combo to reproduce. I can, however, provide Steam keys for the game to Mesa developers for free if it is needed, just shoot me an email. A user of Painkiller Hell & Damnation has reported crashes when using radeonsi from Mesa 10.1.0-devel (git-5a51c1b saucy-oibaf-ppa). LLVM aborts with the following message: LLVM ERROR: ran out of registers during register allocation Relevant part of the backtrace: #7 0xb7a20791 in __run_exit_handlers (status=status@entry=1, listp=0xb7b9d3e4 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:77 #8 0xb7a2081d in __GI_exit (status=1) at exit.c:99 #9 0xb5d28ee3 in llvm::report_fatal_error(llvm::Twine const&, bool) () from /usr/lib/i386-linux-gnu/libLLVM-3.4.so.1 #10 0xb5d28fdb in llvm::report_fatal_error(char const*, bool) () from /usr/lib/i386-linux-gnu/libLLVM-3.4.so.1 #11 0xb54cf6de in llvm::RegAllocBase::allocatePhysRegs() () from /usr/lib/i386-linux-gnu/libLLVM-3.4.so.1 #12 0xb54dec28 in ?? () from /usr/lib/i386-linux-gnu/libLLVM-3.4.so.1 #13 0xb545781e in llvm::MachineFunctionPass::runOnFunction(llvm::Function&) () from /usr/lib/i386-linux-gnu/libLLVM-3.4.so.1 #14 0xb5638974 in llvm::FPPassManager::runOnFunction(llvm::Function&) () from /usr/lib/i386-linux-gnu/libLLVM-3.4.so.1 #15 0xb5638a28 in llvm::FPPassManager::runOnModule(llvm::Module&) () from /usr/lib/i386-linux-gnu/libLLVM-3.4.so.1 #16 0xb563b195 in llvm::legacy::PassManagerImpl::run(llvm::Module&) () from /usr/lib/i386-linux-gnu/libLLVM-3.4.so.1 #17 0xb563b336 in llvm::legacy::PassManager::run(llvm::Module&) () from /usr/lib/i386-linux-gnu/libLLVM-3.4.so.1 #18 0xb5da1bb9 in ?? () from /usr/lib/i386-linux-gnu/libLLVM-3.4.so.1 #19 0xb5da1f30 in LLVMTargetMachineEmitToMemoryBuffer () from /usr/lib/i386-linux-gnu/libLLVM-3.4.so.1 #20 0xb6b92b17 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so #21 0xb6b80f30 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so #22 0xb6b81a9e in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so #23 0xb6b8a382 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so #24 0xb6b8a4e3 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so #25 0xb698f60e in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so #26 0xb6990966 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so #27 0xb6956443 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so #28 0xb695339e in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so #29 0xb6968230 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so #30 0xb6937891 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so #31 0xb6938e4c in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so #32 0xb6939254 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so #33 0xb693934f in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so #34 0x08b65086 in FMeshDrawingPolicy::DrawMesh(FMeshBatch const&, int) const () Anything I can do to improve the diagnostics? -- You are receiving this mail because: You are the assignee for the bug.

1 53

[Bug 75276] New: Implement VGPR Register Spilling
by bugzilla-daemon＠freedesktop.org 06 Feb '15

06 Feb '15

https://bugs.freedesktop.org/show_bug.cgi?id=75276 Priority: medium Bug ID: 75276 Assignee: dri-devel(a)lists.freedesktop.org Summary: Implement VGPR Register Spilling Severity: normal Classification: Unclassified OS: All Reporter: tstellar(a)gmail.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Register spilling is not implemented for VGPRs causing a number of applications to crash. -- You are receiving this mail because: You are the assignee for the bug.

1 67

[Bug 64867] New: Hangs on Cayman (HD6950) when watching flash/using vdpau
by bugzilla-daemon＠freedesktop.org 27 Jan '15

27 Jan '15

https://bugs.freedesktop.org/show_bug.cgi?id=64867 Priority: medium Bug ID: 64867 Assignee: dri-devel(a)lists.freedesktop.org Summary: Hangs on Cayman (HD6950) when watching flash/using vdpau Severity: normal Classification: Unclassified OS: Linux (All) Reporter: serafean(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Created attachment 79658 --> https://bugs.freedesktop.org/attachment.cgi?id=79658&action=edit dmesg after X freeze When watching a flash video (opera + flash-11.2.202.262 ) the kernel log starts filling up with [ 7009.603310] radeon 0000:01:00.0: GPU fault detected: 146 0x0e677004 [ 7009.603313] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 [ 7009.603316] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 to sometimes eventually hang the GPU. When this starts appearing there is graphic corruption everywhere. I also managed to reproduce this when playing back a video using mplayer with the vdpau backend. ( EnableLinuxHWVideoDecode=1 is commented out in /etc/adobe/mms.cfg) I managed to get a dmesg output after the GPU hang (attached) and then tried to save what is in /sys/kernel/debug/dri/0 but not knowing which was important, tried to do it in a bash for cycle, and got a complete hang. linux-3.10-rc1 mesa, libdrm, radeon ddx from git. might be related to https://bugs.freedesktop.org/show_bug.cgi?id=62959 , but piglit just finished fine. (fine = didn't hang in this case, still a bunch of "radeon_gem_object_create:69 alloc size 1365Mb bigger than 256Mb limit" in the logs). Additional info : I have a dual screen setup. Anything more you need, I'll be happy to provide. -- You are receiving this mail because: You are the assignee for the bug.

1 11

← Newer
1
...
46
47
48
49
50
51
52
...
93
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2014