[Bug 42887] Garbled display on external screen when using 1920x1080 instead of 1920x1200
https://bugzilla.kernel.org/show_bug.cgi?id=42887 Florian Mickler changed: What|Removed |Added CC||florian at mickler.org --- Comment #1 from Florian Mickler 2012-03-12 22:23:12 --- A patch referencing this bug report has been merged in Linux v3.3-rc7: commit 38aa4a568ba4c3ccba83e862a01e3e60e3b811ee Author: Alex Deucher Date: Wed Mar 7 19:05:01 2012 -0500 drm/radeon/kms: fix hdmi duallink checks -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug.
[Bug 47007] HDMI monitor polling causing 100ms rendering stalls
https://bugs.freedesktop.org/show_bug.cgi?id=47007 --- Comment #13 from Alex Deucher 2012-03-12 11:34:39 PDT --- Sorry for the confusion, I mixed up the patches. I was referring to the previous patch (attachment 58160). The patch in attachment 58318 looks good. The only thing I would add is a check to make sure rdev->family >= CHIP_R600 since the HPD mapping was not always set up reliably by OEMs on prior asics. With that, you can add: Reviewed-by: Alex Deucher -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 47244] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
https://bugs.freedesktop.org/show_bug.cgi?id=47244 --- Comment #2 from adres7 at gmail.com 2012-03-12 11:13:12 PDT ---
No subject
-- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 47244] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
https://bugs.freedesktop.org/show_bug.cgi?id=47244 --- Comment #1 from adres7 at gmail.com 2012-03-12 11:12:22 PDT --- Created attachment 58336 --> https://bugs.freedesktop.org/attachment.cgi?id=58336 Log from wine -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 47244] New: [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
https://bugs.freedesktop.org/show_bug.cgi?id=47244 Bug #: 47244 Summary: [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! Classification: Unclassified Product: Mesa Version: 7.11 Platform: x86 (IA32) OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: adres7 at gmail.com Created attachment 58335 --> https://bugs.freedesktop.org/attachment.cgi?id=58335 Screenshot Hello. I have problem with a game. I would like to run the game, but it does not work. It's Warcraft. 1. Run Garena. 2. By the Garena start Warcraft III. 3. Garena's window is minimized but there is no Warcraft's window. I only hear music from the game. I get these messages: kernel: [ 2237.829228] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! kernel: [ 2237.836653] [drm:r100_cs_track_check] *ERROR* [drm] No buffer for z buffer ! -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 47007] HDMI monitor polling causing 100ms rendering stalls
https://bugs.freedesktop.org/show_bug.cgi?id=47007 --- Comment #12 from Simon Farnsworth 2012-03-12 08:13:05 PDT --- Alex, The monitor is not polling - the hotplug detect code is being called because the VGA is polled as DRM_CONNECTOR_POLL_CONNECT, and the output_poll_execute function in drm_crtc_helper.c checks every output when a poll happens. Because the VGA needs polling once every ten seconds, output_poll_execute is called on each HPD interrupt, and once every ten seconds beyond that. radeon_dvi_detect is heavy-duty, and does a full EDID fetch every time it's called, stalling us for 100ms once every ten seconds for as long as the VGA is disconnected. Tvrtko's fix changes radeon_dvi_detect to be lightweight in the case that affects us, where a HPD pin is wired up correctly. The alternative is to do major surgery on the core DRM, and teach output_poll_execute and drm_helper_hpd_irq_event, to only check outputs that have either had a HPD interrupt since the last time they were checked, or that are marked for polling. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 47007] HDMI monitor polling causing 100ms rendering stalls
https://bugs.freedesktop.org/show_bug.cgi?id=47007 --- Comment #11 from Alex Deucher 2012-03-12 07:56:06 PDT --- The code is correct as is. I think what's happening is that your monitor is polling and causing hotplug unplug/plug events what cause the detect code to run. Can you try disabling the input polling on your monitor? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 46725] Monitor "disconnected" and refuses to work anymore
https://bugs.freedesktop.org/show_bug.cgi?id=46725 --- Comment #9 from Alex Deucher 2012-03-12 06:53:28 PDT --- Does booting with radeon.disp_priority=2 on the kernel command line in grub help? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 47007] HDMI monitor polling causing 100ms rendering stalls
https://bugs.freedesktop.org/show_bug.cgi?id=47007 Tvrtko Ursulin changed: What|Removed |Added Attachment #58160|0 |1 is obsolete|| --- Comment #10 from Tvrtko Ursulin 2012-03-12 06:44:33 PDT --- Created attachment 58318 --> https://bugs.freedesktop.org/attachment.cgi?id=58318 Different approach on fixing the stalls After talking with a colleague who is more at home in this code we think the previous patch is wrong. This new patch uses a different approach which also works for us. In short, it doesn't do the full EDID re-fetch if HPD sense says we are still connected. Plus some other conditions only of which the shared_ddc one I am not completely sure. I've put it in to minimise the change in behaviour. Comments? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 42490] NUTMEG DP to VGA bridge not working
https://bugs.freedesktop.org/show_bug.cgi?id=42490 Alex Deucher changed: What|Removed |Added CC||diego.abelenda at gmail.com --- Comment #11 from Alex Deucher 2012-03-12 06:43:07 PDT --- *** Bug 47064 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 47201] Absolute modifier does not work with 3-source TGSI instructions
https://bugs.freedesktop.org/show_bug.cgi?id=47201 --- Comment #5 from Vic Lee 2012-03-12 06:34:57 PDT --- Created attachment 58317 --> https://bugs.freedesktop.org/attachment.cgi?id=58317 test program to reproduce 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.
[Bug 47201] Absolute modifier does not work with 3-source TGSI instructions
https://bugs.freedesktop.org/show_bug.cgi?id=47201 --- Comment #4 from Vic Lee 2012-03-12 06:33:54 PDT --- Thanks for concerning this bug. It will be great if this can be fixed at driver level. I created a smallest possible test program which will be able to test the shader I am having problem with. Please see the file header for test info. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH 1/3] drivers-gpu-drm-allow-to-load-edid-firmware.patch
On Sat, 10 Mar 2012 21:20:15 +0100, Carsten Emde said: > EDID data source files are provided for documentation purpose and as a > template to create EDID data sets for other screen resolutions. Note > that source compilation is not part of the build process, but needs to > be done manually, e.g. > > #!/bin/bash > cd firmware/edid > for i in [1-9]*.S > do Would it be possible to include a version of this patch's Changelog as a file under Documentation/fixing-broken-edid.txt or something, so people don't have to go and find the git commit log to know things like "you need to run dos2unix"? Be a shame to have a changelog that does such a good job of documenting what you need to do, and have it lost in git... -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 865 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20120312/eec33259/attachment.pgp>
[Bug 46713] HDMI audio played back at a wrong rate
https://bugs.freedesktop.org/show_bug.cgi?id=46713 --- Comment #15 from Tvrtko Ursulin 2012-03-12 04:28:27 PDT --- Created attachment 58307 --> https://bugs.freedesktop.org/attachment.cgi?id=58307 avivotool register dump under fglrx with non-existant LVDS output turned off -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 46713] HDMI audio played back at a wrong rate
https://bugs.freedesktop.org/show_bug.cgi?id=46713 --- Comment #14 from Tvrtko Ursulin 2012-03-12 04:27:51 PDT --- Created attachment 58306 --> https://bugs.freedesktop.org/attachment.cgi?id=58306 avivotool register dump under fglrx I've managed to get fglrx running and initially playback speed was fine but audio quite distorted (hard to describe). I've noticed in the output a mention of 1024x768 output resolution on the LVDS connector which was unexpected, since the motherboard in question only has HDMI and VGA outputs. I disabled LVDS with xranrd and then audio was perfect. I will attach that register dump as well. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 46725] Monitor "disconnected" and refuses to work anymore
https://bugs.freedesktop.org/show_bug.cgi?id=46725 --- Comment #8 from Tomi Pievil?inen2012-03-12 03:17:18 PDT --- Seems like I can reproduce this every time I view a certain photo taken with my phone in feh... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 46725] Monitor "disconnected" and refuses to work anymore
https://bugs.freedesktop.org/show_bug.cgi?id=46725 --- Comment #7 from Tomi Pievil?inen2012-03-12 03:15:07 PDT --- This has happened several times more to me. It happens very often when watching a HD video, and some times when viewing photos. Hasn't happened in normal desktop use. I've also noticed that I can get it back on by forcing it off with xrandr, and then back on. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 46796] [X800SE] Mouse cursor corruption when switching users
https://bugs.freedesktop.org/show_bug.cgi?id=46796 Michel D?nzer changed: What|Removed |Added Attachment #58066|0 |1 is obsolete|| --- Comment #10 from Michel D?nzer 2012-03-12 05:13:22 UTC --- Created attachment 58312 --> https://bugs.freedesktop.org/attachment.cgi?id=58312 Verbose test patch with crash fixed (In reply to comment #9) > This patch causes my computer to crash at login. However, it's not a super bad > crash because I was able to ssh in and check dmesg. Sorry about that, here's another test patch which shouldn't crash. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 47201] Absolute modifier does not work with 3-source TGSI instructions
https://bugs.freedesktop.org/show_bug.cgi?id=47201 Tom Stellard changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|NOTABUG | --- Comment #3 from Tom Stellard 2012-03-11 18:07:27 PDT --- The is a bug in the r600 driver. The shader compiler should be lowering this to the hardware equivalent of this sequence: ABS TEMP[5], TEMP[1]. CMP TEMP[0].yz, -TEMP[5], TEMP[2]., CONST[0].xyxw Is there a piglit test or application that is hitting this bug? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH 1/3] drivers-gpu-drm-allow-to-load-edid-firmware.patch
Alan, >> This patch allows to load an EDID data set via the firmware interface. >> It contains data sets of frequently used screen resolutions (1024x768, >> 1280x1024, 1680x1050 and 1920x1080). The requested EDID data are >> specified as a module parameter of the drm_kms_helper module, e.g. >> options drm_kms_helper edid_firmware=edid/1280x1024.bin or as kernel >> command line parameter. > [..] > Given the EDID is tiny and is data not code wouldn't it be simpler (and > smaller) if this option compiled in a few generic EDIDs to use ? I liked the idea so much that I gave it a try. The patch looks much better now, but has the same functionality as before. As the only disadvantage, the patch no longer contains the template to produce a particular EDID. But this code may be made available elsewhere - no need to have it in the kernel. Hope you like it. Thanks, -Carsten. -- next part -- A non-text attachment was scrubbed... Name: drivers-gpu-drm-allow-to-load-edid-firmware.patch Type: text/x-patch Size: 15365 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20120312/4d86c899/attachment-0001.bin>
[BUG] inconsistent DPMS settings
Hi I was tracing down a bug that made drmModePageFlip() fail and I noticed that the DPMS settings are not correctly restored when switching between xorg-server and vtcon. In fact, when enabling a monitor with xrandr in X while DPMS=off for that monitor, then it will stay blank. Switching back to VT1 and forth to X will enable it, eventually. That is, the VT-switch handler of the xserver seems to correctly reset the DPMS state but the monitor-hotplug handler does not. The same thing happens if I disable a monitor with xrandr and switch back to vtcon. The monitor is enabled again so I can work with both monitors but if I switch to X again and then back to vtcon, then only one monitor is active in vtcon. I can track the DPMS state with /sys/class/drm/card0-/dpms. However, vtcon doesn't care whether this says On or Off. It sometimes displays even though it is Off or sometimes doesn't display anything even though it is On. Is the DPMS-state even tracked by vtcon/xserver when switching VTs? I expect them to save their state and restore it if I switch back. However, I don't know whether this is the desired behavior. I am using the intel i915 drivers, if that matters. xserver, kernel, mesa etc. are a mixture between most recent release and git-master. Regards David
[PATCH 0/3] Provide workarounds to use DRM/KMS with broken graphics hardware
In the good old days when graphics parameters were configured explicitly in a file called xorg.conf, even broken hardware could be managed. Today, with the advent of Kernel Mode Setting, a graphics board is either correctly working because all components follow the standards - or the computer is unusable, because the screen remains dark after booting or displays the wrong area. Cases when this happens are: - The BIOS assumes that an LVDS is always connected, even if it isn't. - The graphics board does not recognize the monitor. - The graphics board is unable to detect any EDID data. - The graphics board incorrectly forwards EDID data to the driver. - The monitor sends bogus EDID data. - A KVM sends its own EDID data instead of querying the connected monitor. - The brightness setting of the panel backlight does not work. - Any combination of the above. Adding the kernel parameter nomodeset helps in most cases, but causes restrictions later on. The three patches of this series add module parameters to the drm_kms_helper module that 1. allow to load an EDID data set via the firmware interface, 2. provide a module parameter to selectively enable or disable a graphics port, 3. provide a module parameter to select inverted brightness. EDID data sets along with source files are provided for commonly used screen resolutions (1024x768, 1280x1024, 1680x1050, 1920x1080). Please note that these patches neither fix a kernel bug nor provide any extra functionality. They simply work around broken hardware that otherwise would be either unusable or usable in a very restricted way. The patches do not modify the current functionality of the related components in any way, unless the kernel is configured accordingly and/or the newly provided module parameters are set. -Carsten. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH 3/3] drivers-gpu-drm-i915-invert-backlight-brightness
Following the documentation of the Legacy Backlight Brightness (LBB) Register in the configuration space of some Intel PCI graphics adapters, setting the LBB register with the value 0x0 causes the backlight to be turned off, and 0xFF causes the backlight to be set to 100% intensity (http://download.intel.com/embedded/processors/Whitepaper/324567.pdf). At least one of our test systems, however, turns the backlight off at 0xFF and sets it to maximum intensity at 0. In consequence, the screen of this systems becomes dark at an early boot stage which makes it unusable. The same inversion applies to the BLC_PWM_CTL I915 register. This problem was introduced in kernel version 2.6.38 when the PCI device of this system was first supported by the i915 KMS module. This patch adds a module parameter to invert the backlight brightness value before writing and after reading which makes the affected notebook usable again. Signed-off-by: Carsten Emde c.e...@osadl.org --- Documentation/kernel-parameters.txt |9 + drivers/gpu/drm/i915/intel_panel.c | 14 ++ 2 files changed, 23 insertions(+) Index: linux-3.3-rc6/Documentation/kernel-parameters.txt === --- linux-3.3-rc6.orig/Documentation/kernel-parameters.txt +++ linux-3.3-rc6/Documentation/kernel-parameters.txt @@ -975,6 +975,15 @@ bytes respectively. Such letter suffixes i810= [HW,DRM] + i915.invert_brightness + [DRM] Invert the sense of the variable that is used to + set the brightness of the panel backlight. Normally a + value of 0 indicates backlight switched off, and the + maximum value sets the backlight to maximum brightness. + If this parameter is specified, a value of 0 sets the + backlight to maximum brightness, and the maximum value + switches the backlight off. + i8k.ignore_dmi [HW] Continue probing hardware even if DMI data indicates that the driver is running on unsupported hardware. Index: linux-3.3-rc6/drivers/gpu/drm/i915/intel_panel.c === --- linux-3.3-rc6.orig/drivers/gpu/drm/i915/intel_panel.c +++ linux-3.3-rc6/drivers/gpu/drm/i915/intel_panel.c @@ -28,6 +28,7 @@ * Chris Wilson ch...@chris-wilson.co.uk */ +#include linux/moduleparam.h #include intel_drv.h #define PCI_LBPC 0xf4 /* legacy/combination backlight modes */ @@ -191,6 +192,10 @@ u32 intel_panel_get_max_backlight(struct return max; } +static bool brightness_inverted; +MODULE_PARM_DESC(brightness_inverted, Backlight brightness value is inverted + (0 = max brightness, max value = dark)); +module_param_named(brightness_inverted, brightness_inverted, bool, 0600); u32 intel_panel_get_backlight(struct drm_device *dev) { struct drm_i915_private *dev_priv = dev-dev_private; @@ -212,6 +217,10 @@ u32 intel_panel_get_backlight(struct drm } DRM_DEBUG_DRIVER(get backlight PWM = %d\n, val); + if (brightness_inverted) { + u32 max = intel_panel_get_max_backlight(dev); + val = max - val; + } return val; } @@ -229,6 +238,11 @@ static void intel_panel_actually_set_bac DRM_DEBUG_DRIVER(set backlight PWM = %d\n, level); + if (brightness_inverted) { + u32 max = intel_panel_get_max_backlight(dev); + level = max - level; + } + if (HAS_PCH_SPLIT(dev)) return intel_pch_panel_set_backlight(dev, level); ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH 2/2] module: avoid exporting module_mutex
Avoid exporting internal locks to modules, export two functions lock_modules()/unlock_modules() for them instead. Cc: Rusty Russell ru...@rustcorp.com.au Signed-off-by: Cong Wang xiyou.wangc...@gmail.com --- drivers/gpu/drm/drm_fb_helper.c |4 ++-- include/linux/module.h |3 ++- kernel/kprobes.c|4 ++-- kernel/module.c | 16 ++-- 4 files changed, 20 insertions(+), 7 deletions(-) diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/drm/drm_fb_helper.c index aada26f..c184759 100644 --- a/drivers/gpu/drm/drm_fb_helper.c +++ b/drivers/gpu/drm/drm_fb_helper.c @@ -1451,9 +1451,9 @@ static int __init drm_fb_helper_modinit(void) const char *name = fbcon; struct module *fbcon; - mutex_lock(module_mutex); + lock_modules(); fbcon = find_module(name); - mutex_unlock(module_mutex); + unlock_modules(); if (!fbcon) request_module_nowait(name); diff --git a/include/linux/module.h b/include/linux/module.h index 4598bf0..5cf6428 100644 --- a/include/linux/module.h +++ b/include/linux/module.h @@ -374,7 +374,8 @@ struct module #define MODULE_ARCH_INIT {} #endif -extern struct mutex module_mutex; +extern void lock_modules(void); +extern void unlock_modules(void); /* FIXME: It'd be nice to isolate modules during init, too, so they aren't used before they (may) fail. But presently too much code diff --git a/kernel/kprobes.c b/kernel/kprobes.c index c62b854..0670fb1 100644 --- a/kernel/kprobes.c +++ b/kernel/kprobes.c @@ -562,7 +562,7 @@ static __kprobes void kprobe_optimizer(struct work_struct *work) LIST_HEAD(free_list); /* Lock modules while optimizing kprobes */ - mutex_lock(module_mutex); + lock_modules(); mutex_lock(kprobe_mutex); /* @@ -587,7 +587,7 @@ static __kprobes void kprobe_optimizer(struct work_struct *work) do_free_cleaned_kprobes(free_list); mutex_unlock(kprobe_mutex); - mutex_unlock(module_mutex); + unlock_modules(); /* Step 5: Kick optimizer again if needed */ if (!list_empty(optimizing_list) || !list_empty(unoptimizing_list)) diff --git a/kernel/module.c b/kernel/module.c index e0b12f7..1165d5d 100644 --- a/kernel/module.c +++ b/kernel/module.c @@ -95,8 +95,20 @@ * 2) module_use links, * 3) module_addr_min/module_addr_max. * (delete uses stop_machine/add uses RCU list operations). */ -DEFINE_MUTEX(module_mutex); -EXPORT_SYMBOL_GPL(module_mutex); +static DEFINE_MUTEX(module_mutex); + +void lock_modules(void) +{ + mutex_lock(module_mutex); +} +EXPORT_SYMBOL(lock_modules); + +void unlock_modules(void) +{ + mutex_unlock(module_mutex); +} +EXPORT_SYMBOL(unlock_modules); + static LIST_HEAD(modules); #ifdef CONFIG_KGDB_KDB struct list_head *kdb_modules = modules; /* kdb needs the list of modules */ -- 1.7.7.6 ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH 2/3] drivers-gpu-drm-add-disable-enable-connector.patch
Some recent integrated graphics chipset, notably Intel's Pineview, also provide on-chip LVDS support. As an extra service, the LVDS interface supplies EDID data - irrespective of whether an LVDS panel is connected or not. The drm_mode_getresources() function, therefore, causes Xorg to always include the LVDS panel into the display and initialize a separate screen for it. e.g. (II) intel(0): Output LVDS1 connected (II) intel(0): Output VGA1 connected (II) intel(0): Using spanning desktop for initial modes (II) intel(0): Output LVDS1 using initial mode 1024x768 +0+0 (II) intel(0): Output VGA1 using initial mode 1280x1024 +1024+0 which is not what you want, if the only connected screen is a VGA monitor. One would assume that the BIOS settings of such systems would allow to separately enable or disable LVDS support; unfortunately, systems have been found in the wild that do not provide this feature. This patch introduces the module parameter disable_connector of the drm_kms_helper module that may specify the name of the connector to be considered disabled, e.g. # cat /etc/modprobe.d/drm_kms_helper.conf options drm_kms_helper disable_connector=LVDS-1 which lets Xorg correctly initialize the screen, e.g. (II) intel(0): Output LVDS1 disconnected (II) intel(0): Output VGA1 connected (II) intel(0): Using exact sizes for initial modes (II) intel(0): Output VGA1 using initial mode 1280x1024 +0+0 A second scenario applies to broken graphics adapters that are unable to correctly detect connected monitors and end up in a situation where the default screen resolution of 1024x768 is selected that may not be appropriate, e.g. (II) intel(0): Output VGA1 disconnected (II) intel(0): Output HDMI1 disconnected (II) intel(0): Output DP1 disconnected (II) intel(0): Output HDMI2 disconnected (II) intel(0): Output DP2 disconnected (WW) intel(0): No outputs definitely connected, trying again... (II) intel(0): Output VGA1 disconnected (II) intel(0): Output HDMI1 disconnected (II) intel(0): Output DP1 disconnected (II) intel(0): Output HDMI2 disconnected (II) intel(0): Output DP2 disconnected (WW) intel(0): Unable to find connected outputs - setting 1024x768 initial framebuffer This patch introduces a second module parameter enable_connector of the drm_kms_helper module that may specify the name of the connector to be taken as connected, e.g. # cat /etc/modprobe.d/drm_kms_helper.conf options drm_kms_helper enable_connector=VGA-1 which lets Xorg correctly initialize the screen, e.g. (II) intel(0): Output VGA1 connected (II) intel(0): Output HDMI1 disconnected (II) intel(0): Output DP1 disconnected (II) intel(0): Output HDMI2 disconnected (II) intel(0): Output DP2 disconnected (II) intel(0): Using exact sizes for initial modes (II) intel(0): Output VGA1 using initial mode 1280x1024 +0+0 Signed-off-by: Carsten Emde c.e...@osadl.org --- Documentation/kernel-parameters.txt | 13 drivers/gpu/drm/drm_crtc.c | 15 ++--- drivers/gpu/drm/drm_crtc_helper.c |3 ++ drivers/gpu/drm/drm_fb_helper.c | 39 ++-- include/drm/drm_crtc.h |3 +- 5 files changed, 66 insertions(+), 7 deletions(-) Index: linux-3.3-rc6/Documentation/kernel-parameters.txt === --- linux-3.3-rc6.orig/Documentation/kernel-parameters.txt +++ linux-3.3-rc6/Documentation/kernel-parameters.txt @@ -713,12 +713,25 @@ bytes respectively. Such letter suffixes The filter can be disabled or changed to another driver later using sysfs. + drm_kms_helper.disable_connector=connector + The BIOS may always report that a panel is connected, + irrespective of whether it really is or not which may + lead to a bogus screen layout. This parameter is used + to explicitly disable a particular connector, e.g. + drm_kms_helper disable_connector=LVDS-1 + drm_kms_helper.edid_firmware=file Broken monitors, graphic adapters and KVMs may send no or broken EDID data sets. This parameter allows to specify an EDID data set in the /lib/firmware directory that is used instead. + drm_kms_helper.enable_connector=connector + Broken hardware may be unable to correctly discover a + monitor. This parameter is used to let the drm subsystem + assume that a monitor is present at the specified + connector, e.g. drm_kms_helper enable_connector=VGA-1 + dscc4.setup=[NET] earlycon= [KNL] Output early console device and options. Index: linux-3.3-rc6/drivers/gpu/drm/drm_crtc.c === ---
[V2 PATCH 2/3] module: avoid exporting module_mutex
Avoid exporting internal locks to modules, export two functions lock_modules()/unlock_modules() for them instead. Cc: Rusty Russell ru...@rustcorp.com.au Signed-off-by: Cong Wang xiyou.wangc...@gmail.com --- drivers/gpu/drm/drm_fb_helper.c |4 ++-- include/linux/module.h |3 ++- kernel/kprobes.c|4 ++-- kernel/module.c | 24 ++-- 4 files changed, 24 insertions(+), 11 deletions(-) diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/drm/drm_fb_helper.c index aada26f..c184759 100644 --- a/drivers/gpu/drm/drm_fb_helper.c +++ b/drivers/gpu/drm/drm_fb_helper.c @@ -1451,9 +1451,9 @@ static int __init drm_fb_helper_modinit(void) const char *name = fbcon; struct module *fbcon; - mutex_lock(module_mutex); + lock_modules(); fbcon = find_module(name); - mutex_unlock(module_mutex); + unlock_modules(); if (!fbcon) request_module_nowait(name); diff --git a/include/linux/module.h b/include/linux/module.h index 4598bf0..5cf6428 100644 --- a/include/linux/module.h +++ b/include/linux/module.h @@ -374,7 +374,8 @@ struct module #define MODULE_ARCH_INIT {} #endif -extern struct mutex module_mutex; +extern void lock_modules(void); +extern void unlock_modules(void); /* FIXME: It'd be nice to isolate modules during init, too, so they aren't used before they (may) fail. But presently too much code diff --git a/kernel/kprobes.c b/kernel/kprobes.c index c62b854..0670fb1 100644 --- a/kernel/kprobes.c +++ b/kernel/kprobes.c @@ -562,7 +562,7 @@ static __kprobes void kprobe_optimizer(struct work_struct *work) LIST_HEAD(free_list); /* Lock modules while optimizing kprobes */ - mutex_lock(module_mutex); + lock_modules(); mutex_lock(kprobe_mutex); /* @@ -587,7 +587,7 @@ static __kprobes void kprobe_optimizer(struct work_struct *work) do_free_cleaned_kprobes(free_list); mutex_unlock(kprobe_mutex); - mutex_unlock(module_mutex); + unlock_modules(); /* Step 5: Kick optimizer again if needed */ if (!list_empty(optimizing_list) || !list_empty(unoptimizing_list)) diff --git a/kernel/module.c b/kernel/module.c index f0f8d4a..db402a8 100644 --- a/kernel/module.c +++ b/kernel/module.c @@ -95,8 +95,20 @@ * 2) module_use links, * 3) module_addr_min/module_addr_max. * (delete uses stop_machine/add uses RCU list operations). */ -DEFINE_MUTEX(module_mutex); -EXPORT_SYMBOL_GPL(module_mutex); +static DEFINE_MUTEX(module_mutex); + +void lock_modules(void) +{ + mutex_lock(module_mutex); +} +EXPORT_SYMBOL(lock_modules); + +void unlock_modules(void) +{ + mutex_unlock(module_mutex); +} +EXPORT_SYMBOL(unlock_modules); + static LIST_HEAD(modules); #ifdef CONFIG_KGDB_KDB struct list_head *kdb_modules = modules; /* kdb needs the list of modules */ @@ -1713,7 +1725,7 @@ void set_all_modules_text_rw(void) { struct module *mod; - mutex_lock(module_mutex); + lock_modules(); list_for_each_entry(mod, modules, list) { if ((mod-module_core) (mod-core_text_size)) { set_page_attributes(mod-module_core, @@ -1726,7 +1738,7 @@ void set_all_modules_text_rw(void) set_memory_rw); } } - mutex_unlock(module_mutex); + unlock_modules(); } /* Iterate through all modules and set each module's text as RO */ @@ -1734,7 +1746,7 @@ void set_all_modules_text_ro(void) { struct module *mod; - mutex_lock(module_mutex); + lock_modules(); list_for_each_entry(mod, modules, list) { if ((mod-module_core) (mod-core_text_size)) { set_page_attributes(mod-module_core, @@ -1747,7 +1759,7 @@ void set_all_modules_text_ro(void) set_memory_ro); } } - mutex_unlock(module_mutex); + unlock_modules(); } #else static inline void set_section_ro_nx(void *base, unsigned long text_size, unsigned long ro_size, unsigned long total_size) { } -- 1.7.7.6 ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 2/3] drivers-gpu-drm-add-disable-enable-connector.patch
On 03/11/2012 08:20 AM, Dave Airlie wrote: On Sat, Mar 10, 2012 at 8:20 PM, Carsten Emdec.e...@osadl.org wrote: Some recent integrated graphics chipset, notably Intel's Pineview, also provide on-chip LVDS support. As an extra service, the LVDS interface supplies EDID data - irrespective of whether an LVDS panel is connected or not. The drm_mode_getresources() function, therefore, causes Xorg to always include the LVDS panel into the display and initialize a separate screen for it. e.g. (II) intel(0): Output LVDS1 connected (II) intel(0): Output VGA1 connected (II) intel(0): Using spanning desktop for initial modes (II) intel(0): Output LVDS1 using initial mode 1024x768 +0+0 (II) intel(0): Output VGA1 using initial mode 1280x1024 +1024+0 which is not what you want, if the only connected screen is a VGA monitor. One would assume that the BIOS settings of such systems would allow to separately enable or disable LVDS support; unfortunately, systems have been found in the wild that do not provide this feature. So video=LVDS-1:d doesn't work for you? Oops, yes, you are totally right. By some reason, I overlooked this option. I tried two systems that need forced disabling and enabling with video=LVDS-1:d video=VGA-1:e which worked perfectly well. So please skip this patch, sorry for the noise. Thanks, -Carsten. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 1/3] drivers-gpu-drm-allow-to-load-edid-firmware.patch
On 03/11/2012 02:44 PM, Alan Cox wrote: This patch allows to load an EDID data set via the firmware interface. It contains data sets of frequently used screen resolutions (1024x768, 1280x1024, 1680x1050 and 1920x1080). The requested EDID data are specified as a module parameter of the drm_kms_helper module, e.g. options drm_kms_helper edid_firmware=edid/1280x1024.bin or as kernel command line parameter. What if the DRM layer and driver are compiled in. They'll come up as console before the file system so the firmware request will hang ? Admittedly I did not try to compile the DRM layer and driver into the kernel. However, I created an error condition by specifying a non-existing EDID file. In this case, the function returns with error, the mode count remains 0, and the system continues to run as if the edid_firmware= parameter had not been specified. Now that you were asking, I created a static kernel and did some more tests, but I couldn't find any problem. Everything worked as expected. I believe that the early console still runs in BIOS VGA mode, i.e. either using the BIOS default mode or the one that was specified using the vga= parameter, if any. DRM apparently comes into play at a later stage only, but I will do some more testing. Given the EDID is tiny and is data not code wouldn't it be simpler (and smaller) if this option compiled in a few generic EDIDs to use ? Yes, this certainly would be possible. However, we would loose the flexibility to specify an individual EDID data set without recompiling the kernel. As an alternative, we could compile the four standard EDIDs into the DRM helper instead of providing them as a file, but still leave the option to load an individual EDID via the firmware interface. This would make the patch much smaller and avoid spamming the firmware directory. How about that? Thanks, -Carsten. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 1/3] drivers-gpu-drm-allow-to-load-edid-firmware.patch
Alan, This patch allows to load an EDID data set via the firmware interface. It contains data sets of frequently used screen resolutions (1024x768, 1280x1024, 1680x1050 and 1920x1080). The requested EDID data are specified as a module parameter of the drm_kms_helper module, e.g. options drm_kms_helper edid_firmware=edid/1280x1024.bin or as kernel command line parameter. [..] Given the EDID is tiny and is data not code wouldn't it be simpler (and smaller) if this option compiled in a few generic EDIDs to use ? I liked the idea so much that I gave it a try. The patch looks much better now, but has the same functionality as before. As the only disadvantage, the patch no longer contains the template to produce a particular EDID. But this code may be made available elsewhere - no need to have it in the kernel. Hope you like it. Thanks, -Carsten. Broken monitors and/or broken graphic boards may send erroneous or no EDID data. This also applies to broken KVM devices that are unable to correctly forward the EDID data of the connected monitor but invent their own fantasy data. This patch allows to specify an EDID data set to be used instead of probing the monitor for it. It contains built-in data sets of frequently used screen resolutions. In addition, a particular EDID data set may be provided in the /lib/firmware directory and loaded via the firmware interface. The name is passed to the kernel as module parameter of the drm_kms_helper module either when loaded options drm_kms_helper edid_firmware=edid/1280x1024.bin or as kernel commandline parameter drm_kms_helper.edid_firmware=edid/1280x1024.bin The built-in data sets are ResolutionName 1024x768 edid/1024x768.bin 1280x1024 edid/1280x1024.bin 1680x1050 edid/1680x1050.bin 1920x1080 edid/1920x1080.bin They are ignored, if a file with the same name is available in the /lib/firmware directory. The built-in EDID data sets are based on standard timings that may not apply to a particular monitor and even crash it. Ideally, EDID data of the connected monitor should be used. They may be obtained through the drm/cardX/cardX-connector/edid entry in the /sys/devices PCI directory of a correctly working graphics adapter. It is also possible to specify the name of an EDID data set on-the-fly via the /sys/module interface, e.g. echo edid/myedid.bin /sys/module/drm_kms_helper/parameters/edid_firmware The new screen mode is considered when the related kernel function is called for the first time after the change. Such calls are made when the X server is started or when the display settings dialog is opened in an already running X server. Signed-off-by: Carsten Emde c.e...@osadl.org --- Documentation/kernel-parameters.txt | 10 + drivers/gpu/drm/Kconfig | 11 + drivers/gpu/drm/Makefile|3 drivers/gpu/drm/drm_crtc_helper.c |8 + drivers/gpu/drm/drm_edid.c |4 drivers/gpu/drm/drm_edid_load.c | 241 include/drm/drm_crtc.h |1 include/drm/drm_edid.h |1 8 files changed, 276 insertions(+), 3 deletions(-) Index: linux-3.3-rc6/Documentation/kernel-parameters.txt === --- linux-3.3-rc6.orig/Documentation/kernel-parameters.txt +++ linux-3.3-rc6/Documentation/kernel-parameters.txt @@ -713,6 +713,16 @@ bytes respectively. Such letter suffixes The filter can be disabled or changed to another driver later using sysfs. + drm_kms_helper.edid_firmware=file + Broken monitors, graphic adapters and KVMs may + send no or broken EDID data sets. This parameter + allows to specify an EDID data set in the + /lib/firmware directory that is used instead. + Generic built-in EDID data sets are used, if one of + edid/1024x768.bin, edid/1280x1024.bin, + edid/1680x1050.bin, or edid/1920x1080.bin is given + and no file with the same name exists. + dscc4.setup= [NET] earlycon= [KNL] Output early console device and options. Index: linux-3.3-rc6/drivers/gpu/drm/Kconfig === --- linux-3.3-rc6.orig/drivers/gpu/drm/Kconfig +++ linux-3.3-rc6/drivers/gpu/drm/Kconfig @@ -27,6 +27,17 @@ config DRM_KMS_HELPER help FB and CRTC helpers for KMS drivers. +config DRM_LOAD_EDID_FIRMWARE + bool Allow to specify an EDID data set instead of probing for it + depends on DRM_KMS_HELPER + help + Say Y here, if you want to use EDID data to be loaded from the + /lib/firmware directory or one of the provided built-in + data sets. This may be necessary, if the graphics adapter or + monitor are unable to provide appropriate EDID data. Since this + feature is provided as a workaround for broken hardware, the + default case is N. + config DRM_TTM tristate depends on DRM Index: linux-3.3-rc6/drivers/gpu/drm/Makefile
[Bug 46725] Monitor disconnected and refuses to work anymore
https://bugs.freedesktop.org/show_bug.cgi?id=46725 --- Comment #7 from Tomi Pieviläinen tomi.pievilainen+freedesk...@iki.fi 2012-03-12 03:15:07 PDT --- This has happened several times more to me. It happens very often when watching a HD video, and some times when viewing photos. Hasn't happened in normal desktop use. I've also noticed that I can get it back on by forcing it off with xrandr, and then back on. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 46725] Monitor disconnected and refuses to work anymore
https://bugs.freedesktop.org/show_bug.cgi?id=46725 --- Comment #8 from Tomi Pieviläinen tomi.pievilainen+freedesk...@iki.fi 2012-03-12 03:17:18 PDT --- Seems like I can reproduce this every time I view a certain photo taken with my phone in feh... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 46713] HDMI audio played back at a wrong rate
https://bugs.freedesktop.org/show_bug.cgi?id=46713 --- Comment #14 from Tvrtko Ursulin tvrtko.ursu...@onelan.co.uk 2012-03-12 04:27:51 PDT --- Created attachment 58306 -- https://bugs.freedesktop.org/attachment.cgi?id=58306 avivotool register dump under fglrx I've managed to get fglrx running and initially playback speed was fine but audio quite distorted (hard to describe). I've noticed in the output a mention of 1024x768 output resolution on the LVDS connector which was unexpected, since the motherboard in question only has HDMI and VGA outputs. I disabled LVDS with xranrd and then audio was perfect. I will attach that register dump as well. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 46713] HDMI audio played back at a wrong rate
https://bugs.freedesktop.org/show_bug.cgi?id=46713 --- Comment #15 from Tvrtko Ursulin tvrtko.ursu...@onelan.co.uk 2012-03-12 04:28:27 PDT --- Created attachment 58307 -- https://bugs.freedesktop.org/attachment.cgi?id=58307 avivotool register dump under fglrx with non-existant LVDS output turned off -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 46796] [X800SE] Mouse cursor corruption when switching users
https://bugs.freedesktop.org/show_bug.cgi?id=46796 Michel Dänzer mic...@daenzer.net changed: What|Removed |Added Attachment #58066|0 |1 is obsolete|| --- Comment #10 from Michel Dänzer mic...@daenzer.net 2012-03-12 05:13:22 UTC --- Created attachment 58312 -- https://bugs.freedesktop.org/attachment.cgi?id=58312 Verbose test patch with crash fixed (In reply to comment #9) This patch causes my computer to crash at login. However, it's not a super bad crash because I was able to ssh in and check dmesg. Sorry about that, here's another test patch which shouldn't crash. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 47201] Absolute modifier does not work with 3-source TGSI instructions
https://bugs.freedesktop.org/show_bug.cgi?id=47201 --- Comment #4 from Vic Lee ll...@163.com 2012-03-12 06:33:54 PDT --- Thanks for concerning this bug. It will be great if this can be fixed at driver level. I created a smallest possible test program which will be able to test the shader I am having problem with. Please see the file header for test info. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 47201] Absolute modifier does not work with 3-source TGSI instructions
https://bugs.freedesktop.org/show_bug.cgi?id=47201 --- Comment #5 from Vic Lee ll...@163.com 2012-03-12 06:34:57 PDT --- Created attachment 58317 -- https://bugs.freedesktop.org/attachment.cgi?id=58317 test program to reproduce 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. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 42490] NUTMEG DP to VGA bridge not working
https://bugs.freedesktop.org/show_bug.cgi?id=42490 Alex Deucher ag...@yahoo.com changed: What|Removed |Added CC||diego.abele...@gmail.com --- Comment #11 from Alex Deucher ag...@yahoo.com 2012-03-12 06:43:07 PDT --- *** Bug 47064 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 47007] HDMI monitor polling causing 100ms rendering stalls
https://bugs.freedesktop.org/show_bug.cgi?id=47007 Tvrtko Ursulin tvrtko.ursu...@onelan.co.uk changed: What|Removed |Added Attachment #58160|0 |1 is obsolete|| --- Comment #10 from Tvrtko Ursulin tvrtko.ursu...@onelan.co.uk 2012-03-12 06:44:33 PDT --- Created attachment 58318 -- https://bugs.freedesktop.org/attachment.cgi?id=58318 Different approach on fixing the stalls After talking with a colleague who is more at home in this code we think the previous patch is wrong. This new patch uses a different approach which also works for us. In short, it doesn't do the full EDID re-fetch if HPD sense says we are still connected. Plus some other conditions only of which the shared_ddc one I am not completely sure. I've put it in to minimise the change in behaviour. Comments? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 46725] Monitor disconnected and refuses to work anymore
https://bugs.freedesktop.org/show_bug.cgi?id=46725 --- Comment #9 from Alex Deucher ag...@yahoo.com 2012-03-12 06:53:28 PDT --- Does booting with radeon.disp_priority=2 on the kernel command line in grub help? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 47007] HDMI monitor polling causing 100ms rendering stalls
https://bugs.freedesktop.org/show_bug.cgi?id=47007 --- Comment #11 from Alex Deucher ag...@yahoo.com 2012-03-12 07:56:06 PDT --- The code is correct as is. I think what's happening is that your monitor is polling and causing hotplug unplug/plug events what cause the detect code to run. Can you try disabling the input polling on your monitor? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 1/3] drivers-gpu-drm-allow-to-load-edid-firmware.patch
On Sat, 10 Mar 2012 21:20:15 +0100, Carsten Emde said: EDID data source files are provided for documentation purpose and as a template to create EDID data sets for other screen resolutions. Note that source compilation is not part of the build process, but needs to be done manually, e.g. #!/bin/bash cd firmware/edid for i in [1-9]*.S do Would it be possible to include a version of this patch's Changelog as a file under Documentation/fixing-broken-edid.txt or something, so people don't have to go and find the git commit log to know things like you need to run dos2unix? Be a shame to have a changelog that does such a good job of documenting what you need to do, and have it lost in git... pgp5kgga7tOZm.pgp Description: PGP signature ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 47244] New: [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
https://bugs.freedesktop.org/show_bug.cgi?id=47244 Bug #: 47244 Summary: [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! Classification: Unclassified Product: Mesa Version: 7.11 Platform: x86 (IA32) OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: adr...@gmail.com Created attachment 58335 -- https://bugs.freedesktop.org/attachment.cgi?id=58335 Screenshot Hello. I have problem with a game. I would like to run the game, but it does not work. It's Warcraft. 1. Run Garena. 2. By the Garena start Warcraft III. 3. Garena's window is minimized but there is no Warcraft's window. I only hear music from the game. I get these messages: kernel: [ 2237.829228] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream ! kernel: [ 2237.836653] [drm:r100_cs_track_check] *ERROR* [drm] No buffer for z buffer ! -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 47244] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
https://bugs.freedesktop.org/show_bug.cgi?id=47244 --- Comment #1 from adr...@gmail.com 2012-03-12 11:12:22 PDT --- Created attachment 58336 -- https://bugs.freedesktop.org/attachment.cgi?id=58336 Log from wine -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 47244] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
https://bugs.freedesktop.org/show_bug.cgi?id=47244 --- Comment #2 from adr...@gmail.com 2012-03-12 11:13:12 PDT --- From wine: radeon: The kernel rejected CS, see dmesg for 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. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 47007] HDMI monitor polling causing 100ms rendering stalls
https://bugs.freedesktop.org/show_bug.cgi?id=47007 --- Comment #13 from Alex Deucher ag...@yahoo.com 2012-03-12 11:34:39 PDT --- Sorry for the confusion, I mixed up the patches. I was referring to the previous patch (attachment 58160). The patch in attachment 58318 looks good. The only thing I would add is a check to make sure rdev-family = CHIP_R600 since the HPD mapping was not always set up reliably by OEMs on prior asics. With that, you can add: Reviewed-by: Alex Deucher alexander.deuc...@amd.com -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 42887] Garbled display on external screen when using 1920x1080 instead of 1920x1200
https://bugzilla.kernel.org/show_bug.cgi?id=42887 Florian Mickler flor...@mickler.org changed: What|Removed |Added CC||flor...@mickler.org --- Comment #1 from Florian Mickler flor...@mickler.org 2012-03-12 22:23:12 --- A patch referencing this bug report has been merged in Linux v3.3-rc7: commit 38aa4a568ba4c3ccba83e862a01e3e60e3b811ee Author: Alex Deucher alexander.deuc...@amd.com Date: Wed Mar 7 19:05:01 2012 -0500 drm/radeon/kms: fix hdmi duallink checks -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 46796] [X800SE] Mouse cursor corruption when switching users
https://bugs.freedesktop.org/show_bug.cgi?id=46796 --- Comment #11 from jonathan jonathan.v...@gmail.com 2012-03-12 16:41:14 PDT --- I think this patch works as intended. Well actually, it's hard for me to say it actually fixed the problem due to its random nature, but I haven't had the mouse corruption issue on this patched driver, and the message appears in dmesg: [ 524.112945] [drm] Fixing large cursor offset 0x0d1e = 0x [ 537.020931] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id [ 537.308976] [drm] Fixing large cursor offset 0x0cf8 = 0x [ 607.000940] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id I have to say that the log confuses me since 1 27 is not 0. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 39309] vdpau decodes noise on rv350
https://bugs.freedesktop.org/show_bug.cgi?id=39309 --- Comment #9 from Andy Furniss li...@andyfurniss.entadsl.com 2012-03-12 17:29:18 PDT --- (In reply to comment #2) Testing just -vo vdpau with sw decode it works but crashes if the window is resized this happened before as well as today. After playing with gdb, valgrind and VDPAU_TRACE=1 I think I know why this is happening now. Mplayer is asking for video surfaces of a certain size but not checking what size was allocated as the spec says it should. Because npot textures are not enabled for r300 video, this makes it more noticeable than r600 which for SD will allocate buffers with lines = requested. This is not the case for HD, mplayer asking for 1920x1080 will get 1088 - but by luck or design it/ffmpeg seem to use buffers big enough. I have found an exception to this - raw yuv, so I can now crash r600 as well as r300. Enabling npot for r300 makes it almost always work just as r600 does. Is there a reason it's disabled? It seems to be enabled for 3D but not video. This is all with s/w decode - enabling npot doesn't help the decode problems. Valgrind does throw r300 errors for decode, example below, but I don't think that fixing them will help as xvmc has none but still decodes junk. ==17289== Invalid write of size 1 ==17289==at 0x5E4DB86: r300_dsa_inject_stencilref (r300_state.c:664) ==17289==by 0x5EB553D: blitter_restore_fragment_states (u_blitter.c:427) ==17289==by 0x5EB78A6: util_blitter_copy_texture_view (u_blitter.c:1060) ==17289==by 0x5E4074C: r300_resource_copy_region (r300_blit.c:580) ==17289==by 0x5E3EB42: r300_texture_transfer_destroy (r300_transfer.c:71) ==17289==by 0x5EC4A8A: u_transfer_destroy_vtbl (u_resource.c:41) ==17289==by 0x5EEE288: vl_zscan_layout (vl_zscan.c:411) ==17289==by 0x5EE1EAD: vl_create_mpeg12_decoder (vl_mpeg12_decoder.c:857) ==17289==by 0x5EDF353: vl_create_decoder (vl_decoder.c:73) ==17289==by 0x5E36575: vlVdpDecoderCreate (decode.c:92) ==17289==by 0x80F94AC: create_vdp_decoder (vo_vdpau.c:598) ==17289==by 0x80FB0DD: control (vo_vdpau.c:1115) ==17289== Address 0x5c13220 is 40 bytes inside a block of size 184 free'd ==17289==at 0x4022BD8: free (vg_replace_malloc.c:427) ==17289==by 0x5E4DEDC: r300_delete_dsa_state (r300_state.c:692) ==17289==by 0x5EE2750: vl_mpeg12_destroy (vl_mpeg12_decoder.c:413) ==17289==by 0x5E36382: vlVdpDecoderDestroy (decode.c:137) ==17289==by 0x80F944B: create_vdp_decoder (vo_vdpau.c:574) ==17289==by 0x80FB0DD: control (vo_vdpau.c:1115) ==17289==by 0x81771E3: query_format (vf_vo.c:145) ==17289==by 0x8148B8B: mpcodecs_config_vo (vd.c:195) ==17289==by 0x82185D8: init_vo (vd_ffmpeg.c:511) ==17289==by 0x821A0C6: get_format (vd_ffmpeg.c:944) ==17289==by 0x857B3F9: mpeg_get_pixelformat (mpeg12.c:1224) ==17289==by 0x8580D81: decode_chunks (mpeg12.c:1326) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel