dri-devel May 2011

dri-devel@lists.freedesktop.org

118 participants
495 discussions

[Bug 34626] New: Mesa-Gallium with R600 - Framerate limited to 60 fps after suspend-cycle
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=34626 Summary: Mesa-Gallium with R600 - Framerate limited to 60 fps after suspend-cycle Product: DRI Version: XOrg CVS Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: peterle(a)hottemptation.org Hello, I past I thought this is a bug of IOQuake3, but during switching between Mesa-Classic and Mesa-Gallium I recognized, that the problem only exists with Mesa-Gallium! Reproduce: 1. $export vblank_mode=0 // switching of vsync 2. Launch an IOQuake3 based game (Quake3 Arena, OpenArena, World of Padman...) 3. check that VSYNC in IOQuake3 is also disabled! 4. Start a game and set "cg_drawpfs 1", know you should have at the top right corner a display with your current framerate which is hopefully over 60 fps 5. switch to a tty during playing (should be no problem with Kernel-Mode-Setting) 6. #pm-suspend (as root) 7. resume from suspend 8. switch back to X11/IOQuake3 -> framerate is limited to 60 fps To fix this you have to relaunch IOQuake3 or simply type into quake-console "vid_restart". With Mesa-Classic and the R600-Driver this is not necessary, it displays always the maximum possible framerate. Maybe Gallium doesn't read or forget the environment-variable export_vblank during resume from suspend? -- 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 34313] New: RV770 lock-up with OpenGL
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=34313 Summary: RV770 lock-up with OpenGL Product: Mesa Version: 7.7 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: rah(a)bash.sh Created an attachment (id=43405) --> (https://bugs.freedesktop.org/attachment.cgi?id=43405) X server log I get the following GPU lock-up report with many different OpenGL programs, but in this instance Stellarium. ------------[ cut here ]------------ WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:244 radeon_fence_wait+0x38f/0x3f0 [radeon]() Hardware name: P5Q GPU lockup (waiting for 0x000CAA2E last fence id 0x000CAA28) Modules linked in: usb_storage cpufreq_powersave cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_ondemand freq_table lirc_serial(C) lirc_dev sco bnep rfcomm l2cap crc16 binfmt_misc ip6t_LOG ip6table_filter ip6_tables fuse nfsd exportfs nls_iso8859_1 nls_cp437 vfat fat coretemp loop dm_crypt snd_hda_codec_hdmi radeon snd_hda_codec_realtek ttm snd_emu10k1_synth snd_hda_intel snd_emux_synth snd_hda_codec snd_seq_virmidi snd_seq_midi_emul snd_emu10k1 snd_ac97_codec ac97_bus snd_util_mem snd_pcm_oss snd_hwdep snd_mixer_oss snd_seq_dummy snd_seq_oss snd_seq_midi snd_pcm snd_rawmidi gspca_pac207 gspca_main videodev v4l1_compat drm_kms_helper drm snd_seq_midi_event v4l2_compat_ioctl32 snd_page_alloc 8250_pnp snd_seq snd_timer snd_seq_device snd btusb pcspkr i2c_i801 asus_atk0110 bluetooth emu10k1_gp soundcore 8250 gameport evdev serial_core dm_mod usbhid hid sg uhci_hcd sr_mod cdrom atl1e firewire_ohci firewire_core crc_itu_t via_rhine mii ehci_hcd [last unloaded: scsi_wait_scan] Pid: 2992, comm: Xorg Tainted: G WC 2.6.37-linux-2.6-latest-32 #10 Call Trace: [<ffffffff8103c8fb>] ? warn_slowpath_common+0x7b/0xc0 [<ffffffff8103c9f5>] ? warn_slowpath_fmt+0x45/0x50 [<ffffffffa0461b1f>] ? radeon_fence_wait+0x38f/0x3f0 [radeon] [<ffffffff81057740>] ? autoremove_wake_function+0x0/0x30 [<ffffffffa00f90c9>] ? ttm_bo_wait+0x119/0x1d0 [ttm] [<ffffffffa0478b8e>] ? radeon_gem_wait_idle_ioctl+0x8e/0x110 [radeon] [<ffffffffa01fa331>] ? drm_ioctl+0x3c1/0x440 [drm] [<ffffffffa0478b00>] ? radeon_gem_wait_idle_ioctl+0x0/0x110 [radeon] [<ffffffff8100d772>] ? save_i387_xstate+0x92/0x210 [<ffffffff810022df>] ? do_signal+0x19f/0x800 [<ffffffff810e7a5f>] ? do_vfs_ioctl+0x9f/0x550 [<ffffffff8100d538>] ? restore_i387_xstate+0x148/0x1d0 [<ffffffff810e7f90>] ? sys_ioctl+0x80/0xa0 [<ffffffff81002dbb>] ? system_call_fastpath+0x16/0x1b ---[ end trace 37e82fba971a1173 ]--- -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 29

[Bug 33969] New: "unable to handle kernel paging request" crash after playing tuxracer for a few seconds
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=33969 Summary: "unable to handle kernel paging request" crash after playing tuxracer for a few seconds 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: adam.rak(a)streamnovation.com Created an attachment (id=42998) --> (https://bugs.freedesktop.org/attachment.cgi?id=42998) Full dmesg after the crash Hardware is Fusion Zacate APU (HD6310) Mesa is commit ec96b0ecdbe723f4664188010c7f86d5d7f41d82 checkout ddx is commit a4899db96029acde6cd400fc0541693a487898e7 checkout linux kernel is 2.6.38-rc3 commit 44f2c5c841da1b1e0864d768197ab1497b5c2cc1 X.Org X Server 1.7.7 (debian squeeze) Running nexuiz crashes the X when entering play mode. (no apparent error log) Running(and playing) extremetuxracer produces a kernel oops after a few seconds, the dmesg is in the attachment. -- 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 33681] New: Random system lockup with KMS, Mobility Radeon HD3470
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=33681 Summary: Random system lockup with KMS, Mobility Radeon HD3470 Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: jsagarribay(a)gmail.com Created an attachment (id=42685) --> (https://bugs.freedesktop.org/attachment.cgi?id=42685) kernel log The computer often locks itself, the panel suddenly loses the image (it sometimes blooms, or get filled with a solid color or a pattern of vertical white and grey stripes). I don't know how to trigger the bug, it can happen anytime, even with an idle system. It has happened to me since I started using KMS, it was stable both with radeonHD and radeon drivers in UMS mode. The frequency of the problem has varied a lot; with the first KMS versions it happened a lot, then it seemed to be fixed with some kernel versions, but reappeared with others... As the problem is random, it can happen after a few minutes of uptime, or after some hours, or not happen at all. At first, I thougth the kernel was completely dead, but I recently found out that I can use SysRq+S and SysRq+T to get some logs. If I try to reboot with SysRq+B the system locks fully and doesn't react to anything, I always have to do a hard reboot. I'll attach lspci, one X log and three differen kernel logs. -- 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 33301] New: dynpm doesn't downclock
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=33301 Summary: dynpm doesn't downclock Product: DRI Version: XOrg 6.7.0 Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: cristiklein(a)gmail.com Hello, I have an ATI Mobility Radeon HD 2400. I am using Linux 2.6.37. Currently, dynpm does not down-clock the GPU for me. dmesg is filled with the following messages: [245199.552075] [drm:r600_pm_get_dynpm_state], Requested: e: 30000 m: 40000 p: 16 (about 10 messages / second) I attach a script with all the necessary details. Cristi. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 3

[Bug 32399] New: KMS:RS480:X200M LCD Monitor on VGA-0 shows wavy picture
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=32399 Summary: KMS:RS480:X200M LCD Monitor on VGA-0 shows wavy picture Product: Mesa Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: high Component: Drivers/DRI/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: evillanueva(a)roundbox.com Depends on: 32350 When second LCD monitor is connected to VGA-0 picture is wavy. The text on the screen flutters. -- 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 32319] New: Display fades to white screen instead of blanking out in DPMS mode on a Sony Vaio VPCEC3L1E
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=32319 Summary: Display fades to white screen instead of blanking out in DPMS mode on a Sony Vaio VPCEC3L1E Product: DRI Version: DRI 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: bugs.xorg(a)boris64.net Created an attachment (id=41011) --> (https://bugs.freedesktop.org/attachment.cgi?id=41011) Fade-to-white-picture No.1 On my new Sony Vaio laptop (VPCEC3L1E) the screen fades to white (with backlights on, i think) instead of simply blanking out. This can be reproduced by running "xset dpms force off" or by simply waiting until powermanagement kicks in. The graphics card used is a radeon 5xxx(?) (01:00.0 VGA compatible controller: ATI Technologies Inc Device 68e0). This happens on console and in X. I'll attach some pictures showing the issue. Thanks for any help! PS: I hope i did choose the correct product/component for this type of 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 18

[Bug 31230] New: [RV250Lf] Corrupted screen after resume
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=31230 Summary: [RV250Lf] Corrupted screen after resume Product: DRI Version: XOrg CVS Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: johannesobermayr(a)gmx.de Created an attachment (id=39897) --> (https://bugs.freedesktop.org/attachment.cgi?id=39897) specific part of /var/log/messages (~13 MiB, "drm.debug=255") After resume the screen is totally corrupted. -- 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 31213] New: [drm] *ERROR* with KMS (any kernels 2.6.3x.x) and ati mobility radeon X300
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=31213 Summary: [drm] *ERROR* with KMS (any kernels 2.6.3x.x) and ati mobility radeon X300 Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: djnass_18(a)hotmail.com when loading the 'radeon' driver with modeset=1 (KMS enabled) the following error appears in dmesg | grep drm [drm:r100_ring_test] *ERROR* radeon: ring test failed (sracth(0x15E4)=0xCAFEDEAD) [drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22). the result is that OpenGL renderer with be the 'software rasterizer'. and performance is obviously crippled. glxinfo returns: OpenGL vendor string: Mesa Project OpenGL renderer string: Software Rasterizer OpenGL version string: 2.1 Mesa 7.8.1 The error occurs with kernels 2.6.33.4, 2.6.35.7 and even the latest at the time 2.6.36. The pc is a toshiba satellite m40-185 laptop with ati mobility radeon X300 (rv370) gpu. Additionally, I have tried installing the git versions of libdrm, mesa, and xf86-video-ati to this date (29/10/2010) with Gallium support (enabled in turn --enable-gallium, --enable-gallium-radeon and even both, using llvm (version 2.8) compiler. The problem persists. The only way to get 3d accelaration is to disable KMS. then dmesg | grep drm seems to load up fine (see here: http://pastebin.com/vNfyeq7P). But then I have problems with 3d applications 'competing' to stay on top - they don't seem to be able to work well with KDE4 compositing effects. To avoid that I have to disable the compositing effects ( see here for in depth explanation and some Xorg.0.log and dmesg outputs http://www.linuxquestions.org/questions/slackware-14/3d-applications-compet… ) -- 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 30620] New: KMS on RS100: no display on VGA
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=30620 Summary: KMS on RS100: no display on VGA 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: zajec5(a)gmail.com I've bug report from user with old notebook with ATI 320M (RS100). She installed openSUSE 11.3 which comes with 2.6.34 and can not get driver display anything. The important part is that notebook's PANEL is broken and she uses VGA for external monitor. There are two KMS cases I got tested by her: 1) "vga=0x31a" ─ black VGA screen right after booting start 2) "" (no vga) ─ black VGA screen right after booting start So I asked to experiment with UMS a little: 3) "vga=0x31a radeon.modeset=0 3" ─ radeonfb loads, VGA works! 4) "vga=0x31a radeon.modeset=0" ─ radeonfb works, black VGA screen on X start Without radeonfb: 5) "radeon.modeset=0 3" ─ pure console works on VGA, no radeonfb 6) "radeon.modeset=0" ─ pure console works on VGA, black VGA on X start My conclusions: 1) KMS can not initialize VGA 2) UMS can not initialize VGA 3) radeonfb *can* initialize VGA 4) There is no conflict with radeonfb, as dropping "vga=0x31a" does not help What else can I ask for to make it debuggable? I thought of Xorg.0.log but it may be hard to get for her as she had to mount some USB storage in console and copy file to it. Taking "dmesg | grep drm" could be easier. Would it be useful? -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel May 2011