dri-devel March 2015

dri-devel@lists.freedesktop.org

196 participants
1117 discussions

[Bug 44694] New: Crash in WebGL Path Tracing demo on Mesa 7.11 / Gallium 0.4 AMD RV710, in src_register called from translate_src
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=44694 Bug #: 44694 Summary: Crash in WebGL Path Tracing demo on Mesa 7.11 / Gallium 0.4 AMD RV710, in src_register called from translate_src Classification: Unclassified Product: Mesa Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: bjacob(a)mozilla.com My setup: Ubuntu 11.10 x86_64, Mesa 7.11, Gallium 0.4 on AMD RV710. Steps to reproduce: in Firefox (I'm on Firefox 12 / Nightly but that shouldn't matter), go to this URL: http://madebyevan.com/webgl-path-tracing/ Result: Program received signal SIGSEGV, Segmentation fault. 0x00007fffcc851f32 in src_register (t=0x7fffffff88e0, file=PROGRAM_CONSTANT, index=<optimized out>) at state_tracker/st_mesa_to_tgsi.c:243 243 state_tracker/st_mesa_to_tgsi.c: No such file or directory. in state_tracker/st_mesa_to_tgsi.c (gdb) bt #0 0x00007fffcc851f32 in src_register (t=0x7fffffff88e0, file=PROGRAM_CONSTANT, index=<optimized out>) at state_tracker/st_mesa_to_tgsi.c:243 #1 0x00007fffcc8520fc in translate_src (t=0x7fffffff88e0, SrcReg=0x7fffce3ef044) at state_tracker/st_mesa_to_tgsi.c:330 #2 0x00007fffcc855c1d in compile_instruction (inst=0x7fffce3ef040, t=0x7fffffff88e0) at state_tracker/st_mesa_to_tgsi.c:678 #3 st_translate_mesa_program (ctx=0x7fffcfb8600c, procType=<optimized out>, ureg=<optimized out>, program=<optimized out>, numInputs=<optimized out>, inputMapping=<optimized out>, inputSemanticName=0x7fffffff9e00 "", inputSemanticIndex=0x7fffffff9e20 "", interpMode=0x7fffffff9cc0, numOutputs=1, outputMapping=0x7fffffff9dc0, outputSemanticName=0x7fffffff9e40 "\001\313o\321\377\177", outputSemanticIndex=0x7fffffff9e60 "", passthrough_edgeflags=0 '\000') at state_tracker/st_mesa_to_tgsi.c:1230 #4 0x00007fffcc859700 in st_translate_fragment_program (st=0x7fffcf132000, stfp=0x7fffcee25000, key=0x7fffffff9ee0) at state_tracker/st_program.c:609 #5 0x00007fffcc85a54b in st_get_fp_variant (st=<optimized out>, stfp=0x7fffcee25000, key=<optimized out>) at state_tracker/st_program.c:667 #6 0x00007fffcc83c22c in update_fp (st=0x7fffcf132000) at state_tracker/st_atom_shader.c:86 #7 0x00007fffcc839d0f in st_validate_state (st=0x7fffcf132000) at state_tracker/st_atom.c:197 ---Type <return> to continue, or q <return> to quit--- #8 0x00007fffcc84cfb5 in st_draw_vbo (ctx=0x7fffcfb86000, arrays=0x7fffcfba0068, prims=0x7fffffff9fe0, nr_prims=1, ib=0x0, index_bounds_valid=<optimized out>, min_index=0, max_index=3) at state_tracker/st_draw.c:700 #9 0x00007fffccf5f8bb in vbo_draw_arrays (ctx=0x7fffcfb86000, mode=5, start=0, count=<optimized out>, numInstances=1) at vbo/vbo_exec_array.c:640 #10 0x00007ffff29a8fcf in mozilla::gl::GLContext::raw_fDrawArrays (this= 0x7fffcfcc1800, mode=5, first=0, count=4) at ../../../dist/include/GLContext.h:1872 #11 0x00007ffff29a86b2 in mozilla::gl::GLContext::fDrawArrays ( this=0x7fffcfcc1800, mode=5, first=0, count=4) at ../../../dist/include/GLContext.h:1006 #12 0x00007ffff29b31b6 in mozilla::WebGLContext::DrawArrays (this= 0x7fffd26b7800, mode=5, first=0, count=4) at /home/bjacob/mozilla-central/content/canvas/src/WebGLContextGL.cpp:1600 #13 0x00007ffff324a44f in nsIDOMWebGLRenderingContext_DrawArrays (cx= 0x7fffd90f2660, argc=3, vp=0x7fffde5fe340) at /home/bjacob/mozilla-central/obj-firefox-debug/js/xpconnect/src/dom_quickstubs.cpp:24893 #14 0x00007ffff3e967fd in js::CallJSNative (cx=0x7fffd90f2660, native=0x7ffff324a2d2 <nsIDOMWebGLRenderingContext_DrawArrays(JSContext*, uintN, jsval*)>, args=...) at /home/bjacob/mozilla-central/js/src/jscntxtinlines.h:311 ---Type <return> to continue, or q <return> to quit--- #15 0x00007ffff3e7b528 in js::InvokeKernel (cx=0x7fffd90f2660, args=..., construct=js::NO_CONSTRUCT) at /home/bjacob/mozilla-central/js/src/jsinterp.cpp:520 #16 0x00007ffff3e88e90 in js::Interpret (cx=0x7fffd90f2660, entryFrame=0x7fffde5fe0b0, interpMode=js::JSINTERP_NORMAL) at /home/bjacob/mozilla-central/js/src/jsinterp.cpp:3013 #17 0x00007ffff3e7b2dc in js::RunScript (cx=0x7fffd90f2660, script=0x7fffd21f6f18, fp=0x7fffde5fe0b0) at /home/bjacob/mozilla-central/js/src/jsinterp.cpp:475 #18 0x00007ffff3e7b619 in js::InvokeKernel (cx=0x7fffd90f2660, args=..., construct=js::NO_CONSTRUCT) at /home/bjacob/mozilla-central/js/src/jsinterp.cpp:538 #19 0x00007ffff3de1a41 in js::Invoke (cx=0x7fffd90f2660, args=..., construct=js::NO_CONSTRUCT) at /home/bjacob/mozilla-central/js/src/jsinterp.h:157 #20 0x00007ffff3e7b802 in js::Invoke (cx=0x7fffd90f2660, thisv=..., fval=..., argc=1, argv=0x7fffd144b788, rval=0x7fffffffb400) at /home/bjacob/mozilla-central/js/src/jsinterp.cpp:570 #21 0x00007ffff3dc0276 in JS_CallFunctionValue (cx=0x7fffd90f2660, obj=0x7fffd21ca060, fval=..., argc=1, argv=0x7fffd144b788, rval=0x7fffffffb400) at /home/bjacob/mozilla-central/js/src/jsapi.cpp:5468 #22 0x00007ffff2c3e013 in nsJSContext::CallEventHandler (this=0x7fffd9c7eef0, aTarget=0x7fffce77b400, aScope=0x7fffd21ca060, aHandler=0x7fffd195fd60, ---Type <return> to continue, or q <return> to quit--- aargv=0x7fffce3aafc8, arv=0x7fffffffb6d0) at /home/bjacob/mozilla-central/dom/base/nsJSEnvironment.cpp:1962 #23 0x00007ffff2c7c03a in nsGlobalWindow::RunTimeout (this=0x7fffce77b400, aTimeout=0x7fffce278160) at /home/bjacob/mozilla-central/dom/base/nsGlobalWindow.cpp:9292 #24 0x00007ffff2c7cfc6 in nsGlobalWindow::TimerCallback (aTimer= 0x7fffce3a5aa0, aClosure=0x7fffce278160) at /home/bjacob/mozilla-central/dom/base/nsGlobalWindow.cpp:9680 #25 0x00007ffff394eb15 in nsTimerImpl::Fire (this=0x7fffce3a5aa0) at /home/bjacob/mozilla-central/xpcom/threads/nsTimerImpl.cpp:428 #26 0x00007ffff394ef19 in nsTimerEvent::Run (this=0x7fffcfb6c3a0) at /home/bjacob/mozilla-central/xpcom/threads/nsTimerImpl.cpp:524 #27 0x00007ffff39471df in nsThread::ProcessNextEvent (this=0x7ffff6d5dc60, mayWait=false, result=0x7fffffffba0f) at /home/bjacob/mozilla-central/xpcom/threads/nsThread.cpp:660 #28 0x00007ffff38da1e5 in NS_ProcessNextEvent_P (thread=0x7ffff6d5dc60, mayWait=false) at /home/bjacob/mozilla-central/obj-firefox-debug/xpcom/build/nsThreadUtils.cpp:245 #29 0x00007ffff37b8492 in mozilla::ipc::MessagePump::Run (this=0x7fffe874f240, aDelegate=0x7ffff6dd6a80) at /home/bjacob/mozilla-central/ipc/glue/MessagePump.cpp:110 #30 0x00007ffff39986bf in MessageLoop::RunInternal (this=0x7ffff6dd6a80) ---Type <return> to continue, or q <return> to quit--- at /home/bjacob/mozilla-central/ipc/chromium/src/base/message_loop.cc:208 #31 0x00007ffff3998650 in MessageLoop::RunHandler (this=0x7ffff6dd6a80) at /home/bjacob/mozilla-central/ipc/chromium/src/base/message_loop.cc:201 #32 0x00007ffff3998629 in MessageLoop::Run (this=0x7ffff6dd6a80) at /home/bjacob/mozilla-central/ipc/chromium/src/base/message_loop.cc:175 #33 0x00007ffff3654a0e in nsBaseAppShell::Run (this=0x7fffe3d84cf0) at /home/bjacob/mozilla-central/widget/xpwidgets/nsBaseAppShell.cpp:189 #34 0x00007ffff339a966 in nsAppStartup::Run (this=0x7fffe3de47e0) at /home/bjacob/mozilla-central/toolkit/components/startup/nsAppStartup.cpp:220 #35 0x00007ffff21d443f in XRE_main (argc=4, argv=0x7fffffffe6b8, aAppData=0x623c60) at /home/bjacob/mozilla-central/toolkit/xre/nsAppRunner.cpp:3537 #36 0x00000000004023f9 in do_main ( exePath=0x7fffffffd5b0 "/home/bjacob/mozilla-central/obj-firefox-debug/dist/bin/", argc=4, argv=0x7fffffffe6b8) at /home/bjacob/mozilla-central/browser/app/nsBrowserApp.cpp:205 #37 0x0000000000402660 in main (argc=4, argv=0x7fffffffe6b8) at /home/bjacob/mozilla-central/browser/app/nsBrowserApp.cpp:295 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 5

