This restricts the use of the big kernel lock to the i830 and i810
device drivers. The three remaining users in common code (open, ioctl
and release) get converted to a new mutex, the drm_global_mutex,
making the locking stricter than the big kernel lock.
This may have a performance impact, but on
With the ioctl, block, tty, vfs and llseek series
on their way into linux-next, these three patches
are attacking the hardest remaining issues.
If we get these ready for 2.6.36, the kernel should
be almost usable with the BKL disabled. In all three
cases, I'm cheating a bit, because the BKL still
On Sun, 2010-07-11 at 01:24 +0200, Marcin Slusarz wrote:
> Hi
>
> Patch "drm/nouveau: use drm_mm in preference to custom code doing the same
> thing"
> in nouveau tree introduced new deadlock possibility, for which lockdep
> complains loudly:
>
> [ 1541.070202] [drm] nouveau :02:00.0: Alloc
copy_to_user() returns the number of bytes remaining to be copied, but
we want to return a negative error code. This gets copied to user
space.
Signed-off-by: Dan Carpenter
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
b/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
index f1d6261..437ac78 100644
---
Hi
Patch "drm/nouveau: use drm_mm in preference to custom code doing the same
thing"
in nouveau tree introduced new deadlock possibility, for which lockdep
complains loudly:
[ 1541.070202] [drm] nouveau :02:00.0: Allocating FIFO number 3
[ 1541.084772] [drm] nouveau :02:00.0: nouveau_ch
Fixed brace, macro and spacing coding style issues.
Signed-off-by: Nicolas Kaiser
---
Supersedes patch "drm/savage: fixed brace coding style issues".
drivers/gpu/drm/savage/savage_bci.c | 48 +++
drivers/gpu/drm/savage/savage_drv.h | 109 +
dri
This restricts the use of the big kernel lock to the i830 and i810
device drivers. The three remaining users in common code (open, ioctl
and release) get converted to a new mutex, the drm_global_mutex,
making the locking stricter than the big kernel lock.
This may have a performance impact, but on
https://bugs.freedesktop.org/show_bug.cgi?id=28860
--- Comment #8 from Tom Stellard 2010-07-10 13:11:05 PDT
---
Created an attachment (id=36940)
--> (https://bugs.freedesktop.org/attachment.cgi?id=36940)
Failing shaders
I pulled 1 of the 3 failing shaders from the error log. If you have some
https://bugs.freedesktop.org/show_bug.cgi?id=28860
--- Comment #8 from Tom Stellard 2010-07-10 13:11:05
PDT ---
Created an attachment (id=36940)
--> (https://bugs.freedesktop.org/attachment.cgi?id=36940)
Failing shaders
I pulled 1 of the 3 failing shaders from the error log. If you have some
copy_to_user() returns the number of bytes remaining to be copied, but
we want to return a negative error code. This gets copied to user
space.
Signed-off-by: Dan Carpenter
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
b/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
index f1d6261..437ac78 100644
---
https://bugs.freedesktop.org/show_bug.cgi?id=26915
Martin Louda changed:
What|Removed |Added
CC||san...@seznam.cz
--- Comment #8 from Mart
https://bugs.freedesktop.org/show_bug.cgi?id=26915
Martin Louda changed:
What|Removed |Added
CC||sandin at seznam.cz
--- Comment #8 from M
https://bugs.freedesktop.org/show_bug.cgi?id=28994
--- Comment #2 from Jon Sturm 2010-07-10 08:07:05 PDT ---
This is also noticeable on my 2 rv730 cards so it seems to be a mesa or radeon
bug in general and not r300 specific.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=
https://bugs.freedesktop.org/show_bug.cgi?id=28994
--- Comment #2 from Jon Sturm 2010-07-10 08:07:05 PDT
---
This is also noticeable on my 2 rv730 cards so it seems to be a mesa or radeon
bug in general and not r300 specific.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab
https://bugs.freedesktop.org/show_bug.cgi?id=29001
--- Comment #1 from Alex Deucher 2010-07-10 06:57:32 PDT ---
Did you update any other components as well (xserver, ddx, libpixman, etc.)?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=29001
--- Comment #1 from Alex Deucher 2010-07-10 06:57:32 PDT
---
Did you update any other components as well (xserver, ddx, libpixman, etc.)?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=26915
--- Comment #7 from Alex Deucher 2010-07-10 06:54:58 PDT ---
(In reply to comment #6)
> I'm having the same problem with current (2.6.34.1) kernel. Is there a chance
> the fix will hit kernel git tree?
It's already upstream. What chip do you ha
https://bugs.freedesktop.org/show_bug.cgi?id=26915
--- Comment #7 from Alex Deucher 2010-07-10 06:54:58 PDT
---
(In reply to comment #6)
> I'm having the same problem with current (2.6.34.1) kernel. Is there a chance
> the fix will hit kernel git tree?
It's already upstream. What chip do you h
https://bugs.freedesktop.org/show_bug.cgi?id=29001
Summary: latest d-r-t has regular X crashes
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: m
https://bugs.freedesktop.org/show_bug.cgi?id=29001
Summary: latest d-r-t has regular X crashes
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: m
https://bugs.freedesktop.org/show_bug.cgi?id=26915
--- Comment #6 from Martin Louda 2010-07-10 04:36:12 PDT ---
I'm having the same problem with current (2.6.34.1) kernel. Is there a chance
the fix will hit kernel git tree?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=em
https://bugs.freedesktop.org/show_bug.cgi?id=26915
--- Comment #6 from Martin Louda 2010-07-10 04:36:12 PDT
---
I'm having the same problem with current (2.6.34.1) kernel. Is there a chance
the fix will hit kernel git tree?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=e
https://bugs.freedesktop.org/show_bug.cgi?id=28995
--- Comment #4 from Álmos 2010-07-10 02:41:08 PDT ---
Created an attachment (id=36933)
--> (https://bugs.freedesktop.org/attachment.cgi?id=36933)
dmesg after trying vdrift
In the console several hundred lines of numbers were printed, but only 2
https://bugs.freedesktop.org/show_bug.cgi?id=28995
--- Comment #4 from ?lmos 2010-07-10 02:41:08 PDT ---
Created an attachment (id=36933)
--> (https://bugs.freedesktop.org/attachment.cgi?id=36933)
dmesg after trying vdrift
In the console several hundred lines of numbers were printed, but only 2
[NOTES:
* This list seems to be shrinking at last.
* The bug entries with the NEEDINFO status will be closed next round if the
reporters don't follow up.]
This message contains a list of some post-2.6.33 regressions introduced before
2.6.34, for which there are no fixes in the mainline known
25 matches
Mail list logo