dri-devel January 2011

dri-devel@lists.freedesktop.org

70 participants
451 discussions

[Bug 31943] drm EDID checking is too strict
by bugzilla-daemon＠freedesktop.org 10 Jan '11

10 Jan '11

https://bugs.freedesktop.org/show_bug.cgi?id=31943 --- Comment #9 from Thomas Drillich <th(a)drillich.com> 2011-01-10 11:16:29 PST --- Hi, patch of comment #6 helped me, when using kernel 2.6.37. Before patch monitor at hdmi port stays black, cause of: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 254 But is that patch the solution for the bug ? gpu: ATI RS880 [Radeon HD 4200] rev 0 (ChipID = 0x9710) Monitor: VGA: Philips 180P2 (II) RADEON(0): EDID (in hex): (II) RADEON(0): 00ffffffffffff00410c080835110000 (II) RADEON(0): 1f0c01030f241d78ea0925a2574b9724 (II) RADEON(0): 185054bfef80314f454f614f81800101 (II) RADEON(0): 010101010101302a009851002a403070 (II) RADEON(0): 1300671f1100001e000000ff00204844 (II) RADEON(0): 20203030343430350a20000000fc0050 (II) RADEON(0): 68696c697073203138305032000000fd (II) RADEON(0): 00384c1e520e000a202020202020006e HDMI: iiyama PLB2403WS (II) RADEON(0): EDID (in hex): (II) RADEON(0): 7f7f7f7f7f7f7f7f26cd0156fdc40000 (II) RADEON(0): 3111010380342178ea5ad5a7564b9b24 (II) RADEON(0): 135054bdef80714f81908180818ca940 (II) RADEON(0): b300950f9500283c80a070b023403020 (II) RADEON(0): 360007442100001a000000ff00303537 (II) RADEON(0): 34323730313130303031000000fd0038 (II) RADEON(0): 4c1e5311000a202020202020000000fc (II) RADEON(0): 00504c423234303357530a202020018e -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 32918] gnome-shell / mutter crashing.
by bugzilla-daemon＠freedesktop.org 10 Jan '11

10 Jan '11

https://bugs.freedesktop.org/show_bug.cgi?id=32918 --- Comment #6 from Lee Wilson <vixsandlee(a)gmail.com> 2011-01-10 10:03:40 PST --- The version that builds with gnome-shell from source ( http://live.gnome.org/GnomeShell ) I build gnome-shell from that, I tend to test it daily to see if the issue has gone, so its whatever version they had at around 7am GMT -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 32918] gnome-shell / mutter crashing.
by bugzilla-daemon＠freedesktop.org 10 Jan '11

10 Jan '11

https://bugs.freedesktop.org/show_bug.cgi?id=32918 --- Comment #5 from Kevin DeKorte <kdekorte(a)yahoo.com> 2011-01-10 09:59:57 PST --- Lee, What version of clutter do you have installed? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 25052] kernel modesetting still does not work
by bugzilla-daemon＠bugzilla.kernel.org 10 Jan '11

10 Jan '11

https://bugzilla.kernel.org/show_bug.cgi?id=25052 Alex Deucher <alexdeucher(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexdeucher(a)gmail.com --- Comment #7 from Alex Deucher <alexdeucher(a)gmail.com> 2011-01-10 17:58:05 --- make sure you remove the vga= from your kernel command line. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

[Bug 25052] kernel modesetting still does not work
by bugzilla-daemon＠bugzilla.kernel.org 10 Jan '11

10 Jan '11

https://bugzilla.kernel.org/show_bug.cgi?id=25052 Elmar Stellnberger <estellnb(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|PATCH_ALREADY_AVAILABLE | --- Comment #6 from Elmar Stellnberger <estellnb(a)gmail.com> 2011-01-10 17:56:05 --- Oops; it had only worked because the drm.edid_strict option made the still unchanged radeon module refuse to load. The external screen however is only blackened as soon as radeon is modprobed. If you apply the patch correctly and get the changed module shipped (which didn`t work in first place for whatever reason) the following happens if you specify drm.edid_strict on the kernel command line: integrated screen: whitened (fully white) external screen: black, no response At first it was still possible to switch back to vt01-03 and text modes were displayed correctly. Then suddenly everything was black and only a Ctrl-Alt-Delete could help me out. Somehow looks as if it was not beneficial to use the EDID data of that screen or do you see another possibility? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

