dri-devel May 2013

dri-devel@lists.freedesktop.org

116 participants
705 discussions

[Bug 64801] KMS/R7xx - [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!
by bugzilla-daemon＠freedesktop.org 24 May '13

24 May '13

https://bugs.freedesktop.org/show_bug.cgi?id=64801 --- Comment #7 from Michel Dänzer <michel(a)daenzer.net> --- Every time '[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!' appears, the kernel drops some GPU rendering commands on the floor because it runs out of some kind of memory (-12 == -ENOMEM). This could explain any kind of visual corruption. Which version of Mesa are you using? -- You are receiving this mail because: You are the assignee for the bug.

1 0

PA_SC_RASTER_CONFIG
by Sylvain BERTRAND 24 May '13

24 May '13

Hi, ---- In si.c, the PA_SC_RASTER_CONFIG register is set with a golden value in 'si_init_golden_registers' function but get set nearly immediately after in 'si_setup_rb' function at a finer level (for each sh block of each se block). If I remember well, that golden value would be again set to the golden value in mesa. Is there one golden value for all se/sh blocks? Or are there computed (then overwritting the golden value) values for each se/sh? Why mesa would overwrite its value (I have not checked in lastest mesa)? (drm-next-3.10 branch, head 28ff680d66b9c6b8dbe9436742e39a47a16ea396) ---- In drm-next-3.10 branch, commit c9e065819056dd00ccecbf17a73ade03fa03ca8e, in verde_golden_registers, many registers are set several times in a row, expected? (that does not look like sequential programing registers, maybe some register backbone block routing trickery?) ---- Regards, -- Sylvain

2 1

[Bug 64801] KMS/R7xx - [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!
by bugzilla-daemon＠freedesktop.org 24 May '13

24 May '13

https://bugs.freedesktop.org/show_bug.cgi?id=64801 --- Comment #6 from Philip Prindeville <philipp(a)redfish-solutions.com> --- Also seeing the following: ftp://ftp.redfish-solutions.com/pub/Screenshot%20from%202013-05-20%2014:42:… the background isn't set, and the bottom of the screen seems to have fragments of OFF-screen backing store... which are ON-screen anyway. It's not clear if this is related to the parse relocation error or is an entirely different issue. -- You are receiving this mail because: You are the assignee for the bug.

1 0

Radeon atombios power state can cause NULL pointer dereference
by Clément Calmels 23 May '13

23 May '13

Hi, My Packard Bell Dot M/A laptop (ATI x1200/rs690m) fails during resume: [ 73.033179] BUG: unable to handle kernel NULL pointer dereference at 0000000000000020 [ 73.033184] IP: [<ffffffffa0418dc3>] radeon_pm_resume+0xda/0x137 [radeon] [ 73.033227] PGD 0 [ 73.033231] Oops: 0000 [#1] SMP [ 73.033236] CPU 0 [ 73.033238] Modules linked in: cryptd aes_x86_64 aes_generic uinput loop snd_hda_codec_realtek arc4 ath9k joydev snd_hda_intel radeon ath9k_common ath9k_hw snd_hda_codec ath ttm snd_hwdep uvcvideo drm_kms_helper mac80211 videodev snd_pcm snd_page_alloc snd_seq snd_seq_device snd_timer drm v4l2_compat_ioctl32 media cfg80211 edac_mce_amd mperf acerhdf acer_wmi snd sp5100_tco sparse_keymap pcspkr edac_core rfkill soundcore i2c_piix4 i2c_algo_bit k8temp psmouse i2c_core evdev serio_raw video wmi shpchp processor ac battery power_supply button ext4 crc16 jbd2 mbcache sg sd_mod crc_t10dif ata_generic ahci libahci pata_atiixp libata ohci_hcd ehci_hcd usbcore scsi_mod thermal thermal_sys r8169 mii usb_common [last unloaded: scsi_wait_scan] [ 73.033304] [ 73.033310] Pid: 154, comm: kworker/u:6 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.41-2+deb7u2 Packard Bell DOTMA /SJM11-YK [ 73.033317] RIP: 0010:[<ffffffffa0418dc3>] [<ffffffffa0418dc3>] radeon_pm_resume+0xda/0x137 [radeon] [ 73.033347] RSP: 0018:ffff880037631db0 EFLAGS: 00010297 [ 73.033350] RAX: ffff88006b8fa1d0 RBX: ffff88003715c000 RCX: 0000000000000000 [ 73.033354] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88003715d3a8 [ 73.033358] RBP: ffff88003715d3a8 R08: 0000000000000002 R09: 0000000000000028 [ 73.033362] R10: 0000000000001700 R11: 0000000000001700 R12: 0000000000000000 [ 73.033366] R13: ffffffff8142db90 R14: ffff88006d733c05 R15: ffff88006b6156d0 [ 73.033372] FS: 00007f96cf0ea700(0000) GS:ffff88006fc00000(0000) knlGS:0000000000000000 [ 73.033376] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b [ 73.033380] CR2: 0000000000000020 CR3: 0000000001605000 CR4: 00000000000006f0 [ 73.033385] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 73.033389] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 73.033394] Process kworker/u:6 (pid: 154, threadinfo ffff880037630000, task ffff8800375415d0) [ 73.033397] Stack: [ 73.033399] ffff88006b737000 ffff88003715c000 ffff88006b737000 ffffffffa03d5a26 [ 73.033406] ffff88006cc57090 0000000000000000 0000000000000000 ffffffff81255b88 [ 73.033411] ffff880037631d2c ffff88006cc57090 ffff88006cc570f0 0000000000000000 [ 73.033417] Call Trace: [ 73.033439] [<ffffffffa03d5a26>] ? radeon_resume_kms+0x82/0x114 [radeon] [ 73.033448] [<ffffffff81255b88>] ? pm_op+0xa1/0x141 [ 73.033455] [<ffffffff81255f4c>] ? device_resume+0xa2/0xfc [ 73.033461] [<ffffffff81255fba>] ? async_resume+0x14/0x38 [ 73.033469] [<ffffffff810648cc>] ? async_run_entry_fn+0x96/0x142 [ 73.033475] [<ffffffff8105b22d>] ? process_one_work+0x161/0x264 [ 73.033484] [<ffffffff81059b3e>] ? need_to_create_worker+0x9/0x1c [ 73.033489] [<ffffffff8105c1ee>] ? worker_thread+0xc2/0x145 [ 73.033495] [<ffffffff8105c12c>] ? manage_workers.isra.25+0x15b/0x15b [ 73.033502] [<ffffffff8105f329>] ? kthread+0x76/0x7e [ 73.033509] [<ffffffff81354b34>] ? kernel_thread_helper+0x4/0x10 [ 73.033515] [<ffffffff8105f2b3>] ? kthread_worker_fn+0x139/0x139 [ 73.033521] [<ffffffff81354b30>] ? gs_change+0x13/0x13 [ 73.033523] Code: 14 00 00 8b 93 38 14 00 00 89 83 14 14 00 00 48 6b c0 30 48 03 83 08 14 00 00 89 93 2c 14 00 00 83 bb 48 14 00 00 01 48 8b 50 08 <8b> 52 20 66 89 93 30 14 00 00 48 8b 40 08 66 8b 40 22 66 89 83 [ 73.033565] RIP [<ffffffffa0418dc3>] radeon_pm_resume+0xda/0x137 [radeon] [ 73.033593] RSP <ffff880037631db0> [ 73.033596] CR2: 0000000000000020 Digging a little bit, the issue can be highlighted with this patch: --- drivers/gpu/drm/radeon/radeon_atombios.c.orig 2013-05-23 21:54:50.514665155 +0200 +++ drivers/gpu/drm/radeon/radeon_atombios.c 2013-05-24 00:20:43.149263167 +0200 @@ -2159,6 +2159,7 @@ static int radeon_atombios_parse_power_t } /* last mode is usually default */ if (rdev->pm.default_power_state_index == -1) { + WARN_ON(state_index == 0); rdev->pm.power_state[state_index - 1].type = POWER_STATE_TYPE_DEFAULT; rdev->pm.default_power_state_index = state_index - 1; In my case, the laptop report 0 for memory clock for all power states. At the end of the for loop, state_index still equals 0, leading to a wrong access in the rdev->pm.power_state array. When switching memory clock in async mode (instead of sync mode) within the bios, the laptop correctly reports its value (ie 333MHz). Regards, Clement

1 0

Radeon atombios power state can cause NULL pointer dereference
by Clément Calmels 23 May '13

23 May '13

1 0

[Bug 64879] New: i915 doesn't do derivatives, neither gallium nor intel driver
by bugzilla-daemon＠freedesktop.org 23 May '13

23 May '13

https://bugs.freedesktop.org/show_bug.cgi?id=64879 Priority: medium Bug ID: 64879 CC: idr(a)freedesktop.org Assignee: dri-devel(a)lists.freedesktop.org Summary: i915 doesn't do derivatives, neither gallium nor intel driver Severity: normal Classification: Unclassified OS: All Reporter: fjhmesabug(a)gmail.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/i915g Product: Mesa Any way to support dFdx() on i915? -- You are receiving this mail because: You are the assignee for the bug.

1 4

[PATCH 00/33] devm improvement series, part 1, take 2
by Wolfram Sang 23 May '13

23 May '13

Lately, I have been experimenting how to improve the devm interface to make writing device drivers easier and less error prone while also getting rid of its subtle issues. I think it has more potential but still needs work and definately conistency, especiall in its usage. The first thing I come up with is a low hanging fruit regarding devm_ioremap_resouce(). This function already checks if the passed resource is valid and gives an error message if not. So, we can remove similar checks from the drivers and get rid of a bit of code and a number of inconsistent error strings. Unlike the RFC version, this series only removes the unneeded check iff devm_ioremap_resource() follows platform_get_resource directly. The previous version tried to shuffle code if needed, too, what lead to an embarrasing bug. It turned out to me that shuffling code for all cases found will make the automated script too complex, so I am unsure if an automated cleanup is the proper tool for this case. Removing the easy stuff seems worthwhile to me, though, so I post this series in a simplified form. Despite various architectures and platform dependencies, I managed to compile test 45 out of 57 modified files locally using heuristics and defconfigs. If somebody knows how to create a minimal .config with a certain kconfig symbol (and its dependencies) set, I'd love to hear about it. Since this series looks quite different from the RFC (less files touched mainly) I did not copy over the ACKs from the RFC, although a few people agreed with the aproach basically (except the major flaw the old series had). The repo is here [1]. I'd think it would be nice to have in 3.10. and sending a pull request to Linus would be easiest, probably. Some non-buggy RFC patches already slipped into subtrees, yet this won't cause any conflicts. Looking forward to comments. Thanks, Wolfram [1] git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git devm_no_resource_check Wolfram Sang (33): drivers/ata: don't check resource with devm_ioremap_resource drivers/char/hw_random: don't check resource with devm_ioremap_resource drivers/cpufreq: don't check resource with devm_ioremap_resource drivers/dma: don't check resource with devm_ioremap_resource drivers/gpio: don't check resource with devm_ioremap_resource drivers/gpu/drm/exynos: don't check resource with devm_ioremap_resource drivers/gpu/host1x/drm: don't check resource with devm_ioremap_resource drivers/i2c/busses: don't check resource with devm_ioremap_resource drivers/memory: don't check resource with devm_ioremap_resource drivers/mfd: don't check resource with devm_ioremap_resource drivers/misc: don't check resource with devm_ioremap_resource drivers/mtd/nand: don't check resource with devm_ioremap_resource drivers/net/ethernet/renesas: don't check resource with devm_ioremap_resource drivers/pinctrl: don't check resource with devm_ioremap_resource drivers/pwm: don't check resource with devm_ioremap_resource drivers/rtc: don't check resource with devm_ioremap_resource drivers/spi: don't check resource with devm_ioremap_resource drivers/staging/dwc2: don't check resource with devm_ioremap_resource drivers/staging/nvec: don't check resource with devm_ioremap_resource drivers/thermal: don't check resource with devm_ioremap_resource drivers/usb/chipidea: don't check resource with devm_ioremap_resource drivers/usb/gadget: don't check resource with devm_ioremap_resource drivers/usb/host: don't check resource with devm_ioremap_resource drivers/usb/phy: don't check resource with devm_ioremap_resource drivers/video/omap2: don't check resource with devm_ioremap_resource drivers/video/omap2/dss: don't check resource with devm_ioremap_resource drivers/w1/masters: don't check resource with devm_ioremap_resource drivers/watchdog: don't check resource with devm_ioremap_resource arch/arm/mach-tegra: don't check resource with devm_ioremap_resource arch/arm/plat-samsung: don't check resource with devm_ioremap_resource arch/mips/lantiq/xway: don't check resource with devm_ioremap_resource sound/soc/fsl: don't check resource with devm_ioremap_resource sound/soc/kirkwood: don't check resource with devm_ioremap_resource arch/arm/mach-tegra/tegra2_emc.c | 5 ----- arch/arm/plat-samsung/adc.c | 5 ----- arch/mips/lantiq/xway/gptu.c | 4 ---- drivers/ata/pata_ep93xx.c | 5 ----- drivers/char/hw_random/mxc-rnga.c | 6 ------ drivers/char/hw_random/omap-rng.c | 5 ----- drivers/cpufreq/kirkwood-cpufreq.c | 4 ---- drivers/dma/tegra20-apb-dma.c | 5 ----- drivers/gpio/gpio-mvebu.c | 5 ----- drivers/gpio/gpio-tegra.c | 5 ----- drivers/gpu/drm/exynos/exynos_hdmi.c | 5 ----- drivers/gpu/host1x/drm/dc.c | 5 ----- drivers/i2c/busses/i2c-s3c2410.c | 5 ----- drivers/i2c/busses/i2c-sirf.c | 6 ------ drivers/i2c/busses/i2c-tegra.c | 5 ----- drivers/memory/emif.c | 6 ------ drivers/mfd/intel_msic.c | 5 ----- drivers/misc/atmel-ssc.c | 5 ----- drivers/mtd/nand/lpc32xx_mlc.c | 5 ----- drivers/net/ethernet/renesas/sh_eth.c | 5 ----- drivers/pinctrl/pinctrl-coh901.c | 5 ----- drivers/pinctrl/pinctrl-exynos5440.c | 5 ----- drivers/pinctrl/pinctrl-samsung.c | 5 ----- drivers/pinctrl/pinctrl-xway.c | 4 ---- drivers/pwm/pwm-imx.c | 5 ----- drivers/pwm/pwm-puv3.c | 5 ----- drivers/pwm/pwm-pxa.c | 5 ----- drivers/pwm/pwm-tegra.c | 5 ----- drivers/pwm/pwm-tiecap.c | 5 ----- drivers/pwm/pwm-tiehrpwm.c | 5 ----- drivers/pwm/pwm-tipwmss.c | 5 ----- drivers/pwm/pwm-vt8500.c | 5 ----- drivers/rtc/rtc-nuc900.c | 5 ----- drivers/rtc/rtc-omap.c | 5 ----- drivers/rtc/rtc-s3c.c | 5 ----- drivers/rtc/rtc-tegra.c | 6 ------ drivers/spi/spi-tegra20-sflash.c | 5 ----- drivers/staging/dwc2/platform.c | 5 ----- drivers/staging/nvec/nvec.c | 5 ----- drivers/thermal/armada_thermal.c | 10 ---------- drivers/thermal/dove_thermal.c | 4 ---- drivers/thermal/exynos_thermal.c | 5 ----- drivers/usb/chipidea/core.c | 5 ----- drivers/usb/gadget/bcm63xx_udc.c | 10 ---------- drivers/usb/host/ohci-nxp.c | 6 ------ drivers/usb/phy/phy-mv-u3d-usb.c | 5 ----- drivers/usb/phy/phy-mxs-usb.c | 5 ----- drivers/usb/phy/phy-samsung-usb2.c | 5 ----- drivers/usb/phy/phy-samsung-usb3.c | 5 ----- drivers/video/omap2/dss/hdmi.c | 4 ---- drivers/video/omap2/vrfb.c | 5 ----- drivers/w1/masters/omap_hdq.c | 5 ----- drivers/watchdog/ath79_wdt.c | 5 ----- drivers/watchdog/davinci_wdt.c | 5 ----- drivers/watchdog/imx2_wdt.c | 5 ----- sound/soc/fsl/imx-ssi.c | 6 ------ sound/soc/kirkwood/kirkwood-i2s.c | 5 ----- 57 files changed, 296 deletions(-) -- 1.7.10.4

3 3

[Bug 64738] New: graphics corruption with glamor
by bugzilla-daemon＠freedesktop.org 23 May '13

23 May '13

https://bugs.freedesktop.org/show_bug.cgi?id=64738 Priority: medium Bug ID: 64738 Assignee: dri-devel(a)lists.freedesktop.org Summary: graphics corruption with glamor Severity: normal Classification: Unclassified OS: All Reporter: alexander(a)tsoy.me Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa I have these problems with Cape Verde Pro (HD 7750) card: 1. Graphics corruption when scrolling in gtk2/gtk3 apps (screenshot [1]) 2. Graphics corruption when moving windows in wm whithout compositing. Both gtk and qt apps are affected. No such artifacts when compositing enabled, e.g. in gnome 3. (screenshot [2]) 3. Missing notification icons of gtk2 apps in awesome wm. All of this things works great whithout glamor. Also no such problems with HD 6450 card with both EXA and glamor acceleration. Software: - mesa-9.2 from git - llvm-3.{3,4} from git - xorg-server-1.13.4, also tried 1.12* - xf86-video-ati-7.1.0 - glamor-0.5 - linux kernel 3.8* including latest 3.8.13 Also note, that with mesa-9.0* and mesa-9.1* Xorg segfaults at startup on this system when glamor enabled, but this is a subject for another bug report. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 49981] On HD6850, Power Profile doesn't change if 2 screen is attached.
by bugzilla-daemon＠freedesktop.org 23 May '13

23 May '13

https://bugs.freedesktop.org/show_bug.cgi?id=49981 --- Comment #34 from Evgeny <evgenyz(a)gmail.com> --- Excuse me for disturbing all of you here, but, please, can anyone help me finding kernel with these patches already packaged? Some PPAs? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[GIT PULL] exynos-drm-fixes
by Inki Dae 23 May '13

23 May '13

Hi Dave, This pull request includes drm_send_vblank_event() helper relevant patch I missed and code cleanups. And also it fixes a pended page flip issue. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 0eca56f9467038ee0b798637f03581aaa1186fac: drm/imx: use drm_send_vblank_event() helper (2013-05-22 09:13:42 +1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos exynos-drm-fixes Inki Dae (1): drm/exynos: wait for the completion of pending page flip Lars-Peter Clausen (1): drm/exynos: exynos_hdmi: Pass correct pointer to free_irq() Rob Clark (2): drm/exynos: page flip fixes drm/exynos: use drm_send_vblank_event() helper Sachin Kamat (2): drm/exynos: exynos_drm_fbdev: Fix incorrect usage of IS_ERR_OR_NULL drm/exynos: exynos_drm_ipp: Fix incorrect usage of IS_ERR_OR_NULL Seung-Woo Kim (4): drm/exynos: cleanup device pointer usages drm/exynos: fix build warnings from ipp fimc drm/exynos: remove unnecessary devm_kfree drm/exynos: replace request_threaded_irq with devm function drivers/gpu/drm/exynos/exynos_drm_crtc.c | 27 ++++++++++++++++++--------- drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 2 +- drivers/gpu/drm/exynos/exynos_drm_fimc.c | 12 ++++-------- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 10 +++++----- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 6 +++--- drivers/gpu/drm/exynos/exynos_drm_gsc.c | 12 +++--------- drivers/gpu/drm/exynos/exynos_drm_hdmi.c | 2 +- drivers/gpu/drm/exynos/exynos_drm_ipp.c | 18 +++++++++--------- drivers/gpu/drm/exynos/exynos_drm_rotator.c | 13 +++---------- drivers/gpu/drm/exynos/exynos_drm_vidi.c | 4 ++-- drivers/gpu/drm/exynos/exynos_hdmi.c | 21 ++++++++------------- drivers/gpu/drm/exynos/exynos_mixer.c | 14 +++++++------- 12 files changed, 64 insertions(+), 77 deletions(-)

1 0

← Newer
1
...
52
53
54
55
56
57
58
...
71
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel May 2013