dri-devel June 2013

dri-devel@lists.freedesktop.org

132 participants
727 discussions

[Bug 48472] New: GPU Lockup while running demo in wine
by bugzilla-daemon＠freedesktop.org 24 Jun '16

24 Jun '16

https://bugs.freedesktop.org/show_bug.cgi?id=48472 Bug #: 48472 Summary: GPU Lockup while running demo in wine Classification: Unclassified Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: nathanhirschauer(a)verfriemelt.org While running Razor 1911 - Scene is dead (http://www.chiptune.com/razor/rzr-the_scene_is_dead.zip) in wine I get a GPU Lockup: [ 690.049988] radeon 0000:01:00.0: GPU lockup CP stall for more than 10233msec [ 690.049993] GPU lockup (waiting for 0x00002749 last fence id 0x00002746) [ 690.051188] radeon 0000:01:00.0: GPU softreset [ 690.051191] radeon 0000:01:00.0: R_008010_GRBM_STATUS=0xE5700030 [ 690.051193] radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00110103 [ 690.051195] radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200000C0 [ 690.051202] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00007FEE [ 690.066201] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00000001 [ 690.082204] radeon 0000:01:00.0: R_008010_GRBM_STATUS=0xA0003030 [ 690.082206] radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00000003 [ 690.082208] radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200080C0 [ 690.083209] radeon 0000:01:00.0: GPU reset succeed [ 690.103443] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). [ 690.103467] radeon 0000:01:00.0: WB enabled [ 690.134854] [drm] ring test succeeded in 1 usecs [ 690.134861] [drm] ib test succeeded in 1 usecs I'm using mesa-git (c653287) with Linux 3.2.13 (Arch Linux) and Xorg 1.12.0.901 on a Thinkpad R500 (which has the following VGA Controller: 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] (Mobility Radeon HD 3450) Attached the a logfile with WINEDEBUG=+wgl,+opengl. Seems like the lockup occurs while the following message appears (Line 1232): trace:opengl:wine_glDrawArrays (7, 0, 4) I hope I attached all important files/infos - If I forgot something, let me know. -- 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 46713] New: HDMI audio played back at a wrong rate
by bugzilla-daemon＠freedesktop.org 15 Jun '16

15 Jun '16

https://bugs.freedesktop.org/show_bug.cgi?id=46713 Bug #: 46713 Summary: HDMI audio played back at a wrong rate Classification: Unclassified Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: tvrtko.ursulin(a)onelan.co.uk I am experiencing audio being played back at roughly 28665Hz instead of expected 44100Hz. This rate is derived for timing for how long it takes to play sample of a known size. Pitch of audio being played is obviously comical. Hardware: AMD G-T56N (Radeon HD 6310) box connected to the monitor via native HDMI connector. This is with kernel.org 3.3.0-rc4 kernel. Only thing I see in kernel log with apparent relevance is this: [ 56.086500] HDMI hot plug event: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 56.086526] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 56.086545] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 56.086561] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 56.127063] HDMI hot plug event: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=1 [ 56.127090] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 56.127109] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 56.127125] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 56.387045] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 56.387069] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 56.387086] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 56.699469] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 56.699494] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 56.699510] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 56.990752] HDMI hot plug event: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 56.990777] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 56.990795] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 56.990811] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 57.001054] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 57.001079] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 57.001095] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 57.302064] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 57.302092] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 57.302108] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 57.420102] HDMI hot plug event: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=1 [ 57.420130] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 57.420149] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 57.420165] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 57.437447] HDMI hot plug event: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 57.437471] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 57.437489] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 57.437505] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 57.493091] HDMI hot plug event: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=1 [ 57.493117] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 57.493136] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 57.493152] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 57.618528] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 57.618552] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 57.618568] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 57.919028] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 57.919059] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 57.919075] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 58.220081] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 58.220115] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 58.220131] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 58.521039] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 58.521071] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 58.521087] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 63.136948] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. While playing back hw_info looks fine: aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: SB [HDA ATI SB], device 0: ALC883 Analog [ALC883 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: SB [HDA ATI SB], device 1: ALC883 Digital [ALC883 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 cat /proc/asound/card0/pcm3p/sub0/hw_params access: RW_INTERLEAVED format: S16_LE subformat: STD channels: 2 rate: 44100 (44100/1) period_size: 5504 buffer_size: 22016 Not sure what other info should I provide? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 32

[Bug 44647] New: [wine regression] Call of Duty 4: Intro videos renders garbage
by bugzilla-daemon＠freedesktop.org 20 Apr '16

20 Apr '16