[Bug 20142] enabling underscan by default behaves badly with so many monitors.
by bugzilla-daemon＠bugzilla.kernel.org 10 Jan '11

10 Jan '11

https://bugzilla.kernel.org/show_bug.cgi?id=20142 --- Comment #9 from Rafał Miłecki <zajec5(a)gmail.com> 2011-01-10 11:59:03 --- [PATCH] drm/radeon/kms: disable underscan by default http://www.mail-archive.com/dri-devel@lists.freedesktop.org/msg06695.html http://permalink.gmane.org/gmane.comp.video.dri.devel/53051 This is in drm-next already: http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdiff;… -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

Re: [Intel-gfx] [PATCH] drm: Aggressively disable vblanks
by Mario Kleiner 10 Jan '11

10 Jan '11

> ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 20 Dec 2010 19:23:40 -0800 > From: Keith Packard <keithp(a)keithp.com> > Subject: Re: [Intel-gfx] [PATCH] drm: Aggressively disable vblanks > To: Andy Lutomirski <luto(a)MIT.EDU>, Jesse Barnes > <jbarnes(a)virtuousgeek.org>, Chris Wilson <chris(a)chris-wilson.co.uk>, > David Airlie <airlied(a)linux.ie> > Cc: intel-gfx(a)lists.freedesktop.org, dri-devel(a)lists.freedesktop.org > Message-ID: <yunfwtrrepv.fsf(a)aiko.keithp.com> > Content-Type: text/plain; charset="us-ascii" > > On Mon, 20 Dec 2010 14:00:54 -0500, Andy Lutomirski <luto(a)MIT.EDU> > wrote: > >> Enabling and disabling the vblank interrupt (on devices that >> support it) is cheap. So disable it quickly after each >> interrupt. > > So, the concern (and reason for the original design) was that you > might > lose count of vblank interrupts as vblanks are counted differently > while > off than while on. If vblank interrupts get enabled near the interrupt > time, is it possible that you'll end up off by one somehow? > > Leaving them enabled for 'a while' was supposed to reduce the > impact of > this potential error. > > -- > keith.packard(a)intel.com >

5 8

Problems with X starting up w/ Nouveau on NV11 chipset
by Alex Buell 10 Jan '11

10 Jan '11

Hi! After experiencing the exact same problem with two other distributions (Fedora 15 and Ubuntu Natty), and again with Gentoo, I'm now asking whether anyone has experienced the same problems with the NV11 chipset. Symptoms: First my Xorg.0.log: (only the last few lines included) [ 70.626] (II) GLX: Initialized DRI2 GL provider for screen 0 [ 70.632] (II) NOUVEAU(0): NVEnterVT is called. [ 70.653] (EE) NOUVEAU(0): failed to set mode: Invalid argument Fatal server error: [ 70.654] failed to create screen resources [ 70.654] Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 70.654] Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 70.654] [ 70.655] (II) AIGLX: Suspending AIGLX clients for VT switch [ 70.655] (II) NOUVEAU(0): NVLeaveVT is called. And in my /var/log/messages, I get these messages: Jan 10 01:54:11 hydrogen kernel: [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:6] Jan 10 01:54:12 hydrogen kernel: [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:6] Jan 10 01:54:13 hydrogen kernel: [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:6] Jan 10 01:56:40 hydrogen kernel: [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:6] Jan 10 01:57:56 hydrogen kernel: [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:6] Any ideas why? Thanks for any advice given! -- Tactical Nuclear Kittens

1 0

[PATCH] drm/radeon/kms: disable underscan by default
by Alex Deucher 10 Jan '11

10 Jan '11

