headers
Dan Carpenter | 2 Jan 2010 15:46
Picon

Re: drm: gem_object_free without struct_mutex

On Wed, Dec 30, 2009 at 11:17:48PM +0100, Rafael J. Wysocki wrote:
> [CC to Jesse.]
> 
> On Wednesday 30 December 2009, Hugh Dickins wrote:
> > I've changed BUG_ON to WARN_ON in drm_gem.c (patch at bottom) to
> > get this dmesg when I resume after suspend, instead of crashing.
> > 
> > Perhaps it's a patch that should go in, perhaps not, but obviously
> > the real problem lies elsewhere.  Happens with 2.6.33-rc1 and -rc2.
> > 
> > No surprise if I'm stupidly misconfigured to get the "pin power context"
> > error in the first place (.config on demand), but I don't deserve to BUG!
> > 

The problem is dev_priv->mm.suspended which was set in i915_suspend().

In i915_resume()

   107          i915_restore_state(dev);

The i915_restore_state() fails because i915_gem_object_bind_to_gtt()
does this:

        if (dev_priv->mm.suspended)
                return -EBUSY;

   108  
   109          intel_opregion_init(dev, 1);
   110  
   111          /* KMS EnterVT equivalent */
(Continue reading)

Permalink | Reply | 0 comments |
headers
bugzilla-daemon | 3 Jan 2010 14:01

[Bug 25871] New: nearest neighbour samples wrong texel (precision/rounding problem)

http://bugs.freedesktop.org/show_bug.cgi?id=25871

           Summary: nearest neighbour samples wrong texel
                    (precision/rounding problem)
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/R600
        AssignedTo: dri-devel <at> lists.sourceforge.net
        ReportedBy: pierre-bugzilla <at> ossman.eu

The following fragment program does the wrong thing on r600/r700 hardware:

TEX result.color, 0.498046860099, texture[0], 2D;

(the texture coord is as far as I got before I got bored. I'm not sure the
precision goes much further anyway)

The circumstances is that I have a 4x4 texture with nearest neighbour
interpolation. The above code should be sampling texel 1,1 but is instead
sampling texel 2,2. This causes problems for fragment programs that try to do
things based on texel coords (like bicubic interpolation).

This seems to be a hw bug as I've tried it with fglrx (albeit with a slightly
different card) and it exhibits the same bug. As such, I'm not sure it can be
solved but hopefully there is a workaround.
(Continue reading)

Permalink | Reply | 11 comments |
headers
bugzilla-daemon | 3 Jan 2010 17:22

[Bug 14535] Memory corruption detected in low memory

http://bugzilla.kernel.org/show_bug.cgi?id=14535

Henrique de Moraes Holschuh <hmh <at> hmh.eng.br> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hmh <at> hmh.eng.br

--- Comment #2 from Henrique de Moraes Holschuh <hmh <at> hmh.eng.br>  2010-01-03 16:22:53 ---
We have multiple reports of filesystem corruption on DRI radeon.  Kernels
2.6.30 and later with mesa 7.6 (galium disabled) cause the issue.  Kernel
2.6.30 with mesa 2.5 doesn't cause the issue.

It is likely this bug.

What is the status of this issue?  It causes filesystem corruption and data
loss, so it is a very nasty one.

Related (gives more data about the bug, and the reporter is a potential tester
for fixes):
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550977

--

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
(Continue reading)

Permalink | Reply | 0 comments |
headers
Anssi Hannula | 3 Jan 2010 17:10
Picon
Picon
Favicon

Re: [PATCH 5/5] drm/edid: Decode 3-byte CVT codes from EDID 1.4

Adam Jackson wrote:
> +static int drm_cvt_modes(struct drm_connector *connector,
> +			 struct detailed_timing *timing)
> +{
> +	int i, j, modes = 0;
> +	struct drm_display_mode *newmode;
> +	struct drm_device *dev = connector->dev;
> +	struct cvt_timing *cvt;
> +	const int rates[] = { 60, 85, 75, 60, 50 };
> +
> +	for (i = 0; i < 4; i++) {
> +		int width, height;
> +		cvt = &(timing->data.other_data.data.cvt[i]);
> +
> +		height = (cvt->code[0] + ((cvt->code[1] & 0xf0) << 8) + 1) * 2;
> +		switch (cvt->code[1] & 0xc0) {

Is it just me, or do the above two lines look very wrong?
1) Height can never be between 512 and 8194.
2) Same bits are used for height and aspect ratio.

> +		case 0x00:
> +			width = height * 4 / 3;
> +			break;
> +		case 0x40:
> +			width = height * 16 / 9;
> +			break;
> +		case 0x80:
> +			width = height * 16 / 10;
> +			break;
(Continue reading)

Permalink | Reply | 0 comments |
headers
bugzilla-daemon | 3 Jan 2010 19:01

[Bug 25875] New: Bugs in 3D Apps when using Mesa 7.7 and r100

http://bugs.freedesktop.org/show_bug.cgi?id=25875

           Summary: Bugs in 3D Apps when using Mesa 7.7 and r100
           Product: Mesa
           Version: git
          Platform: All
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/Radeon
        AssignedTo: dri-devel <at> lists.sourceforge.net
        ReportedBy: dmitri.amariei <at> gmail.com

Created an attachment (id=32417)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=32417)
Example of a 3D application where you can see a "stripe" at the side