[Bug 43018] New: (NI Turks Pro) : UT2004-demo crashes after few minutes of launch
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=43018 Bug #: 43018 Summary: (NI Turks Pro) : UT2004-demo crashes after few minutes of launch Classification: Unclassified Product: Mesa Version: unspecified Platform: x86 (IA32) OS/Version: All Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: hysvats(a)gmail.com Created attachment 53627 --> https://bugs.freedesktop.org/attachment.cgi?id=53627 Xorg.log Driver Stack Details: ========================= 1) Kernel- 3.0.0-12-generice-pae 2) Libdrm-2.4.27 3) Mesa-7.12-devel (git-f1a677c) 4) Xorg-server-1.10.1 5) xf86-video-ati-master System Environment: =================== Asic : NI Turks Pro (6759) O.S. : Ubuntu-11.10 (32 bit) Processor: AMD Athlon 64 X2 5000+ @ 2.60GHz Chipset : ATI RS690 + SB600 Memory : 2048MB Steps to Reproduce: =================== 1) Install phoronix test suite from the attachment http://phoronix-test-suite.com/releases/repo/pts.debian/files/phoronix-test… and resolve any dependency related to PHP with synaptic 2) Install ut2004-demo with phoronix-test-suite install-test ut2004-demo 3) Run phoronix-test-suite run ut2004-demo Map: 1: AS-Convoy Botmatch Resolution: 3: 1280 x 1024 Observed : 1) UT2004-demo crashes after few minutes 2) Regression Info : Ut2004-demo passed on the same Asic on 5 September 3) The same behaviour is observed on NI Caicos also -- 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 42678] New: Dual Screen Monitor Gnome-shell 3 hard lock ups - ATI open source Radeon
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=42678 Bug #: 42678 Summary: Dual Screen Monitor Gnome-shell 3 hard lock ups - ATI open source Radeon Classification: Unclassified Product: Mesa Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: blocker Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: Wattos(a)gmail.com Created attachment 53265 --> https://bugs.freedesktop.org/attachment.cgi?id=53265 last 3000 lines of .xsession-errors I am running Ubuntu 11.10 64 bit with gnome shell 3,2 on a Intel i7-940XM with an ATI Radeon HD 5850M. The drivers which are currently being used are the open source drivers (xf86-video-ati 6.14.99). I am experiencing random (on save, on dialog open, on workspace switch) hard lockups (CTRL + ALT + F1 doesnt work, nor does ALT+PrntScrn R S E I U B). This only happens when using two screens (independent of which output (e.g. Displayport + VGA, Displayport + Notebook LCD) are used). This issue is a complete show stopper since the pc requires a hard reboot and any unsaved items are lost indefinitely (or worse, things might get corrupted). I am attaching the last 3000 lines of .xsession-errors. uname -a: Linux filipw-M15x 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Please let me know if you require any more information -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 15

