[Bug 16265] Why is kslowd accumulating so much CPU time?
https://bugzilla.kernel.org/show_bug.cgi?id=16265 --- Comment #12 from Chris Wilson 2011-01-15 22:35:48 --- (In reply to comment #11) > This issue is still present for me with Intel 4500 MHD (intel driver 2.14.0, > xorg-server 1.9.3.901, mesa 7.9.1, libdrm 2.4.23) with gentoo-sources 2.6.37. > I've read this announcement and disabled my drm_kms_helper.poll=N kernel boot > param but the issue has come up after few minutes after booting. System was > sluggish and kworker process appeared eating 60% CPU. Different culprit - you neither have the affected hardware nor the responsible hotplug polling enabled. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 26812] Radeon module causes hard reset on modprobe
https://bugzilla.kernel.org/show_bug.cgi?id=26812 Alex Deucher changed: What|Removed |Added CC||alexdeucher at gmail.com --- Comment #1 from Alex Deucher 2011-01-15 22:11:00 --- What radeoon chip do you have? If it's an r6xx, r7xx, or evergreen asic, this possibly a duplicate of this bug: https://bugs.freedesktop.org/show_bug.cgi?id=33027 If so, does the patch there help? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 26712] Weird X display upon hibernating
https://bugzilla.kernel.org/show_bug.cgi?id=26712 --- Comment #4 from Alex Deucher 2011-01-15 22:07:52 --- I think Karmic used UMS rather than KMS, so it's not a regression as KMS and UMS are basically different driver stacks. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 26812] Radeon module causes hard reset on modprobe
https://bugzilla.kernel.org/show_bug.cgi?id=26812 --- Comment #4 from Michael Evans 2011-01-16 05:57:33 --- I noticed something when looking at the files in /lib/firmware/radeon to make sure I had /all/ the correct ones in place. BARTS*, which wasn't in my config (I copy/pasted an example for that section without paying it much attention, and wouldn't have remembered which chip codename I had anyway.) when added allows at /least/ drm-next to work correctly. There are two outstanding issues I noticed however. 1) When the firmware isn't found the module very un-gracefully reboots without //any// explanation (no information provided to lead to enlightenment). Correct behavior should be to fail gracefully and provide a clean message in the kernel log without taking the system fully offline. 2) the EXTRA firmware line has a size limit. I didn't look at what it was exactly, but it can't contain the expansion of cd /lib/firmware; ls radeon/* ; a more preferable solution might be to allow the use of shell wildcards (or document that they are evaluated). I am --not-- marking this as resolved since the first issue is still a major problem (it makes this error non-trivial to diagnose for no good reason). -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26812] New: Radeon module causes hard reset on modprobe
https://bugzilla.kernel.org/show_bug.cgi?id=26812 Summary: Radeon module causes hard reset on modprobe Product: Drivers Version: 2.5 Kernel Version: 2.6.37-git9 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri at kernel-bugs.osdl.org ReportedBy: mjevans1983 at gmail.com Regression: No I'm using the git snapshots between when Linus merged from drm-core-next and when network drivers were merged (breaks build). If there is a better patch relative to a released source I'll gladly test it too; however the other sources I tried also had similar issues. When radeon.ko (or build in init) starts the screens blank and a few seconds later the system completely reboots. This is 100% repeatable. I have firmware from Arch's (AUR) linux-firmware-git package installed, /lib/firmware pointed as the source, and the relevant blobs for the recent ATI/AMD GPUs. When built as a module I can modprobe radeon to trigger the exact same behavior. Problems debugging: * It resets so hard there isn't a peep from netconsole. * It resets so hard that my disks loose md raid sync and need to completely rebuild (yeah, I know, I'll add a write-intent log before I test this again next time...; it wasn't an issue before I got the brainwave of making it a module to try to give netconsole/syslog time to get setup.) How can I possibly approach isolating this? Even a link to the correct documentation would be helpful. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 26712] Weird X display upon hibernating
https://bugzilla.kernel.org/show_bug.cgi?id=26712 --- Comment #3 from Siddu 2011-01-15 21:12:32 --- (In reply to comment #2) > Did hibernate ever work properly on your system? If so when and can you > bisect? It used to work fine with Ubuntu Karmic. And i just found out that the issue seems to be present with the distro(Ubuntu Lucid) kernel(2.6.32-21-generic) as well . So that concludes hibernate never has been working on lucid -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 16265] Why is kslowd accumulating so much CPU time?
https://bugzilla.kernel.org/show_bug.cgi?id=16265 Bc. Slavomir Danas changed: What|Removed |Added CC||slavomir.danas at gmail.com --- Comment #11 from Bc. Slavomir Danas 2011-01-15 20:42:49 --- This issue is still present for me with Intel 4500 MHD (intel driver 2.14.0, xorg-server 1.9.3.901, mesa 7.9.1, libdrm 2.4.23) with gentoo-sources 2.6.37. I've read this announcement and disabled my drm_kms_helper.poll=N kernel boot param but the issue has come up after few minutes after booting. System was sluggish and kworker process appeared eating 60% CPU. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[PATCH 4/5] nouveau: Change the backlight parent device to the connector, not the PCI dev
On Fri, 2011-01-14 at 14:24 -0500, Matthew Garrett wrote:
> We may eventually end up with per-connector backlights, especially with
> ddcci devices. Make sure that the parent node for the backlight device is
> the connector rather than the PCI device.
>
> Signed-off-by: Matthew Garrett
Acked-by: Ben Skeggs
> ---
> drivers/gpu/drm/nouveau/nouveau_backlight.c | 24 ++--
> drivers/gpu/drm/nouveau/nouveau_connector.c |9 +
> drivers/gpu/drm/nouveau/nouveau_drv.h |8
> drivers/gpu/drm/nouveau/nouveau_state.c |6 --
> 4 files changed, 27 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/gpu/drm/nouveau/nouveau_backlight.c
> b/drivers/gpu/drm/nouveau/nouveau_backlight.c
> index 18d7bcc..00a55df 100644
> --- a/drivers/gpu/drm/nouveau/nouveau_backlight.c
> +++ b/drivers/gpu/drm/nouveau/nouveau_backlight.c
> @@ -88,10 +88,11 @@ static const struct backlight_ops nv50_bl_ops = {
> .update_status = nv50_set_intensity,
> };
>
> -static int nouveau_nv40_backlight_init(struct drm_device *dev)
> +static int nouveau_nv40_backlight_init(struct drm_connector *connector)
> {
> - struct backlight_properties props;
> + struct drm_device *dev = connector->dev;
> struct drm_nouveau_private *dev_priv = dev->dev_private;
> + struct backlight_properties props;
> struct backlight_device *bd;
>
> if (!(nv_rd32(dev, NV40_PMC_BACKLIGHT) & NV40_PMC_BACKLIGHT_MASK))
> @@ -100,7 +101,7 @@ static int nouveau_nv40_backlight_init(struct drm_device
> *dev)
> memset(&props, 0, sizeof(struct backlight_properties));
> props.type = BACKLIGHT_RAW;
> props.max_brightness = 31;
> - bd = backlight_device_register("nv_backlight", &dev->pdev->dev, dev,
> + bd = backlight_device_register("nv_backlight", &connector->kdev, dev,
> &nv40_bl_ops, &props);
> if (IS_ERR(bd))
> return PTR_ERR(bd);
> @@ -112,10 +113,11 @@ static int nouveau_nv40_backlight_init(struct
> drm_device *dev)
> return 0;
> }
>
> -static int nouveau_nv50_backlight_init(struct drm_device *dev)
> +static int nouveau_nv50_backlight_init(struct drm_connector *connector)
> {
> - struct backlight_properties props;
> + struct drm_device *dev = connector->dev;
> struct drm_nouveau_private *dev_priv = dev->dev_private;
> + struct backlight_properties props;
> struct backlight_device *bd;
>
> if (!nv_rd32(dev, NV50_PDISPLAY_SOR_BACKLIGHT))
> @@ -124,7 +126,7 @@ static int nouveau_nv50_backlight_init(struct drm_device
> *dev)
> memset(&props, 0, sizeof(struct backlight_properties));
> props.type = BACKLIGHT_RAW;
> props.max_brightness = 1025;
> - bd = backlight_device_register("nv_backlight", &dev->pdev->dev, dev,
> + bd = backlight_device_register("nv_backlight", &connector->kdev, dev,
> &nv50_bl_ops, &props);
> if (IS_ERR(bd))
> return PTR_ERR(bd);
> @@ -135,8 +137,9 @@ static int nouveau_nv50_backlight_init(struct drm_device
> *dev)
> return 0;
> }
>
> -int nouveau_backlight_init(struct drm_device *dev)
> +int nouveau_backlight_init(struct drm_connector *connector)
> {
> + struct drm_device *dev = connector->dev;
> struct drm_nouveau_private *dev_priv = dev->dev_private;
>
> #ifdef CONFIG_ACPI
> @@ -149,9 +152,9 @@ int nouveau_backlight_init(struct drm_device *dev)
>
> switch (dev_priv->card_type) {
> case NV_40:
> - return nouveau_nv40_backlight_init(dev);
> + return nouveau_nv40_backlight_init(connector);
> case NV_50:
> - return nouveau_nv50_backlight_init(dev);
> + return nouveau_nv50_backlight_init(connector);
> default:
> break;
> }
> @@ -159,8 +162,9 @@ int nouveau_backlight_init(struct drm_device *dev)
> return 0;
> }
>
> -void nouveau_backlight_exit(struct drm_device *dev)
> +void nouveau_backlight_exit(struct drm_connector *connector)
> {
> + struct drm_device *dev = connector->dev;
> struct drm_nouveau_private *dev_priv = dev->dev_private;
>
> if (dev_priv->backlight) {
> diff --git a/drivers/gpu/drm/nouveau/nouveau_connector.c
> b/drivers/gpu/drm/nouveau/nouveau_connector.c
> index a21e000..3a1ecc7 100644
> --- a/drivers/gpu/drm/nouveau/nouveau_connector.c
> +++ b/drivers/gpu/drm/nouveau/nouveau_connector.c
> @@ -116,6 +116,10 @@ nouveau_connector_destroy(struct drm_connector
> *connector)
> nouveau_connector_hotplug, connector);
> }
>
> + if (connector->connector_type == DRM_MODE_CONNECTOR_LVDS ||
> + connector->connector_type == DRM_MODE_CONNECTOR_eDP)
> + nouveau_backlight_exit(connector);
> +
> kfree(nv_connector->edid);
> drm_sysfs_connector_remove(connector);
> drm_connector_cleanup(connector);
> @@ -893,6 +897,11 @@ nouveau
[Bug 30651] r600g: gl output in mplayer have no colors if used with a fragment program with additional lookup and bicubic B-spline filtering
https://bugs.freedesktop.org/show_bug.cgi?id=30651 --- Comment #4 from Sergey Kondakov 2011-01-15 19:29:04 PST --- Created an attachment (id=42092) --> (https://bugs.freedesktop.org/attachment.cgi?id=42092) gl:yuv=6 - broken output.jpg recently method '6' was broken and i have to fallback on method '2'. every video in mplayer with yuv=6 looks like green thing on picture plus some changing random artefacts while video playing. were even were some git revision with which any gl output was broken that way (or at least mplayer with -vo gl and warzone2100 game) but it's ok now. only yuv=6 output with mplayer is broken. yuv=4 glitching the same way as before and have no colors. there also were a glitch with yuv=6 when it still worked: bright whitish places in videos were just plain white but this may be mplayer bug since i have never tested it on some other hardware or non-open drivers. -- 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 30651] r600g: gl output in mplayer have no colors if used with a fragment program with additional lookup and bicubic B-spline filtering
https://bugs.freedesktop.org/show_bug.cgi?id=30651 --- Comment #4 from Sergey Kondakov 2011-01-15 19:29:04 PST --- Created an attachment (id=42092) --> (https://bugs.freedesktop.org/attachment.cgi?id=42092) gl:yuv=6 - broken output.jpg recently method '6' was broken and i have to fallback on method '2'. every video in mplayer with yuv=6 looks like green thing on picture plus some changing random artefacts while video playing. were even were some git revision with which any gl output was broken that way (or at least mplayer with -vo gl and warzone2100 game) but it's ok now. only yuv=6 output with mplayer is broken. yuv=4 glitching the same way as before and have no colors. there also were a glitch with yuv=6 when it still worked: bright whitish places in videos were just plain white but this may be mplayer bug since i have never tested it on some other hardware or non-open drivers. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 26812] Radeon module causes hard reset on modprobe
https://bugzilla.kernel.org/show_bug.cgi?id=26812 --- Comment #3 from Michael Evans 2011-01-16 02:09:58 --- Created an attachment (id=43702) --> (https://bugzilla.kernel.org/attachment.cgi?id=43702) lspci, dmidecode, config and netconsole logs -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26812] Radeon module causes hard reset on modprobe
https://bugzilla.kernel.org/show_bug.cgi?id=26812 --- Comment #2 from Michael Evans 2011-01-16 01:41:59 --- It's a 6850 with two DVI's in use. I think that's a "Northern Islands" chip? The system is an Athlon II x4, 00:00.0 Host bridge: Advanced Micro Devices [AMD] RS880 Host Bridge ( M4A785TD-V EVO vendor: ASUSTeK Computer INC. ) I'm going to try booting a copy of drm-next's tree that finished compiling while I was running errands; it should have everything possible already. drm-2.6-drm-next-56bec7c - Nope, that totally failed too. I'm going to collect some system information and what logs I can. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26712] Weird X display upon hibernating
https://bugzilla.kernel.org/show_bug.cgi?id=26712 Rafael J. Wysocki changed: What|Removed |Added CC||florian at mickler.org, ||maciej.rutecki at gmail.com, ||rjw at sisk.pl Blocks||21782 Alex Deucher changed: What|Removed |Added CC||alexdeucher at gmail.com --- Comment #2 from Alex Deucher 2011-01-15 17:36:54 --- Did hibernate ever work properly on your system? If so when and can you bisect? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[PATCH 1/5] Backlight: Add backlight type
[...] +What: /sys/class/backlight//type +Date: September 2010 +KernelVersion: 2.6.37 [...] 2.6.37? Will this go into 2.6.38? 2.6.39? Through which subsystem will these patches walk through? drm-2.6? platform-drivers-x86? Are you planning a GIT tree/branch for this patch-set? The patch-set from 14-Jan-2011 applies against linux-next (next-20110115). I will compile, test and report. - Sedat -
[Bug 33172] [r600g] ingame rendering broken (black screen) in ut2003
https://bugs.freedesktop.org/show_bug.cgi?id=33172 Jan Buecken changed: What|Removed |Added CC||jb@gmx.de --- Comment #1 from Jan Buecken 2011-01-15 15:21:09 PST --- I have the same problem with ut2004 (r600g-64bit), and my kernel log is filled with [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! also. (ut2003 simply crashes ingame with r600g-32bit , its all ok with r600c) System: Radeon HD Mobility 2600 (rv630) amd64 architecture d-r-t-git and 2.6.37 tested libdrm, mesa, xf86-video-ati are all git master xorg-server-1.9.3.901 (gentoo) -- 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 33172] [r600g] ingame rendering broken (black screen) in ut2003
https://bugs.freedesktop.org/show_bug.cgi?id=33172 Jan Buecken changed: What|Removed |Added CC||jb.faq at gmx.de --- Comment #1 from Jan Buecken 2011-01-15 15:21:09 PST --- I have the same problem with ut2004 (r600g-64bit), and my kernel log is filled with [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! also. (ut2003 simply crashes ingame with r600g-32bit , its all ok with r600c) System: Radeon HD Mobility 2600 (rv630) amd64 architecture d-r-t-git and 2.6.37 tested libdrm, mesa, xf86-video-ati are all git master xorg-server-1.9.3.901 (gentoo) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33172] New: [r600g] ingame rendering broken (black screen) in ut2003
https://bugs.freedesktop.org/show_bug.cgi?id=33172 Summary: [r600g] ingame rendering broken (black screen) in ut2003 Product: DRI Version: DRI CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: liquid.a...@gmx.net Hello! Found some time to retest this popular game with fresh git pulls and it looks like that it completly broke. The menu renders fine, but upon entering the actual game you just get a black screen. The kernel log then produces these nice messages: [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! ... System: ATI Technologies Inc Radeon HD 4770 [RV740] drm-radeon-testing kernel libdrm, mesa and xf86-video-ati are all git master xorg-server-1.9.3.901 Greets, Tobias -- 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 33172] New: [r600g] ingame rendering broken (black screen) in ut2003
https://bugs.freedesktop.org/show_bug.cgi?id=33172 Summary: [r600g] ingame rendering broken (black screen) in ut2003 Product: DRI Version: DRI CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: liquid.acid at gmx.net Hello! Found some time to retest this popular game with fresh git pulls and it looks like that it completly broke. The menu renders fine, but upon entering the actual game you just get a black screen. The kernel log then produces these nice messages: [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! ... System: ATI Technologies Inc Radeon HD 4770 [RV740] drm-radeon-testing kernel libdrm, mesa and xf86-video-ati are all git master xorg-server-1.9.3.901 Greets, Tobias -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33171] [r600g, wine] kernel crash when loading level in FEAR
https://bugs.freedesktop.org/show_bug.cgi?id=33171 --- Comment #1 from Tobias Jakobi 2011-01-15 14:55:32 PST --- Created an attachment (id=42088) --> (https://bugs.freedesktop.org/attachment.cgi?id=42088) this GPU resets before the actual 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 33171] [r600g, wine] kernel crash when loading level in FEAR
https://bugs.freedesktop.org/show_bug.cgi?id=33171 --- Comment #1 from Tobias Jakobi 2011-01-15 14:55:32 PST --- Created an attachment (id=42088) --> (https://bugs.freedesktop.org/attachment.cgi?id=42088) this GPU resets before the actual 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 33171] New: [r600g, wine] kernel crash when loading level in FEAR
https://bugs.freedesktop.org/show_bug.cgi?id=33171 Summary: [r600g, wine] kernel crash when loading level in FEAR Product: DRI Version: DRI CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/Radeon AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: liquid.a...@gmx.net Created an attachment (id=42087) --> (https://bugs.freedesktop.org/attachment.cgi?id=42087) kernel log Hello! I just triggered a kernel crash while trying out some game in wine (the same as in bug #33066). Jan 15 23:17:22 voodoomaster kernel: BUG: unable to handle kernel paging request at c9001028 When loading the intro sequence in FEAR the screen suddenly went blank and switched back to console to display this error. The full error is attached as textfile. Could still log into the machine via ssh and salvage the kernel log. System: ATI Technologies Inc Radeon HD 4770 [RV740] drm-radeon-testing kernel libdrm, mesa and xf86-video-ati are all git master xorg-server-1.9.3.901 wine is version 1.3.11 and the game I triggered this with is the FEAR demo: http://www.gamershell.com/download_10167.shtml GLSL was enabled in wine. Greets, Tobias -- 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 33171] New: [r600g, wine] kernel crash when loading level in FEAR
https://bugs.freedesktop.org/show_bug.cgi?id=33171 Summary: [r600g, wine] kernel crash when loading level in FEAR Product: DRI Version: DRI CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/Radeon AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: liquid.acid at gmx.net Created an attachment (id=42087) --> (https://bugs.freedesktop.org/attachment.cgi?id=42087) kernel log Hello! I just triggered a kernel crash while trying out some game in wine (the same as in bug #33066). Jan 15 23:17:22 voodoomaster kernel: BUG: unable to handle kernel paging request at c9001028 When loading the intro sequence in FEAR the screen suddenly went blank and switched back to console to display this error. The full error is attached as textfile. Could still log into the machine via ssh and salvage the kernel log. System: ATI Technologies Inc Radeon HD 4770 [RV740] drm-radeon-testing kernel libdrm, mesa and xf86-video-ati are all git master xorg-server-1.9.3.901 wine is version 1.3.11 and the game I triggered this with is the FEAR demo: http://www.gamershell.com/download_10167.shtml GLSL was enabled in wine. Greets, Tobias -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 31046] [r600g, tiling] visual errors and GPU resets
https://bugs.freedesktop.org/show_bug.cgi?id=31046 Tobias Jakobi changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #8 from Tobias Jakobi 2011-01-15 14:45:11 PST --- I have retested this with all important components updated: Issue is no longer present for me. Forcing tiling on doesn't create any (more) major issues on quake3, doom3 and ut then without this option. Setting this to RESOLVED, FIXED. -- 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 31046] [r600g, tiling] visual errors and GPU resets
https://bugs.freedesktop.org/show_bug.cgi?id=31046 Tobias Jakobi changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #8 from Tobias Jakobi 2011-01-15 14:45:11 PST --- I have retested this with all important components updated: Issue is no longer present for me. Forcing tiling on doesn't create any (more) major issues on quake3, doom3 and ut then without this option. Setting this to RESOLVED, FIXED. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 16265] Why is kslowd accumulating so much CPU time?
https://bugzilla.kernel.org/show_bug.cgi?id=16265 --- Comment #12 from Chris Wilson 2011-01-15 22:35:48 --- (In reply to comment #11) > This issue is still present for me with Intel 4500 MHD (intel driver 2.14.0, > xorg-server 1.9.3.901, mesa 7.9.1, libdrm 2.4.23) with gentoo-sources 2.6.37. > I've read this announcement and disabled my drm_kms_helper.poll=N kernel boot > param but the issue has come up after few minutes after booting. System was > sluggish and kworker process appeared eating 60% CPU. Different culprit - you neither have the affected hardware nor the responsible hotplug polling enabled. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33078] Sauerbraten refuses to start
https://bugs.freedesktop.org/show_bug.cgi?id=33078 --- Comment #4 from barisu...@gmail.com 2011-01-15 14:25:18 PST --- (In reply to comment #3) > (In reply to comment #2) > > > That does look like an SDL issue. What version of it are you using? > > Still waiting for an answer. > > > > From Xorg.1.log: > > > > [12.618] (EE) open /dev/fb0: No such file or directory > > [12.618] (EE) No devices detected. > > [12.618] > > Fatal server error: > > [12.618] no screens found > > [12.618] > > Not sure what that's to do with the sauerbraten problem. SDL version: 1.2.14-4ubuntu1.1 "> Not sure what that's to do with the sauerbraten problem." I'm not sure too coz I'm just a qt4 gui guy :) Its the only error I could find in the X logs. -- 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 33078] Sauerbraten refuses to start
https://bugs.freedesktop.org/show_bug.cgi?id=33078 --- Comment #4 from barisurum at gmail.com 2011-01-15 14:25:18 PST --- (In reply to comment #3) > (In reply to comment #2) > > > That does look like an SDL issue. What version of it are you using? > > Still waiting for an answer. > > > > From Xorg.1.log: > > > > [12.618] (EE) open /dev/fb0: No such file or directory > > [12.618] (EE) No devices detected. > > [12.618] > > Fatal server error: > > [12.618] no screens found > > [12.618] > > Not sure what that's to do with the sauerbraten problem. SDL version: 1.2.14-4ubuntu1.1 "> Not sure what that's to do with the sauerbraten problem." I'm not sure too coz I'm just a qt4 gui guy :) Its the only error I could find in the X logs. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28623] [r300g] ETQW: Invalid index buffer range.
https://bugs.freedesktop.org/show_bug.cgi?id=28623 --- Comment #16 from Álmos 2011-01-15 14:20:15 PST --- Now this problem appeared again, and I was able to investigate it. In .etqwctl/base/etqwconfig.cfg the correct setting is seta r_useIndexBuffers "1" and the incorrect is "0". I still don't know why, when, or how this was changed automatically. -- 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 28623] [r300g] ETQW: Invalid index buffer range.
https://bugs.freedesktop.org/show_bug.cgi?id=28623 --- Comment #16 from ?lmos 2011-01-15 14:20:15 PST --- Now this problem appeared again, and I was able to investigate it. In .etqwctl/base/etqwconfig.cfg the correct setting is seta r_useIndexBuffers "1" and the incorrect is "0". I still don't know why, when, or how this was changed automatically. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 26812] Radeon module causes hard reset on modprobe
https://bugzilla.kernel.org/show_bug.cgi?id=26812 Alex Deucher changed: What|Removed |Added CC||alexdeuc...@gmail.com --- Comment #1 from Alex Deucher 2011-01-15 22:11:00 --- What radeoon chip do you have? If it's an r6xx, r7xx, or evergreen asic, this possibly a duplicate of this bug: https://bugs.freedesktop.org/show_bug.cgi?id=33027 If so, does the patch there help? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26712] Weird X display upon hibernating
https://bugzilla.kernel.org/show_bug.cgi?id=26712 --- Comment #4 from Alex Deucher 2011-01-15 22:07:52 --- I think Karmic used UMS rather than KMS, so it's not a regression as KMS and UMS are basically different driver stacks. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26552] Screen flickering with 2.6.37 [ATI X1600]
https://bugzilla.kernel.org/show_bug.cgi?id=26552 --- Comment #14 from Andrea Iob 2011-01-15 14:06:50 --- I've spoken too soon, patch of comment #11 did NOT fix the problem. After at least 10 reboots without any problems, today the flickering is back. Now I'm back with patch of comment #8. After a couple of reboots all seems ok, I'll wait some days to see if the problem comes back again. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 31565] [r300] radeon_texture.c:136: radeon_teximage_map: Assertion `!image->base.Data' failed.
https://bugs.freedesktop.org/show_bug.cgi?id=31565 --- Comment #2 from Marcel 2011-01-15 13:43:51 PST --- I'm experiencing this problem under Arch Linux (x64, 2.6.36.2, Mesa 7.10) when trying to launch Gnome-Shell from git on an R600: 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3650 -- 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 31565] [r300] radeon_texture.c:136: radeon_teximage_map: Assertion `!image->base.Data' failed.
https://bugs.freedesktop.org/show_bug.cgi?id=31565 --- Comment #2 from Marcel 2011-01-15 13:43:51 PST --- I'm experiencing this problem under Arch Linux (x64, 2.6.36.2, Mesa 7.10) when trying to launch Gnome-Shell from git on an R600: 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3650 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 26812] New: Radeon module causes hard reset on modprobe
https://bugzilla.kernel.org/show_bug.cgi?id=26812 Summary: Radeon module causes hard reset on modprobe Product: Drivers Version: 2.5 Kernel Version: 2.6.37-git9 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-...@kernel-bugs.osdl.org ReportedBy: mjevans1...@gmail.com Regression: No I'm using the git snapshots between when Linus merged from drm-core-next and when network drivers were merged (breaks build). If there is a better patch relative to a released source I'll gladly test it too; however the other sources I tried also had similar issues. When radeon.ko (or build in init) starts the screens blank and a few seconds later the system completely reboots. This is 100% repeatable. I have firmware from Arch's (AUR) linux-firmware-git package installed, /lib/firmware pointed as the source, and the relevant blobs for the recent ATI/AMD GPUs. When built as a module I can modprobe radeon to trigger the exact same behavior. Problems debugging: * It resets so hard there isn't a peep from netconsole. * It resets so hard that my disks loose md raid sync and need to completely rebuild (yeah, I know, I'll add a write-intent log before I test this again next time...; it wasn't an issue before I got the brainwave of making it a module to try to give netconsole/syslog time to get setup.) How can I possibly approach isolating this? Even a link to the correct documentation would be helpful. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26712] Weird X display upon hibernating
https://bugzilla.kernel.org/show_bug.cgi?id=26712 --- Comment #3 from Siddu 2011-01-15 21:12:32 --- (In reply to comment #2) > Did hibernate ever work properly on your system? If so when and can you > bisect? It used to work fine with Ubuntu Karmic. And i just found out that the issue seems to be present with the distro(Ubuntu Lucid) kernel(2.6.32-21-generic) as well . So that concludes hibernate never has been working on lucid -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 16265] Why is kslowd accumulating so much CPU time?
https://bugzilla.kernel.org/show_bug.cgi?id=16265 Bc. Slavomir Danas changed: What|Removed |Added CC||slavomir.da...@gmail.com --- Comment #11 from Bc. Slavomir Danas 2011-01-15 20:42:49 --- This issue is still present for me with Intel 4500 MHD (intel driver 2.14.0, xorg-server 1.9.3.901, mesa 7.9.1, libdrm 2.4.23) with gentoo-sources 2.6.37. I've read this announcement and disabled my drm_kms_helper.poll=N kernel boot param but the issue has come up after few minutes after booting. System was sluggish and kworker process appeared eating 60% CPU. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH 3/5] radeon: Expose backlight class device for legacy LVDS encoder
On Fri, Jan 14, 2011 at 2:24 PM, Matthew Garrett wrote:
> From: Michel D?nzer
>
> Allows e.g. power management daemons to control the backlight level. Inspired
> by the corresponding code in radeonfb.
>
> (Updated to add backlight type and make the connector the parent device - mjg)
>
> Signed-off-by: Michel D?nzer
> Signed-off-by: Matthew Garrett
Acked-by: Alex Deucher
> Cc: dri-devel at lists.freedesktop.org
> ---
> ?drivers/gpu/drm/radeon/Kconfig ? ? ? ? ? ? ? ? ?| ? ?1 +
> ?drivers/gpu/drm/radeon/radeon_connectors.c ? ? ?| ? 15 ++
> ?drivers/gpu/drm/radeon/radeon_legacy_encoders.c | ?257
> ++-
> ?drivers/gpu/drm/radeon/radeon_mode.h ? ? ? ? ? ?| ? 10 +
> ?4 files changed, 277 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/Kconfig b/drivers/gpu/drm/radeon/Kconfig
> index 1c02d23..9746fee 100644
> --- a/drivers/gpu/drm/radeon/Kconfig
> +++ b/drivers/gpu/drm/radeon/Kconfig
> @@ -1,6 +1,7 @@
> ?config DRM_RADEON_KMS
> ? ? ? ?bool "Enable modesetting on radeon by default - NEW DRIVER"
> ? ? ? ?depends on DRM_RADEON
> + ? ? ? select BACKLIGHT_CLASS_DEVICE
> ? ? ? ?help
> ? ? ? ? ?Choose this option if you want kernel modesetting enabled by default.
>
> diff --git a/drivers/gpu/drm/radeon/radeon_connectors.c
> b/drivers/gpu/drm/radeon/radeon_connectors.c
> index 22b7e3d..e842fb5 100644
> --- a/drivers/gpu/drm/radeon/radeon_connectors.c
> +++ b/drivers/gpu/drm/radeon/radeon_connectors.c
> @@ -40,6 +40,10 @@ radeon_atombios_connected_scratch_regs(struct
> drm_connector *connector,
> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? struct drm_encoder *encoder,
> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? bool connected);
>
> +extern void
> +radeon_legacy_backlight_init(struct radeon_encoder *radeon_encoder,
> + ? ? ? ? ? ? ? ? ? ? ? ? ? ?struct drm_connector *drm_connector);
> +
> ?void radeon_connector_hotplug(struct drm_connector *connector)
> ?{
> ? ? ? ?struct drm_device *dev = connector->dev;
> @@ -1517,6 +1521,17 @@ radeon_add_legacy_connector(struct drm_device *dev,
> ? ? ? ? ? ? ? ?connector->polled = DRM_CONNECTOR_POLL_HPD;
> ? ? ? ?connector->display_info.subpixel_order = subpixel_order;
> ? ? ? ?drm_sysfs_connector_add(connector);
> + ? ? ? if (connector_type == DRM_MODE_CONNECTOR_LVDS) {
> + ? ? ? ? ? ? ? struct drm_encoder *drm_encoder;
> +
> + ? ? ? ? ? ? ? list_for_each_entry(drm_encoder,
> &dev->mode_config.encoder_list, head) {
> + ? ? ? ? ? ? ? ? ? ? ? struct radeon_encoder *radeon_encoder;
> +
> + ? ? ? ? ? ? ? ? ? ? ? radeon_encoder = to_radeon_encoder(drm_encoder);
> + ? ? ? ? ? ? ? ? ? ? ? if (radeon_encoder->encoder_id ==
> ENCODER_OBJECT_ID_INTERNAL_LVDS)
> + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? radeon_legacy_backlight_init(radeon_encoder,
> connector);
> + ? ? ? ? ? ? ? }
> + ? ? ? }
> ? ? ? ?return;
>
> ?failed:
> diff --git a/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
> b/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
> index 59f834b..ba7dcc6 100644
> --- a/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
> +++ b/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
> @@ -28,6 +28,10 @@
> ?#include "radeon_drm.h"
> ?#include "radeon.h"
> ?#include "atom.h"
> +#include
> +#ifdef CONFIG_PMAC_BACKLIGHT
> +#include
> +#endif
>
> ?static void radeon_legacy_encoder_disable(struct drm_encoder *encoder)
> ?{
> @@ -39,7 +43,7 @@ static void radeon_legacy_encoder_disable(struct
> drm_encoder *encoder)
> ? ? ? ?radeon_encoder->active_device = 0;
> ?}
>
> -static void radeon_legacy_lvds_dpms(struct drm_encoder *encoder, int mode)
> +static void radeon_legacy_lvds_update(struct drm_encoder *encoder, int mode)
> ?{
> ? ? ? ?struct drm_device *dev = encoder->dev;
> ? ? ? ?struct radeon_device *rdev = dev->dev_private;
> @@ -47,15 +51,23 @@ static void radeon_legacy_lvds_dpms(struct drm_encoder
> *encoder, int mode)
> ? ? ? ?uint32_t lvds_gen_cntl, lvds_pll_cntl, pixclks_cntl, disp_pwr_man;
> ? ? ? ?int panel_pwr_delay = 2000;
> ? ? ? ?bool is_mac = false;
> + ? ? ? uint8_t backlight_level;
> ? ? ? ?DRM_DEBUG_KMS("\n");
>
> + ? ? ? lvds_gen_cntl = RREG32(RADEON_LVDS_GEN_CNTL);
> + ? ? ? backlight_level = (lvds_gen_cntl >> RADEON_LVDS_BL_MOD_LEVEL_SHIFT) &
> 0xff;
> +
> ? ? ? ?if (radeon_encoder->enc_priv) {
> ? ? ? ? ? ? ? ?if (rdev->is_atom_bios) {
> ? ? ? ? ? ? ? ? ? ? ? ?struct radeon_encoder_atom_dig *lvds =
> radeon_encoder->enc_priv;
> ? ? ? ? ? ? ? ? ? ? ? ?panel_pwr_delay = lvds->panel_pwr_delay;
> + ? ? ? ? ? ? ? ? ? ? ? if (lvds->bl_dev)
> + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? backlight_level = lvds->backlight_level;
> ? ? ? ? ? ? ? ?} else {
> ? ? ? ? ? ? ? ? ? ? ? ?struct radeon_encoder_lvds *lvds =
> radeon_encoder->enc_priv;
> ? ? ? ? ? ? ? ? ? ? ? ?panel_pwr_delay = lvds->panel_pwr_delay;
> + ? ? ? ? ? ? ? ? ? ? ? if (lvds->bl_dev)
> + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? backlight_level = lvds->backlight_level;
> ? ? ? ? ? ? ? ?}
> ? ? ? ?}
>
> @@ -82,11 +94,13 @@ static void radeon_legacy_lvds_dpms(struct drm_encoder
> *encoder, int mode)
> ? ? ? ? ? ? ? ?l
[Bug 26712] Weird X display upon hibernating
https://bugzilla.kernel.org/show_bug.cgi?id=26712 Rafael J. Wysocki changed: What|Removed |Added CC||flor...@mickler.org, ||maciej.rute...@gmail.com, ||r...@sisk.pl Blocks||21782 Alex Deucher changed: What|Removed |Added CC||alexdeuc...@gmail.com --- Comment #2 from Alex Deucher 2011-01-15 17:36:54 --- Did hibernate ever work properly on your system? If so when and can you bisect? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 3/5] radeon: Expose backlight class device for legacy LVDS encoder
On Fri, Jan 14, 2011 at 2:24 PM, Matthew Garrett wrote:
> From: Michel Dänzer
>
> Allows e.g. power management daemons to control the backlight level. Inspired
> by the corresponding code in radeonfb.
>
> (Updated to add backlight type and make the connector the parent device - mjg)
>
> Signed-off-by: Michel Dänzer
> Signed-off-by: Matthew Garrett
Acked-by: Alex Deucher
> Cc: dri-devel@lists.freedesktop.org
> ---
> drivers/gpu/drm/radeon/Kconfig | 1 +
> drivers/gpu/drm/radeon/radeon_connectors.c | 15 ++
> drivers/gpu/drm/radeon/radeon_legacy_encoders.c | 257
> ++-
> drivers/gpu/drm/radeon/radeon_mode.h | 10 +
> 4 files changed, 277 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/Kconfig b/drivers/gpu/drm/radeon/Kconfig
> index 1c02d23..9746fee 100644
> --- a/drivers/gpu/drm/radeon/Kconfig
> +++ b/drivers/gpu/drm/radeon/Kconfig
> @@ -1,6 +1,7 @@
> config DRM_RADEON_KMS
> bool "Enable modesetting on radeon by default - NEW DRIVER"
> depends on DRM_RADEON
> + select BACKLIGHT_CLASS_DEVICE
> help
> Choose this option if you want kernel modesetting enabled by default.
>
> diff --git a/drivers/gpu/drm/radeon/radeon_connectors.c
> b/drivers/gpu/drm/radeon/radeon_connectors.c
> index 22b7e3d..e842fb5 100644
> --- a/drivers/gpu/drm/radeon/radeon_connectors.c
> +++ b/drivers/gpu/drm/radeon/radeon_connectors.c
> @@ -40,6 +40,10 @@ radeon_atombios_connected_scratch_regs(struct
> drm_connector *connector,
> struct drm_encoder *encoder,
> bool connected);
>
> +extern void
> +radeon_legacy_backlight_init(struct radeon_encoder *radeon_encoder,
> + struct drm_connector *drm_connector);
> +
> void radeon_connector_hotplug(struct drm_connector *connector)
> {
> struct drm_device *dev = connector->dev;
> @@ -1517,6 +1521,17 @@ radeon_add_legacy_connector(struct drm_device *dev,
> connector->polled = DRM_CONNECTOR_POLL_HPD;
> connector->display_info.subpixel_order = subpixel_order;
> drm_sysfs_connector_add(connector);
> + if (connector_type == DRM_MODE_CONNECTOR_LVDS) {
> + struct drm_encoder *drm_encoder;
> +
> + list_for_each_entry(drm_encoder,
> &dev->mode_config.encoder_list, head) {
> + struct radeon_encoder *radeon_encoder;
> +
> + radeon_encoder = to_radeon_encoder(drm_encoder);
> + if (radeon_encoder->encoder_id ==
> ENCODER_OBJECT_ID_INTERNAL_LVDS)
> + radeon_legacy_backlight_init(radeon_encoder,
> connector);
> + }
> + }
> return;
>
> failed:
> diff --git a/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
> b/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
> index 59f834b..ba7dcc6 100644
> --- a/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
> +++ b/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
> @@ -28,6 +28,10 @@
> #include "radeon_drm.h"
> #include "radeon.h"
> #include "atom.h"
> +#include
> +#ifdef CONFIG_PMAC_BACKLIGHT
> +#include
> +#endif
>
> static void radeon_legacy_encoder_disable(struct drm_encoder *encoder)
> {
> @@ -39,7 +43,7 @@ static void radeon_legacy_encoder_disable(struct
> drm_encoder *encoder)
> radeon_encoder->active_device = 0;
> }
>
> -static void radeon_legacy_lvds_dpms(struct drm_encoder *encoder, int mode)
> +static void radeon_legacy_lvds_update(struct drm_encoder *encoder, int mode)
> {
> struct drm_device *dev = encoder->dev;
> struct radeon_device *rdev = dev->dev_private;
> @@ -47,15 +51,23 @@ static void radeon_legacy_lvds_dpms(struct drm_encoder
> *encoder, int mode)
> uint32_t lvds_gen_cntl, lvds_pll_cntl, pixclks_cntl, disp_pwr_man;
> int panel_pwr_delay = 2000;
> bool is_mac = false;
> + uint8_t backlight_level;
> DRM_DEBUG_KMS("\n");
>
> + lvds_gen_cntl = RREG32(RADEON_LVDS_GEN_CNTL);
> + backlight_level = (lvds_gen_cntl >> RADEON_LVDS_BL_MOD_LEVEL_SHIFT) &
> 0xff;
> +
> if (radeon_encoder->enc_priv) {
> if (rdev->is_atom_bios) {
> struct radeon_encoder_atom_dig *lvds =
> radeon_encoder->enc_priv;
> panel_pwr_delay = lvds->panel_pwr_delay;
> + if (lvds->bl_dev)
> + backlight_level = lvds->backlight_level;
> } else {
> struct radeon_encoder_lvds *lvds =
> radeon_encoder->enc_priv;
> panel_pwr_delay = lvds->panel_pwr_delay;
> + if (lvds->bl_dev)
> + backlight_level = lvds->backlight_level;
> }
> }
>
> @@ -82,11 +94,13 @@ static void radeon_legacy_lvds_dpms(struct drm_encoder
> *encoder, int mode)
> lvds
[Bug 33078] Sauerbraten refuses to start
https://bugs.freedesktop.org/show_bug.cgi?id=33078 --- Comment #3 from Michel Dänzer 2011-01-15 08:33:27 PST --- (In reply to comment #2) > > That does look like an SDL issue. What version of it are you using? Still waiting for an answer. > From Xorg.1.log: > > [12.618] (EE) open /dev/fb0: No such file or directory > [12.618] (EE) No devices detected. > [12.618] > Fatal server error: > [12.618] no screens found > [12.618] Not sure what that's to do with the sauerbraten problem. -- 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 33078] Sauerbraten refuses to start
https://bugs.freedesktop.org/show_bug.cgi?id=33078 --- Comment #3 from Michel D?nzer 2011-01-15 08:33:27 PST --- (In reply to comment #2) > > That does look like an SDL issue. What version of it are you using? Still waiting for an answer. > From Xorg.1.log: > > [12.618] (EE) open /dev/fb0: No such file or directory > [12.618] (EE) No devices detected. > [12.618] > Fatal server error: > [12.618] no screens found > [12.618] Not sure what that's to do with the sauerbraten problem. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: [PATCH 1/5] Backlight: Add backlight type
[...] +What: /sys/class/backlight//type +Date: September 2010 +KernelVersion: 2.6.37 [...] 2.6.37? Will this go into 2.6.38? 2.6.39? Through which subsystem will these patches walk through? drm-2.6? platform-drivers-x86? Are you planning a GIT tree/branch for this patch-set? The patch-set from 14-Jan-2011 applies against linux-next (next-20110115). I will compile, test and report. - Sedat - ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26552] Screen flickering with 2.6.37 [ATI X1600]
https://bugzilla.kernel.org/show_bug.cgi?id=26552 --- Comment #14 from Andrea Iob 2011-01-15 14:06:50 --- I've spoken too soon, patch of comment #11 did NOT fix the problem. After at least 10 reboots without any problems, today the flickering is back. Now I'm back with patch of comment #8. After a couple of reboots all seems ok, I'll wait some days to see if the problem comes back again. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33142] r300g produces black textures in nexuiz with glsl offsetmapping on
https://bugs.freedesktop.org/show_bug.cgi?id=33142 Marek Olšák changed: What|Removed |Added Product|DRI |Mesa Version|XOrg CVS|unspecified Component|DRM/Radeon |Drivers/Gallium/r300 --- Comment #1 from Marek Olšák 2011-01-15 02:42:00 PST --- I believe it's the issue with texture indirections we had before. The conclusion was that it's a hardware limitation that we can't overcome. I don't remember the exact details but I'll wait for Tom if he has anything to say. -- 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 33142] r300g produces black textures in nexuiz with glsl offsetmapping on
https://bugs.freedesktop.org/show_bug.cgi?id=33142 Marek Ol??k changed: What|Removed |Added Product|DRI |Mesa Version|XOrg CVS|unspecified Component|DRM/Radeon |Drivers/Gallium/r300 --- Comment #1 from Marek Ol??k 2011-01-15 02:42:00 PST --- I believe it's the issue with texture indirections we had before. The conclusion was that it's a hardware limitation that we can't overcome. I don't remember the exact details but I'll wait for Tom if he has anything to say. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: [PATCH 4/5] nouveau: Change the backlight parent device to the connector, not the PCI dev
On Fri, 2011-01-14 at 14:24 -0500, Matthew Garrett wrote:
> We may eventually end up with per-connector backlights, especially with
> ddcci devices. Make sure that the parent node for the backlight device is
> the connector rather than the PCI device.
>
> Signed-off-by: Matthew Garrett
Acked-by: Ben Skeggs
> ---
> drivers/gpu/drm/nouveau/nouveau_backlight.c | 24 ++--
> drivers/gpu/drm/nouveau/nouveau_connector.c |9 +
> drivers/gpu/drm/nouveau/nouveau_drv.h |8
> drivers/gpu/drm/nouveau/nouveau_state.c |6 --
> 4 files changed, 27 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/gpu/drm/nouveau/nouveau_backlight.c
> b/drivers/gpu/drm/nouveau/nouveau_backlight.c
> index 18d7bcc..00a55df 100644
> --- a/drivers/gpu/drm/nouveau/nouveau_backlight.c
> +++ b/drivers/gpu/drm/nouveau/nouveau_backlight.c
> @@ -88,10 +88,11 @@ static const struct backlight_ops nv50_bl_ops = {
> .update_status = nv50_set_intensity,
> };
>
> -static int nouveau_nv40_backlight_init(struct drm_device *dev)
> +static int nouveau_nv40_backlight_init(struct drm_connector *connector)
> {
> - struct backlight_properties props;
> + struct drm_device *dev = connector->dev;
> struct drm_nouveau_private *dev_priv = dev->dev_private;
> + struct backlight_properties props;
> struct backlight_device *bd;
>
> if (!(nv_rd32(dev, NV40_PMC_BACKLIGHT) & NV40_PMC_BACKLIGHT_MASK))
> @@ -100,7 +101,7 @@ static int nouveau_nv40_backlight_init(struct drm_device
> *dev)
> memset(&props, 0, sizeof(struct backlight_properties));
> props.type = BACKLIGHT_RAW;
> props.max_brightness = 31;
> - bd = backlight_device_register("nv_backlight", &dev->pdev->dev, dev,
> + bd = backlight_device_register("nv_backlight", &connector->kdev, dev,
> &nv40_bl_ops, &props);
> if (IS_ERR(bd))
> return PTR_ERR(bd);
> @@ -112,10 +113,11 @@ static int nouveau_nv40_backlight_init(struct
> drm_device *dev)
> return 0;
> }
>
> -static int nouveau_nv50_backlight_init(struct drm_device *dev)
> +static int nouveau_nv50_backlight_init(struct drm_connector *connector)
> {
> - struct backlight_properties props;
> + struct drm_device *dev = connector->dev;
> struct drm_nouveau_private *dev_priv = dev->dev_private;
> + struct backlight_properties props;
> struct backlight_device *bd;
>
> if (!nv_rd32(dev, NV50_PDISPLAY_SOR_BACKLIGHT))
> @@ -124,7 +126,7 @@ static int nouveau_nv50_backlight_init(struct drm_device
> *dev)
> memset(&props, 0, sizeof(struct backlight_properties));
> props.type = BACKLIGHT_RAW;
> props.max_brightness = 1025;
> - bd = backlight_device_register("nv_backlight", &dev->pdev->dev, dev,
> + bd = backlight_device_register("nv_backlight", &connector->kdev, dev,
> &nv50_bl_ops, &props);
> if (IS_ERR(bd))
> return PTR_ERR(bd);
> @@ -135,8 +137,9 @@ static int nouveau_nv50_backlight_init(struct drm_device
> *dev)
> return 0;
> }
>
> -int nouveau_backlight_init(struct drm_device *dev)
> +int nouveau_backlight_init(struct drm_connector *connector)
> {
> + struct drm_device *dev = connector->dev;
> struct drm_nouveau_private *dev_priv = dev->dev_private;
>
> #ifdef CONFIG_ACPI
> @@ -149,9 +152,9 @@ int nouveau_backlight_init(struct drm_device *dev)
>
> switch (dev_priv->card_type) {
> case NV_40:
> - return nouveau_nv40_backlight_init(dev);
> + return nouveau_nv40_backlight_init(connector);
> case NV_50:
> - return nouveau_nv50_backlight_init(dev);
> + return nouveau_nv50_backlight_init(connector);
> default:
> break;
> }
> @@ -159,8 +162,9 @@ int nouveau_backlight_init(struct drm_device *dev)
> return 0;
> }
>
> -void nouveau_backlight_exit(struct drm_device *dev)
> +void nouveau_backlight_exit(struct drm_connector *connector)
> {
> + struct drm_device *dev = connector->dev;
> struct drm_nouveau_private *dev_priv = dev->dev_private;
>
> if (dev_priv->backlight) {
> diff --git a/drivers/gpu/drm/nouveau/nouveau_connector.c
> b/drivers/gpu/drm/nouveau/nouveau_connector.c
> index a21e000..3a1ecc7 100644
> --- a/drivers/gpu/drm/nouveau/nouveau_connector.c
> +++ b/drivers/gpu/drm/nouveau/nouveau_connector.c
> @@ -116,6 +116,10 @@ nouveau_connector_destroy(struct drm_connector
> *connector)
> nouveau_connector_hotplug, connector);
> }
>
> + if (connector->connector_type == DRM_MODE_CONNECTOR_LVDS ||
> + connector->connector_type == DRM_MODE_CONNECTOR_eDP)
> + nouveau_backlight_exit(connector);
> +
> kfree(nv_connector->edid);
> drm_sysfs_connector_remove(connector);
> drm_connector_cleanup(connector);
> @@ -893,6 +897,11 @@ nouveau
[Bug 33077] Broken rendering with black areas in Doom3-demo also falls to 3-4 fps time to time
https://bugs.freedesktop.org/show_bug.cgi?id=33077 Pavel Ondračka changed: What|Removed |Added Component|Drivers/DRI/r300|Drivers/Gallium/r300 -- 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 33077] Broken rendering with black areas in Doom3-demo also falls to 3-4 fps time to time
https://bugs.freedesktop.org/show_bug.cgi?id=33077 Pavel Ondra?ka changed: What|Removed |Added Component|Drivers/DRI/r300|Drivers/Gallium/r300 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 33142] New: r300g produces black textures in nexuiz with glsl offsetmapping on
https://bugs.freedesktop.org/show_bug.cgi?id=33142 Summary: r300g produces black textures in nexuiz with glsl offsetmapping on 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@lists.freedesktop.org ReportedBy: kontrolla...@gmx.de When i run stock phoronix test suite nexuiz i get black textures. I found that this is caused by using th effects-high.cfg. when i swith to effects-normal all textures look as they should. i found that this is caused by glsl_offsetmapping set to 1 (aka enabled). when i change it to 0 everything is okay, when i change it to 1 all textures are black. System is an rv410 (x700 mobility), latest mesa / drm / kernel from git as of today. i filed this bug against drm, if it is more likely a mesa problem feel free to reassign it. if you need more info please tell me. thank you for your time. greetings jan kreuzer -- 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 33142] New: r300g produces black textures in nexuiz with glsl offsetmapping on
https://bugs.freedesktop.org/show_bug.cgi?id=33142 Summary: r300g produces black textures in nexuiz with glsl offsetmapping on 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 at lists.freedesktop.org ReportedBy: kontrollator at gmx.de When i run stock phoronix test suite nexuiz i get black textures. I found that this is caused by using th effects-high.cfg. when i swith to effects-normal all textures look as they should. i found that this is caused by glsl_offsetmapping set to 1 (aka enabled). when i change it to 0 everything is okay, when i change it to 1 all textures are black. System is an rv410 (x700 mobility), latest mesa / drm / kernel from git as of today. i filed this bug against drm, if it is more likely a mesa problem feel free to reassign it. if you need more info please tell me. thank you for your time. greetings jan kreuzer -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
