From: Ben Hutchings
Date: Thu, Aug 26, 2010 at 04:59:21PM +0100
> should define dummy inline functions if CONFIG_VGA_ARB
> is not defined. It already does this for vga_client_register() but should
> cover the other functions as well.
But what if you still need the VGA arbitration functionality
On Thu, Aug 26, 2010 at 05:29:54PM +0200, Carlos R. Mafra wrote:
> On Do 26.Aug'10 at 16:59:18 +0200, Borislav Petkov wrote:
> > I get:
> >
> > LD init/built-in.o
> > LD .tmp_vmlinux1
> > drivers/built-in.o: In function `intel_modeset_init':
> > (.text+0xa993f): undefined reference t
On Do 26.Aug'10 at 16:59:18 +0200, Borislav Petkov wrote:
> I get:
>
> LD init/built-in.o
> LD .tmp_vmlinux1
> drivers/built-in.o: In function `intel_modeset_init':
> (.text+0xa993f): undefined reference to `vga_get'
> drivers/built-in.o: In function `intel_modeset_init':
> (.text+0x
I get:
LD init/built-in.o
LD .tmp_vmlinux1
drivers/built-in.o: In function `intel_modeset_init':
(.text+0xa993f): undefined reference to `vga_get'
drivers/built-in.o: In function `intel_modeset_init':
(.text+0xa9963): undefined reference to `vga_put'
make: *** [.tmp_vmlinux1] Error 1
With the code cleanup in
7a6b2896f261894dde287d3faefa4b432cddca53 is the first bad commit
commit 7a6b2896f261894dde287d3faefa4b432cddca53
Author: Daniel Vetter
Date: Fri Jul 2 15:02:15 2010 +0100
drm_mm: extract check_free_mm_node
I've botched up the range-restriction checks. The result i
On poniedzia?ek, 23 sierpnia 2010 o 19:01:45 Jonathan Corbet wrote:
> So I decided to fire up -rc2 today to see what would happen...the
> results are best described by the attached images. Something is
> clearly scrambled between my hardware and the i915 driver. Display with X
> is hosed, but thi
Hi Linus,
Some regression fixes, a couple around the BKL removal, and one in the
drm_mm code that was causing SIGBUS errors for some radeon users.
Dave.
The following changes since commit d03330383c9255cdb184dd33594e89c3542f191b:
Merge remote branch 'nouveau/for-airlied' of /ssd/git/drm-nou
On niedziela, 22 sierpnia 2010 o 17:26:19 Pekka Enberg wrote:
> Hi,
>
> I'm seeing tons of these error messages with current Linus' git:
>
> [ 95.941618] [drm:intel_calculate_wm] *ERROR* Insufficient FIFO for
> plane, expect flickering: entries required = 36, available = 31.
>
> Contrary to th
From: Ben Hutchings
Date: Thu, Aug 26, 2010 at 04:59:21PM +0100
> should define dummy inline functions if CONFIG_VGA_ARB
> is not defined. It already does this for vga_client_register() but should
> cover the other functions as well.
But what if you still need the VGA arbitration functionality
https://bugs.freedesktop.org/show_bug.cgi?id=29652
Jon Severinsson changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugs.freedesktop.org/show_bug.cgi?id=29652
Jon Severinsson changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugs.freedesktop.org/show_bug.cgi?id=29738
--- Comment #13 from Alexandre 2010-08-26 17:41:29 PDT
---
Me too. Before you patch I was finishing testing with 2.6.36-rc2 with the two
previous patches removed and it worked fine. I am testing with your patch and
it works, I could not crash it
https://bugs.freedesktop.org/show_bug.cgi?id=29738
--- Comment #13 from Alexandre 2010-08-26 17:41:29
PDT ---
Me too. Before you patch I was finishing testing with 2.6.36-rc2 with the two
previous patches removed and it worked fine. I am testing with your patch and
it works, I could not crash it
On Do 26.Aug'10 at 16:59:18 +0200, Borislav Petkov wrote:
> I get:
>
> LD init/built-in.o
> LD .tmp_vmlinux1
> drivers/built-in.o: In function `intel_modeset_init':
> (.text+0xa993f): undefined reference to `vga_get'
> drivers/built-in.o: In function `intel_modeset_init':
> (.text+0x
On Thu, Aug 26, 2010 at 05:29:54PM +0200, Carlos R. Mafra wrote:
> On Do 26.Aug'10 at 16:59:18 +0200, Borislav Petkov wrote:
> > I get:
> >
> > LD init/built-in.o
> > LD .tmp_vmlinux1
> > drivers/built-in.o: In function `intel_modeset_init':
> > (.text+0xa993f): undefined reference t
I get:
LD init/built-in.o
LD .tmp_vmlinux1
drivers/built-in.o: In function `intel_modeset_init':
(.text+0xa993f): undefined reference to `vga_get'
drivers/built-in.o: In function `intel_modeset_init':
(.text+0xa9963): undefined reference to `vga_put'
make: *** [.tmp_vmlinux1] Error 1
https://bugs.freedesktop.org/show_bug.cgi?id=28955
Scott Moreau changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugs.freedesktop.org/show_bug.cgi?id=28955
Scott Moreau changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugs.freedesktop.org/show_bug.cgi?id=28955
--- Comment #12 from Scott Moreau 2010-08-26 16:57:09 PDT ---
I am closing this bug since it no longer occurs with latest components. It must
have got fixed somewhere in the mix.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?
https://bugs.freedesktop.org/show_bug.cgi?id=28955
--- Comment #12 from Scott Moreau 2010-08-26 16:57:09 PDT
---
I am closing this bug since it no longer occurs with latest components. It must
have got fixed somewhere in the mix.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi
https://bugs.freedesktop.org/show_bug.cgi?id=28517
--- Comment #27 from Ian Romanick 2010-08-26 16:31:51
PDT ---
(In reply to comment #26)
> (In reply to comment #25)
> > Is the rendering correct on Intel hardware? If the rendering isn't correct
> > anywhere, then the performance issues are irr
https://bugs.freedesktop.org/show_bug.cgi?id=28517
--- Comment #27 from Ian Romanick 2010-08-26 16:31:51
PDT ---
(In reply to comment #26)
> (In reply to comment #25)
> > Is the rendering correct on Intel hardware? If the rendering isn't correct
> > anywhere, then the performance issues are irr
https://bugs.freedesktop.org/show_bug.cgi?id=28517
--- Comment #26 from Sven Arvidsson 2010-08-26 16:09:38 PDT ---
(In reply to comment #25)
> Is the rendering correct on Intel hardware? If the rendering isn't correct
> anywhere, then the performance issues are irrelevant. The performance will
https://bugs.freedesktop.org/show_bug.cgi?id=28517
--- Comment #26 from Sven Arvidsson 2010-08-26 16:09:38 PDT ---
(In reply to comment #25)
> Is the rendering correct on Intel hardware? If the rendering isn't correct
> anywhere, then the performance issues are irrelevant. The performance will
https://bugs.freedesktop.org/show_bug.cgi?id=28517
--- Comment #25 from Ian Romanick 2010-08-26 15:41:05
PDT ---
(In reply to comment #20)
> With latest git master (commit b5c07b9226d8e7de78f6367b5799b39caf820ef3) I
> only
> get a black background and a mouse cursor.
>
> As for performance, i
https://bugs.freedesktop.org/show_bug.cgi?id=28517
--- Comment #25 from Ian Romanick 2010-08-26 15:41:05
PDT ---
(In reply to comment #20)
> With latest git master (commit b5c07b9226d8e7de78f6367b5799b39caf820ef3) I
> only
> get a black background and a mouse cursor.
>
> As for performance, i
https://bugs.freedesktop.org/show_bug.cgi?id=28474
--- Comment #17 from Tormod Volden 2010-08-26
14:57:18 PDT ---
I also tried the patch and with drm_kms_helper.poll=0 I can watch antmaze as
much as I want and more, and the lugaru bunny just keeps jumping without any
issues. If any test users wa
https://bugs.freedesktop.org/show_bug.cgi?id=28474
--- Comment #17 from Tormod Volden 2010-08-26
14:57:18 PDT ---
I also tried the patch and with drm_kms_helper.poll=0 I can watch antmaze as
much as I want and more, and the lugaru bunny just keeps jumping without any
issues. If any test users wa
https://bugs.freedesktop.org/show_bug.cgi?id=28517
--- Comment #24 from Sven Arvidsson 2010-08-26 14:32:38 PDT ---
(Sorry for the bug spam)
The performance problem I'm having seems to be a result of the glsl2 merge, and
not from the vs loops. So I guess that's a different problem than what Pavel
https://bugs.freedesktop.org/show_bug.cgi?id=28517
--- Comment #24 from Sven Arvidsson 2010-08-26 14:32:38 PDT ---
(Sorry for the bug spam)
The performance problem I'm having seems to be a result of the glsl2 merge, and
not from the vs loops. So I guess that's a different problem than what Pavel
https://bugs.freedesktop.org/show_bug.cgi?id=28517
--- Comment #23 from Sven Arvidsson 2010-08-26 14:09:58 PDT ---
Dunno why, but the black screen was caused by libtxc_dxtn, removing it made the
problem go away. Anyway, some more observations about the performance problem:
* It's not CPU-relate
https://bugs.freedesktop.org/show_bug.cgi?id=28517
--- Comment #23 from Sven Arvidsson 2010-08-26 14:09:58 PDT ---
Dunno why, but the black screen was caused by libtxc_dxtn, removing it made the
problem go away. Anyway, some more observations about the performance problem:
* It's not CPU-relate
https://bugs.freedesktop.org/show_bug.cgi?id=29738
--- Comment #12 from Till Matthiesen 2010-08-26
13:49:21 PDT ---
Thanks, Daniel.
I'm testing against rc2-git4 and it runs fine so far (~30 min),
doing all that 'stuff' that made it easily crash within 2-5 minutes.
--
Configure bugmail: https:
https://bugs.freedesktop.org/show_bug.cgi?id=29738
--- Comment #12 from Till Matthiesen 2010-08-26
13:49:21 PDT ---
Thanks, Daniel.
I'm testing against rc2-git4 and it runs fine so far (~30 min),
doing all that 'stuff' that made it easily crash within 2-5 minutes.
--
Configure bugmail: https:
With the code cleanup in
7a6b2896f261894dde287d3faefa4b432cddca53 is the first bad commit
commit 7a6b2896f261894dde287d3faefa4b432cddca53
Author: Daniel Vetter
Date: Fri Jul 2 15:02:15 2010 +0100
drm_mm: extract check_free_mm_node
I've botched up the range-restriction checks. The result i
https://bugs.freedesktop.org/show_bug.cgi?id=29738
--- Comment #11 from Daniel Vetter 2010-08-26 12:37:10 PDT ---
Created an attachment (id=38195)
View: https://bugs.freedesktop.org/attachment.cgi?id=38195
Review: https://bugs.freedesktop.org/review?bug=29738&attachment=38195
fix range restric
https://bugs.freedesktop.org/show_bug.cgi?id=29738
--- Comment #11 from Daniel Vetter 2010-08-26 12:37:10 PDT
---
Created an attachment (id=38195)
View: https://bugs.freedesktop.org/attachment.cgi?id=38195
Review: https://bugs.freedesktop.org/review?bug=29738&attachment=38195
fix range restri
On poniedziaĆek, 23 sierpnia 2010 o 19:01:45 Jonathan Corbet wrote:
> So I decided to fire up -rc2 today to see what would happen...the
> results are best described by the attached images. Something is
> clearly scrambled between my hardware and the i915 driver. Display with X
> is hosed, but thi
I missed this one in the i2c unification patch. This
is handled in the core radeon i2c code now.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/radeon_pm.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_pm.c
b/drivers/gpu/drm/rad
On niedziela, 22 sierpnia 2010 o 17:26:19 Pekka Enberg wrote:
> Hi,
>
> I'm seeing tons of these error messages with current Linus' git:
>
> [ 95.941618] [drm:intel_calculate_wm] *ERROR* Insufficient FIFO for
> plane, expect flickering: entries required = 36, available = 31.
>
> Contrary to th
On Thu, 26 Aug 2010 02:15:20 +0200, Peter Stuge wrote:
> It could be - the resetting backlight thing happened also before the
> backlight commit. Before pulling I was using the directly preceding
> commit.
https://bugs.freedesktop.org/show_bug.cgi?id=29716
That patch isn't complete but is on the
Hi Daniel,
Your recent drm lru and mm changes seem to be the cause of sigbus
errors with recent kernels. Any insight was to what the problem is?
https://bugs.freedesktop.org/show_bug.cgi?id=29738
Thanks,
Alex
I missed this one in the i2c unification patch. This
is handled in the core radeon i2c code now.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/radeon_pm.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_pm.c
b/drivers/gpu/drm/rad
https://bugs.freedesktop.org/show_bug.cgi?id=29389
--- Comment #2 from Niels Ole Salscheider
2010-08-26 09:09:06 PDT ---
I can confirm this problem. With polling disabled my computer does not lock up
anymore.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- Yo
https://bugs.freedesktop.org/show_bug.cgi?id=29389
--- Comment #2 from Niels Ole Salscheider
2010-08-26 09:09:06 PDT ---
I can confirm this problem. With polling disabled my computer does not lock up
anymore.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- Yo
Hi Daniel,
Your recent drm lru and mm changes seem to be the cause of sigbus
errors with recent kernels. Any insight was to what the problem is?
https://bugs.freedesktop.org/show_bug.cgi?id=29738
Thanks,
Alex
___
dri-devel mailing list
dri-devel@li
https://bugs.freedesktop.org/show_bug.cgi?id=29738
Alex Deucher changed:
What|Removed |Added
CC||mikko@gmail.com
--- Comment #10 from
https://bugs.freedesktop.org/show_bug.cgi?id=29738
Alex Deucher changed:
What|Removed |Added
CC||mikko.cal at gmail.com
--- Comment #10 fr
https://bugs.freedesktop.org/show_bug.cgi?id=28966
--- Comment #7 from Sven Arvidsson 2010-08-26 06:43:14 PDT ---
Since error messages was added to r300g it now reports:
r300 FP: Compiler Error:
Fragment program does not support relative addressing of source operands.
Using a dummy shader inste
https://bugs.freedesktop.org/show_bug.cgi?id=28966
--- Comment #7 from Sven Arvidsson 2010-08-26 06:43:14 PDT ---
Since error messages was added to r300g it now reports:
r300 FP: Compiler Error:
Fragment program does not support relative addressing of source operands.
Using a dummy shader inste
https://bugs.freedesktop.org/show_bug.cgi?id=28517
--- Comment #22 from Sven Arvidsson 2010-08-26 06:38:10 PDT ---
No, nothing in dmesg. And just to clarify, it's only the game that's black, X
is unaffected.
I'll see if I can figure out where it broke, as it was working at least a
little bit bet
https://bugs.freedesktop.org/show_bug.cgi?id=28517
--- Comment #22 from Sven Arvidsson 2010-08-26 06:38:10 PDT ---
No, nothing in dmesg. And just to clarify, it's only the game that's black, X
is unaffected.
I'll see if I can figure out where it broke, as it was working at least a
little bit bet
https://bugs.freedesktop.org/show_bug.cgi?id=29818
Summary: r600g "vbo resource seems too big" spam
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
C
https://bugs.freedesktop.org/show_bug.cgi?id=29818
Summary: r600g "vbo resource seems too big" spam
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
C
On Thu, 26 Aug 2010 02:15:20 +0200, Peter Stuge wrote:
> It could be - the resetting backlight thing happened also before the
> backlight commit. Before pulling I was using the directly preceding
> commit.
https://bugs.freedesktop.org/show_bug.cgi?id=29716
That patch isn't complete but is on the
Chris Wilson wrote:
> > > > Xv performance
> > >
> > > That should now be fixed in -intel,
> >
> > Sounds good! I'd love to test. Which branch/commit is that?
>
> Master with -vo xv should be good, if it doesn't hang.
Doesn't hang, mplayer says:
X11 error: BadAlloc (insufficient resources for
Hi again,
Chris Wilson wrote:
> > In general, Xv performance with KMS leaves me with a feeling that
> > something is not quite right in terms of playback, both with mplayer
> > and vlc. But while movies are nice, this stalling issue is more
> > important.
>
> That should now be fixed in -intel,
On Thu, 26 Aug 2010 01:33:15 +0200, Peter Stuge wrote:
> Hi again,
>
> Chris Wilson wrote:
> > > In general, Xv performance with KMS leaves me with a feeling that
> > > something is not quite right in terms of playback, both with mplayer
> > > and vlc. But while movies are nice, this stalling iss
https://bugs.freedesktop.org/show_bug.cgi?id=29738
--- Comment #9 from Alexandre 2010-08-26 00:33:25 PDT
---
In my bisect (I tried to reduce the number of tests) by restricting the commits
to the drivers/gpu/drm include/drm directories.
The commit I got is the one below. I am not 100% confident
https://bugs.freedesktop.org/show_bug.cgi?id=29738
--- Comment #9 from Alexandre 2010-08-26 00:33:25
PDT ---
In my bisect (I tried to reduce the number of tests) by restricting the commits
to the drivers/gpu/drm include/drm directories.
The commit I got is the one below. I am not 100% confident
60 matches
Mail list logo