Lots of HDMI TVs overscan the incoming image by default. The underscan option was added as a way to compensate for that by underscanning the image so that the edges would not be cut off on an overscanning TV. However, the TV provides no way of knowing whether it is overscanning or not. If the user has disabled overscan on their TV or has a TV that does not overscan, you will get black bars around the edges of your screen. Prior to the patch we got complaints and bug reports from users with overscanning TVs, now with the patch, we get lots of complaints and bug reports from users with non-overscanning TVs. There's no good default, but on average there have been more users complaining about it being on by default than off, so change it to off. This will probably result in a new deluge of overscanning TV user complaints. There's no winning. Signed-off-by: Alex Deucher <alexdeucher(a)gmail.com> --- drivers/gpu/drm/radeon/radeon_connectors.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/radeon/radeon_connectors.c b/drivers/gpu/drm/radeon/radeon_connectors.c index 5b00f92..22b7e3d 100644 --- a/drivers/gpu/drm/radeon/radeon_connectors.c +++ b/drivers/gpu/drm/radeon/radeon_connectors.c @@ -1219,7 +1219,7 @@ radeon_add_atom_connector(struct drm_device *dev, if (ASIC_IS_AVIVO(rdev)) { drm_connector_attach_property(&radeon_connector->base, rdev->mode_info.underscan_property, - UNDERSCAN_AUTO); + UNDERSCAN_OFF); drm_connector_attach_property(&radeon_connector->base, rdev->mode_info.underscan_hborder_property, 0); @@ -1259,7 +1259,7 @@ radeon_add_atom_connector(struct drm_device *dev, if (ASIC_IS_AVIVO(rdev)) { drm_connector_attach_property(&radeon_connector->base, rdev->mode_info.underscan_property, - UNDERSCAN_AUTO); + UNDERSCAN_OFF); drm_connector_attach_property(&radeon_connector->base, rdev->mode_info.underscan_hborder_property, 0); @@ -1302,7 +1302,7 @@ radeon_add_atom_connector(struct drm_device *dev, if (ASIC_IS_AVIVO(rdev)) { drm_connector_attach_property(&radeon_connector->base, rdev->mode_info.underscan_property, - UNDERSCAN_AUTO); + UNDERSCAN_OFF); drm_connector_attach_property(&radeon_connector->base, rdev->mode_info.underscan_hborder_property, 0); -- 1.7.1.1

2 1

[WARNING] radeon/DRM lockup in 2.6.36.3
by Chris Rankin 09 Jan '11

09 Jan '11

Hi, My RV350 has just locked up while (presumably) running an OpenGL screensaver. Here is the dmesg trace, in the hope that it might be useful: radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec ------------[ cut here ]------------ radeon 0000:01:00.0: GPU lockup CP stall for more than 10004msec ------------[ cut here ]------------ WARNING: at /home/chris/LINUX/linux-2.6.36/drivers/gpu/drm/radeon/radeon_fence.c:235 radeon_fence_wait+0x1d5/0x261 [radeon]() Hardware name: Precision WorkStation 650 GPU lockup (waiting for 0x002B4CEB last fence id 0x002B4CEA) Modules linked in: snd_seq_oss snd_seq_midi snd_seq_dummy fuse cpufreq_ondemand nfsd exportfs autofs4 nfs lockd auth_rpcgss sunrpc p4_clockmod speedstep_lib af_packet ipt_LOG xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables ip6t_LOG nf_conntrack_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables x_tables ipv6 binfmt_misc loop dm_mirror dm_region_hash dm_log dm_mod uinput snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_event snd_seq_midi_emul snd_emu10k1 snd_ac97_codec snd_usb_audio ac97_bus snd_seq snd_pcm snd_util_mem snd_timer joydev uvcvideo snd_page_alloc snd_hwdep videodev v4l1_compat usbhid ppdev parport_pc firewire_ohci snd_usbmidi_lib snd_rawmidi snd_seq_device firewire_core snd parport floppy pcspkr psmouse i2c_i801 serio_raw soundcore dcdbas crc_itu_t sg ext3 jbd mbcache sr_mod cdrom sd_mod pata_acpi sata_sil uhci_hcd ata_piix libata ehci_hcd scsi_mod e1000 usbcore thermal button radeon intel_agp ttm drm_kms_helper drm agpgart i2c_algo_bit cfbcopyarea cfbimgblt cfbfillrect [last unloaded: mperf] Pid: 2721, comm: Xorg Not tainted 2.6.36.3 #1 Call Trace: [<c102558f>] ? warn_slowpath_common+0x6a/0x7d [<f81d2a55>] ? radeon_fence_wait+0x1d5/0x261 [radeon] [<c1025608>] ? warn_slowpath_fmt+0x28/0x2c [<f81d2a55>] ? radeon_fence_wait+0x1d5/0x261 [radeon] [<c10373dd>] ? autoremove_wake_function+0x0/0x29 [<f81e31ea>] ? radeon_ib_get+0xd7/0x16f [radeon] [<f81e3f93>] ? radeon_cs_parser_init+0x158/0x230 [radeon] [<f81e4145>] ? radeon_cs_ioctl+0x69/0x164 [radeon] [<f8074181>] ? drm_ioctl+0x234/0x2d4 [drm] [<f81e40dc>] ? radeon_cs_ioctl+0x0/0x164 [radeon] [<c1020b74>] ? get_parent_ip+0x8/0x19 [<c1020bf9>] ? sub_preempt_count+0x74/0x80 [<c103ab53>] ? __srcu_read_unlock+0x2c/0x44 [<c10ad59f>] ? fsnotify+0x1b5/0x1cc [<c1055af8>] ? audit_syscall_exit+0x2cc/0x2e4 [<c10095ed>] ? syscall_trace_leave+0x29/0xc8 [<f8073f4d>] ? drm_ioctl+0x0/0x2d4 [drm] [<c1096d1d>] ? do_vfs_ioctl+0x47c/0x4b9 [<c1020b74>] ? get_parent_ip+0x8/0x19 [<c1020bf9>] ? sub_preempt_count+0x74/0x80 [<c11e8907>] ? _raw_spin_unlock_irq+0xd/0x21 [<c103d49a>] ? ktime_get_ts+0xee/0xf6 [<c1096d87>] ? sys_ioctl+0x2d/0x46 [<c100268c>] ? sysenter_do_call+0x12/0x22 ---[ end trace e305e2f6d38485d4 ]--- radeon: wait for empty RBBM fifo failed ! Bad things might happen. WARNING: at /home/chris/LINUX/linux-2.6.36/drivers/gpu/drm/radeon/radeon_fence.c:235 radeon_fence_wait+0x1d5/0x261 [radeon]() Hardware name: Precision WorkStation 650 GPU lockup (waiting for 0x002B4CEF last fence id 0x002B4CEA) Modules linked in: snd_seq_oss snd_seq_midi snd_seq_dummy fuse cpufreq_ondemand nfsd exportfs autofs4 nfs lockd auth_rpcgss sunrpc p4_clockmod speedstep_lib af_packet ipt_LOG xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables ip6t_LOG nf_conntrack_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables x_tables ipv6 binfmt_misc loop dm_mirror dm_region_hash dm_log dm_mod uinput snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_event snd_seq_midi_emul snd_emu10k1 snd_ac97_codec snd_usb_audio ac97_bus snd_seq snd_pcm snd_util_mem snd_timer joydev uvcvideo snd_page_alloc snd_hwdep videodev v4l1_compat usbhid ppdev parport_pc firewire_ohci snd_usbmidi_lib snd_rawmidi snd_seq_device firewire_core snd parport floppy pcspkr psmouse i2c_i801 serio_raw soundcore dcdbas crc_itu_t sg ext3 jbd mbcache sr_mod cdrom sd_mod pata_acpi sata_sil uhci_hcd ata_piix libata ehci_hcd scsi_mod e1000 usbcore thermal button radeon Failed to wait GUI idle while programming pipes. Bad things might happen. intel_agp ttm drm_kms_helper drm agpgart i2c_algo_bit cfbcopyarea cfbimgblt cfbfillrect [last unloaded: mperf] Pid: 3031, comm: compiz Tainted: G W 2.6.36.3 #1 Call Trace: [<c102558f>] ? warn_slowpath_common+0x6a/0x7d [<f81d2a55>] ? radeon_fence_wait+0x1d5/0x261 [radeon] [<c1025608>] ? warn_slowpath_fmt+0x28/0x2c [<f81d2a55>] ? radeon_fence_wait+0x1d5/0x261 [radeon] [<c10373dd>] ? autoremove_wake_function+0x0/0x29 [<f80c34d7>] ? ttm_bo_wait+0x98/0x146 [ttm] [<c1020bf9>] ? sub_preempt_count+0x74/0x80 [<f81e2e9e>] ? radeon_gem_wait_idle_ioctl+0x68/0xbe [radeon] [<f8074181>] ? drm_ioctl+0x234/0x2d4 [drm] [<f81e2e36>] ? radeon_gem_wait_idle_ioctl+0x0/0xbe [radeon] [<c108b995>] ? do_sync_read+0x9e/0xd3 [<f8073f4d>] ? drm_ioctl+0x0/0x2d4 [drm] [<c1096d1d>] ? do_vfs_ioctl+0x47c/0x4b9 [<c1096d87>] ? sys_ioctl+0x2d/0x46 [<c100268c>] ? sysenter_do_call+0x12/0x22 ---[ end trace e305e2f6d38485d5 ]--- Cheers, Chris

1 0

← Newer
1
...
37
38
39
40
41
42
43
...
46
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel January 2011