https://bugs.freedesktop.org/show_bug.cgi?id=44647 Bug #: 44647 Summary: [wine regression] Call of Duty 4: Intro videos renders garbage Classification: Unclassified Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: sa(a)whiz.se Created attachment 55392 --> https://bugs.freedesktop.org/attachment.cgi?id=55392 Screenshot of broken video Intro videos in the game Call of Duty 4 (running with Wine) no longer renders correctly, bisecting leads to this: e8139ebf583acf37150a8b341bcbef6b924a7792 is the first bad commit commit e8139ebf583acf37150a8b341bcbef6b924a7792 Author: Mathias Fröhlich <Mathias.Froehlich(a)gmx.net> Date: Tue Jul 26 07:05:10 2011 +0200 r600g: Replace needless flush in texture upload. Replace pipe->flush() with pipe->texture_barrier() in the texture upload path for the staging texture. This should be enough to get data out of the gpu caches ready to be read for texture fetch. :040000 040000 b3f16d1a114f54d753ba7845b697888307f6246e faab26149053fdb2fb65d81bb2a777a77e130de2 M src Adding the flush back fixes the problem. -- 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 34643] New: ut2004/doom3 looping in submenu on r300g/PageFlip
by bugzilla-daemon＠freedesktop.org 19 Mar '16

19 Mar '16

https://bugs.freedesktop.org/show_bug.cgi?id=34643 Summary: ut2004/doom3 looping in submenu on r300g/PageFlip Product: Mesa Version: git Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: krzysztof.krakowiak(a)gmail.com Created an attachment (id=43736) --> (https://bugs.freedesktop.org/attachment.cgi?id=43736) gdb/ut2k4 output and backraces. ut2004(32/64bit) and doom3(32bit) are looping everytime in submenu on r300g/PageFlip. I believe that bug occured during last two weeks, but bisecting would be hard, because I was bisecting for: https://bugs.freedesktop.org/show_bug.cgi?id=34418 And everytime supertuxkart wasnt working, ut2k4 also and vice versa, altough bugs were definitely different. Now previous bug is fixed(which affected only 64bit apps), but ut2004/doom3 got very similar behaviour(like looped video tape or something, moving forward and back), similar spam in console, but a bit different at output. Disabling PageFLip fixes this problem definitely, but I was happpy pflip user from a long time. Kernel is fresh D-R-T, DDX/DRM/Mesa from master. --- UT2004 dmesg --- [...] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0xe [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x1f [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0xe [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x1f [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! [...] --- EOF UT2004 dmesg --- --- UT2004 gdb output/backtrace --- [...] [Thread 0x7fffe50cd700 (LWP 5934) exited] [New Thread 0x7fffe50cd700 (LWP 5935)] [Thread 0x7fffe50cd700 (LWP 5935) exited] [New Thread 0x7fffe50cd700 (LWP 5936)] [...] [Thread 0x7fffe50cd700 (LWP 6540) exited] [New Thread 0x7fffe50cd700 (LWP 6541)] radeon: The kernel rejected CS, see dmesg for more information. [Thread 0x7fffe50cd700 (LWP 6541) exited] [...] Program received signal SIGINT, Interrupt. 0x00007ffff6e0a1f3 in poll () from /lib64/libc.so.6 (gdb) bt #0 0x00007ffff6e0a1f3 in poll () from /lib64/libc.so.6 #1 0x00007ffff65eac6a in ?? () from /usr/lib64/libxcb.so.1 #2 0x00007ffff65ec2ff in xcb_wait_for_reply () from /usr/lib64/libxcb.so.1 #3 0x00007ffff684392d in _XReply () from /usr/lib64/libX11.so.6 #4 0x00007fffe6c1748c in DRI2GetBuffersWithFormat () from /opt/xorg/lib64/libGL.so.1 #5 0x00007fffe6c14bf9 in dri2GetBuffersWithFormat () from /opt/xorg/lib64/libGL.so.1 #6 0x00007fffe56de4d8 in dri2_allocate_textures () from /opt/xorg/lib64/dri/gallium/r300_dri.so #7 0x00007fffe56dfb77 in dri_st_framebuffer_validate () from /opt/xorg/lib64/dri/gallium/r300_dri.so #8 0x00007fffe573f132 in st_framebuffer_validate () from /opt/xorg/lib64/dri/gallium/r300_dri.so #9 0x00007fffe5740916 in st_manager_validate_framebuffers () from /opt/xorg/lib64/dri/gallium/r300_dri.so #10 0x00007fffe58e3c1e in st_validate_state () from /opt/xorg/lib64/dri/gallium/r300_dri.so #11 0x00007fffe58ebb3a in st_Clear () from /opt/xorg/lib64/dri/gallium/r300_dri.so #12 0x0000000000d291d9 in FOpenGLRenderInterface::Clear(int, FColor, int, float, int, unsigned int) () #13 0x000000000069d234 in UGameEngine::Draw(UViewport*, int, unsigned char*, int*) () #14 0x0000000000d1d106 in USDLViewport::Repaint(int) () #15 0x0000000000d1ab09 in USDLClient::Tick() () #16 0x00000000006a0f54 in UGameEngine::Tick(float) () #17 0x000000000053d2a3 in CMainLoop::RunLoop() () #18 0x000000000053344f in ?? () #19 0x000000000052f1a0 in main () --- UT2004 gdb output/backtrace --- --- Doom3 output --- [...] radeon: The kernel rejected CS, see dmesg for more information. radeon: The kernel rejected CS, see dmesg for more information [...] --- EOF Doom3 output --- TIP: For full logs, look into attachements (but nothing special in xorg.log) -- 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 43016] New: DVI is wrongly detected as Display Port
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=43016 Bug #: 43016 Summary: DVI is wrongly detected as Display Port Classification: Unclassified Product: Mesa Version: unspecified Platform: x86 (IA32) OS/Version: other Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: hysvats(a)gmail.com Created attachment 53622 --> https://bugs.freedesktop.org/attachment.cgi?id=53622 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 : EG Madison Pro 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) Connect the DFP With DVI to DVI Cable. 2) Xrandr -q Expected : xrandr output should list DVI observed : xrandr output list DisplayPort Output of xrandr -q Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192 DisplayPort-0 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 473mm x 296mm 1680x1050 59.9*+ 1280x1024 76.0 75.0 70.0 60.0 1152x864 75.0 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 75.0 60.3 56.2 640x480 72.8 75.0 60.0 720x400 70.1 DisplayPort-1 disconnected (normal left inverted right x axis y axis) VGA-0 disconnected (normal left inverted right x axis y axis) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 8