[Bug 40425] New: Maker3D graphics bugs with opensource ati drivers
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=40425 Summary: Maker3D graphics bugs with opensource ati drivers Product: Mesa Version: unspecified Platform: All OS/Version: Linux (All) Status: NEW Severity: minor Priority: medium Component: Drivers/DRI/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: gerilegend(a)freemail.hu Created an attachment (id=50619) --> (https://bugs.freedesktop.org/attachment.cgi?id=50619) gallium (left) - catalyst (right) These bugs appear with RadeonHD 3200 series IGP on linux. look the attached image for explanation. operating system: ubuntu 11.04 (built in graphics driver) demo version: http://ftp.sth.sze.hu/~andras/Maker3D_demo.zip homepage: http://Maker3D.tk -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 46866] New: Piglit:Multiple failures observed while running quick-driver.tests
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=46866 Bug #: 46866 Summary: Piglit:Multiple failures observed while running quick-driver.tests Classification: Unclassified Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: hysvats(a)gmail.com Driver Stack Details: ========================= 1) Kernel-3.0.0-12-generice-pae 2) drm-2.4.31 3) Mesa-8.1-devel (git-897af1d) 4) Xorg-server-1.11.4 5) xf86-video-ati- master System Environment: =================== Asic : EG CedarPro O.S. : Ubuntu-11.10 (32 bit) Processor : AMD Athlon(tm) 64 X2 @ 1 GHz Memory : 2 GB Steps to Reproduce: =================== 1) Install piglit from git clone git://anongit.freedesktop.org/git/piglit 2) #./piglit-run.py tests/quick-driver.tests results/quick-driver.results #./piglit-summary-html.py summary/quick-driver results/quick-driver.results Observation : Multiple failures observed while running quick-driver.tests =========== -- 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 28943] New: Red=cyan? Why?
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=28943 Summary: Red=cyan? Why? Product: Mesa Version: unspecified Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/MGA AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: eblanca76(a)users.sourceforge.net I'm having a strange color replacement in ubuntu 10.04. Hardware is matrox g550 agp dual head, 32 MB. Well, running silent hill 2 in wine, I have cyan blood when it should be red! Here you can read the (closed) bug: http://bugs.winehq.org/show_bug.cgi?id=17741 (there are a lot of details about the bug) I thought it was due to wine but it isn't, so it was closed as invalid. Please note, this `bug' appears since a couple of years ago and even now, with mesa 7.7.1. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 1

[Bug 80678] New: xrandr scaling / transform does not work with radeon
by bugzilla-daemon＠freedesktop.org 25 Feb '16

25 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=80678 Priority: medium Bug ID: 80678 Assignee: dri-devel(a)lists.freedesktop.org Summary: xrandr scaling / transform does not work with radeon Severity: normal Classification: Unclassified OS: Linux (All) Reporter: h.judt(a)gmx.at Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Scaling doesn't work with radeon. Screen rotation does work, though. On a laptop with intel driver, the following works fine, except the mouse pointer is confined to the mode area, but I believe that is a known xorg-server bug to which a patch is available in bug #39949: xrandr --fb 1920x1080 --output eDP1 --mode 1600x900 --scale-from 1920x1080 The same command, adapted to the radeon output device doesn't work. Same software configuration (xorg-1.15.99.903, libdrm-git, mesa-git, xf86-video-ati-git, various kernel versions (at the moment 3.15.2)). lspci -vvv: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO [Radeon HD 6950] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 0b00 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 41 Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at f7e20000 (64-bit, non-prefetchable) [size=128K] Region 4: I/O ports at e000 [size=256] Expansion ROM at f7e00000 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited 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 5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee0100c Data: 4191 Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Kernel driver in use: radeon Is scaling not implemented in radeon? -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 76321] New: Incorrect hwmon temperature when radeon card is turned off
by bugzilla-daemon＠bugzilla.kernel.org 20 Feb '16

20 Feb '16

https://bugzilla.kernel.org/show_bug.cgi?id=76321 Bug ID: 76321 Summary: Incorrect hwmon temperature when radeon card is turned off Product: Drivers Version: 2.5 Kernel Version: 3.15-rc3 Hardware: All 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: pali.rohar(a)gmail.com Regression: No When radeon card is turned off (automatically via runpm) sensors program show totally incorrect temperature: radeon-pci-0100 Adapter: PCI adapter temp1: +511.0°C (crit = +120.0°C, hyst = +90.0°C) When some opengl program is running with DRI_PRIME=1 then sensors reports: radeon-pci-0100 Adapter: PCI adapter temp1: +46.0°C (crit = +120.0°C, hyst = +90.0°C) So kernel radeon driver should not report temperature (e.g. returns -EINVAL in hwmon) when radeon card is turned off (via vgaswitcheroo or runpm). -- You are receiving this mail because: You are watching the assignee of the bug.

1 14

[Bug 66352] New: GPU lockup in L4D2 on TURKS with HyperZ
by bugzilla-daemon＠freedesktop.org 19 Feb '16

19 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=66352 Priority: medium Bug ID: 66352 Assignee: dri-devel(a)lists.freedesktop.org Summary: GPU lockup in L4D2 on TURKS with HyperZ Severity: normal Classification: Unclassified OS: FreeBSD Reporter: russianneuromancer(a)ya.ru Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 81668 --> https://bugs.freedesktop.org/attachment.cgi?id=81668&action=edit dmesg Lockup described in bug 64220 was happen right after campaign start (in first minute) but this lockup usually happen later - in first hour of playing. This lockup is not reproducible when HyperZ is disabled, so probably (like bug 64220) is related to HyperZ. [ 2160.750951] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec [ 2160.750966] radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000002525f last fence id 0x000000000002525c) [ 2160.786068] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000174118 and cpu addr 0xffffc9000681c118 [ 2160.787147] radeon 0000:01:00.0: Saved 183 dwords of commands on ring 0. [ 2160.787166] radeon 0000:01:00.0: GPU softreset: 0x00000019 [ 2160.787175] radeon 0000:01:00.0: GRBM_STATUS = 0xE7730CA0 [ 2160.787177] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0xFC000001 [ 2160.787180] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 2160.787182] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 2160.787184] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [ 2160.787186] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x01000000 [ 2160.787189] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x000D1000 [ 2160.787191] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00068506 [ 2160.787193] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80878647 [ 2160.787196] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 2160.787356] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B [ 2160.787410] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 [ 2160.788559] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 [ 2160.788561] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 [ 2160.788563] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [ 2160.788565] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [ 2160.788568] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [ 2160.788570] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 2160.788572] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [ 2160.788574] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [ 2160.788576] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [ 2160.788579] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 2160.788589] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [ 2160.793777] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). [ 2160.793895] radeon 0000:01:00.0: WB enabled [ 2160.793900] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8801fb519c00 [ 2160.793904] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8801fb519c0c [ 2160.796145] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000174118 and cpu addr 0xffffc900079b2118 [ 2160.812389] [drm] ring test on 0 succeeded in 2 usecs [ 2160.812457] [drm] ring test on 3 succeeded in 1 usecs [ 2160.987496] [drm] ring test on 5 succeeded in 1 usecs [ 2160.987512] [drm] UVD initialized successfully. [ 2161.219416] [drm] ib test on ring 0 succeeded in 0 usecs [ 2161.219497] [drm] ib test on ring 3 succeeded in 1 usecs [ 2161.370073] [drm:r600_uvd_ib_test] *ERROR* radeon: failed to get create msg (-22). [ 2161.370094] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-22). ~$ lspci | grep VGA 00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI BeaverCreek [Radeon HD 6620G] 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Whistler [Radeon HD 6600M/6700M/7600M Series] (DRI_PRIME is used to launch game.) Linux 3.10-rc7 libdrm 2.4.45+git20130607.a0178c00 Mesa 9.2.0~git20130627.15085b47 xserver-xorg-video-radeon 7.1.99+git20130531.bd2557ea Xserver 1.13.4~git20130508+server-1.13-branch.10c42f57 Kubuntu 13.04 x86_64 updated from Xorg Edgers PPA. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 89521] New: Radeon driver fails to set dpm power state after resume from S3
by bugzilla-daemon＠bugzilla.kernel.org 19 Feb '16

19 Feb '16

https://bugzilla.kernel.org/show_bug.cgi?id=89521 Bug ID: 89521 Summary: Radeon driver fails to set dpm power state after resume from S3 Product: Drivers Version: 2.5 Kernel Version: 3.18.0 Hardware: x86-64 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: anhermann(a)gmx.net Regression: No Created attachment 160341 --> https://bugzilla.kernel.org/attachment.cgi?id=160341&action=edit dmesg output from 3 resume cycles Using a Radeon R9 270X and kernel 3.18.0 I get the following error message only after resume from S3 state: [drm:si_dpm_set_power_state] *ERROR* si_set_sw_state failed I would like to notice that this also happened with older kernel versions (3.17 and 3.16 with radeon.dpm=1) and other cards. My other PC has a HD 5450 with the same problem (slightly other ERROR string as its not SI). Besides the error message, I cannot see any strange behaviour, performance is good, no freezes etc. . But it sounds like performance level switching is not working correctly? I added the dmesg output showing three resume cycles with the mentioned error message as attachment. Thanks -- You are receiving this mail because: You are watching the assignee of the bug.

1 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2015