Using The Following:

Graphics Card - r100 (Radeon 7200) with opensource ati/radeon driver
OpenGL Version - 1.3 Mesa 7.7
Kernel - 2.6.32-996-generic
Also,
KMS is enabled through - radeon.modeset=1
and HW TCL is disabled.

Bug Occurs:
When running a 3D game or program, some rendering issues occur.
i.e - improper textures, some parts not visibile, etc...
(Continue reading)

Permalink | Reply | 1 comment |
headers
bugzilla-daemon | 4 Jan 2010 00:29

[Bug 25876] New: Direct Rendering Disabled Due to Undefined Symbols

http://bugs.freedesktop.org/show_bug.cgi?id=25876

           Summary: Direct Rendering Disabled Due to Undefined Symbols
           Product: Mesa
           Version: git
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/Radeon
        AssignedTo: dri-devel <at> lists.sourceforge.net
        ReportedBy: tstellar <at> gmail.com

I just built the latest version of mesa from git, commit:      
e388d62b4712bcd75cecad53f5ca20a2bb6f89b1

Direct rendering is disabled due to some undefined symbols, here is the
debugging output from glxinfo:

libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0)
libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so
libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
libGL error: dlopen /usr/lib/dri/r300_dri.so failed (/usr/lib/dri/r300_dri.so:
undefined symbol: _glthread_GetID)
libGL error: unable to load driver: r300_dri.so
libGL: OpenDriver: trying /usr/lib/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib/dri/swrast_dri.so
libGL error: dlopen /usr/lib/dri/swrast_dri.so failed
(/usr/lib/dri/swrast_dri.so: undefined symbol: _glapi_check_multithread)
(Continue reading)

Permalink | Reply | 3 comments |
headers
bugzilla-daemon | 4 Jan 2010 03:04

[Bug 25876] Direct Rendering Disabled Due to Undefined Symbols

http://bugs.freedesktop.org/show_bug.cgi?id=25876

Kristian Høgsberg <krh <at> bitplanet.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #1 from Kristian Høgsberg <krh <at> bitplanet.net>  2010-01-03 18:04:19 PST ---
Should be fixed now, please give git master a try.

thanks,
Kristian

--

-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
--
_______________________________________________
Dri-devel mailing list
Dri-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
(Continue reading)

Permalink | Reply | 0 comments |
headers
bugzilla-daemon | 4 Jan 2010 03:46

[Bug 25876] Direct Rendering Disabled Due to Undefined Symbols

http://bugs.freedesktop.org/show_bug.cgi?id=25876

--- Comment #2 from Tom Stellard <tstellar <at> gmail.com>  2010-01-03 18:46:50 PST ---
I just tried again with mesa master, commit:   
b8326b011d9b16dcc502507a52bd747a4b709399
I can confirm this bug has been fixed.

--

-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
--
Permalink | Reply | 0 comments |
headers
bugzilla-daemon | 4 Jan 2010 03:51

[Bug 25876] Direct Rendering Disabled Due to Undefined Symbols

http://bugs.freedesktop.org/show_bug.cgi?id=25876

Kristian Høgsberg <krh <at> bitplanet.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #3 from Kristian Høgsberg <krh <at> bitplanet.net>  2010-01-03 18:51:19 PST ---
Thanks, closing bug.

--

-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
--
_______________________________________________
Dri-devel mailing list
Dri-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
Permalink | Reply | 0 comments |
headers
bugzilla-daemon | 4 Jan 2010 06:36

[Bug 25881] New: drm.h , drm_mode.h and <driver>_drm.h use types defined stdint.h but do not include stdint.h

http://bugs.freedesktop.org/show_bug.cgi?id=25881

           Summary: drm.h , drm_mode.h and <driver>_drm.h use types defined
                    stdint.h but do not include stdint.h
           Product: DRI
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: libdrm
        AssignedTo: dri-devel <at> lists.sourceforge.net
        ReportedBy: pebender <at> gmail.com

drm.h, drm_mode.h and (at least some <driver>_drm.h files use the types int8_t,
uint8_t, int16_t, uint16_t, int32_t, uint32_t, int64_t and uint64_t. Per c99,
these are defined in stdint.h. However, the drm.h, drm_mode.h and
<driver>_drm.h files do not include stdint.h. As a result, it causes build
problems with newer gcc compile versions and files that include one of these
without first including stdint.h or a header file that includes stdint.h (eg
xf86drm.h). For example, it breaks compilation of the
xf86-video-openchrome-0.2.904 driver.

As the use in drm.h is for to non-Linux systems and the use in drm_mode.h was
added after 2.4.16, and many files include xf86drm.h before the other headers.
Therefore, the problem is not likely to show up too often.

--

-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
(Continue reading)

Permalink | Reply | 2 comments |

Gmane