[Bug 40024] New: Power management does not work on ATI Mobility Radeon 9700
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=40024 Summary: Power management does not work on ATI Mobility Radeon 9700 Product: Mesa Version: 7.10 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: robegrassi(a)gmail.com Created an attachment (id=50139) --> (https://bugs.freedesktop.org/attachment.cgi?id=50139) output of dmesg Hi, I have an old Asus laptop with a Mobility Radeon 9700 card: $ lspci -nn | grep VGA 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] [1002:4e50] I am using Xubuntu 11.04 with KMS and Gallium driver. I would like to set the card to a lower power state because the fan goes often high and the laptop gets hot. The problem is that these three files are missing: cat: /sys/class/drm/card0/device/power_method: No such file or directory cat: /sys/class/drm/card0/device/power_profile: No such file or directory cat: /sys/kernel/debug/dri/0/radeon_pm_info: No such file or directory Does it mean that my card does not support power management? Thank you very much for your help, Roberto -- 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 36817] New: RV670 - Kernel fails to enable acceleration when RAM greater than 32-bit limit
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=36817 Summary: RV670 - Kernel fails to enable acceleration when RAM greater than 32-bit limit Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: reg(a)achart.me.uk I sure hope I'm in the right place... Using a Radeon HD3870 that works fine under Windows (64-bit). After a supposed initial success using a pre-release version of KMS drivers (which may be a red herring), I have been unable to get 3D acceleration on any Ubuntu release from Lucid, unless I use a non-PAE kernel (I have 4GB RAM). My Ubuntu bug ticket (including logs) is here: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/574884 Another bug that looks similar: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/657576 A similar looking bug with a similar workaround (which I'll shortly try on mine) on SUSE: http://web.archiveorange.com/archive/v/wmeLDauZzOL6SFQx1uKY -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

[Bug 36598] New: [RS880] Slow resume from suspend generates kernel oops
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=36598 Summary: [RS880] Slow resume from suspend generates kernel oops Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: steve(a)stevemurphy.org Created an attachment (id=46075) --> (https://bugs.freedesktop.org/attachment.cgi?id=46075) dmesg output for boot and suspend, showing the issue around 78.3 I'm forwarding this bug from ubuntu - https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/764788 Problem] Resume from suspend triggers a kernel oops due to the radeon kms module taking more than 10 seconds to resume [Discussion] When resuming from the suspend state, a popup box is displayed indicating an error has occured and "Your system might become unstable now and might need to be restarted.". In the dmesg output, the following lines are present before the kernel oops, showing that the radeon driver took 11408.919 msecs to resume and the kernel oops is due to resume taking longer than 10 seconds total (11430 msecs). Interesting lines in the dmesg output when the error occurs are below (with kernel.drm=0x04 set, adding a bit of verbosity when the radeon driver is restoring): [ 69.792851] PM: resume of drv:scsi_disk dev:2:0:0:0 complete after 2644.379 msecs [ 70.122093] [drm:output_poll_execute], [CONNECTOR:15:VGA-1] status updated from 2 to 2 [ 70.124058] [drm:radeon_atombios_connected_scratch_regs], DFP1 disconnected [ 70.124062] [drm:output_poll_execute], [CONNECTOR:17:HDMI-A-1] status updated from 2 to 2 [ 71.960104] [drm:radeon_atom_encoder_dpms], encoder dpms 21 to mode 3, devices 00000001, active_devices 00000000 [ 71.960113] [drm:radeon_atom_encoder_dpms], encoder dpms 30 to mode 3, devices 00000008, active_devices 00000000 [ 71.960136] [drm:radeon_compute_pll_avivo], 7187, pll dividers - fb: 130.5 ref: 2, post 13 [ 71.980174] [drm:drm_crtc_helper_set_mode], [ENCODER:12:LVDS-12] set [MODE:30:1366x768] [ 76.950136] [drm:avivo_crtc_load_lut], 0 [ 76.950200] [drm:radeon_atom_encoder_dpms], encoder dpms 31 to mode 0, devices 00000002, active_devices 00000002 [ 76.960133] [drm:radeon_atom_encoder_dpms], encoder dpms 31 to mode 3, devices 00000002, active_devices 00000002 [ 78.303704] [drm:radeon_atom_encoder_dpms], encoder dpms 21 to mode 3, devices 00000001, active_devices 00000000 [ 78.303713] [drm:radeon_atom_encoder_dpms], encoder dpms 30 to mode 3, devices 00000008, active_devices 00000000 [ 78.303734] [drm:avivo_crtc_load_lut], 0 [ 78.303790] [drm:radeon_atom_encoder_dpms], encoder dpms 31 to mode 0, devices 00000002, active_devices 00000002 [ 78.310132] PM: resume of drv:radeon dev:0000:01:05.0 complete after 11408.919 msecs [ 78.310148] PM: resume of drv:drm dev:controlD64 complete after 8513.702 msecs [ 78.310173] PM: resume of devices complete after 11409.422 msecs [ 78.330262] PM: resume devices took 11.430 seconds [ 78.330265] ------------[ cut here ]------------ [ 78.330272] WARNING: at /build/buildd/linux-2.6.38/kernel/power/suspend_test.c:53 suspend_test_finish+0x86/0x90() [ 78.330274] Hardware name: 1215T [ 78.330277] Component: resume devices, time: 11430 Upon investigating further, it looks like portions of the the following workarounds were discovered that allow resume from suspend to work as expected, by avoid the radeon driver: [Workarounds] 1. Add "nomodeset" to the linux command line in grub 2. Use the proprietary FGLRX driver. [System Environment] ASUS 1215T running a fresh install of 11.04 beta or 11.04 beta2. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

[Bug 35988] New: Power management not working on ATI M92 LP [Mobility Radeon HD 4300]
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=35988 Summary: Power management not working on ATI M92 LP [Mobility Radeon HD 4300] Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: s.j.turner(a)uqconnect.net A launchpad user reports "If I deactivate the ATI restricted driver, and then restart my computer, GPU temp is between 70-80 degrees Celsius instead of the usual 40-50, without doing anything, no application running, no effects." lspci -nn | grep VGA 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M92 LP [Mobility Radeon HD 4300 Series] [1002:9552] MachineType: Hewlett-Packard HP ProBook 4710s This was originally reported on Ubuntu 9.10 "Karmic Koala" with a 2.6.31-based kernel (which of course does not have power management support), but persists on an Ubuntu 11.04 "Natty Narwhal" pre-release with a 2.6.38-based kernel. The problem is that this user reports "I've tried setting the power (management) profile settings and dynpm, but nothing has changed, still running above 70 degrees Celsius." -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 11

[Bug 34556] New: BUG in drm/radeon/ttm after leaving fullscreen flash.
by bugzilla-daemon＠freedesktop.org 26 Feb '16

26 Feb '16

https://bugs.freedesktop.org/show_bug.cgi?id=34556 Summary: BUG in drm/radeon/ttm after leaving fullscreen flash. Product: DRI Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: monraaf(a)gmail.com Created an attachment (id=43645) --> (https://bugs.freedesktop.org/attachment.cgi?id=43645) black screen of death Watching a youtube video fullscreen with adobe flashplayer and then leaving fullscreen sometimes triggers a bug in the drm/radeon/ttm, this is with kernel 2.6.38-rc5, ddx from git and happens with both stock r600c from ubuntu 10.10 and r600g from git master. The bug is only triggered sporadicly, but a good way to reproduce I found is to go and play a youtube video. e.g. http://www.youtube.com/watch?v=8ETDE0VGJY4 then position the mouse pointer at the bottom-right of the player where the fullscreen button is and start clicking many times as fast as you can. The player will go fullscreen and leave fullscreen a couple of times and will eventually trigger the bug. -- 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

← Newer
1
...
22
23
24
25
26
27
28
...
73
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2013